Skip to content

Cloud Pak for Business AutomationπŸ”—

Contains CP4BA version 25.0.0.
Contains IPM version 2.0.2. Contains RPA version 30.0.0.

Disclaimer βœ‹πŸ”—

This is not an official IBM documentation.
Absolutely no warranties, no support, no responsibility for anything.
Use it on your own risk and always follow the official IBM documentations.
It is always your responsibility to make sure you are license compliant when using this repository to install IBM Cloud Pak for Business Automation.

Please do not hesitate to create an issue here if needed. Your feedback is appreciated.

Not for production use (neither dev nor test or prod environments). Suitable for Demo and PoC environments - but with Production deployment.

!Important - Keep in mind that this deployment contains capabilities (the ones which are not bundled with CP4BA) which are not eligible to run on Worker Nodes covered by CP4BA OCP Restricted licenses. More info on https://www.ibm.com/docs/en/cloud-paks/1.0?topic=clusters-restricted-openshift-entitlement.

Documentation base πŸ“πŸ”—

Deploying CP4BA is based on official documentation which is located at https://www.ibm.com/docs/en/cloud-paks/cp-biz-automation.

Deployment of other parts is also based on respective official documentations.

Benefits πŸš€πŸ”—

  • Automatic deployment of the whole platform where you don't need to take care about almost any prerequisites
  • OCP Ingress certificate is used for Routes so there is only one certificate you need to trust in you local machine to trust all URLs of the whole platform
  • Trusted certificate in browser also enable you to save passwords
  • Wherever possible a common admin user cpadmin with adjustable password is used, so you don't need to remember multiple credentials when you want to access the platform (convenience also comes with responsibility - so you don't want to expose your platform to whole world)
  • The whole platform is running on containers, so you don't need to manually prepare anything on traditional VMs and take care of them including required prerequisites
  • Many otherwise manual post-deployment steps have been automated
  • Pre integrated and automatically connected extras are deployed in the platform for easier access/management/troubleshooting
  • You have a working Production deployment which you can use as a reference for further custom deployments

General information πŸ“’πŸ”—

What is not included:

  • ICCs - not covered.
  • FNCM External share - Currently not supported with ZEN & IAM as per limitation on FNCM limitations
  • Asset Repository - it is more part of CP4I.
  • Workflow Server and Workstream Services - this is a dev deployment. BAW Authoring and (BAW + IAWS) are mutually exclusive in single project.
  • ADP Runtime deployment - this is a dev deployment.

You can review the code here and here to directly view how certain components are enabled based on parameter settings.

What is in the package πŸ“¦πŸ”—

Only fully configured CP4BA, RPA and IPM including all Extras and Prerequisites is validated. As validation activities have NOT been executed using partial components, please report any issues you may encounter.

More details about each section from the picture follows below it.

images/cp4ba-installation.png

Extras sectionπŸ”—

Contains extra software which makes working with the platform even easier.

  • phpLDAPadmin - Web UI for OpenLDAP directory making it easier to admin and troubleshoot the LDAP.
  • Installed if enabled in configuration (default).
  • Gitea - Contains Git server with web UI and is used for ADS and ADP for project sharing and publishing. Organizations for ADS and APD are automatically created. Gitea is connected to OpenLDAP for authentication and authorization.
  • Installed if ADS or Document Processing is enabled.
  • Nexus - Repository manager which contains pushed ADS java libraries needed for custom development and also for publishing custom ADS jars. Nexus is connected to OpenLDAP for authentication and authorization.
  • Installed if ADS is enabled.
  • Roundcube - Web UI for included Mail server to be able to browse incoming emails.
  • Installed if enabled in configuration (default) and if Mail server (below) is installed.
  • Cerebro - Web UI elastic search browser automatically connected to ES instance deployed with CP4BA.
  • Installed if enabled in configuration (default) and if BAI or BAW is enabled.
  • AKHQ - Web UI kafka browser automatically connected to Kafka instance deployed with CP4BA.
  • Installed if enabled in configuration (default) and if BAI or BAW with Kafka feature is enabled.
  • OpenSearch Dashboards - Web UI OpenSearch dashboard tool automatically connected to OpenSearch instance deployed with CP4BA.
  • Installed if enabled in configuration (default) and if BAI or BAW is enabled.
  • Mail server - For various mail integrations e.g. from BAN, BAW and RPA.
  • Installed if CP4BA or RPA is enabled.
  • CloudBeaver - Web UI for Postgresql and MSSQL databases making it easier to admin and troubleshoot the DBs.
  • Installed if enabled in configuration (default) and if PostgreSQL or MSSQL (from Pre-requisites) is installed.

