Enhancing business automation with integration
Technical Sales Level 3 demo

To provision your own Red Hat OpenShift cluster for the Cloud Pak for Integration, follow these steps:

1. To deploy a Red Hat OpenShift cluster, go here. Select if you prefer to make a reservation now or schedule for later.
   
   

2. If you do not have a sales opportunity, select the purpose Practice / Self-Education (1) for a 2-day reservation (which can be extended without any approvals to 6 days) and fill in the Purpose description (2).
   
   

3. Select the Preferred Geography.
   
   

4. Several additional fields will appear. Select 4.14 (1) as the OpenShift version, ODF - 2TB (2) for the storage, 16 vCPU x 64 GB - 100 GB ephemeral storage (3) as the worker node flavor, accept the terms and conditions (4) and click Submit.
   
   

5. You will receive a few emails as the provisioning process continues. You should expect the final email to be sent after an hour. The final email should look similar to the following.
   
   

Go to top

In this section, you access your OpenShift cluster and install the OpenShift command line tool.

1. Open the Reservation ID link that was included in the “Reservation Ready on IBM Technology Zone” email.
   
   

2. Copy the kubeadmin Password (1) and open the OpenShift console by clicking on Open your IBM Cloud environment (2).
   
   

3. Use kubeadmin (1) as the user, paste the Password (2) and click Login (3).
   
   

4. On the web console page, click ? (1), and select Command line tools (2).
   
   

5. Follow the links to install the OpenShift Command Line Interface (CLI) for your Operating System.
   
   

6. To configure the command line on your machine, click on the down arrow to the right of kubeadmin (1) and select Copy login command.
   </br>

7. Click on Display token.

8. Copy the Login with this token and run in the command line.
   </br>

You have successfully configured the Openshift command line on your machine.

Go to top

To copy the repository you will need to have the Git CLI on your machine. If you don’t have it, follow the installation steps described in this page, based on your operating system.

1. To download the scripts to install the demo, create a new directory, change to this newly created directory, and run the following command:

   git clone https://github.com/IBM/platinum-demo-code-cp4icp4ba.git

   
   

2. Change to the new platinum-demo-code-cp4icp4ba/cp4i/ directory:

   cd platinum-demo-code-cp4icp4ba/cp4i/

   
   

Go to top

1. To deploy the demo run:

   ./deploy.sh

   This will automatically deploy the resources into the CP4I namespace.

2. The deployment will take approximately 30-45 minutes to install. Wait for the deployment to complete. The URL and credentials will be shown once the installation is complete.

Your have installed the Cloud Pak for Integration ready to be configured.

Go to top

Connect Cloud Pak for Integration to your endpoints

Now, let’s configure our services endpoints in Cloud Pak for Integration.

1. Return to the command line and access the Platform Navigator using the provided URL. Copy and paste the Username (1) and Password (2) from the command line output, and click Sign In (3).
   
   
   

2. You will be asked to provide a new password as you are using a temporary password. Provide a new password and click Submit.
   
   

3. In the menu on the top left, open the Design folder (1) and select Integrations (2).
   
   

4. Click on the ace-designer-demo entry.
   
   

5. Click the Catalog icon to see a list of the available connectors.
   
   

6. To configure the MQ connection, search for ‘IBM MQ’ (1) and click Connect (2).
   
   

7. Enter ‘basicmq’ for the Queue manager name (1), ‘basicmq-ibm-mq’ for the Queue manager hostname (2), and ‘1414’ for the Listener port number (3).
   
   

8. Enter ‘SYSTEM.DEF.SVRCONN’ for the Channel name (1), and click Connect (2).
   
   

9. Click Continue.
   
   

10. Scroll to the top of the page, and click the + button to the right of the search bar.
    
    

11. Access the API definition for the external account service here. Download the file using File –> Save Page as.
    
    

12. Assure Import a connector file or API document (1) is selected and select Next (2).
    
    

13. Select OpenAPI (1) for the Document type, use the downloaded CustomerAccountOpenAPIJSONServer.yaml file (2), and click Next (3).
    
    

14. Click Import API.
    
    

15. Search for Customer Account (1), and click Connect (2).
    
    

16. Scroll down and click Connect.
    
    

Import flows to App Connect Designer

1. Download the following two files:
   • MQ flow to simulate the acquired bank
   • Accounts API flow that workflow will use
   

2. Import the MQExternalProvider.yaml file by clicking the Dashboard icon (1), then New (2), and then Import flow… (3).
   
   

3. Use the downloaded MQExternalProvider.yaml file (1), and click Import (2).
   
   

4. Start the imported flow by selecting Start flow (1).
   
   

5. Repeat steps 2 - 4 for the Accounts.yaml file. This time, the flow is started by switching the toggle from Stopped to Started.
   
   

