Complete upgrade of data
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.
If you use solution HOPEX GDRP, skip this section. Even if you have imported a Solution Pack 'GDPR' in the past, do not import it again: You would lose update made on data.
Otherwise, solutions packs (identified before migration) need to be imported again in HOPEX V3 in particular '
'Archimate'.
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
o 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 an need resources (CPU,RAM) or large data repositories.
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.
o Select the data repository
o R click > Properties
o Verify that 'Repository indexing' is checked and click OK.
o R click > Index for full search
o Wait for the end of the processing
• Exit
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 V3 (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 HOPEX V3.
|
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 HOPEX V3 in MEGA Community, KB 00004513:
Convert custom report templates (MS Word) to format RTF
Standard report templates (MS Word) are natively provided in the format RTF.
Custom report templates (MS Word) need to be converted to RTF.
Pre-requisites:
Use a machine where
• HOPEX V3 is installed.
• MS Word is installed (version Office 2010/2013/2016, 32-bit version only).
• HOPEX environment to be converted are available (update file permissions).
• Verify that no process WINWORD.EXE is running.
• For each environment, manually edit file megaenv.ini, section [Office] and change DocumentFormat is needed (see below table).
|
Not correct
|
Correct
|
|
[Office]
DocumentFormat=20
|
[Office]
DocumentFormat=10
|
Notes:
• If the parameter DocumentFormat is not present in megaenv.ini, consider that format RTF (default format).
• DOCX is a variant of RTF format.
Procedure:
If you already use RTF/DOCX format, conversion of custom report templates (MS Word) is not required.
If you have used DOC format so far, conversion of custom report templates (MS Word) is required.
On a machine where MS Word (32 bit) is installed.
For each HOPEX environment:
6. Start the Windows Administration Console (Administration.exe).
7. Select and open the environment with the appropriate login (ex: system).
8. In the folder 'Repositories', select Systemdb.
9. R click > Conversions > Utilities:
A list of conversions is displayed.
10. Check only 'MEGA Repository - Convert Report Templates (MS Word) to RTF format'.
Wait until the processing is finished.
11. Exit Administration Console
Result:
For the HOPEX environment
• Each report template (MS word) is saved in the RTF format in the system database.
• Each RTF style sheet used by a report template (MS Word) is duplicated and converted to the RTF format. The duplicate has the .RTF file extension and is saved in the folder 'Mega_usr' of the HOPEX environment.
It is recommended to verify in the error logfile (megaerrYYYYMMDD.txt) that each report template (MS word) has been converted without error.
Restore web settings
If you need to restore this information when migrating from to HOPEX V2R1, restore (file copy) the file MegaSettings-*.ini on the server hosting the target installation (HOPEX V3).
With HOPEX V3, such files are expected in the folder:
%ProgramData%\MEGA\HOPEX V3\ClusterRoot\UserSettings