Upgrade Guide for DB2 UDB for z/OS and OS/390 > Postupgrade Tasks for Applications >

Upgrading Inbound Workflows


Upgrades: Release 7.0.x.

Environments: All environments.

This topic is part of an upgrade process. See How to Perform the Upgrade.

  • Change inbound workflows that contain a String type process property to pass the value into type Binary; otherwise, the workflow presents the following error message:

    Output argument '<Value>' in step 'Read from File' contains data that cannot be passed to string type property 'InputXML'. Data type: 'MEMBLOCK'; String representation of data body: '<?xml version="1.0" encoding="UTF-8"?><?'

  • After an upgrade from Release 6.x to 7.7, manually change the name of the EAI MQSeries Transport business service to EAI MQ Series Server Transport; otherwise, the workflow presents the following error message:

    [1] Unable to create the Business Service 'EAI MQSeries Transport'
    [2] Could not find 'Class' named 'EAI MQSeries Transport'. This object is inactive or nonexistent.

Transitioning from Development to Production

To transition to production, you must import tables from the main Siebel Database, as well as importing the Siebel Tools Repository. A special utility, REPIMEXP, is provided to migrate the Siebel Tools Repository to production. Refer to the Siebel Business Process Designer Administration Guide for the steps required to transition to production.

The tables are named as follows:

  • Siebel Database tables containing workflow information begin S_WFA.
  • Siebel Tools Repository tables containing workflow information begin S_WFR.
  • Siebel Database tables that contain workflow information for releases prior to Release 7.7 begin S_WF_ (Note the underscore after WF.) After the upgrade to Release 7.7, these tables are obsolete and are not referenced by applications.

If you have long-running workflows, verify they are all functioning correctly before transitioning to production.

Upgrade Guide for DB2 UDB for z/OS and OS/390