Test the flow

1. Select the Test tab (1), Get /Accounts/{customerId} operation (2), and then the Try it tab (3).
   
   

2. Scroll down and enter ‘1234567890’ in the customerId field (1), and click Send (2).
   
   

3. The first test will fail due to a known timeout issue with the error shown in the screenshot below. Click Send a second time to receive the correct response.
   
   

4. You will see the following correct response.
   
   

5. Three environmentally specific pieces of information are required to integrate the API into the workflow: the API URL, client ID and hostname.
   
   Scroll to the top of the screen and save the API URL (1) and client ID (2).
   
   The hostname is contained within the API URL. It is the portion between “https://” and the next “/”.
   
   The hostname will look like this: ademo-gw-gateway-cp4i.itzroks-120000k3ak-vzlud5-4b4a324f027aea19c5cbc0c3275c4656-0000.eu-de.containers.appdomain.cloud
   
   Save the hostname, API URL and client ID.
   
   

Go to top

1. Reserve a Technology Zone demo environment here.

2. Wait until your reservation status is Ready on the IBM Technology Zone’s My Library → My Reservations page. (You can either keep refreshing the My Reservation page or wait for a confirmation email.)
   
   When your reservation is Ready, click the reservation tile to view the reservation details.
   
   

3. On the reservation details page, copy or bookmark the Published services links for BAW Workflow Center and BAW Process Portal.
   
   When your reservation is Ready, click the reservation tile to view the reservation details.
   
   

Go to top

1. Open the BAW VM Remote Console. Use the links on the reservation page. Open the link on the left. Then click to open the console in Full screen.
   
   

2. Click the red Ctrl+Alt+Del button.
   
   
   

3. Click Yes on the Networks dialog box.

   

4. On the Windows desktop, double-click the WebSphere Console shortcut to open the WebSphere Console.
   
   

5. Click Advanced…, then Accept the Risk and Continue to continue past the security warning.
   
   

6. Enter ‘admin’ as the User ID and ‘admin’ as the Password.
   
   

7. Open Security (1) and click SSL certificate and key management (2).
   

8. Click Key stores and certificates.
   
   

9. Click CellDefaultTrustStore.
   

10. Click Signer certificates.
    
    

11. Click Retrieve from port.
    
    

12. For Host, enter your Cloud Pak for Integration ROKS hostname. For Port, enter ‘443’. For Alias, enter ‘integration-1’. Click Retrieve signer information.
    
    

13. Click Apply.
    
    

14. Click Save.
    
    

15. The new certificate is now added.
    
    

You can now close the BAW VM console window.

Go to top

Before completing this section, download the Select the New Account Opening.twx file.

1. Using a browser on your local computer, open BAW Workflow Center using the Published Services link from the top of the Technology Zone reservation page.
   

2. Log in to Workflow Center using ‘admin’ as both the User name and Password.
   
   

3. Click Process Apps.
   
   

4. Click Import.
   
   

5. Click Browse.
   
   

6. Select the New_Account_Opening.twx file (1). Click Open (2).
   
   

7. Click OK.
   
   

8. Wait for the import to complete. Click New Account Opening.
   
   

9. Click the Servers tab.
   
   

10. In Process App Settings, AccountsServer must be updated with the hostname of your Cloud Pak for Integration ROKS environment. Set Hostname to the hostname of your Cloud Pak for Integration ROKS environment.
    
    

Go to top

1. Open Cloud Pak for Integration using your username (1), credentials (2) and click Login (3).
   
   

2. In the menu on the top left, open the Design folder (1) and select Integrations (2).
   
   

3. Click on the ace-designer-demo entry.
   
   

Go to top

1. Using Firefox on your local computer, open BAW Workflow Center using the Published Services link from the top of the Technology Zone reservation page.

2. Log in to Workflow Center using ‘admin’ as both the User name and Password.
   
   

3. Click Process Apps.
   
   

4. Click New Account Opening.
   
   

5. Click Processes (1) and then New Account (Current Workflow) (2).
   
   

6. The New Account (Current Workflow) process definition is now open.
   
   

Go to top

1. Using Chrome on your local computer, open BAW Process Portal using the Published Services link from the top of the Technology Zone reservation page.

2. Log in with ‘assistant’ as the Username and ‘passw0rd’ as the Password.
   
   

3. Process Portal is now open.
   
   

Go to top

The very last step of the Cloud Pak for Integration installation (above) required you to save the API key (client ID).

In the demo script, you will be required to enter the Cloud Pak for Integration API key into the process application. Make sure the API key is easily accessible.

Go to top

In the demo script, you will be required to use the OpenAPI 3.0 YAML file to discover the API. Download the YAML file here.

Go to top