CP4BA (Cloud Pak for Business Automation) sectionπŸ”—

CP4BA capabilitiesπŸ”—

CP4BA capabilities are in purple color.

More info for CP4BA capabilities is available in official docs at https://www.ibm.com/docs/en/cloud-paks/cp-biz-automation/latest.

More specifically in overview of patterns at https://www.ibm.com/docs/en/cloud-paks/cp-biz-automation/latest?topic=deployment-capability-patterns-production-deployments.

Pink color is used for CPFS dedicated capabilities.

More info for CPFS dedicated capabilities is available in official docs at https://www.ibm.com/docs/en/cloud-paks/foundational-services/latest.

Magenta color is used for additional capabilities.

More info for Process Mining is available in official docs at https://www.ibm.com/docs/en/process-mining/latest.

More info for RPA is available in official docs at https://www.ibm.com/docs/en/rpa/latest.

Assets are currently not deployed.

CPFS (Cloud Pak Foundational Services) sectionπŸ”—

Contains services which are reused by Cloud Paks.

More info available in official docs at https://www.ibm.com/docs/en/cpfs.

  • License service - Tracks license usage.
  • Certificate Manager - Provides certificate handling.

Pre-requisites sectionπŸ”—

Contains prerequisites for the whole platform.

  • PostgreSQL - Database storage for the majority of capabilities.
  • Installed if CP4BA or IPM is enabled.
  • OpenLDAP - Directory solution for users and groups definition.
  • Always installed.
  • MSSQL server - Database storage for RPA server.
  • nstalled if RPA is enbled.

Environments used for installation πŸ’»πŸ”—

With proper sizing of the cluster and provided RWX File and RWO Block Storage Class, CP4BA deployed with Deployer should be working on any OpenShift 4.16 with Worker Nodes which in total have free 96 CPU, 384GB Memory for requests.

Automated post-deployment tasks βœ…πŸ”—

For your convenience the following post-deployment setup tasks have been automated:

Usage & operations πŸ“‡πŸ”—

Endpoints, access info and other useful information is available in Project cloud-pak-deployer in ConfigMap cp4ba-usage in usage.md file after installation. It is best to copy the contents and open it in nice MarkDown editor like VSCode. The ConfigMap name can begin with a different name if you customized main CP4BA project name.

Optional post deployment steps πŸ“‹πŸ”—

CP4BA
Review and perform post deploy manual steps for CP4BA as specified in Project cloud-pak-deployer in ConfigMap cp4ba-postdeploy in postdeploy.md file. It is best to copy the contents and open it in nice MarkDown editor like VSCode. The ConfigMap name can begin with a different name if you customized main CP4BA project name.

RPA
Review and perform post deploy manual steps for RPA as specified in Project cloud-pak-deployer in ConfigMap cp4ba-rpa-postdeploy in postdeploy.md file. It is best to copy the contents and open it in nice MarkDown editor like VSCode. The ConfigMap name can begin with a different name if you customized main CP4BA project name.

Process Mining
Review and perform post deploy manual steps for IPM as specified in Project cloud-pak-deployer in ConfigMap cp4ba-pm-postdeploy in postdeploy.md file. It is best to copy the contents and open it in nice MarkDown editor like VSCode. The ConfigMap name can begin with a different name if you customized main CP4BA project name.

Licensing πŸ“‘πŸ”—

Referrence to licenses of used tools apart from those from IBM