Upgrading HOPEX programs
The CP installation program is an .EXE file.
For example: HOPEX_V2_CP1.0.exe
The procedure varies with the front-ends that you may use:
o Web Front-end: an IIS web server is used, a specific SSP service (1) is used
o Windows Front-end: no web server is used, no service is used.
As a consequence, it is very important that you identify the front-ends deployed and the target machines.
|
Front-end
|
Deployment
|
Target machine
|
|
Web Front-end
|
Standard deployment
|
Application Server where HOPEX programs are installed
|
|
Web Front-end
|
Cluster deployment
|
Each application server of the cluster where HOPEX programs are installed
|
|
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
|
|
Front-end
|
SSP Service (1)
|
IIS
|
HOPEX processes
|
|
Web Front-end
|
Yes
|
Application 'HOPEX' (2)
|
mgwmapp.exe, mgwmwas.exe, mgwspro.exe, mgwssp.exe, mgwfcgi.exe, Mega Server Supervisor.exe
|
|
Windows Front-end
|
No
|
|
mgwmapp.exe
|
(1) Windows service name is 'Mega Site Service Provider'.
(2) By default, an application 'HOPEX' is configured for 'Default Web Site'.
Upgrading Web Front-end
Pre-install:
1. Identify the target machine(s).
The machine varies with the chosen deployment: see above table.
2. Archive key configuration file of IIS application (web.config file) and HOPEX installation (Megasite.ini).
3. Login in as administrator of the machine.
4. Verify ‘Control Panel > Administrative tools > Services’.
The service 'Mega Site Service Provider' must set to 'Stopped'.
The service 'Mega Service Watchdog' must set to 'Stopped'.
5. Verify ‘Internet Information Services (IIS) Manager’.
The web site hosting the IIS applications (by default it is 'Default Web Site') must be stopped.
6. Verify the Task Manager.
No HOPEX process (mgw*.exe, or HOPEX*) must be running.
7. Verify ‘Control Panel > Add or Remove programs’.
The required patch level must be installed.
For example, HOPEX V2 CP7.0 is a requirement before installing HOPEX V2 CP8.0.
Procedure:
For each machine:
1. Select the .EXE file of the CP.
Example: Select HOPEX_V2_CP1.0.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.
Post-install:
o Verify ‘Control Panel > Administrative tools > Services’.
The service 'Mega Site Service Provider' must be set back to 'Automatic' and be started.
The service 'Mega Service Watchdog' must be set back to 'Automatic' and be started.
o Verify ‘Internet Information Services (IIS) Manager’.
The web site hosting the IIS applications (by default it is 'Default Web Site') must be started.
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 Windows Front-end
Pre-install:
1. Identify the target machine(s).
The machine varies with the chosen deployment: see above table.
2. Archive key configuration file of IIS application (file web.config) and HOPEX installation (Megasite.ini).
3. Login in as administrator of the machine.
4. Verify the Task Manager.
No HOPEX process mgwmapp.exe must be running.
5. Verify ‘Control Panel > Add or Remove programs’.
The required patch level must be installed.
For example, HOPEX V2 CP7.0 is a requirement before installing HOPEX V2 CP8.0.
Procedure:
For each machine:
1. Select the .EXE file of the CP.
Example: Select HOPEX_V2_CP1.0.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.