Installation and Deployment > How to Migrate to HOPEX V3
How to Migrate to HOPEX V3
 
Main steps to migrate data to HOPEX V3
Prepare upgrade of data
Check metamodel, locks, workspaces and workflows
Verify that GBMS storage is no longer used
Verify that Windows Front-End is no longer used for runtime
Verify format of report templates (MS Word)
Verify technology of web desktops
Identify Solution packs used
Decide 'Definition of path of MetaAssociation'
Check license with your sales representative
Review use of the profile 'Enterprise Architect'
Review authentication mode
Decide to keep web settings
Upgrade data from HOPEX V2R1 to HOPEX V3
Check data upgrade pre-requisites
Upgrade environment with SQL Server storage
Update stored procedures with SQL Server storage
Complete upgrade of data
Set a value for 'Definition of path of MetaAssociation'
Re-import solutions packs
Rebuild full search indexes
Review command line parameters
Convert custom report templates (MS Word) to format RTF
Restore web settings
Check upgraded data
First control of migration
Check data modelling consistency
Other checking indications
Appendix
Conversion details
Utilities details
FAQs
Warning 'Run the menu 'Perform SQL conversion on the repository' to perform the upgrade
Warning 'Your environment and site are not of the same version. Your environment requires updating…'
Warning 'Writing access diagram is not compiled…'
How to run a specific conversion or utility?
 
 
 
Summary
 
Check if a more recent version of this document is available in online documentation (MEGA Community).
 
This document describes the procedures necessary for upgrading HOPEX Data to version HOPEX V3.
Migration is allowed with specific CPs for source and target versions.
 
Source version
Target version (direct migration path)
HOPEX V2R1 Update 3 CP5
HOPEX V3 CP2 last hotfix
Then CP upgrade to last CP (1)
 
For previous versions or releases (HOPEX V2R1 Update 2, HOPEX V2R1 Update 1, HOPEX V2, HOPEX V1R2... MEGA 2009) it is necessary to perform an intermediate upgrade to HOPEX V2R1 Update 3 CP5.
 
Source version
Target version (indirect migration path)
HOPEX V2R1 Update 2
HOPEX V2R1 Update 2 > HOPEX V2R1 Update 3 CP5 > HOPEX V3 CP2 (1)
HOPEX V2R1 Update 1
HOPEX V2R1 Update 1 > HOPEX V2R1 Update 3 CP5 > HOPEX V3 CP2 (1)
HOPEX V2
HOPEX V2 CP07.0 > HOPEX V2R1 Update 3 CP5 > HOPEX V3 CP2 (1)
HOPEX V1R3
HOPEX V1R3 CP17.0 > HOPEX V2R1 Update 3 CP5 > HOPEX V3 CP2 (1)
HOPEX V1R2
HOPEX V1R2 CPx > HOPEX V1R3 CP 17.0 -> HOPEX V2R1 Update 3 CP5 > HOPEX V3 CP2 (1)
HOPEX V1R1
HOPEX V1R1 CPx > HOPEX V1R3 CP 17.0 -> HOPEX V2R1 Update 3 CP5 > HOPEX V3 CP2 (1)
MEGA 2009
MEGA 2009 SP5 CP11.0 > HOPEX V1R3 CP 17.0 -> HOPEX V2R1 Update 3 CP5 > HOPEX V3 CP2 (1)
 
(1) from HOPEX V3 CP2 you can apply CP upgrades to attain the latest CP.
 
It does not describe:
• System requirements and possible architectures (see architecture overview documentation).
• Change is product list (see your sales representative)
• How to perform installations (see installation documentation).
• How to install update (see how to install update documentation).
• How to manage installations (see administrator manuals).
• How products are licensed (see license installation documentation).
• How to use features (see user manuals).