Capabilities for production deployments

Foundation (pattern name foundation)

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 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 a number of components, some of which are always installed, others are installed if they are selected or needed, and IBM Process Mining and IBM Robotic Process Automation are installed only if you install them independently. For more information, see IBM Cloud platform foundation and IBM Automation foundation system requirements.

The components can be created with varying sizes and replicas with the deployment profile size you choose for your Cloud Pak deployment. By default, they are set for a minimum configuration. For a true production environment, you need to adjust the sizes of these requirements. For example, you might need to increase the number of elastic nodes to handle the load of the log storage. For more information about these configuration values, see Configuring IBM Cloud Pak foundational services by using the CommonService custom resource.

Automation Decision Services (pattern name decisions_ads)

Automation Document Processing (pattern name document_processing)

* You do not need to select FileNet Content Manager to include components from the content pattern. The always-installed components are automatically included when you select the development environment. The optional components are included when you select them.

* You do not need to select FileNet Content Manager to include components from the content pattern. The always-installed components are automatically included when you select the runtime environment. The optional components are included when you select them.

Automation Workstream Services (pattern name workstreams)

* You do not need to select FileNet Content Manager to include components from the content pattern. These components are automatically included with the workstreams pattern.

Business Automation Application (pattern name application)

* You do not need to select FileNet Content Manager to include components from the content pattern. These components are automatically included when you select Application Engine data persistence.

Business Automation Workflow (pattern name workflow)

You can choose Business Automation Workflow Authoring or Business Automation Workflow Runtime.

Workflow Authoring and Workflow Runtime must be in different instances (different custom resource and namespaces).

Business Automation Workflow Authoring

Application Designer is not installed by default with Business Automation Workflow Authoring. To use Application Designer, install the Business Automation Application pattern with the optional Application Designer component. If you need an external Workplace environment, you can select the Business Automation Application pattern to install Application Engine, which automatically includes an external Workplace.

Table 8. Business Automation Workflow Authoring components

Components	Capability or pattern	Installed
Business Automation Insights (BAI)	Foundation	Optional. Machine Learning Server is available only if Business Automation Insights is installed.
Process Federation Server (PFS)	Business Automation Workflow Authoring	Always
Content Platform Engine	FileNet Content Manager *	Always
Content Management Interoperability Services	FileNet Content Manager *	Always
GraphQL API	FileNet Content Manager *	Always
Workflow Authoring	Business Automation Workflow Authoring	Always
Business Automation Navigator (BAN)	Foundation	Always
Business Automation Studio (BAS) (JMS included)	Foundation	Always
Resource Registry (RR)	Foundation	Always
Default foundational services, which include IBM Cloud Pak Platform UI (or Zen UI) Identity and Access Management (IAM) Common Web UI Service License Service Certificate management Business Teams Service (BTS)	Foundation	Always

* You do not need to select FileNet Content Manager to include components from the content pattern. These components are automatically included with Workflow Authoring.

Business Automation Workflow Runtime

Table 9. Business Automation Workflow Runtime components

Components	Capability or pattern	Installed
Business Automation Insights (BAI)	Foundation	Optional. Machine Learning Server is available only if Business Automation Insights is installed.
Workflow server (JMS included)	Business Automation Workflow Runtime	Always
Process Federation Server (PFS)	Business Automation Workflow Runtime	Always
Content Platform Engine	FileNet Content Manager	Always
Content Management Interoperability Services	FileNet Content Manager	Always
GraphQL API	FileNet Content Manager	Always
Application Engine (AE) (data persistence required)	Foundation	Always
Business Automation Navigator (BAN)	Foundation	Always
Resource Registry (RR)	Foundation	Always
Default foundational services, which include IBM Cloud Pak Platform UI (or Zen UI) Identity and Access Management (IAM) Common Web UI Service License Service Certificate management Business Teams Service (BTS)	Foundation	Always

* You do not need to select FileNet Content Manager to include components from the content pattern. These components are automatically included with Workflow Runtime.

FileNet Content Manager (pattern name content)

Operational Decision Manager (pattern name decisions)

Workflow Process Service Authoring (pattern name workflow-process-service)