3. Upgrading HOPEX data
Most changes apply to HOPEX programs. However, some changes apply to the systemdb repository. It is therefore necessary to update all HOPEX environments to benefit from all the changes and fixes. The procedure varies with the storage.
With HAS deployment, Windows Administration Console (Administration.exe) is installed in a subfolder of the HAS Instance:%programdata%\MEGA\Hopex Application Server\<instance port number>, ex: C:\ProgramData\MEGA\Hopex Application Server\5001
3.1. Pre-update:
Unlike previous versions, Administration.exe cannot run if all processes and services are stopped.
To enable environment upgrade, it is expected that:
• HAS Instance manager is started
• An HAS instance is created (with licence configured) and started.
• Module Hopex.Core is stopped
• No workspace persists.
Procedure to stop module HOPEX Core Back-end V5.0 (hopex.core):
• Select HAS instance, ex https://mymachine:5000
• Open HAS Console and login
• In HAS console, display tab Cluster
• For module HOPEX Core Back-end V5.0 (hopex.core), select action Stop on the right.
3.2. Update Procedure:
Unlike previous versions, Administration.exe cannot run if all processes and services are stopped.
To enable environment upgrade, it is required that:
• HAS Instance manager is started.
• An HAS instance is created (with licence configured) and started.
• Module Hopex.Core is stopped
Stop module HOPEX Core Back-end V5.0 (hopex.core):
• Select HAS instance, ex https://mymachine:5000
• Open HAS Console and login
• In HAS console, display tab Cluster
• For module HOPEX Core Back-end V5.0 (hopex.core), select action Stop on the right.
Update HOPEX environment:
1. Start Administration.exe.
2. Select the environment to be upgraded.
3. R click > Open.
4. Login with the System identifier.
5. Select the target environment.
6. R click > Environment automatic update.
A wizard 'Environment Update Center' is displayed.
• Read text, check 'I have taken note of the above test' and click Next.
• Keep the selected actions checked and click Run.
o Wait until processing is complete.
7. Exit Administration.exe.
3.3. Additional conversions:
Certain CP required additional conversions (after environment automatic update).
|
Condition
|
Manual conversion required
|
Comment
|
|
From HOPEX V5.0 to HOPEX V5.0 CP1
|
No need
|
|
|
From HOPEX V5.0 X to V5.0 CP2 or higher
|
Needed. See below
|
Once data have been updated to CP2 or higher format, it is not required to run this conversion again
|
|
From HOPEX V5.0 X to HOPEX V5.0 CP5 or higher CP
|
Needed if solution HOPEX Business Continuity Management is used. See below
|
Once data have been updated to CP5 or higher format, it is not required to run this conversion again
|
|
Direct migration to HOPEX V5.0 CP5 or higher CP
|
No need
|
|
When upgrading from HOPEX V5.0 X to V5.0 CP2 or higher
For each HOPEX environment:
1. Start Administration.exe.
2. Select the environment to be upgraded.
3. R click > Open.
4. Login with the System identifier.
5. For each Data Repository.
6. Select the Data Repository.
7. R click > Conversions > Convert data into current version > From HOPEX V3 data
A list of elementary conversions is displayed.
• Select only the following conversions
o MEGA Repository - Conversion of Business Policy names
o MEGA Repository - Data Conversion - Conversion of Risk Mitigation, GDPR Risk and GDPR Minimization
• Click OK to start the conversion
• Wait until processing is complete.
8. Select the SystemDb Repository.
9. R click > Conversions > Convert data into current version > From HOPEX V3 data
A list of elementary conversions is displayed.
• Select only the following conversions
o MEGA Repository - Conversion of Profile Options
o MEGA Repository - Conversion of query objects (V5.0 and earlier versions)
o MEGA Repository - Deletion of System Job Executions
• Click OK to start the conversion
Wait until processing is complete
10. Exit Administration.exe.
When upgrading from HOPEX V5.0 X to HOPEX V5.0 CP5 or higher CP
For each HOPEX environment:
11. Start Administration.exe.
12. Select the environment to be upgraded.
13. R click > Open.
14. Login with the System identifier.
15. For each Data Repository.
16. Select the Data Repository.
17. R click > Conversions > Convert data into current version > From HOPEX V5 data
A list of elementary conversions is displayed.
• Select only the following conversions
o MEGA Repository - Conversion of RTO and Business Impact of BIA
• Click OK to start the conversion
• Wait until processing is complete.
18. Exit Administration.exe.
3.4. Post-update:
• If you use data reading access management feature (ex-confidentiality), check that data reading access is compiled.
• Verify that environment is fully compiled (Metamodel, Technical Data and Permissions)
• In HAS Console
• Restart HAS Instance with the update version and check dependencies
• Test web login. No warning should be displayed.
• If you use batch automated processing (Administration API script), update HAS installation path in Windows registry.
If environment is not fully compiled
For each HOPEX environment:
1. Start Administration.exe.
2. Select the environment to be upgraded.
3. R click > Open.
4. Login with the System identifier.
5. Select the target environment.
6. R click > Metamodel > Translate and Compile.
o Verify that checkbox Compile Permissions… is unchecked
o Otherwise, check the three checkboxes below and click Start to compile
Compile Metamodel
Compile Technical Data
Compile Permissions (recommended in Production)
o Wait until compilation process is completed.
7. Exit Administration.exe.
If you use batch automated processing (Administration API script)
Permissions to run PowerShell scripts are required.
For each HAS Instance:
• Browse the root folder of the HAS Instance
o Ex: C:\ProgramData\MEGA\Hopex Application Server\5000
• Run the script HOPEX-regserver.ps1