4. Complete upgrade of data
4.1. Set a value for 'Definition of path of MetaAssociation'
Once a decision has been made (see section Decide 'Definition of path of MetaAssociation' sooner in the document), it must be implemented.
For each HOPEX environment:
1. Start the Windows Administration Console (administration.exe).
2. Select and open the environment with the appropriate login (ex: system).
3. Select the environment
4. R click > Options > Modify
A list of options is displayed.
• In the left tree, select the folder Repository > Metamodel
• In the right pane, select a value for Definition of path of MetaAssociation according to the decision made.
5. Exit Administration Console
4.2. Review command line parameters
A property 'Command Line' is available at two levels:
• In properties of profile objects
• In properties of login objects (login objects are created when converting user objects)
If a string is set and contains codes that are not available for HOPEX V5.0 (ex: code 'PRO'), it will not be considered. No error should be displayed to screen but in the error logfile. It is therefore recommended to review command line parameters and remove codes that are not available for the version.
|
Before removal
|
After removal
|
|
/RW'PRO,DMO'
|
/RW'DMO'
|
To identify the objects to be updated, you can run the following queries:
|
Object Type
|
Example of query for the code 'PRO'
|
|
Login
|
Select [Login] Where [Command Line] Like '#PRO#'
|
|
Profile
|
Select [Profile] Where [Command Line] Like '#PRO#'
|
You can get a list of codes not available for the version in MEGA Community, KB 00004513.
4.3. Restore user web settings for an instance
If you need to restore this information when migrating to HOPEX V5.0, restore (file copy) the files MegaSettings-*.ini on the server hosting the target installation (HOPEX V5.0).
This will enable that the information is imported to the database of the instance.
With HOPEX V5.0, such files are expected in the folder:
%ProgramData\MEGA\Hopex Application Server\<instance>\LocalData\UserSettings
Ex: C:\ProgramData\MEGA\Hopex Application Server\5011\LocalData\UserSettings
If target installation is a cluster installation, the files MegaSettings-*.ini must be duplicated on each node of the cluster.
Note that this is not a batch tool. If an end user does not login to HOPEX V5.0, related user setting is not imported to the database of the instance.
4.4. Backup data
Check with the system administrator that all HOPEX environment have been backed up.
This means for each environment.
• A .BAK file for the system database (SystemDb)
• A .BAK file for each data repository
• A .BAK file for configuration database
In case of a further error requesting to restore data, this will be a stable point of restore.