Online Help for Oracle SOA Suite

1.29 Deploy Composite Wizard - Deploy Configuration Page

Use to deploy SOA composite applications to the server.

This page shows one or more tabs, each representing one composite. If the deployment profile is a SAR profile, it shows only one tab for the current composite. If the deployment profile is a SOA bundle profile, it shows one or more tabs for each SAR profile included in the SOA bundle.

Element	Description
Composite Revision ID	Displays details about the revision ID of the SOA composite application.
Project	Displays the SOA project name. This field cannot be edited.
Current Revision ID	Displays the current revision ID of the SOA composite application. This field cannot be edited.
New Revision ID	Displays the current revision ID value by default. Use this field to specify a new value or continue to use the current value. This revision ID becomes the value for the `${composite.revision_id}` variable in the application name. For example, if you enter `2.0` as the new revision ID for a composite named `OrderBooking, ${composite.revision_id}` is replaced with `_rev2.0` (`sca_OrderBooking_rev2.0.jar`).
SOA Configuration Plan	Expand to display a list of available configuration plans. A configuration plan enables you to define the URLs and property values to use for development, test, and production environments. During process deployment, the configuration plan is used to search the SOA project for values that must be replaced to adapt the project to the next target environment.
Do not attach	Select if you do not want to attach a configuration plan to the application. This is the default selection.
Configuration_Plan.xml	Select the specific plan. A configuration plan must already exist in the SOA project for this selection to be available.
BPEL Monitor	Expand to specify whether to ignore or display BPEL Monitor deployment errors.
Ignore BPEL Monitor deployment errors	Deselect this checkbox to display BPEL Monitor deployment errors. This checkbox corresponds to the `ignoreErrors` property in the `monitor.config` BPEL project file. This file defines runtime and deployment properties needed to connect with Oracle BAM Server to create the Oracle BAM data objects and dashboards. If Oracle BAM Server is unreachable, and `ignoreErrors` is set to `true`, deployment of the composite does not stop. If set to false and Oracle BAM Server is unavailable, deployment fails. Note: This checkbox only appears if there is at least one `.monitor` file in the application.
Mark composite revision as default	Select to make this the default revision of the SOA composite application. This revision is instantiated when a new request comes in. This checkbox only displays if a current revision already exists for this composite and you selected Deploy to Application Server on the Deployment Action page.
Overwrite any existing composites with the same revision ID	Select to overwrite any existing composites with the same revision ID. The consequences of this action are as follows: A new revision of the currently deployed SOA composite application is redeployed (for example, old version 1.0 is redeployed as new version 1.0). The older, currently-deployed version of this revision is removed (overwritten). If the older, currently-deployed version of this revision has running instances, the state of those instances is changed to aborted. This checkbox only displays if a current revision already exists for this composite and you selected Deploy to Application Server on the Deployment Action page.
Keep running instances on redeploy	Select to enable existing instances of the overwritten revision to continue running instead of being aborted. These instances run side by side with any new instances that you create with the new revision of the SOA composite application.
Force deployment of incompatible processes	If Keep running instances on redeploy is checked, this option is displayed. Select this checkbox to force deployment of incompatible BPM processes. When a composite with BPM processes is overwritten, the system checks to see if the BPM processes being overwritten are compatible with the processes being deployed. If they are compatible, running instances of these processes are not marked as stale and deployment is successful. If they are incompatible, deployment fails unless you select this checkbox.
Use the following SOA configuration plan for all composites	Click Browse to select the same configuration plan to use for all applications. If you specify a configuration plan, it ignores all configuration plans listed in the composite tabs and uses this plan for all composites.