Installation and Deployment > How to migrate to HOPEX V2R1 > Complete upgrade of data
Complete upgrade of data
 
Re-import solutions packs
Set a value for 'Definition of path of MetaAssociation'
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
Restore web settings
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 V2R1.
Note that certain solution packs do not exist any longer:
 
Executable
Comment
Audit.exe
Solution Pack provided in HOPEX V1R2-V1R3 for HOPEX Internal Audit. Not used with HOPEX V2R1.
Compliance.exe
Solution Pack provided in HOPEX V1R2-V1R3 for HOPEX Regulatory Compliance. Not used with HOPEX V2R1.
ERM.exe
Solution Pack provided in HOPEX V1R2-V1R3 for HOPEX Enterprise Risk Management. Not used with HOPEX V2R1.
ICM.exe
Solution Pack provided in HOPEX V1R2-V1R3 for HOPEX Internal Control. Not used with HOPEX V2R1.
ITGRC.exe
Solution Pack provided in HOPEX V1R2-V1R3 for HOPEX IT Risk Management. Not used with HOPEX V2R1.
ITPM.exe
Solution Pack provided in HOPEX V1R2-V1R3 for HOPEX IT Portfolio Management. Not used with HOPEX V2R1.
 
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.
 
Set a value for 'Definition of path of MetaAssociation'
Once a decision has been made (see section Decide 'Definition of path of MetaAssociation' sooner in the document), it must be implemented.
 
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. Select the environment
4. R click > Options > Modify
A list of options is displayed.
• In the left tree, select the folder Repository
• In the right pane, select a value for Definition of path of MetaAssociation according to the decision made.
5. Exit Administration Console
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 V2R1 (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
/RW'PRO,DMO'
/RW'DMO'
 
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 V2R1 in MEGA Community, KB 00004513:
 
 
Check format of report templates (MS Word)
 
By default, with HOPEX V2R1,
• Standard report templates (MS Word) are installed in the format RTF.
• Generation mode is RTF (with conversion to DOCX).
 
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
Standard report templates (MS Word) are natively provided in the format RTF.
Custom report templates (MS Word) need to be converted if:
• Project decision is to keep format RTF
• They have not yet been converted to format RTF.
 
Pre-requisites:
 
Use a machine where
• HOPEX V2R1 is installed.
• MS Word is installed (version Office 2010/2013/2016, 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:
6. Start the Windows Administration Console (Administration.exe).
7. Select and open the environment with the appropriate login (ex: system).
8. In the folder 'Repositories', select 'Systemdb'.
9. R click > Conversions > Utilities:
A list of conversions is displayed.
10. Check 'MEGA Repository - Convert Report Templates (MS Word) to RTF format'.
Wait until the processing is finished.
11. 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).
 
 
Restore web settings
 
If you need to restore this information when migrating from HOPEX V1R3 or HOPEX V2 to HOPEX V2R1, restore (file copy) the file MegaSettings-*.ini on the server hosting the target installation (HOPEX V2R1). With HOPEX V2R1, such files are expected in the folder:
%ProgramData%\MEGA\HOPEX V2R1\ClusterRoot\UserSettings