The starter pattern is new in 21.0.3, replacing the demo pattern of previous releases. It is intended for evaluation purposes. Compared with enterprise deployment, starter pattern is easier to deploy. It comes with utility images such as openldap, busybox, phpldapadmin, alpine, and sets default credentials to make it easy to use.
Workflow-workstreams demo pattern first appeared in 20.0.3. After deploying this pattern, you can author workflow projects (process applications and case solutions) in Business Automation Studio and run them in the IBM Cloud Pak for Automation environment.
As an important capability for demonstration purpose, it included many components. If you deploy workflow-workstreams demo pattern, you will get:
- Business Automation Navigator (BAN)
- Resouce Registry(RR)
- User Management Services (UMS)
- Business Automation Studio (BAS)
- Workflow Authoring(Java Message Service included)
- Process Federation Server (PFS)
- Elasticsearch
- Content Platform Engine (CPE)
- Content Management Interoperability Services (CMIS)
- Application Engine (AE)
- Business Automation Insights (BAI) (optional component)
- Mechine Learning Server (BAML)(optional component)
The disadvantage of installing so many components is that it is easy to make mistakes, and it is inconvenient to find the root cause of the errors because these components depend on each other. In addition, deploying it will consume a lot of resources, but some functions may not be used by people who only use workflow function.
In 21.0.3, Workflow-workstreams starter pattern cuts its deployment footprint in half. It merges Business Automation Studio with Workflow Authoring in one container, only the process capability is now enabled by default. Case, Content Integration, and Workstream Services are optional components. Application Designer, Application Engine are no longer available in this pattern. PFS, BAI and BAML functions will be provided in 21.0.3 fix pack later.
If you don't choose any optional component, you will get:
- Resouce Registry(RR)
- Business Automation Studio (BAS)
If you choose Content Integration or Workstream as optional component, you will get:
- Resouce Registry(RR
- Business Automation Studio (BAS)
- Content Platform Engine (CPE)
- Content Management Interoperability Services (CMIS)
If you choose Case as optional component, you will get:
- Resouce Registry(RR)
- Business Automation Studio (BAS)
- Content Platform Engine (CPE)
- Content Management Interoperability Services (CMIS)
- Business Automation Navigator (BAN)
In this way, the footprint is reduced to less than half of the original. For users, installation is easier and finding the cause of errors is faster.
For further details, please read