How to Use ant to Deploy a SOA Composite Application

The following provides an example of deploying a SOA composite application. You can also use this command to deploy shared data such as WSDLs, XSDs, and other file types across SOA composite applications. For information about shared data, see How to Deploy and Use Shared Data Across Multiple SOA Composite Applications in Oracle JDeveloper.

ant -f ant-sca-deploy.xml 
-DserverURL=http://localhost:8001 
-DsarLocation=C:\demo\end2end-105-POProcessing\po\solutions\ch9\POProcessing\POPro
cessing\deploy\sca_POProcessing_rev6-cmdline.jar 
-Doverwrite=true 
-Duser=weblogic 
-DforceDefault=true 
-Dconfigplan=C:\demo\end2end-105-POProcessing\po\solutions\ch9\POProcessing\POProc
 essing\demed_cfgplan.xml
-Dscac.user.classpath=C:\jarfolder\custom.jar
-Dpartition=partition.name

Note:

After specifying the user name, enter the password when prompted.

Table 48-14 describes the syntax.

Table 48-14 ant Deployment Commands

Argument	Definition
`serverURL`	URL of the server that hosts the SOA Infrastructure application (for example, `http://myhost10:8001`).
`sarLocation`	Absolute path to one the following: SAR file. ZIP file that includes multiple SARs.
`overwrite`	Optional. Indicates whether to overwrite an existing SOA composite application on the server. `false` (default): Does not overwrite the file. `true`: Overwrites the file.
`user`	Optional. User name to access the composite deployer servlet when basic authentication is configured.
`password`	Optional. Password to access the composite deployer servlet when basic authentication is configured. If you enter the user name, you are prompted to enter the password if you do not provide it here.
`forceDefault`	Optional. Indicates whether to set the version being deployed as the default version for that composite application. `true` (default): Makes it the default composite. `false`: Does not make it the default composite.
`configplan`	Absolute path of a configuration plan to be applied to a specified SAR file or to all SAR files included in the ZIP file.
`sysPropFile`	Passes in a system properties file that is useful for setting extra system properties, for debugging, for SSL configuration, and so on. If you specify a file name (for example, `tmp-sys.properties`), you can define properties such as the following: javax.net.debug=all
`scac.user.classpath`	Optional. The name of the external custom library. If you have a SOA composite application with a BPEL process service component that refers to a custom JAR file, set this property.
`partition`	Optional. The name of the partition in which to deploy the SOA composite application. The default value is `default`. If you do not specify a partition, the composite is automatically deployed into the `default` partition.

Note:

Human workflow artifacts such as task mapped attributes (previously known as flex field mappings) and rules (such as vacation rules) are defined based on the namespace of the task definition. Therefore, the following issues are true when the same SOA composite application with a human workflow task is deployed into multiple partitions:

For the same task definition type, mapped attributes defined in one partition are visible in another partition.
Rules defined on a task definition in one partition can apply to the same definition in another partition.