Moving from on-premises Case Manager to Cloud Pak for Business Automation
About this task
The Case Manager system is composed of the IBM FileNet Content Platform Engine, IBM Content Navigator, and Case Manager. To move Case Manager from on-prem to cloud, you must also move the FileNet Content Platform Engine and IBM Content Navigator to Cloud Pak for Business Automation.
When you move to Cloud Pak for Business Automation, the case development environment is migrated to the Business Automation Workflow Authoring environment and the case production environment is moved to the Business Automation Workflow Runtime environment.
Before you move to any Cloud Pak for Business Automation capability, it is important to understand what you need, what options you have, and your license entitlements. Complete the following steps in the specified sequence.

1. Assessing your readiness
At the start of your transformation journey, assess your current readiness to adopt Cloud Pak for Business Automation.
About this task
Before you move IBM Case Manager to Business Automation Workflow in Cloud Pak for Business Automation, be aware of the prerequisites.
- For Case Manager
production or development environments:
- It is recommended that you install Case Manager 5.3.3 interim fix *10* or later. For more information about creating a development or production deployment, see Configuring IBM Case Manager.
- When you configure the Case Manager profile, select the development environment or production environment and deploy Case Manager with the default configuration tasks.
- The Content Platform Engine and IBM Content Navigator versions in the on-prem environment must be the same version or earlier than what is supported by Cloud Pak for Business Automation. If the versions of Content Platform Engine and IBM Content Navigator are later than the one supported by Cloud Pak for Business Automation, database conflicts might occur.
- For databases and object stores:
- The database that has the global configuration (GCD) database, IBM Content Navigator, design object store (DOS), and target object store (TOS) is the same database that is used after the migration. Ensure that the database is available after the migration. If you use file storage object stores, take a backup.
- The same LDAP is used in the on-prem and container environments.
- The DOCS (Documents Object Store) and AEOS (Application Engine object store) must be created in the on-prem environment before the migration.
- Solutions that use forms do not work as expected in container environments because forms are not supported.
- Migrated object stores from the on-prem environment are not used after migration. The IBM Content Navigator URL of the on-prem environment no longer works.
- The traditional Content Platform Engine cannot be used along with the container Content Platform Engine after migration.
2. Preparing to move
After you assess your readiness, prepare for the move from IBM Case Manager to Cloud Pak for Business Automation. Make sure that the required databases are online.
Before you begin
The databases of Content Platform Engine and IBM Content Navigator are used after the move, so make sure that the databases are online. The Lightweight Directory Access Protocol (LDAP) server that is used in the on-prem environment is also used after the move, so make sure that the LDAP server is running. When you are ready to start the move, stop the Content Platform Engine, IBM Content Navigator, and Case Manager applications that are hosted on WebSphere Application Server or Oracle WebLogic Server.
About this task
This document describes the Content Platform Engine and IBM Content Navigator actions required for moving Case Manager. If you require any other capabilities of FileNet Content Manager, see Moving from on-premises FileNet Content Manager to Cloud Pak for Business Automation.
2a. Preparing the case solutions
Export the case solutions and prepare them for moving from IBM Case Manager to Cloud Pak for Business Automation.
About this task
Use the migration planning sheet to gather the on-prem environment configuration data that is required for migration. After you generate the custom resource, check that all the values listed in the migration planning sheet are entered. See Migration planning sheet.
Procedure
To prepare your case solutions:
2b. Preparing the cluster
Use the migration planning sheet to gather information. Prepare the cluster for moving from IBM Case Manager to Cloud Pak for Business Automation.
About this task
Use the migration planning sheet to gather the on-prem environment configuration data that is required for migration. After you generate the custom resource, check that all the values listed in the migration planning sheet are correctly filled in. See Migration planning sheet.
Procedure
3. Generating the CR
After you prepare the cluster, you can generate and run a custom resource (CR) file. The CR file acts as a template of what you will install, and can be customized according to the components that the operator supports for installation.
Procedure
4. Deploying the CR
After you successfully generate the custom resource (CR) file, you can deploy Cloud Pak for Business Automation. The CR acts as a template of what you will install.
Procedure
- Validate your CR file before you apply it or save it in the YAML view. It is likely that you edited the file multiple times, and possibly introduced errors or missed values during your customizations. For more information, see Validating the YAML in your custom resource file.
- Apply the upgraded CR to the operator. For more information, see Applying the updated custom resource.
What to do next
5. Performing required post-migration steps
You must perform post-migration steps if you work with file storage target object stores.
Procedure
If you use file storage target object stores:
6. Optional: Completing post-migration tasks
After migration, you can update the Daeja Viewer log file path, work with custom plug-ins and extensions, enable case analyzer and case history, configure the case event emitter, and index case instances.