Complete upgrade of data
Activate standard mode for questionnaires
If this activation was decided previously (see sooner in this document, 'Decide how to manage questionnaires'), it is required for each HOPEX environment to:
• Install new module
• Run a conversion utility
Procedure:
• Start the Windows Administration Console (Administration.exe)
• Select and open the environment with the login System
• Select the environment and R click > Modules
• In the window 'Import a module', select Questionnaire Builder and click OK.
Wait until the end of the processing
• Close the environment
• Exit the Windows Administration Console
Duration is approximately 30 minutes.
Run a conversion utility:
Procedure:
• Start the Windows Administration Console (Administration.exe)
• Select and open the environment with the login System
• For each data repository involved:
• Select the data repository
• R click > Convert > Utilities
• Check only the option Utility - Convert Questionnaire Templates to New Mode and click OK (1)
• Wait until conversion is complete
• Close the environment
• Exit the Windows Administration Console
(1) Note that you can check the option 'Apply to all repositories of the environment' to run this conversion for all repositories in a single action.
Duration is a few minutes.
After this activation, it is necessary to check if converted questionnaire templates are fully compatible. See later in this document, 'Other checking indications'.
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
• In the right pane, select a value for Definition of path of MetaAssociation according to the decision made
5. Exit Administration Console
Re-import solutions packs
If you did not use solution packs, skip this section.
Solutions packs (identified before migration) need to be imported again in HOPEX V4.
For each HOPEX environment, re-install each solution pack using the standard procedure.
Pre-requisite:
For each solution pack
In the HOPEX installation:
• Browse the folder \Utilities\Solution Pack
• Uncompress the .exe related to the appropriate framework
ex: PPM.exe for Solution Pack 'PPM'
Procedure:
In HOPEX installation:
• Start the Windows Administration Console (Administration.exe)
• Select and open the environment.
• Select the appropriate repository.
• R click > Object Management > Import Solution Pack
• For each solution pack
• Select the appropriate framework and click 'OK'
wait until the process is completed
• Close the environment.
• Exit the Windows Administration Console.
Rebuild full search indexes
Full search required that indexes are built.
Such indexes are initialized from full indexing and completed by incremental indexing (scheduled)
The format of theses indexes has changed. It is therefore required to rebuild them if full search is used.
Note that full indexing can be time consuming and need resources (CPU, RAM) or large data repositories.
Note also that full indexing is not required to start HOPEX. It is required to benefit from full-text search feature.
Procedure:
For each HOPEX environment.
For each data repository indexed.
• Browse the index folder using Windows explorer
Ex: <HOPEX environment path>\Db\<Repository>\<Repository>.ix
• Manually delete all files
Then, it is possible to rebuild them using Administration.exe
Procedure:
• Run Administration.exe
• Open each HOPEX environment.
• Select the environment
• R click > Options > Modify
• In group 'Languages', verify that the language to be indexed are checked and click OK
• For each data repository indexed.
• Select the data repository
• R click > Properties
• Verify that Repository indexing is checked and click OK.
• R click > Index for full-text search. A window reminds the languages considered.
• Click OK and wait for the end of the processing. Duration can vary according to various parameters (number of languages selected, infrastructure performances, size and number of repositories). It can last up to several hours.
• Exit the Windows Administration Console.
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 V4 (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:
Restore web settings
If you need to restore this information when migrating to HOPEX V4, restore (file copy) the file MegaSettings-*.ini on the server hosting the target installation (HOPEX V4).
With HOPEX V4, such files are expected in the folder:
%ProgramData%\MEGA\HOPEX V4\ClusterRoot\UserSettings
Custom files in Mega_usr folder
This applies from HOPEX V4 CP2
An option 'Customization folder' enables to define a customization folder (optional)
Folder <installation path>\java\lib_usr is no longer considered
Folder <installation path>\DotNet\Assemblies_usr is no longer considered
Custom Java (.Jar) files must be copied to a new folder according to the situation:
By default when no customization folder is set
<installation path>\Customizations\javalib
If a customization folder is set
<customization folder path>\javalib
Folder <installation path>\java\lib_usr is no longer considered.
Custom .Net files must be copied to a new folder according to the situation:
By default when no customization folder is set
<installation path>\Customizations\dotnet
If a customization folder is set
<customization folder path>\dotnet
Other custom files (ex: .Mgs, .Gif, .Png…) must be copied according to the situation
By default when no customization folder is set
<installation path>\Customizations\mega_usr
If a customization folder is set
<customization folder path>\mega_usr