SPM architecture on OpenShift
SPM OpenShift cluster - Reference Architecture
The reference architecture in this section represents how Merative Social Program Management (SPM) should be deployed into OpenShift. This architecture allows SPM to leverage the benefits of flexibility, elasticity, efficiency and the strategic value offered by cloud native architecture.
Figure 1: SPM on OpenShift - deployment architecture
- SPM deployed in WebSphere Liberty, lightweight JavaEE application server, designed for cloud native platforms.
- EAR files deployed in their own Liberty instance.
- Liberty instances packaged in Docker images, which are run as Docker containers.
- Batch packaged as Docker images, which are run as containers.
- XML Server packaged as Docker images, which are run as containers.
- SPM only supports SPM Docker containers when deployed into pods.
- Deployment of the database is supported on bare metal and VMs when the application tier is running in Kubernetes.
- JMS messaging engine deployed separately using IBM MQ, managed through Helm Charts.
- IBM MQ certified containers (MQ CI) from the IBM Cloud Container Registry which are run as stateful pods.
- SPM supports IBM MQ Long Term Support (LTS) and Continuous Delivery (CD) releases with the following limitations:
- MQ LTS is only supported on bare metal and VMs
- MQ CD is only supported in OpenShift containers
- Keep the database and queue manager tiers close to the application tier to reduce latency.