Installation et déploiement : How to migrate to HOPEX V2 EN : Complete upgrade of data
   
Complete upgrade of data
 
Re-import solutions packs
Review important options
Definition of path of MetaAssociation
Automatic Session Timeout
Risk modeling
MEGA Architecture modeling
Review command line parameters
Check format of report templates (MS Word)
Convert custom report templates (MS Word) to format RTF
Configure MS Word generation mode for each HOPEX environment
Re-import solutions packs
If you did not use solution packs, you can skip this section.
 
Otherwise, solutions packs (identified before migration) need to be imported again in HOPEX V2.
Note that certain Solution Pack do not exist any longer:
 
Executable
Comment
Audit.exe
Solution Pack provided in HOPEX V1R2-V1R3 for HOPEX Internal Audit. Not used with HOPEX V2.
Compliance.exe
Solution Pack provided in HOPEX V1R2-V1R3 for HOPEX Regulatory Compliance. Not used with HOPEX V2.
ERM.exe
Solution Pack provided in HOPEX V1R2-V1R3 for HOPEX Enterprise Risk Management. Not used with HOPEX V2.
ICM.exe
Solution Pack provided in HOPEX V1R2-V1R3 for HOPEX Internal Control. Not used with HOPEX V2.
ITGRC.exe
Solution Pack provided in HOPEX V1R2-V1R3 for HOPEX IT Risk Management. Not used with HOPEX V2.
ITPM.exe
Solution Pack provided in HOPEX V1R2-V1R3 for HOPEX IT Portfolio Management. Not used with HOPEX V2.
 
For each HOPEX environment, re-install each solution pack using the standard procedure.
 
Pre-requisite:
For each solution pack
In the HOPEX installation:
• Browse the folder \Utilities\Solution Pack
• Uncompress the .exe related to the appropriate framework
ex: DoDAF.exe for Solution Pack 'DODAF'
 
Procedure:
 
In HOPEX installation:
• Start the Windows Administration Console (Administration.exe)
• Select and open the environment.
• Select the appropriate repository.
• R click > Object Management > Import Solution Pack
• For each solution pack
o Select the appropriate framework and click 'OK'
wait until the process is completed
• Close the environment.
• Exit the Windows Administration Console.
 
Review important options
This section applies if the source version is HOPEX V1R2. Otherwise (source version is HOPEX V1R3), you can skip it.
Definition of path of MetaAssociation
According to decision taken before migration (see sooner in this document), verify the value the option 'Definition of path of MetaAssociation'.
Automatic Session Timeout
From HOPEX V1R2-V1R3, a feature 'Automatic Session Timeout' is enabled by default for both Windows Front-End and Web Front-End. Once enabled:
• Authentication is required after a period of inactivity
• Application closes after a period inactivity.
 
