IBM Cloud Docs
Learning about IBM OpenPages as a Service architecture and workload isolation

Learning about IBM OpenPages as a Service architecture and workload isolation

IBM OpenPages as a Service is a multi-tenant service with dedicated resources per tenant. To learn more, review the following architecture diagram to see how IBM OpenPages can meet the requirements of the sensitive workloads that you want to run in the cloud.

IBM OpenPages as a Service architecture

The following image shows the main components of IBM OpenPages as a Service.

Tenant isolation architecture
Main components of OpenPages as a Service - AWS

Tenant isolation architecture
Main components of OpenPages as a Service - IBM Cloud

  • A service instance of IBM OpenPages uses a dedicated RDBMS service instance and a dedicated document storage folder at the data layer.

  • Application pods on the Red Hat® OpenShift® cluster are allocated in a dedicated fashion for IBM OpenPages service instances. Tenant network is isolated by the Red Hat® OpenShift® namespace with network policy.

  • The IBM OpenPages service assigns a dedicated URL for each service instance for accessing the application by using the web UI, API, or CLI. The network edge nodes and load balancers are shared across tenants and the requests are dispatched to the application per the service instance URL.

IBM OpenPages as a Service workload isolation

The IBM OpenPages service assigns a dedicated URL, dedicated application pods, a dedicated RDMS service, and dedicated S3 document storage folder for each instance. The tenant workload is isolated all the way from the network layer, to the application layer, to the data layer.