PLATFORM - Installation and Deployment > How to Migrate to Hopex Aquila 6.2 > Install Test Platform
3. Install Test Platform
 
Install Hopex Aquila (development)
Initialize migration document (development)
Restore data in SQL Server (development)
Create a HAS Instance (development)
Complete HAS instance (development)
Deploy migration module (development)
Deploy customization module (development)
Deploy additional modules (development)
Customization of module hopex360
Update configuration (development)
 
3.1. Install Hopex Aquila (development)
 
See Hopex Application Server (HAS) Architecture Overview documentation, in particular Software Technology Stack chapter.
 
Important prerequisites:
• .NET Core 8 (NET 8) is installed
• HAS Instance Manager is in the latest version
 
Condition
Update of Instance Manager
Comment
Upgrading to Aquila 6.1
Update to HAS Instance Manager 16.1.x version
.Net 8 support
Upgrading to Aquila 6.2
Update to HAS Instance Manager 62.1.x version
.Net 8 support
…
 
 
 
Update of Instance Manager is performed systematically if you run Hopex installer (e.g.: new installation, offline installation).
To perform a new installation, see Hopex Application Server (HAS) Installation Guide documentation.
Note that, if the expected version of .NET core is not installed, the Instance Manager will not restart.
 
3.2. Initialize migration document (development)
 
A specific migration document should be created. It will detail all steps required to migrate:
• From source version (HOPEX V5.0 CPX)
• To target version Hopex Aquila (Hopex V6.2 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.
 
3.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.2
Copy of production data HOPEX V5.0
Standard_SystemDb
Migration1_SystemDb
Standard_MasterData
Migration1_MasterData
Standard_HAS_5000
Migration1_HAS_5001
 
 
3.4. Create a HAS Instance (development)
 
In Instance Manager console, create a HAS Instance in Development mode in Hopex Aquila version. This is necessary to tune the customization module.
 
It is recommended to reuse the HAS Database created previously (ex: Migration_HAS_5000). For this, enter this name as Cluster name when creating the HAS Instance. Otherwise, a new HAS Database will be created and certain settings of the source version (in particular, user settings) will not be restored.
 
After this step:
• a Hopex Environment is configured (mapped to database restored previously, see Restore data in SQL Server (development)
• a Hopex license is configured
 
3.5. Complete HAS instance (development)
 
As a general rule, each module deployment must be completed by environment automatic update. In the context of the migration, environment automatic update will be run later in step 3.
 
3.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.
 
3.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.
 
Due to security changes (macro calling CreateObject), code needs to be updated for Hopex Aquila.
See also release note for Hopex Aquila, reference #56811.
 
3.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):
1. Search the module, ex: IT-Pedia (itpm.itpedia).
2. Select the public version of the module compatible with Hopex Aquila V6.2:
• Use version 17.1.X if it exists.
 
Note that each module deployment must be completed by environment automatic update.
 
 
Specific modules need to be updated for .NET 8.0 if used:
• IT-Pedia (itpm.itpedia): version 17.1.0+6835 or higher
• ServiceNow Integration (servicenow.integrations.hopex): version 2.0.0+54 or higher
• HOPEX GraphQL IDE (graphql.ide): version 8.0.0+15 or higher
• Enterprise Portal (website.static.navigator): version 16.1.0+5 or higher
• Static Website Macros (website.static.macros): version 16.1.0+5 or higher
• HOPEX Cyber Resilience (hopex.cyber-resilience): version 17.1.0+6805 or higher
• HOPEX Data Discovery Standalone (tool.data.discovery): version 17.1.0+6829 or higher
• HOPEX Data Discovery (data.discovery): version 17.1.0+6829 or higher
• AI-Driven APM (tool.itpm.apmauto): version 17.1.0+6827 or higher
• HOPEX Simulation Engine (simulation.engine): version 17.1.1+6827 or higher
 
If you use module Archimate 3.1, it is strongly recommended to install version 17.1.x (17.1.0+6820 or higher) or to benefit from the new features.
 
3.5.4. Customization of module hopex360
 
From HOPEX Aquila V6.1, a new version 17.1.x of module hopex360 (17.1.0+6838 or higher) is available.
• New look and feel (compliant with Aquila visual identity)
• Improve accessibility (web accessibility)
• Updated content (compliant with Aquila methodology changes)
 
The previous version can also be used (version 17.0.0+6662)
 
Good practices when customizing a web site from hopex360 template consists in:
• Duplicating standard web site template and its components
• Customizing the duplicated web site template
When this is done, your customization is independent from the standard web site template and its components.
 
This means that:
• It will not be impacted by a change in standard module hopex360
• It will not benefit from fixed and improvement of standard module hopex360
 
3.5.5. Update configuration (development)
 
When the HAS instance was created, various settings (megasitesettings) have been initialized.
 
Situation
Impact
Recommendations
An existing HAS Database has been re-used (recommended)
Settings of source installation have been restored
Check that settings of source installation are valid for this HAS Instance (Development)
 
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
 
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.