Prepare upgrade of data
Check license with your sales representative
The list of products/solutions changes with each version:
• Certain products/solutions are removed (not available).
• Certain products/solutions are deprecated (available and supported as is).
• Certain products/solutions are repackaged (features still available through another product/ solution)
• SQL Server storage is now required.
This document will not describe the product lists or the changes between versions. Please contact your sales representative to see if a new license needs to be programmed.
Check metamodel, locks, workspaces and workflows
In the source version, for each environment:
|
Check
|
Detail
|
|
Check that the metamodel is stable
|
In Windows Administration Console (Administration.exe), compile the environment. If the environment compilation generates a log entry in the HOPEX error log, you should fix such errors before migrating your data
|
|
Check that no private workspace (ex-transactions) persists
|
In Windows Administration Console (Administration.exe), check workspaces. If a private workspace persists, dispatch or delete it.
|
|
Check that no lock persists
|
In Windows Administration Console (Administrration.exe), check locks. With RDBMS storage (SQL Server), you need to dispatch of delete related workspace.
|
Verify that Windows Front-End is no longer used for runtime
Windows Front-End (HOPEX.exe) is no longer allowed for execution (runtime) in HOPEX V3 and higher versions.
It is required to move to Web Front-end. This can lead to review de deployment architecture of HOPEX.
From HOPEX V3, Windows Front-End is allowed only for:
1) For Administration tasks with HOPEX.exe
• Standard administration tasks
• Advanced administration features (HOPEX Power Supervisor, code SUP)
• Management of reporting DataMart (HOPEX Reporting Datamart, code HDT)
2) For Customization with HOPEX.exe
This requires specific profiles such as HOPEX Customizer and a licence with HOPEX Power Studio (code MTS2).
Verify that Oracle storage is no longer used for runtime
Oracle storage is not supported in HOPEX V3 and higher versions.
It is required to migrate data to SQL Server before migration to HOPEX V4.
See document 'How to migrate data from Oracle to SQL Server storage HOPEX V3'.
Verify that GBMS storage is no longer used for runtime
From HOPEX V2 GBMS storage is not supported with Web Front-end but allowed for Windows Front-end provided volume of data is limited.
In HOPEX V3 and higher versions, GBMS storage is not supported at all.
It is required to migrate data to SQL Server before migration to HOPEX V4.
Identify Solution packs used
Solutions packs are add-ins installing data or templates. There are imported in data repositories using the Administration Console, but they can update the system database.
Example: Archimate, NAF …
For each HOPEX environment, identify the list of solution packs imported:
• In the system database
• In a data repository
Verify technology of web desktops
This section is regarding GRC Solutions:
• HOPEX Enterprise Risk Management (code ERMW)
• HOPEX Internal Control (code ICM)
• HOPEX LDC (code LDC)
• HOPEX Internal Audit (code MIAW)
Each profile used with Web Front-End is associated to one or several web desktops.
Each web desktop is based on one of these technologies.
• Classic Desktops (also called V1 Desktops, legacy technology).
• Universal Desktops (latest technology).
With GRC Solutions (including solution HOPEX Internal Audit), Universal Desktop technology is now used. This can have an impact according to project customizations. Each project needs to identify its situation.
|
Situation
|
Impacts on customization
|
Impact on look and feel
|
Comment
|
|
Full standard (standard profiles with standard desktops)
|
No impact
|
Change
|
Profiles are now associated to Universal Desktops instead of the Classic GRC Desktops
|
|
Full custom (custom profiles with custom desktops)
|
No impact
|
No change
|
By default, profiles are still associated to Classic GRC Desktops. Of course, project can decide to use Universal Desktop instead. A review of customization is required.
|
|
Mixed (standard profiles customized with standard desktops, custom profiles with standard desktops…)
|
Possible impact.
|
Possible change
|
A case by case review is required.
A case-by-case review is required.
It is highly recommended to create custom profiles. Project must decide if they are associated to Universal Desktops (recommended) but keeping working with the Classic GRC Desktop is still possible
|
A standard element (profile, desktop ...) is a configuration provided out of the box by HOPEX. It can be customized.
Customization of standard profiles (to change CRUD/Object UI permissions) is not recommended (bad practice).
Decide 'Definition of path of MetaAssociation'
This step requires a decision for each HOPEX environment.
In the HOPEX options, group 'Repository', an option 'Definition of path of MetaAssociation' is available at installation and environment level. This option enables to control the way MetaAssociation behaviors are interpreted according to the value chosen:
|
Value
|
Recommendation
|
|
Standard Mode
|
Recommended for new projects. Default value.
|
|
Compatibility Mode
|
Recommended for compatibility with behaviors and customizations performed in version MEGA 2009 and lower (data and system database customization). When switching to 'Standard mode', a review that may require time and expertise is necessary.
|
Note that ' Standard Mode' is the default value. You can change the value and compile the environment without impact on data except namespace. However, the change will affect the behaviors (namespace, navigation, extraction, protection, export, comparison…).
Decide how to manage questionnaires
This step requires a decision for each HOPEX environment.
It is required to choose and activate a mode in each environment. This will determine the engine used and indirectly the user experience when designing questionnaire templates (customizer, functional administrator) or when filling questionnaire (end-user, respondent). The assessment engine is not modified.
|
Mode
|
Recommendation
|
|
Standard Mode
|
Mandatory for new projects (new environments created from HOPEX V4). See below its benefits.
Recommended for environments created before HOPEX V4. This new mode is based on a new questionnaire engine named questionnaire builder. Explicit actions are required during migration.
|
|
Compatibility Mode
|
Although not recommended, it can be used for compatibility with previous behaviors for environments created before HOPEX V4. This mode will not be available in the coming version HOPEX V5.0.
Note that warnings will be displayed in Administration tools to recommend the standard mode.
This mode is based on the classic questionnaire engine.
|
Benefits of Standard mode
• Modern and easy to use WYSIWYG interface to quickly build questionnaire templates via drag and drop functionalities (design).
• Better user experience for users having to answer a questionnaire, thanks to a new improved questionnaire layout (execution).
Also read document 'New Questionnaire Builder – Migration of Existing Clients' than explains functional changes and feature provided to adapt existing questionnaire templates if needed.
Once Standard mode is activated and questionnaire templates are converted, there is no way back.
See later in this document
• Activate standard mode for questionnaires
• Other checking indications, Questionnaire templates
Review use of the profile 'Enterprise Architect'
For many versions, the profile 'Enterprise Architect' (ex-EA Standard) has been used for multiple purpose
• Use legacy products (MEGA Architecture…)
• Perform customizations
• Use HOPEX Solutions
This profile is designed for use of legacy products.
• It is not designed for customization: use the profile 'HOPEX Customizer'.
• It is not designed for use HOPEX Solutions: use dedicated profiles and desktops.
With HOPEX V4, the profile 'Enterprise Architect' has a command line that filters HOPEX Studio and HOPEX Solution:
/RW'NAF;ARC;HBPA;DOD2;FEA;UML;ITD;ETOM;MPL;SOIA;TOG;SAP;MBS;DMO;ERML;CMDB'
If projects need a profile and desktops that combines legacy product and HOPEX solutions or that combines HOPEX Solutions, a specific study is required.
Review authentication mode
With HOPEX V2R1 and higher version, a new authentication framework called UAS (Unified Authentication Service) is available.
Authentication configured with previous versions will run natively in most cases (see section 'Other checking indications' in this document). Anyway, it is recommended to consider the UAS framework capabilities:
• OpenID authentication (out of the box, configuration required).
• SAML2 authentication (out of the box, configuration required).
• Windows authentication (out of the box, configuration required).
For more details, see online documentation 'Installation and Deployment : HOPEX Unified Authentication Service'.
Decide to keep web settings
Web settings are user related settings. They contain information that can be considered as useful, ex:
• List of tiles selected by user in web desktop
• List of dashboards (widgets) selected by user in web desktop
Web settings persist in different folders.
If you need to restore this information when migrating to HOPEX V4, archive (file copy) the file MegaSettings-*.ini on the server hosting the source installation (ex: HOPEX V3).
With HOPEX V3, such files are saved in the folder:
%ProgramData%\MEGA\HOPEX V3\ClusterRoot\UserSettings