Verify that the business process container or task container is installed and configured for each application server on which you want to install your application.
For each application server on which you want to install the Service Component Architecture (SCA) Enterprise JavaBeans (EJB) modules that contain processes, you must have performed the steps described in ../../../com.ibm.wsps.ins.doc/doc/bpc/t2co.dita or ../../../com.ibm.wsps.ins.doc/doc/bpc/t2cotask.dita, as appropriate.
Before you install a business process or human task application, make sure that the following conditions are true:
You can install business process and task applications from the administrative console, from the command line, or by running an administrative script, for example.
If you are installing an application on a cluster, you might have to adapt the data source resource reference to the data source for the cluster.
All business process templates and human task templates are put into the start state.
If you installed a process application on a cluster, verify that the application uses the data source that is named after the cluster. For example, if the application was generated using the default data source BPEDB, change the data source for the application to BPEDB_cluster_name, where cluster_name is the name of the cluster on which you installed the application.
Before you can create process instances or task instances, you must start the application.
Deployment of models
When WebSphere Integration Developer generates the deployment code for your process, the constructs in the process or task model are mapped to various Java 2 Enterprise Edition (J2EE) constructs and artifacts. All deployment code is packaged into the enterprise application (EAR) file. Each new version of a model that is to be deployed must be packaged into a new enterprise application.Application management
This topic explains application management considerations that are specific to enterprise applications that contain business processes or human tasks.