Upgrade data to HOPEX V4
For each HOPEX environment, several steps are required:
• Check data upgrade pre-requisites.
• Perform technical conversion of the system database for SQL Server.
• Upgrade of both the system database and data repositories using an environment update wizard. It is no longer required to convert explicitly each data repository. Of course, if a data repository is referenced after environment upgrade, the environment update wizard needs to be run again so that it is converted.
Note that environment upgrade consists in running:
• Technical conversions. They update SQL tables and indexes to the expected format. They apply for each data repository and for the systemdb database.
• System database upgrade. It upgrades the metamodel and templates stored in the system database to the format expected for the target version.
• Functional conversions. They update the system objects stored in system database and the data objects stored in the data repositories to the expected format.
Check data upgrade pre-requisites
Before proceeding, check the following:
|
Check
|
Detail
|
|
No private workspace persists
|
For each HOPEX environment, check that no private workspace persists. Each private workspace must be published or discarded (abandoned)
|
|
All HOPEX environments compile without errors
|
For each HOPEX environment, check that you can compile (metamodel and technical data) without error
|
|
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).
Check that all customizations have been backed up (physical backup).
|
|
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 'HOPEX' are set to 'Disabled'. Ex:
HOPEX Site Service Provider
HOPEX Service Watchdog
|
|
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, end it.
|
Upgrade environment (SQL Server storage)
In the procedure, various warning messages will be displayed. Most of them will be ignored.
If a message is displayed that is not quoted in the procedure, see the FAQs section of this document.
Note that only data repositories already referenced when the environment is upgraded will be migrated.
Procedure in version HOPEX V4:
1. Start the Windows Administration Console (Administration.exe).
2. Reference the environment to be converted.
3. Select the environment.
• A warning can be displayed: Run the menu 'Perform SQL conversion on the repository' to perform the upgrade.
• Click OK to hide the warning.
• Select the environment and R click > Perform SQL conversion on the repository.
A window 'MEGA RDBMS Conversion' is displayed.
A window 'MEGA RDBMS Conversion' is displayed.
• Click OK to trigger technical conversion of the SystemDb repository.
• Wait until the conversion is over. Duration can vary according to various parameters (source and target versions, size of system database, infrastructure performances). It is usually fast.
A line 'Technical conversion completed' is displayed'.
A line 'Technical conversion completed' is displayed'.
• Click Close.
4. Select and open the environment to be upgraded with the login System.
A message is displayed: 'Your environment requires an update for compatibility with your version of HOPEX. Do you wish to run this procedure now?
• Click Yes to trigger the environment upgrade.
A wizard Environment updating center - Welcome is displayed.
• Read the text, check the option I have taken note of the above text and click Next.
A list of actions is displayed. Keep them checked.
A list of actions is displayed. Keep them checked.
• Click Run to start the update. Duration can vary according to various parameters (source and target versions, infrastructure performances, size, and number of repositories). It usually lasts about 1 hour with one data repository.
A list of reports is displayed (one tab for each action).
A list of reports is displayed (one tab for each action).
• Review reports and click Close to exit the wizard.
• A warning can be displayed: The indexing format changed. Re-index your repositories to be able to use the full-text search.
• Click OK to hide it.
• A message should be displayed: Your environment has been successfully updated.
• Click OK to hide it.
• Close the environment.
• Exit the Administration Console.
Update stored procedures with SQL Server storage
This step is mandatory for each data repository or system database. The code of existing stored procedures (created in a previous version) needs to be initialized with the HOPEX V4.
Pre-requisite:
• SQL Server Service account for HOPEX has permissions to delete and create stored procedures
Procedure:
1. Start the Windows Administration Console (Administration.exe).
2. Select and open the environment with the login System.
3. For each data repository
• Select the data repository
• R click RDBMS Administration > Remove private workspace temporary data
• Click Execute and wait until the conversion is over.
• R click RDBMS Administration > Shrink unused repository historical data
• Click Execute and wait until the conversion is over.
4. Close the environment.
5. Exit the Windows Administration Console.
Duration can vary according to various parameters (source and target versions, infrastructure performances, size, and number of repositories).
Note that it is important that the execution of certain stored procedures are scheduled (batched) via a maintenance plan. Refer to the administration documentation.
Perform a physical backup
This step is highly recommended for each data repository or system database just after core migration. If data is altered during next steps of migration, this can save a significant time to restore this backup rather that redo the full migration.