Installation and Deployment > How to Migrate to HOPEX V3 > Prepare upgrade of data
Prepare upgrade of data
 
Check metamodel, locks, workspaces and workflows
Verify that GBMS storage is no longer used
Verify that Windows Front-End is no longer used for runtime
Verify format of report templates (MS Word)
Verify technology of web desktops
Identify Solution packs used
Decide 'Definition of path of MetaAssociation'
Check license with your sales representative
Review use of the profile 'Enterprise Architect'
Review authentication mode
Decide to keep web settings
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 GBMS storage is no longer used
 
GBMS storage is no longer supported in HOPEX V3.
It is required to change storage to SQL storage before upgrading data.
A license Repository Storage (SQL Server) is required.
 
For more details, see only documentation, reorganization feature
HOPEX Administration: Administrator Guide : Managing Repositories : Managing Repositories : Reorganizing an RDBMS Repository
 
Pre-requisites:
• Check that you have a license with Repository Storage (SQL Server).
• Stop user activity and backup data
• Verify that a physical backup of data is available
• Dispatch of delete all pending workspaces
• Verify you have enough working space
• Create SQL Server database with appropriate permissions
 
Recommendations:
• Decide if you can delete repository log
• Use a server machine close to SQL Instances
• Leave the process running quietly.
• Check process (test) on a copy of production
• Loop until the processing runs without unexpected error.
 
 
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 format of report templates (MS Word)
 
With HOPEX, two formats were available for Report (MS Word) objects and RTF stylesheets.
• RTF/DOCX format: This generation mode is the only one allowed with HOPEX V3.
• DOC format: This generation mode is no longer supported with HOPEX V3 as Windows Front-end is no longer supported for runtime.
 
Format
Impacts
RTF/DOCX
Reports have the .rtf or .docx file extension according to an option (2).
RTF stylesheets has the .rtf file extension. MS word is not used at runtime.
No links exist in generated reports. Fields (such as table of content) are not refreshed automatically. RTF macros are not supported. Application of styles is not enforced after generation, which may cause differences in display.
DOC
Reports have the .doc file extension.
RTF stylesheets has the .doc file extension.
MS word is used at runtime.
Links exist in generated reports (can be removed with detach).
This format is now deprecated.
 
For each environment, check file megaenv.ini
[Office]
DocumentFormat=XX
 
Document format
Interpretation
[Office]
DocumentFormat=10
RTF/DOCX format
[Office]
DocumentFormat=20
DOC format
Not specified (default)
RTF/DOCX format
 
If an environment is configured with DOC format, it is required to convert report templates (MS Word). See later in this document Convert report templates (MS Word).
 
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 (except for 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).
Keep in mind that Solution HOPEX Internal Audit is not impacted with HOPEX V3. Change of web desktop technology is planned for a coming version.
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: DoDAF, NAF …
 
For each HOPEX environment, identify the list of solution packs imported:
• In the system database
• In a data repository
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:
• Compatibility up to MEGA 2009: MetaAssociation behaviors are interpreted using the logic of MEGA 2009.
• From MEGA HOPEX 1.0: MetaAssociation behaviors are interpreted using a new logic.
 
Value
Recommended
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 from HOPEX V1R2/V1R3. 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…).
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.
 
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 Process BPMN edition, 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.
 
From HOPEX V3, 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 V3, 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).
• .NET project template provided to quickly develop a custom authentication provider (UAS custom provider).
 
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
With HOPEX V3, web settings persist in different folders.
 
If you need to restore this information when migrating to HOPEX V3, archive (file copy) the file MegaSettings-*.ini on the server hosting the source installation (ex: HOPEX V2R1).
With HOPEX V2R1, such files are saved in the folder:
%ProgramData%\MEGA\HOPEX V2R1\ClusterRoot\UserSettings