You can deploy SOA composite applications and shared data (for example, WSDL and XSD files) with no managed SOA servers or administration servers running (known as offline deployment mode). When the servers are restarted, the SOA composite applications and shared data are deployed.

Offline deployment is beneficial for the following use cases:

• Shared data and new SOA composite applications (for example, the system is new and does not have any deployed composites).

• One-off patches that may contain a single SOA composite application (new or patched) or a resource bundle of shared data.

Note the following guidelines when using offline deployment:

• The SOA composite applications and shared data are available in read-only format in the Oracle home directory. You cannot delete or update the composites.

• The same SOA composite application or shared data file can be included in one or all of the supported use cases when offline deployment occurs. However, for a particular SOA composite application, only one composite SAR or shared data file is in the data location relative to the product data root directory. All cases must point to the same root product data directory. The same composite data is overwritten by the order of applied use cases.

• You cannot redeploy or undeploy the SOA composite application through offline deployment.

• Shared data (resource bundle) redeployment is supported since there is no revision concept with shared data.

• WLST commands are provided for adding and removing individual SOA composite applications and shared data to and from offline deployments. For information, see SOA Composite Application Offline Management Deployment in WLST Command Reference for SOA Suite.

• Configuration plans are not supported with offline deployments.

For information about SAR file naming conventions, see Deployed Service Archives.

For information about shared data, see How to Deploy and Use Shared Data Across Multiple SOA Composite Applications in Oracle JDeveloper.