Migrate business process applications

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

Migrate business process applications

If you have business process applications developed for previous versions, make changes to the business process and portlets Do this prior to running post-installation tasks for business processes.

This topic does not apply to System i5.

Migrate business processes
Changes that you need to apply to business processes to migrate them to the current version of WebSphere Portal Express are described in the WebSphere Business Process Management information center. In particular, read the following topics for migrating business processes:

Migration overview: http://publib.boulder.ibm.com/infocenter/dmndhelp/v6rxmx/index.jsp?topic=/com.ibm.wsps.mig.doc/doc/cmig_toplevel.html
Migrating source artifacts to WebSphere Integration Developer from WebSphere Studio Application Developer Integration Editionhttp://publib.boulder.ibm.com/infocenter/dmndhelp/v6rxmx/index.jsp?topic=/com.ibm.wbit.help.migration.ui.doc/topics/tsrcartifacts.html

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

Make sure the task list or task definition pages have already been placed on your custom pages.
Make sure 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 the default pages created by the action-setup-process-integration configuration task have been deleted.

Migrate 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. This is described in detail in the WebSphere Integration Developer information center at http://publib.boulder.ibm.com/infocenter/dmndhelp/v6rxmx/index.jsp?topic=/com.ibm.wbit.help.migration.ui.doc/topics/tmigclientbpcejb.html.

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 Version 6.0 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 
When you have completed updating and testing the migrated portlets, copy them to a location that is available for the migration tasks.

Parent topic:
Migrating additional components

Related information
Make portlet applications available to migration tasks for deployment