Installation and Deployment : Installation and Deployment : How to install hotfix HOPEX V2 EN : Upgrading HOPEX programs
   
Upgrading HOPEX programs
 
Upgrading Web Front-end
Upgrading HOPEX Data
The hotfix installation program is an .EXE file.
Example: HOPEX_V2_CP01_HF01.01.exe
 
It must be installed on each machine where the version HOPEX V2 has been previously installed. The components initially installed (HOPEX Kernel and/or IIS components) will be updated.
 
Server
Windows Service
HOPEX Kernel
IIS Application
HOPEX processes
SSP server
Mega Site Service Provider
Mega Service Watchdog
Yes
MEGASSP
mgwssp.exe
mgwspro.exe
mgwfcgi.exe
mgwswd.exe
Mega Server Supervisor.exe
Web Application Server
 
Mega Service Watchdog
Yes
HOPEX
HOPEXMWAS
mgwmapp.exe
mgwmwas.exe
mgwspro.exe
mgwfcgi.exe
mgwswd.exe
Mega Server Supervisor.exe
 
Note that only IIS application 'HOPEX' installs programs. The other IIS applications 'HOPEXMWAS' and 'MEGASSP' only install a configuration file (web.config).
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 'Mega Site Service Provider' must set to 'Stopped'.
On all the servers, the service 'Mega 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 patch level must be installed.
For example, HOPEX V2 CP1.0 is a requirement before installing HOPEX V2 CP1.0 Hotfix 1.01.
 
Procedure:
For each machine:
1. Select the .EXE file of the CP.
Example: Select HOPEX_V2_CP01_HF01.01.exe
2. R click > Run as administrator
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 patch 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 exist in read/write mode.
Verify ‘Control Panel > Administrative tools > Services’.
On the SSP server, the service 'Mega Site Service Provider' must set to 'Stopped'.
On the all servers, the service 'Mega 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 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 'Mega_Std' of the installation
Ex: C:\Program Files (x86)\MEGA\HOPEX V2\Mega_Std.
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 'Mega Site Service Provider' must set to 'Automatic' and be started.
On the all servers, the service 'Mega Service Watchdog' must set to 'Automatic' 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.