Installation et déploiement : How to migrate to HOPEX V2 EN : 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 licence
Check metamodel, locks, workspaces and workflows
In the source version (HOPEX V1R2-V1R3), for each environment:
 
Check
Detail
Check that the metamodel is stable
In Windows Administration Console (Administrration.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 (Administrration.exe), check workspaces. If a private workspace persists, dispatch or delete it.
Check that no locks 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).
 
By default, with HOPEX V2, RTF format is used. If you need MS Word format, you should 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
A unique mode called Profile assignment mode is available: a Person (System) is mapped to one/several Profiles within an environment.
The previous modes 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 V2 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
Compatibility up to MEGA 2009
Required for compatibility with version MEGA 2009 and lower (data and system database customization)
From MEGA HOPEX 1.0
Recommended for new projects and for repository alignment (stricter control on objects). If behavior has been customized (system database customization) in version MEGA 2009, compatibility is not guaranteed. A review that may require time and expertise is necessary.
 
Note that 'From MEGA HOPEX 1.0' 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 behavior (namespace, navigation, extraction, protection, export, comparison…).
Check licence
Topic
Change
Recommendation
MEGA Process BPMN edition
With HOPEX V2, MEGA Process BPMN Edition (code PMN) is replaced with HOPEX Business Process Analysis (HBPA). MEGA Process BPMN Edition (code PMN) is removed as such. No migration/conversion is required: diagrams of PMN can be edited with HBPA
Contact your sales representative
GBMS storage
With HOPEX V2, GBMS storage is not supported for Web Front-End. A licence for a RDBMS storage product is required.
Contact your sales representative