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.
When you install an enterprise application that contains business process model or human task model J2EE constructs, the model constructs are stored as process templates or task templates, as appropriate, in the Business Process Choreographer database. If the database system is not running, or if it cannot be accessed, the deployment fails. Newly installed templates are, by default, in the started state. However, the newly installed enterprise application is in the stopped state. Each installed enterprise application can be started and stopped individually.
New versions of a process template or task template have the same name, but a different valid-from attribute. You can deploy many different versions of a process template or task template, each in a different application. All the different process versions are stored in the database.
If you do not specify a valid-from date, a default date is assumed. The process is valid immediately after installation.
Parent topic: Installing and uninstalling business process and human task applications
Related concepts
Application management
Related tasks
Uninstalling business process and human task applications