Installation procedure:
Follow the document How to upgrade CP HOPEX V1R2-V1R3 EN
Note thar if you upgrade from HOPEX V1R2 (base version, CP1.0/CP2.0) to a higher CP:
It is required to:
- 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
Note that if you upgrade from HOPEX V1R2 (base version, CP1.0/CP2.0/CP3.0/CP4.0/CP5.0/CP6.0/CP7.0) to CP8 or higher:
It is required to convert files related to .must licence. Read the the above article or see KB 00005681.
General notes:
- With HOPEX V1R2-V1R3, CP are provided as .EXE files. It is possible to get a file .MSP file from the .EXE file: read the above article.
- It is recommended that the administrator changes the environment reference if a physical backup has been restored
See KB 00005357
- 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
- A warning can be displayed if version is not identified. See KB 00005621
Content:
HOPEX V1R2-V1R3 CP8.0 delivers various fixes and improvements.
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 CP8 Changes EN
A What’s New document is available in this page http://www.mega.com/en/customer/hopex-release-v1r3
Fixes related to cases open with Technical Support are documented in the document Fix list for MEGA HOPEX V1R2cp8.0.
