Capabilities for Demo deployments

You can install one or more capabilities for demonstration purposes. Depending on the selected capabilities, or patterns, the needed components of the foundation pattern and IBM Automation foundation are also installed.

Remember:

The demo deployment mode is intended for evaluation purposes. It uses some utility images such as openldap, busybox, phpldapadmin, and alpine to deploy a complete CP4BACluster instance with some default services. These images might have vulnerabilities and are not suitable for production. The demo mode also sets default credentials to make it easy to deploy, and for this reason you must not keep an Demo deployment for development or for production.

Deployments for development and for production must use an Enterprise deployment.

Depending on the selected capabilities, the needed components of the foundation pattern are installed. The final custom resource file combines capabilities and components from one or more capability patterns.

Foundation (pattern name foundation), which includes
  • Business Automation Navigator (BAN)
  • Resource Registry (RR)
  • User Management Services (UMS) if needed by combined capabilities
  • Business Automation Studio (BAS) if needed by combined capabilities
  • Business Automation Insights (BAI) if needed by combined capabilities
  • Application Engine (AE) if needed by combined capabilities
Foundation pattern visual
Note: BAN and RR are always installed. BAS, AE, BAI, and UMS are installed in the environment if they are needed by other selected capabilities. For example, BAI needs UMS installed.

The "demo" deployment includes Db2® and OpenLDAP. The databases are for internal purposes only and cannot be accessed.

The foundation pattern cannot be installed by itself running the deployment script or in the Form View in the OCP console. The deployment of any Cloud Pak for Business Automation capability includes the foundation pattern. A deployment of the Cloud Pak custom resource also includes an instance of IBM Automation foundation (IAf) and the foundational services. Depending on the capabilities that you select, the dependency operators create the service instances. Foundational services connect all IBM Cloud Paks with Operand Deployment Lifecycle Manager (ODLM) and use a specific namespace (ibm-common-services) to manage the service instances. IBM Automation foundation includes the following components, some of which are always installed, others are installed if the options are dependencies, and IBM Process Mining and IBM Robotic Process Automation are installed only if you install them independently:

  • IBM Cloud Pak Platform UI (or Zen UI)
  • MongoDB
  • IBM Process Mining (IPM)
  • IBM Robotic Process Automation (IRPA)
  • Foundational services, which include
    • Identity and Access Management (IAM)
    • Common Web UI Service
    • License Service
    • Certificate management
  • Event framework (AutomationBase)
IAf visual
Automation Decision Services, which includes
  • Automation Decision Services (ADS)
    • Decision Designer
    • Decision Runtime
  • From the Foundation pattern
    • User Management Service (UMS)
    • Business Automation Insights (BAI) as an optional component
Automation Document Processing, which includes
  • Document Processing Designer interface and REST API
  • Document Processing Designer Repository API
  • Document Processing Project Deployment Service
  • Viewer service
  • Common Git Gateway Service
  • Content Analyzer
  • From the Content pattern:
    • Content Platform Engine
    • Content Services GraphQL API
    • External Share as an optional component
    • Content Search Services as an optional component
    • Content Management Interoperability Services as an optional component
    • Task Manager as an optional component
  • From the Foundation pattern
    • Business Automation Navigator, SSO
    • Application Engine
    • Business Automation Studio
Business Automation Application, which includes
  • Application Designer
  • Application Engine playback server
  • From the Foundation pattern
    • User Management Service (UMS)
Business Automation Workflow and Automation Workstream Services, which includes
  • Workflow Authoring (JMS included), which also includes Workstream Services server
  • Process Federation Server (PFS)
  • Elasticsearch
  • From the Content pattern
    • Content Platform Engine (CPE)
    • Content Management Interoperability Services (CMIS)
  • From the Foundation pattern
    • Application Engine (no data persistence)
    • Business Automation Studio (BAS)
    • User Management Service (UMS)
    • Business Automation Insights (BAI) as an optional component
FileNet® Content Manager, which includes
  • Content Platform Engine (CPE)
  • Content Services GraphQL
  • Content Search Services (CSS) as an optional component
  • Content Management Interoperability Services (CMIS) as an optional component
  • Content Collector for SAP (ICC4SAP) as an optional component
  • Enterprise Records (IER) as an optional component
  • Task Manager (TM) as an optional component
  • From the Foundation pattern
    • User Management Service (UMS) as an optional component
    • Business Automation Insights (BAI) as an optional component
Note: Enterprise Records (IER) does not integrate with the User Management Service (UMS).
Operational Decision Manager, which includes
  • Operational Decision Manager (ODM)
    • Decision Center
    • Decision Runner
    • Rule Execution Server
  • From the Foundation pattern
    • User Management Service (UMS) as an optional component
    • Business Automation Insights (BAI) as an optional component