It is possible to configure or disable this feature. See the environment options (group 'Workspace, 'Automatic Session Timeout').
Risk modeling
Several options related to risk are available:
 
Group of options
Option
Business Process and Architecture Modeling
Risk modeling MEGA 2009 (*)
Risk modeling HOPEX
Compatibility > Others
Risk properties compatibility MEGA 2009
(*) previously named 'Risk modeling'.
 
Here are recommendations according to the methodology chosen in the project
 
Context
Recommendation
The project does NOT use HOPEX Solutions. Before upgrading, the option 'Risk modeling' was checked.
Risk modeling MEGA 2009: checked
Risk modeling HOPEX: unchecked
Risk properties compatibility MEGA 2009: checked (optional)
The project uses HOPEX Solutions. Before upgrading, the option 'Risk modeling' was checked.
Risk modeling MEGA 2009: unchecked
Risk modeling HOPEX: checked
Risk properties compatibility MEGA 2009: checked (optional)
The project does NOT use HOPEX Solutions. Before upgrading, the option 'Risk modeling' was uncheked.
Risk modeling MEGA 2009: unchecked
Risk modeling HOPEX: unchecked
Risk properties compatibility MEGA 2009: unchecked
MEGA Architecture modeling
Group of options
Option
Business Process and Architecture Modeling
Application Creation of an application environment diagram
Compatibility > Others
Exchange contracts (protocols) modeling before MEGA 2009 SP5 R7
 
Here are recommendations according to the methodology chosen in the project.
 
Context
Recommendation
The project used Application Environment Diagram before upgrading.
Application Creation of an application environment diagram: checked (default value for release V1R2)
The project did not use Application Environment Diagram before upgrading.
Application Creation of an application environment diagram: unchecked (default value for release V1R2)
The project did not use protocols before upgrading or intends to use one of the following products (1)
Exchange contracts (protocols) modeling before MEGA 2009 SP5 R7: unchecked
The project did use protocols before upgrading and does not intend to use one of the following products (1)
Exchange contracts (protocols) modeling before MEGA 2009 SP5 R7: checked
 
(1) MEGA Service Design (SDE), MEGA Suite For TOGAF (TOG), MEGA System Oriented IT Architecture (SOIA)
Review command line parameters
A property 'Command Line' is available at two levels:
• In properties of profile objects
• In properties of login objects (login objects are created when converting user objects)
 
If a string is set and contains codes that are not available for HOPEX V2 (ex: code 'PRO'), it will not be considered. No error should be displayed to screen but in the error logfile. It is therefore recommended to review command line parameters and remove codes that are not available for HOPEX V2.
 
Before removal
After removal
/K'PRO,ARC'
/K'ARC'
 
To identify the objects to be updated, you can run the following queries:
 
Object Type
Example of query for the code 'PRO'
Login
Select [Login] Where [Command Line] Like '#PRO#'
Profile
Select [Profile] Where [Command Line] Like '#PRO#'
 
You can get a list of codes not available for HOPEX V2 in MEGA Community, KB 00004513:
http://community.mega.com/t5/custom/page/page-id/mega-kb-solution?sid=501D00000012hECIAY
Check format of report templates (MS Word)
 
By default with HOPEX V2,
• Standard report templates (MS Word) are installed in the format RTF.
• Generation mode is RTF.
 
According to your decision (see the section 'Decide format of report templates (MS Word)' sooner in this document), you need to do the following:
 
Decision
Custom report templates (MS Word)
Actions required
Keep format RTF
No
None
Keep format RTF
Yes
Convert custom report templates (MS Word) to format RTF.
Switch back to format MS word
-
Configure MS Word generation mode for each HOPEX environment.
 
Convert custom report templates (MS Word) to format RTF
 
Pre-requisites:
 
Use a machine where
• HOPEX V2 is installed.
• MS Word is installed (version Office 2010/2013, 32-bit version only).
• HOPEX environment to be converted are available (update file permissions).
• Verify that no process WINWORD.EXE is running.
 
Procedure:
 
For each HOPEX environment:
1. Start the Windows Administration Console (Administration.exe).
2. Select and open the environment with the appropriate login (ex: system).
3. In the folder 'Repositories', select 'Systemdb'.
4. R click > Conversions > Utilities:
A list of conversions is displayed.
5. Check 'MEGA Repository - Convert Report Templates (MS Word) to RTF format'.
Wait until the processing is finished.
6. Exit Administration Console
 
Result:
 
For the HOPEX environment
• Each report template (MS word) is saved in the RTF format in the system database.
• Each RTF style sheet used by a report template (MS Word) is duplicated and converted to the RTF format. The duplicate has the .RTF file extension and is saved in the folder 'Mega_usr' of the HOPEX environment.
 
It is recommended to verify in the error logfile (megaerrYYYYMMDD.txt) that each report template (MS word) has been converted without error.
 
Configure MS Word generation mode for each HOPEX environment
Procedure:
 
For each HOPEX environment:
• Manually edit the file Megaenv.ini with a text editor
• Check that the following lines are present
[Office]
DocumentFormat=20
• Save the file.
 
Result:
 
For each HOPEX environment configured, generation mode is MS Word (.doc extension).