Upgrading HOPEX programs
The hotfix installation program is a .MSP file.
Example: HOPEX_V2R1_U01_HF01.01.msp.
 
It must be installed on each machine where the version HOPEX V2R1 has been previously installed. The components initially installed (HOPEX Kernel and/or IIS components) will be updated.
 
Front-end
Deployment
Target machine
Web Front-end
Standalone deployment
Unique Server where HOPEX programs are installed
Web Front-end
Cluster deployment
Each application server of the cluster where HOPEX programs are installed
HOPEX Front-end
HOPEX Back-end
SSP
Windows Front-end
 
Standard deployment
Each workstation where HOPEX programs are installed
Windows Front-end
 
Citrix/Terminal Server deployment
Each Citrix/TSE application server where HOPEX programs are installed
 
 
 
Deployment
Machine
Windows Service
IIS Web site (1)
HOPEX processes
Web standalone deployment
Unique server
Yes
Yes
Yes
Web cluster deployment
Server running SSP
Yes
 
Yes
Web cluster deployment
Server running HOPEX Back-end
Server running HOPEX Front-end
Yes
 
Yes
Windows Citrix/Terminal Server deployment
Each workstation
No
 
Yes
Windows standard deployment
Each Citrix/TSE application server
No
 
Yes
 
(1) By default, an application 'HOPEX' is configured for 'Default Web Site'.
 
Upgrading Web Front-end
 
Pre-install:
Identify the target machine(s).
The machine varies with the chosen deployment: see above table.
Archive key configuration file of IIS application (web.config file) and HOPEX installation (Megasite.ini).
Login in as administrator of the machine.
Verify ‘Control Panel > Administrative tools > Services'.
On the SSP server, the service HOPEX Site Service Provider must set to 'Stopped'.
On all the servers, the service HOPEX Service Watchdog must set to 'Stopped'.
Verify ‘Internet Information Services (IIS) Manager'.
The web site hosting the IIS applications (by default it is 'Default Web Site') must be stopped.
Verify the Task Manager.
No HOPEX process (mgw*.exe, or HOPEX*) must be running.
Verify 'Control Panel > Add or Remove programs'.
The required update level must be installed.
For example, HOPEX V2R1 U1.0 is a requirement before installing HOPEX V2R1 U01.0 Hotfix 1.01.
 
Note: you can also use the utility Hopex Server Supervisor and R click > HOPEX > Stop HOPEX Processes Services and Web Application.
 
Procedure:
For each machine:
1. Select the .MSP file of the update.
Example: Select HOPEX_V2R1_U01_HF01.01.msp
2. R click > Apply
The wizard can take more than 1 min to load.
3. Click Update >.
The installation process can take a minute to initialize.
Wait until the processing is complete.
4. Click Finish.
 
Notes:
o The location of the installation folder can be found after a search is conducted in the machine registry. This location is not visible on the machine during installation or in the control panel.
o If the expected update level is not identified for the HOPEX programs registered on the machine, an error is displayed.
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.
 
Pre-upgrade:
Verify that no workspace exists in read/write mode.
Verify ‘Control Panel > Administrative tools > Services'.
On the SSP server, the service HOPEX Site Service Provider must set to 'Stopped'.
On the all servers, the service HOPEX Service Watchdog must set to 'Stopped'.
Verify the Task Manager.
No HOPEX process (mgw*.exe, or HOPEX*) must be running.
 
 
Procedure:
 
For each HOPEX environment:
1. Start the Administration Console (Administration.exe).
2. Select the environment to be upgraded.
3. R click > Open.
4. Login with the System identifier.
5. In the folder 'Repositories', select Systemdb.
6. R click > Object Management > Import.
7. Select file 'UpgradeHF.mol' and click Import.
It is located in the folder '\Install\Update' of the installation
Ex: C:\Program Files (x86)\MEGA\HOPEX V2R1\Install\Update
Before Update 3, this file was located in the folder '\Mega_Std' of the installation.
8. In the tree, select the environment.
9. R click > Metamodel > Translate and compile.
10. Check at least 'Compile metamodel' and 'Compile technical data' and click 'Start'.
Wait until compilation is complete.
11. Exit the Administration Console.
 
 
Post-installation and data upgrade:
Verify ‘Control Panel > Administrative tools > Services'.
On the SSP server, the service HOPEX Site Service Provider must set to 'Automatic (Delayed Start)' and be started.
On the all servers, the service HOPEX Service Watchdog must set to 'Automatic (Delayed Start)' and be started.
Verify ‘Internet Information Services (IIS) Manager'.
The web site hosting the IIS applications (by default it is 'Default Web Site') must be started.
 
Note: you can also use the utility Hopex Server Supervisor and R click > HOPEX > Restart HOPEX Processes Services and Web Application.