Deployment Instructions
The Document Storage Microservice can be built and packaged as a binary ZIP file, and then deployed in one of the following containers:
- Docker
- AWS – currently not supported
- Azure – currently not supported
- K8 (On-Premise/Helm)
- AWS (EKS)
- Azure (AKS)
JDK 11 is required for all deployments.
Sling - Document Microservice also supports the connection to Apache Sling, an open-source DMS option. However, the clients need to purchase the Apache Sling product (which Temenos doesn't offer) to manage the deployment and support the Apache Sling system to connect to the Document Microservice.
ClamAV - Due to the GPL license restriction, the ClamAV provides the virus scanning capability, which is not a part of the Infinity software distribution and is disabled by default. Please refer to the Antivirus module on how to enable it.
Formpipe- Customers can contact FormPipe(efs) vendor directly for Autoform and Lasernet credentials and server details.
The deployment package contains the following components for various containers:
| Component | Docker | AWS (EKS) | Azure (AKS) | K8 |
|---|---|---|---|---|
|
Microservice Java runtime |
Docker |
AWS (EKS) | Azure (AKS) | K8 |
|
SQL DB |
MySQL, MMSQL,Oracle, Postgresql. |
MySQL, MMSQL,Oracle, Postgresql. | MySQL, MMSQL,Oracle, Postgresql. | MySQL, MMSQL,Oracle, Postgresql. |
The deployment package contains the following components and responsibilities:
For a detailed deployment installation, refer to specific container instructions.
In this topic