Installation procedure:
Important notes if you upgrade from HOPEX V1R2 (base version, CP1.0/CP2.0) to HOPEX V1R2 CP3.0 or higher CP:
It is required to:
- Run technical conversion for each repository, if you use RDBMS storage. KB 00003530.
- Run a specific conversion named 'MEGA Repository - Conversion of Code Template related to MetaCommand' on system database if you have customized web desktops. KB 00005095 .
- Check disk size on the server. A RDBMS local cache is activated by default to improve performances with RDBMS storage. This activation can create up to 5 GB per MEGA environment. Uncheck the option 'Activate RDBMS local cache' to disable this cache. KB 00005155
More generally, with HOPEX V1R2, CP are provided as .EXE files. It is possible to get a file .MSP file from the .EXE file: read the above article.
Follow the document How to upgrade CP HOPEX V1R2 EN
It is recommended that the administrator changes the environment reference if a physical backup has been restored
See KB 00005357
Besides, different IIS parameters are set when installing HOPEX to favor stability
It is recommended to check them for existing installations. See KB 00005159 and KB 00005168
Content:
HOPEX V1R2 CP7.0 delivers various fixes.
In particular:
- Robustness fixes (collaborative workspace, communication with SQL server, import from LDAP, Thai language, stored procedure SP_CLEAN_MEGA_DATABASE...)
- Possible conflicts with maintenance tools (SQL Server) KB 00005486
- Unexpected error of HOPEX application (API script, MegaCurrentEnv) KB 00005447
To know the functional changes of recent CP, you can read the following documents
HOPEX V1R2 CP3 Changes EN
HOPEX V1R2 CP4 Changes EN
HOPEX V1R2 CP5 Changes EN
HOPEX V1R2 CP6 Changes EN
Fixes are documented in the document Fix list for MEGA HOPEX V1R2cp7.0.
