2. Install Test Platform
2.1. Install HOPEX Aquila (development)
There are technical requirements. See online documentation for HOPEX V6.0 HOPEX Application Server (HAS) Architecture Overview, in particular section 'Software Technology Stack'.
For the installation procedure, see online documentation for HOPEX V6.0 HOPEX Application Server (HAS) Installation Guide.
2.2. Initialize migration document (development)
A specific migration document should be created. It will detail all steps required to migrate:
• From source version (HOPEX V4.0 CP7 or HOPEX V5.0 CPX)
• To target version HOPEX Aquila (HOPEX V6.0 SPx)
Whenever a test feedback identifies an additional step, this step should be added to the documented so that migration can be played again from source data.
2.3. Restore data in SQL Server (development)
Data must be initialized in development from a copy of production data (down data alignment). It is essential to use test data that are representative from production data.
Example: Restore copy of production data of HOPEX V5.0.
|
Production data of HOPEX V5.0
|
Development data in HOPEX Aquila V6.0
Copy of production data HOPEX V5.0
|
|
Standard_SystemDb
|
Migration1_SystemDb
|
|
Standard_MasterData
|
Migration1_MasterData
|
|
Standard_HAS_5000
|
Migration1_HAS_5001
|
2.4. Create a HAS Instance (development)
In Instance Manager console, create a HAS Instance in mode Development in version HOPEX Aquila. This is necessary to tune the customization module.
To reuse the HAS Database created previously (ex: Migration_HAS_5000), enter this name as Cluster name when creating the HAS Instance. Otherwise, a new HAS Database will be created.
After this step:
• A HOPEX license is configured
2.5. Complete HAS instance (development)
As a general rule, each module deployment must be completed by environment automatic update. In the context of migration, environment automatic update will be run later in step 3.
2.5.1. Deploy migration module (development)
In HAS Console, install module HOPEX Environment Migration Package Aquila (hopex.core.migrate) in version 17.0.0+6771.
This module is required to upgrade SystemDb to version HOPEX Aquila V6.0.
2.5.2. Deploy customization module (development)
If customization exist, customization module (has.custom) must be deployed and adapted if necessary. Install this module from HAS Console.
Note that customization module must be deployed before upgrade of data.
Note also that the version of customization module available on HOPEX Store is only a template. Only project has the real version to use. This version is incremented when module content is updated following the appropriate procedure.
2.5.3. Deploy additional modules (development)
Reminder:
When a HAS instance is created, keys modules (called system modules, grouped in a bundle) are installed automatically. Other modules are called additional modules.
In HAS Console, install additional modules (menu Modules > Module List, Add new)
For each additional module used in the source version except customization module (has.custom):
• Select the module, ex: hopex360.
• Select the public version of the module compatible with HOPEX Aquila V6.0:
• Use version 17.0.X if it exists.
• Otherwise use version 15.0.X.
Note that each module deployment must be completed by environment automatic update.
If Archimate is used in HOPEX V4.0, note that module 'Archimate V3.1' should be installed.
If you use module hopex360 note that there is a distinct set of versions for HOPEX Aquila V6.0 (version 17.x). You need to install this new version.
If you have customized web site template available with module hopex360 in version HOPEX V5.0 you need to:
• Duplicate standard web site template and components
• Customize the duplicated web site template
Due to security changes (macro calling CreateObject), code needs to be update for HOPEX Aquila V6.0.
See also release note for HOPEX Aquila V6.0
2.5.4. Update configuration (development)
When the HAS instance was created various settings (megasitesettings) have been initialized
|
Situation
|
Impact
|
Recommendations
|
|
A new HAS Database has been created
|
Settings are default settings for HOPEX Aquila.
|
Check that settings of source installation are valid for this HAS Instance (Development)
Replace certain settings with settings of source installation backed up previously
|
|
An existing HAS Database has been re-used
|
Settings of source installation have been restored
|
Check that settings of source installation are valid for this HAS Instance (Development)
|
|
Section that could be updated:
|
Sections that should not be updated:
|
|
[System]
[General]
[Mail]
[Filter]
…
|
[Customization]
[Must Licence]
[HOPEX]
[HAS]
[Environment Shortcuts]
[SQL SERVER CONFIG]
|
In a similar way, environment level settings (options) have been initialized with default settings for HOPEX Aquila.
It is recommended to replace certain settings with settings of source environment backed up previously (Megaenv.ini).
|
Section that could be updated:
|
Sections that should not be updated:
|
|
[Filter-Available]
[Filter]
…
|
[Env.Def]
[DbReferences]
|
Such changes in configuration should be documented in the specific migration document.
2.5.5. Restore user web settings for an instance (HOPEX V4.0)
This section applies only if source version is HOPEX V4.0.
If you need to restore this information when migrating to HOPEX Aquila, restore (file copy) the files MegaSettings-*.ini on the server hosting the target installation (HOPEX Aquila V6.0).
This will enable that the information is imported to the HAS database of the instance.
With HOPEX Aquila V6.0, such files are expected in the folder:
%ProgramData\MEGA\Hopex Application Server\<instance>\LocalData\UserSettings
Ex: C:\ProgramData\MEGA\Hopex Application Server\<Instance>\LocalData\UserSettings
Note that this is not a batch tool. Conversion is made on the fly when login. If an end user does not login to HOPEX Aquila, related user settings are not imported to the database of the instance.