PLATEFORME - Installation & Deployment (EN) > How to Migrate to HOPEX Aquila (V6.0) > FAQs
6. FAQs
 
Why a customization module (has.custom)?
Build customization module (HOPEX V4.0)
What is the list of system modules
Error Inconsistent format for MetaAttribute
Cannot find the option to enable data modification
Warning 'Run the menu 'Perform SQL conversion on the repository' to perform the upgrade
Warning 'Your environment requires an update for compatibility with your version of HOPEX…'
Warning 'Writing access diagram is not compiled. The diagram should be recompiled …'
How to set a HAS Instance as current in registry?
 
6.1.1. Why a customization module (has.custom)?
 
Various customization can be made, for example
• .MGS files (shapes)
• .JAR files (java code)
• .JSON (GraphQL Schema)
 
Resources and code persist in specific folders up to HOPEX V4.0:
• <installation path>\Customizations\javalib
• <customization folder path>\javalib
• <installation path>\Customizations\dotnet
• <customization folder path>\dotnet
• <installation path>\Customizations\mega_usr
• <customization folder path>\mega_usr
• <installation path>\DotNet\hopex.graphql\1.0.0.0\CONFIG\V3\Custom
 
In HOPEX Aquila, external files (customizations) and well as new system update should be package in a customization module (has.custom). This enables to capture and deploy customization easily.
 
6.1.2. Build customization module (HOPEX V4.0)
 
A HAS instance in 'development' mode is required.
Time to build customization module can vary according to number of customizations.
 
Main steps
Comment
Initialize customization module
In HAS instance (development), create development context mainly folder structure for customization module
Gather customizations
Capture systemdb and/or data updates.
Move external files or components to appropriate folders
Build package of customization module
Generate a .haspkg file with a script
Test customization module
Test installation in HAS instance (staging/test)
If necessary, do a loop to tune the customization module in HAS instance (development)
 
See online documentation for HOPEX Aquila V6.0: MODULES > Customization Lifecycle Management
 
6.1.3. What is the list of system modules
 
When a HAS instance is created, keys modules (called system modules, grouped in a bundle) are installed automatically. Other modules are called additional modules.
 
List of system modules.
 
Module code
Module
has.console
HAS Console
has.uas
HAS Identity Provider
hopex.assessment
HOPEX Questionnaire Builder
Hopex.core
HOPEX Core Back-End Aquila
hopex.dtpx
HOPEX Aquila
hopex.graphql
HOPEX GraphQL
hopex.redis
HOPEX Redis
hopex.rest.api
HOPEX REST API
hopex.rest.api
HOPEX Server Supervisor Module
hopex.specific.assets
HOPEX Aquila specific assets
 
6.1.4. Error Inconsistent format for MetaAttribute
 
During environment automatic upgrade of when accessing data, an error can be displayed of logged such as
Inconsistent format for MetaAttribute "EA4430554424043A" (304630847021378116). Physical Format (X). Meta Format (L).
This reveals a data inconsistency that needs to be addressed.
See KB 00009355 in MEGA Community for more details.
 
6.1.5. Cannot find the option to enable data modification
 
The option was moved and renamed to 'Authorize HOPEX data modification'
Note that it is not recommended to use this option.
If you need to configure it, go in options, display Extended level, browse group 'Installation > Customization'.
 
6.1.6. Warning 'Run the menu 'Perform SQL conversion on the repository' to perform the upgrade
 
This means that the format of tables in SQL Server must be converted.
You need to run a menu Perform SQL conversion on the repository from the Administration Console (Administration.exe).
 
6.1.7. Warning 'Your environment requires an update for compatibility with your version of HOPEX…'
 
This warning report that the system database is not up to date. This occurs if the programs have been updated and the environment has not/not yet been updated.
 
You can click 'No' and trigger the upgrade of the environment later (menu Environment Automatic Update)
 
6.1.8. Warning 'Writing access diagram is not compiled. The diagram should be recompiled …'
 
Certain actions can leave the writing access diagram (ex-User diagram/Authorization diagram) is in a state not compiled.
 
To compile the writing access diagram, see online documentation for HOPEX V6.0: PLATFORM - Administration > Administrator Guide > Data Writing Access > Managing Users from the Writing Access Diagram > Compiling the Writing Access Diagram
 
6.1.9. How to set a HAS Instance as current in registry?
 
If several HAS instances exist on a machine, only one can run components using Administration API script at a given moment.
Before each execution of components using Administration API script, it is required to reference Mega.Application.
This is done using a powershell script (HOPEX-regserver.ps1) installed at the root folder of the HAS Instance.