Migrating business process applications

Portal, Express Beta Version 6.1
Operating systems: i5/OS, Linux,Windows

Migrating business process applications

If you have business process applications that were developed for earlier versions, update the business process and portlets prior to running post-installation tasks for business processes. This topic does not apply to System i5.

The WebSphere Business Process Management information center describes changes that you need to apply to business processes to migrate them to the current version of WebSphere Portal Express. In particular, read the following topics for migrating business processes:

"Migration overview"

"Migrating source artifacts to WebSphere Integration Developer from WebSphere Studio Application Developer Integration Edition"

Migrating custom pages

If you created custom pages to use in place of the default pages to contain the task list and task definition pages, verify the following before running the migration:

Make sure that the task list or task definition pages have already been placed on your custom pages.

Make sure that your custom pages are configured correctly.
- If you use a custom page to contain the task list, see "Changing the location of the task list."
- If you use a custom page to contain task definition pages, see "Configuring the pages and portlets for process integration."

Make sure that the default pages created by the action-setup-process-integration configuration task have been deleted.

Migrating portlets

Task portlets and business process portlets that use the generic client APIs provided by WebSphere Business Integration Server Foundation Version 5.1 need to be changed. There is a new version of the Generic EJB API that uses DataObjects as its message format, which is described in the WebSphere Integration Developer Information Center.

The JNDI name of the old Generic EJBs that takes WSIFMessage objects are:

GenericProcessChoreographerEJB
JNDI Name: com/ibm/bpe/api/BusinessProcessHome
Interface: com.ibm.bpe.api.BusinessProcess

TaskManagerEJB
JNDI Name: com/ibm/task/api/TaskManagerHome
Interface: com.ibm.task.api.TaskManager

The V6.1 JNDI names of these Generic EJBs are:

GenericBusinessFlowManagerEJB
JNDI Name: com/ibm/bpe/api/BusinessFlowManagerHome
Interface: com.ibm.bpe.api.BusinessFlowManager

HumanTaskManagerEJB
JNDI Name: com/ibm/task/api/HumanTaskManagerHome
Interface: com.ibm.task.api.HumanTaskManager

After you update and test the migrated portlets, copy them to a location that is available for the migration tasks.

Parent topic: Migrating additional components

Library | Support | Terms of use |