Deploying and Managing SOA Composite Applications with ant Scripts
You can manage SOA composite applications with the ant utility. ant is a Java-based build tool used by Oracle SOA Suite for managing SOA composite applications. The configuration files are XML-based and call out a target tree where various tasks are executed. The ant utility is well-suited for automation and can be easily integrated into existing release processes.
Note:
Before using the Oracle SOA Suite ant scripts, you must first run the setDomainEnv.sh script (for Linux) or setDomainEnv.cmd script (for Windows). This script adds the necessary JAR files for using ant to the classpath.
Table 48-10 lists the ant scripts available in the Middleware_Home\SOA_Suite_Home\bin directory.
Table 48-10 ant Management Scripts
| Script | Description |
|---|---|
|
|
Automates the testing of SOA composite applications. |
|
|
Compiles a SOA composite application. |
|
|
Packages a SOA composite application into a composite SAR file. |
|
|
Deploys a SOA composite application. |
|
|
Undeploys a SOA composite application. |
|
|
Exports a composite into a SAR file. |
|
|
Exports postdeployment changes of a composite into a JAR file. |
|
|
Imports postdeployment changes of a composite. |
|
|
Exports shared data of a given pattern into a JAR file. |
|
|
Removes a top-level shared data folder. |
|
|
Starts a SOA composite application. |
|
|
Stops a SOA composite application. |
|
|
Activates a SOA composite application. |
|
|
Retires a SOA composite application. |
|
|
Assigns a default revision version. |
|
|
Lists deployed SOA composite applications. |
|
|
Lists all available partitions in the SOA Infrastructure. |
|
|
Lists all composites in a partition. |
|
|
Creates a partition in the SOA Infrastructure. |
|
|
Undeploys all composites in a partition before deleting the partition. |
|
|
Starts all composites in a partition. |
|
|
Stops all composites in a partition. |
|
|
Activates all composites in a partition. |
|
|
Retires all composites in a partition. |
|
|
Migrates BPEL and Oracle Enterprise Service Bus (ESB) release 10.1.3 metadata to release 11g. Note: If any Java code is part of the project, you must manually modify the code to pass compilation with an 11g compiler. For BPEL process instance data, active data used by the 10.1.3 Oracle BPEL Server is not migrated. |
For additional information about ant, visit the following URL:
http://ant.apache.org