Installing a Demo deployment
Containers:
A deployment that is intended for demonstration purposes is much quicker to install than an Enterprise deployment. Unix-based shell scripts are provided to help a cluster administrator set up the cluster and for a non-administrator user to run the installation. The Business Automation Workflow capabilities to install are packaged into several patterns to simplify integration and share resources.
A deployment that is intended for demonstration purposes is much quicker to install than an Enterprise deployment. Unix-based shell scripts are provided to help a cluster administrator set up the cluster and for a non-administrator user to run the installation. The Business Automation Workflow capabilities to install are packaged into several patterns to simplify integration and share resources.
About this task
For more information about Demo deployments and how to plan for them, see "Demo installation" in Planning for IBM Business Automation Workflow on containers in 21.0.2. Ignore any information about Workstream Services, Business Automation Insights, and Machine Learning Server (including Intelligent Task Prioritization and Workforce Insights). These are not included in stand-alone IBM Business Automation Workflow.
Remember: A Demo deployment is intended for evaluation purposes. It uses utility images
such as openldap, busybox, phpldapadmin, and alpine to deploy a complete CP4BACluster instance with
default services. These images 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 a Demo deployment for
development or for production.
Deployments for development and for production must use an Enterprise deployment.
You'll install the "IBM Business Automation Workflow" capability and pattern. For the list of components that are installed, see Containers in V21.0.2: Installing, configuring, and migrating.