Deploy SOA Archive Dialog

1.50 Deploy SOA Archive Dialog

Use to select the SOA composite application archive to deploy.

When attempting to deploy an archive to Oracle WebLogic Server, always create a connection to the Oracle WebLogic Server Administration Server. Deployment then prompts you by displaying all SOA configured servers (can be the administration server or one or more managed servers).

Note: The archive must already exist. You cannot create an archive in this dialog.

Choose the target SOA server(s) to which you want to deploy this archiveSelect the Oracle WebLogic Servers to which to deploy the archive.

Element	Description
SOA Server	Select the SOA server to which to deploy the archive.
Partition	Select the partition in which to deploy the archive. If the server contains no partitions, you cannot deploy this archive. By default, a partition named default is automatically included with Oracle SOA Suite.
Status	Displays the status of the server. If the server is not in a running state, you cannot deploy this archive.
Server URL	Displays the URL of the server.
SOA Archive	Click Browse to select a prebuilt SOA composite application archive. The archive consists of a JAR file of a single application or a SOA bundle ZIP file containing one or more composite archives. If the older, currently-deployed version of this revision has running instances, the state of those instances is changed to aborted.
Configuration Plan (Optional)	Click Browse to select a configuration plan to attach to the SOA composite application archive. 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.
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.
Overwrite any existing composites with the same revision ID	Select to overwrite (redeploy) an existing SOA composite application 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.