Skip to content

CP4BA Demos Environment based on Apollo Business Automation/Cloud Pak Deployer for CP4BA 24.0.0

Important

  • As this approach relies on reserving an environment from IBM TechZone, this document is only applicable to IBM Business Partners that have the ability to request environments from TechZone and IBMers.
  • Showcasing RPA in action as part of the Client Onboarding scenario requires a few manual configuration steps as described below.

If you have your own Cloud Pak for Business Automation (CP4BA) 24.0.0 environment, please refer to this document for other options.

Quick Start

  1. Reserve a CP4BA Demos environment as described in the section below
  2. Read the Lab Considerations section for specifics of using the labs in the context of this CP4BA Demos environment
  3. Follow the link to the documentation of the lab you want to perform in the Lab Instructions section

Overview

This Jam-in-a-Box environment is provided to you as a cooperation between the owners of the Apollo Business Automation approach and the IBM Business Automation and Digital Labor Tiger (aka SWAT) team.

The major benefits of using this environment are:

  • Environment can be used for a single-user use case and for running mini-Tech Jams with approximately 10 participants (feedback welcome in case you used it with more users)
  • Client Onboarding scenario and lab artifacts are pre-deployed for you
  • 20 business users have been created that can be given to participants of a mini-Tech Jam

Caution

It can take 5-7 hours until the environment is available.

Reserve the CP4BA Demos Environment

Follow the journey Apollo Business Automation - CP4BA Demos to reserve your environment on IBM TechZone. It consists of three steps:

  1. Requesting the environment 2. CP4BA Demos (24.0.0 / 1.15.0) or CP4BA Demos (24.0.0 / 1.15.0) bizauto from the Archive in step 1 and waiting till the environment is Ready and fully deployed. This will normally take approximately 5-7 hours. The difference between the two tiles is that for one tile the passwords for usr001-usr020 are randomly generated, whereas the password for the other tile is set to a pre-defined value as stated on the tile itself.
  2. Validating the successful deployment of the Cloud Pak for Business Automation as described in step 2.
  3. Validating the successful deployment of the Client Onboarding scenario assets as described in step 3.

(Optional) Reserve an RPA VM and Update the Jam-in-a-Box Single User Environment

  1. Reserve your RPA environment on IBM TechZone from the IBM Business Automation - Traditional and On-Premises collection by clicking on one of the *IBM Business Automation - Traditional and On-premises. V4.3x tiles
  2. Fill in the reservation details and wait till the environment is Ready. This will normally take between 2-3 hours
  3. Once your environment is Ready, click on the reservation in TechZone and copy the URL shown for RPA Asynch Server API at the top under Published services
  4. In your Apollo Business Automation - CP4BA Demos environment you need to launch the Cloud Pak Accelerator homepage in your browser. There are two different ways to do so:

    1. Construct the URL based on the following naming pattern, replacing the your-environment in the link https://cp4accelerator.apps.your-environment.ocp.techzone.ibm.com/demos with the value (e.g. console-openshift-console.apps.66e433006794d822e0236c61.ocp.techzone.ibm.com/) from the Desktop url from the reservation
    2. Open the OpenShift Console, navigate to Networking --> Routes and use the link under location for the cp4accelerator-route route and switch to the Deploy Demo tab
  5. Click the blue Update button for the Client Onboarding tile

  6. Put the value of the RPA Asynch Server API that you copied in step 3 into the RPA Server field
  7. Put cpadmin or any other user for which the RPA bot should be invoked into the RPA User field
  8. Finally click on the blue Update Client Onboarding button

Tip

Even after you have made the change, the value shown on the update Client Onboarding deployment page will remain to reflect the original values. That is expected, as only the runtime, not the design time values are updated while the design time values are shown.

After you have applied this configuration change the RPA bot will be invoked when you perform the Client Onboarding scenario with use cpadmin or the user you specified.

Labs Instructions & Considerations

Lab Considerations

The lab instructions are written in context of a Tech Jam event. When performing the labs as part of Jam-in-a-Box keep in mind:

Lab instructions mention... As part of this Jam-in-a-Box environment...
using the URLs found on the Tech Jam event page please login to the OpenShift console, go to Workloads -> ConfigMaps, and check the 000-client-onboarding-information ConfigMap. It should appear at the top of the list.
The ConfigMap contains all relevant URLs for this environment.
For a mini-Tech Jam share them with the participants in a suitable form.
how to receive your user credentials using a link on the Tech Jam event page please login to the OpenShift console, go to Workloads -> ConfigMaps, and check the 000-client-onboarding-information ConfigMap. It should appear at the top of the list.
The ConfigMap contains all relevant user names and password for this environment.
For a mini-Tech Jam share a dedicated user name and password with each participants in a suitable form.
to prefix your artifacts with "usrXYZ" depending on if you use the environment as a single-user environment or for running a mini-Tech Jam, you may choose to follow the instructions in this point.
object store CONTENT (Content labs) the object store to use is called BAWDOCS.

Lab Instructions

Below you find the links to the lab instructions for the labs supported in this environment:

Support

We aim to support successfully utilizing our assets as part of Jam-in-a-Box. For questions and issues around Apollo Business Automation, please reach out to its authors.

For questions and issues around the Client Onboarding labs:

Business Partners (require an invitation) and IBMers

To engage us, drop us a message at #jam-in-a-box-ba-dl.

All others

For anyone who doesn’t fall into the business partner or IBM employee category, please feel free to open a new issue on our GitHub repository. We’ll be more than happy to address your questions and concerns there.

Disclaimer

The information, tools, and artifacts describes and linked are provided AS-IS and without any warranty. Please also refer to the license that is part of this repository for details.