BPM, Workflow, and Case

BPM, Workflow, and Case

Come for answers. Stay for best practices. All we’re missing is you.

 View Only

Move from on-prem IBM Case Manager to Cloud Pak for Business Automation by following step-by-step instructions

By Ann Ewan posted Mon February 05, 2024 04:31 PM

  
A symbolic diagram that shows a square icon for Case Manager, a cloud shape for IBM Cloud, and an arrow between the two to symbolize moving from Case Manager to IBM Cloud

Co-Authors: Aparna Bulusu, Prateek Gulur Suryanarayanara

To move an on-premises IBM Case Manager 5.3.3 environment to IBM Cloud Pak for Business Automation and still keep the databases and LDAP of your on-prem environment, you can now follow step-by-step instructions that make the process easier and less error-prone. Starting in 23.0.2, a new automated script also reduces the number of required steps. The script also provides validation of all the updated fields in the custom resource (CR) to ensure that the move will be a success.

For 22.0.2 or 23.0.1

Without the script, you can follow the instructions in the Migrating IBM Case Manager to IBM Business Automation Workflow on Cloud Pak for Business Automation 22.0.2 or 23.0.1 technote.

For 23.0.2

In 23.0.2, you can use the automated script and follow the instructions in 23.0.2: Moving from on-premises IBM Case Manager to Cloud Pak for Business Automation in the Business Automation Workflow docs, or in Moving from on-premises Case Manager to Cloud Pak for Business Automation in the Cloud Pak docs. (The instructions are the same in both doc sets.)

The automated script in 23.0.2 addresses the following challenges:

Challenge

Solution

After you generated the CR using the prerequisites script, you had to manually modify 11 fields. The CR is a lengthy file with many fields, and any manual error resulted in failure.

The automated script takes care of modifying the CR for all 11 fields, based on the on-prem configuration you provide. Instructions to modify the CR are no longer needed. The script also validates the migration fields in the CR.

Multi Target Object store (TOS) configuration wasn’t implemented in the prerequisites script. For Multi TOS, you had to manually modify the CR to provide complete data source information for each TOS.

Multi TOS configuration is implemented in the script, which handles all the data source configuration for migration.

For Multi TOS, you had to manually create the secrets that were required for database connection. Otherwise, the move would fail.

The script handles the Multi TOS database secrets.

0 comments
43 views

Permalink