Upgrade data from HOPEX V1R2-V1R3
For each HOPEX environment, several steps are required:
• Check data upgrade pre-requisites.
• Upgrade the system database using environment automatic upgrade.
• Run technical conversion on system database and data repositories using RDBMS storage.
• Run conversion tools on the system database.
• Run conversion tools on the data repositories.
The procedure varies with the type of storage.
Check data upgrade pre-requisites
Before proceeding, check the following:
|
Check
|
Detail
|
|
Data is backed up
|
Check with the system administrator that all HOPEX environment have been backed up (physical backup).
Archive key configuration file of IIS application related to HOPEX (file web.config) and HOPEX installation (Megasite.ini).
|
|
Password of the login 'System'
|
For each HOPEX environment, check that the password of the login 'System' is known or set to empty before migration.
This is very important since it will be requested to login with 'System'.
|
|
All IIS web sites related to HOPEX are stopped
|
For the machine running HOPEX, Run 'Internet Information Services (IIS) Manager':
Check that All IIS web sites related to HOPEX are stopped.
|
|
All Windows services related to HOPEX are disabled
|
For the machine running SSP, in Control Panel, Administrative Tools, Services:
Check if that all services with name beginning with 'Mega' are set to 'Disabled'.
Ex: Mega Site Service Provider
|
|
No processes related to HOPEX is running
|
For the machine running HOPEX, in Windows Task Manager:
Check if a process mgw*.exe is running. If a process persists, kill it.
|
Note that with RDBMS storage (Oracle, SQL Server), a conversion called 'Technical Conversion' is required for each data repository and for the system database.
As long as conversion is not performed for a data repository (ex: ProductionData):
• This repository is displayed as not available (red cross icon).
• A warning can be displayed such as 'You cannot access repository XXX. Its internal structure is not up to date. Run the menu "Technical Conversion" to perform the upgrade. Click 'OK' to hide this warning.
Upgrade environment with RDBMS storage (Oracle and SQL Server)
Procedure in version HOPEX V2:
1. Start the Windows Administration Console (Administration.exe).
2. Reference the environment to be converted.
3. Select the environment:
A warning is displayed: You cannot access repository "SystemDb". Its internal structure is not up to date. Run the menu "Technical Conversion" to perform the upgrade.'
4. Click 'OK' to hide the warning.
5. Select the environment and R click > Technical Conversions.
A window 'MEGA RDBMS Technical Conversion' is displayed.
6. Click 'OK' to confirm conversion of the systemdb repository.
Wait until the conversion is over (it takes approximately 1 hour).
A line 'Technical conversion completed' is displayed'.
7. Click 'Close'.
8. Select and open the environment to be upgraded with the login System.
A warning is displayed: Your environment and site are not of the same version. Your environment requires updating. Refer to documentation for how to carry out this action.
9. Click 'OK'.
A Message is displayed: Your environment requires an update for compatibility with your version of HOPEX. Do you wish to run this procedure now?
10. Click 'Yes'.
A window 'Automatic Update' is displayed.
11. Read the text, check the option 'I have taken note of the above text' and click 'OK'.
The processing 'environment automatic upgrade' is executed.
Wait until the conversion is over.
A message is displayed 'Your environment has been successfully updated.
12. Click 'OK'.
13. For each data repository:
a. Select the data repository (ex: MEGA (Tutorial)).
b. R click > Technical Conversions.
A window 'MEGA RDBMS Technical Conversion' is displayed.
c. Click 'OK' to confirm conversion of the data repository.
Wait until the conversion is over. A line 'Technical conversion completed' is displayed'.
d. Click 'Close'.
14. Close the environment.
15. Exit the Windows Administration Console.
Upgrade environment with GBMS Storage
Procedure in version HOPEX V2:
1. Start the Windows Administration Console (Administration.exe)
2. Select and open the environment to be upgraded with the login System
3. A warning is displayed 'Your environment and site are not of the same version. Your environment requires updating. Refer to documentation for how to carry out this action.'
4. Click 'OK'
5. A question is displayed 'Your environment requires an update for compatibility with your version of MEGA. Do you wish to run this procedure now?
6. Read the information, check the option 'I have taken note of the above text' then click 'OK'
7. The processing 'environment automatic upgrade' is executed
8. Wait until the update is complete
9. A message is displayed like 'Your environment has been successfully updated'
10. Click 'OK'.
11. Close the environment
12. Exit the Windows Administration Console
Running conversion tools
Before proceeding, consult the table 'Conversion details' in this document to understand if conversions are relevant in your context.
Procedure:
1. Start the Windows Administration Console
2. Select and open the environment to be converted with the login System.
3. In the folder 'Repositories', select 'Systemdb'
4. R click > Conversions > Convert data into current version and select From HOPEX V1R2 data.
5. Check the appropriate conversions.
See the table 'Conversion details', later in this document
6. Click 'OK' to trigger the conversion
Wait until the conversion is complete
7. Close the environment
8. Select and open the environment with the login System
9. In the folder 'Repositories', for each data repository
10. Select the repository
11. R click > Conversions > Convert data into current version and select From HOPEX V1R2 data.
12.
13. Check the appropriate conversions.
See the table 'Conversion details', later in this document
14. Click 'OK' to trigger the conversion
Wait until the conversion is complete
15. Exit the Windows Administration Console
Update stored procedures
This step is mandatory for each data repository or system database using RDBMS storage (Oracle, SQL Server).
Code of existing stored procedures (created in a previous version) needs to be initialized with the HOPEX V2.
Pre-requisite:
• Permissions to delete and create stored procedures
Procedure:
In HOPEX installation:
• Start the Windows Administration Console (Administration.exe)
• Select and open the environment with the identifier system (no password by default).
• In the folder 'Repositories', R click > Manage: a window 'Manage repositories' is displayed.
• In the list 'Action list', check both
o Private workspace temporary data deletion
o Repository historical data deletion
• In the list 'Repository list', check appropriated repositories.
• Click 'Execute' and wait until processing is finished.
• Close the environment.
• Exit the Windows Administration Console
Note that it is still important that the execution of all these stored procedure is scheduled (batch). Refer to the document RDBMS Repository Installation guide HOPEX V2 to get the complete list.