PLATFORM - Installation and Deployment > How to Upgrade a HOPEX Bundle > Foreword
1. Foreword
 
HAS instance
HAS module
HAS bundle
Service Pack in HAS deployment
1.1. HAS instance
In HOPEX Application Server (HAS) deployment, an installation is named instance.
Each HAS Instance is mapped to:
• a Port: 5000, 5001, 5002…
• a version of HOPEX
• one mode: Development, Training, Staging (synonym: Test, QA...), Production.
• one HOPEX environment. Using multiple environments is not supported
HAS Instances are managed by a program named Instance Manager.
1.2. HAS module
In HAS deployment, each component is delivered as a module.
Each module has its version and dependencies.
A module is a .haspkg file.
Module
System module
Short description
HOPEX Core Back-End Aquila
Yes
Core of HOPEX platform
Code: hopex.core
HAS Identity Provider
Yes
Component used for authentication
Code: has.uas
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.
A bundle is a .haspackages folder containing a set of .haspkg files.
A bundle packages a combination of modules in different versions compatible with each other.
Example:
Bundle
Module
Version
Bundle 6.0.1+301 (HOPEX Aquila)
HAS Console
16.0.1+181
HAS Identity Provider
16.0.1+181
HOPEX Questionnaire Builder
17.0.1+6659
HOPEX Core Back-End Aquila
17.0.1+6659
HOPEX Environment Installation Package Aquila
17.0.0+6583
HOPEX Aquila
17.0.1+6659
HOPEX GraphQL
7.87.507+6551
HOPEX Redis
6.2.6+41.0.2
HOPEX REST API
7.87.507+6551
HOPEX Server Supervisor Module
20.0.0+5
HOPEX Aquila specific assets
6.0.7
1.4. Service Pack in HAS deployment
A Service Pack (SP) provides a consistent set of fixes within a major version of HOPEX. GUI should be stable. For each version, several SPs are scheduled and heavily tested by QA department.
An SP enables to update the system module of an HAS instance. It is installed via a bundle.
There are not SP for non-system module.
 
The SPs provided for the bundle are cumulative.
E.g.: HOPEX Aquila 6.0 SP2 includes fixes provided for HOPEX Aquila 6.0 SP1.
 
Each SP of a bundle is a new version of this bundle. It updates all the system modules included in this bundle. Each component of the related module is replaced.
 
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 first downloaded as offline package and installed offline afterward.
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, SP updates) in cluster is not automatic.
It is required to download and install bundle on each server of the cluster.