Installation and Deployment > How to Install Hotfix > Foreword
1. Foreword
 
HAS instance
HAS module
HAS bundle
Hotfix in HAS deployment
 
1.1. HAS instance
 
In HOPEX Application Server deployment, an installation is named instance.
Each HAS Instance is mapped to:
• A Port: 5000, 5001, 5002…
• A mode: Development, Training, Staging (synonym: Test, QA...), Production.
• A version of HOPEX
• One HOPEX environment. Using multiple environments is not supported
 
HAS Instances are managed by a program named Instance Manager.
 
1.2. HAS module
 
In HOPEX Application Server deployment, each component is delivered as a module.
Each module has its version, its dependencies.
In concrete terms, a module is a .haspkg file.
 
Module
System module
Short description
HOPEX Core Back-End V5.0
Yes
Core of HOPEX platform. Most important module.
Code: hopex.core
HAS Identity Provider
Yes
Component used for authentication.
Code: has.uas
Bold BI
No
Component used to design widgets.
Code: dashboard.boldbi
HOPEX360
No
Web site Template.
Code: hopex360
…
 
 
 
1.3. HAS bundle
 
System modules are packaged in a bundle named 'HOPEX'.
Non-system modules are available as independent modules.
In concrete terms, a bundle is a folder .haspackages containing a set of .haspkg files.
 
 
A bundle packages a specific combination of system-modules in different versions compatible with each other. Example:
 
Bundle
Module
Version
Bundle 5.0.710 (HOPEX V5.0 - 64 bits)
HAS Console
15.0.0+157
HAS Identity Provider
15.0.0+157
HOPEX Questionnaire Builder
15.0.0+5947
HOPEX Core Back-End V5.0
15.0.0+5947
HOPEX Web Front-End V5.0
15.0.0+5947
HOPEX GraphQL
7.87.506+5947
HOPEX Redis
1.0.2
HOPEX REST API
7.87.506+5947
 
1.4. Hotfix in HAS deployment
 
A hotfix provides a consistent set of urgent fixes (severe error fixes or security fixes), for one or several modules of an HAS Instance.
 
The hotfixes provided for HOPEX Software are cumulative.
• Each hotfix of a module is a new version of this module.
• Each hotfix of a bundle is a new version of this bundle. It will update all the modules included in this bundle.
When the hotfix is installed, each elementary component of the related module will be replaced. This means that hotfix size can be significant.
 
Modules and Bundles can be downloaded and installed via administration consoles provided access to HOPEX Store is available online (https://store.mega.com/).
Bundles can be downloaded first as offline package to be installed later offline.
 
The action depends on the situation.
 
Example of hotfix
Modules impacted
Action
Situation 1: one or several system modules is/are impacted
hopex.core (system)
Update the whole bundle using the bundle hotfix
Situation 2: one or several non-system modules is/are impacted
dashboard.boldbi (non-system)
Update each module impacted, ex: dashboard.boldbi
Situation 3: both system modules and non-system modules are impacted
hopex.core (system)
dashboard.boldbi (non-system)
Update the whole bundle
+ update module dashboard.boldbi
 
Certain modules (ex: 'hopex.core') require an update of the data (system repository).
 
Before proceeding, make sure that, for all the HOPEX environments to upgrade:
• Data is backed up (physical backup).
• The password of the login System is known.
This is very important since it will be requested to login with the login System.

 
There are two typical deployment contexts for HOPEX Application Server (HOPEX programs)
• HOPEX programs are deployed on a single server. There is no concern to replicate updated programs.
• HOPEX programs are deployed on multiple servers (cluster deployment). There is a concern to replicate updated programs to each server (node) of the cluster.
 
So far, deployment of bundles (hotfix update, CP updates) in cluster is not automatic.
It is required to download and install bundle on each server of the cluster.