4. 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 Intance: %programdata%\MEGA\Hopex Application Server\<instance port number>, ex: C:\ProgramData\MEGA\Hopex Application Server\5001
4.1. Pre-update
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
• No private workspace persists.
Procedure to stop module HOPEX Core Back-end V5.0 (hopex.core):
• 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.
4.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.
4.3. 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