Installation and Deployment > How to migrate to HOPEX V2R1 > Prepare upgrade of data
Prepare upgrade of data
 
Check metamodel, locks, workspaces and workflows
Decide format of report templates (MS Word)
Identify Solution packs used
Management of login assignments
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 (HOPEX V1R3, HOPEX V2), 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 GBMS storage, you can delete remaining locks. With RDBMS storage (Oracle or SQL Server), you need to dispatch of delete related workspace.
Decide format of report templates (MS Word)
With HOPEX, two formats are available for Report (MS Word) objects and RTF stylesheets.
 
Format
Recommended or required
RTF
Required for the environment in the following situations:
• If reports (MS Word) are generated from both Windows and Web Front-ends (1).
• If reports (MS Word) are generated only from Web Front-ends.
• If Report (MS Word) are generated in batch mode with Windows scheduler.
MS Word
Compatibility mode that can be used only if Reports (MS Word) are generated:
• In interactive mode (no batch).
• From Windows Front End.
 
Format
Impacts
RTF
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.
MS Word
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.
 
By default, with HOPEX V2R1, RTF format is used. If you need MS Word format, you must configure each HOPEX environment. See section 'Check format of report templates (MS Word)' later in this document.
(1) A configuration enables to benefit from links and refreshing in report (MS Word). It requires that if MS Word is installed.
(2) Option 'Activate generation of documents in DOCX.
 
 
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
Management of login assignments
To enable login to HOPEX, a user must be mapped to a profile (directly or indirectly).
The management of login assignment has changed to favor better performances.
 
Version of HOPEX
Comment
HOPEX V1R1
HOPEX V1R2-V1R3
An option 'Management of assignment of business roles to persons' enables to switch between 2 modes
• Person assignment mode: a user (Person (System)) is mapped to one/several Business Roles within a data repository. Each Business Role is mapped to a Profile.
• Profile mode: a user (Login) is mapped to one/several Profiles within an environment
HOPEX V2
HOPEX V2R1
A unique mode called Profile assignment mode is available: a Person (System) is mapped to one/several Profiles within an environment.
The previous configurations are converted to the new mode for login. The option 'Management of assignment of business roles no longer exists.
 
Note that person assignment is also used to manage responsibility on object (ex: John Smith is 'Local Application owner' for the application 'Internal reporting'. This kind of assignment persists with HOPEX V2R1 as in HOPEX V1R2-V1R3.
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)
 
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 version, 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 V2R1, 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, 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 article 'HOPEX Unified Authentication Service Installation guide'.
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
From HOPEX V2R1, web settings persist in different folder.
 
If you need to restore this information when migrating from HOPEX V1R3 or HOPEX V2 to HOPEX V2R1, archive (file copy) the file MegaSettings-*.ini on the server hosting the source installation (HOPEX V1R3 or HOPEX V2). With HOPEX V1R3 and HOPEX V2, such files are saved in the folder:
%windir%\SysWOW64\config\systemprofile\AppData\Roaming\Mega