IBM Business Automation Workflow V 19.0.0.1

Upgrading IBM Case Manager V5.3.3 to IBM Business Automation Workflow

Install Business Automation Workflow and upgrade your environment. You can benefit from the full spectrum of Business Automation Workflow capabilities to manage and deploy unified process and case solutions by using the new common Workflow Center.

When you upgrade to Business Automation Workflow, your case data and navigator configuration are preserved, and no migration is necessary. The main steps for the upgrade include:
  • Upgrade Content Platform Engine.
  • Upgrade IBM Content Navigator.
  • Augment your case installation with an IBM Business Automation Workflow topology.
For information about the system upgrade, see Upgrading your IBM Case Manager system.
You don't need to upgrade your runtime projects. You have the option to manage the case solutions in your development environment in the enhanced Workflow Center. For more information, see Workflow Center.
Reasons to upgrade your system
  • Stay up-to-date. Business Automation Workflow is the environment through which all the future maintenance and enhancement packs will be delivered.
  • Simplify deployment with unified workflow projects instead of separate projects for your process and case solutions, and manage your projects with the added versioning support.
  • Take advantage of the state-of-the-art user interface and page deployment capabilities in the Process Designer.
  • Update your library of case solutions and make it ready for workflow automation. Access all the case management capabilities as before, but take advantage of the enhanced features in the Workflow Center.
FAQs
  • Can I use legacy IBM Case Manager solutions that exist in the external FileNet® Content Manager target object store of Business Automation Workflow?

    Yes. After configuring the external FileNet Content Manager server, you can re-run the Business Automation Workflow case configuration tasks to configure Business Automation Workflow case functionality with the external FileNet Content Manager server. This step is part of the procedure to switch to an external FileNet Content Manager server.

  • Can I use legacy IBM Case Manager solutions with the legacy IBM Case Manager components, such as the Case Client, Case administration client, and Case Builder, after the FileNet Content Manager server that contains their repositories is configured as an external FileNet Content Manager server in Business Automation Workflow?

    No. This is not a tested or supported use case. You need to use the Business Automation Workflow case components to work with the existing IBM Case Manager solutions. A large part of the Business Automation Workflow case functionality is configured in the embedded Content Navigator in Business Automation Workflow. It is an option to configure your existing Content Navigator server as an external server. That allows you to keep using most of the case components as plugins on your existing Content Navigator server. These case components are the ones that are configured in Content Navigator, such as the Case Client, Case administration client, and custom widgets. After configuring an external Content Navigator server, you will use the Case configuration tool in Business Automation Workflow to configure and maintain the case components on the external server. Case Builder is not a Content Navigator plugin, which means that you will use the Case Builder in Business Automation Workflow to edit case solutions. Do not use the legacy IBM Case Manager or the legacy IBM Case Manager configuration tool after configuring the external FileNet Content Manager server.

  • Do I need to migrate the FileNet Content Manager tasks or workflows to Business Automation Workflow process workflows (previously known as IBM BPM workflows) after configuring an external FileNet Content Manager server in Business Automation Workflow?

    No. The workflows in the external FileNet Content Manager server remain fully functional, operational, and supported.