Description Syntax sca_deployComposite

9-2 Oracle Fusion Middleware WebLogic Scripting Tool Command Reference

9.2 Deployment Commands

Use the deployment commands, listed in Table 9–2 , to deploy and undeploy SOA composite applications.

9.2.1 sca_deployComposite

Command Category: Deployment Commands Use with WLST: Offline

9.2.1.1 Description

Deploys a SOA composite application to the Oracle WebLogic Server. This command does not package the artifact files of the application for deployment. See Section 9.7, SOA Composite Application Management Commands Start, stop, activate, retire, assign a default revision version, and list deployed SOA composite applications. Configuration Plan Management Commands Attach, extract, generate, and validate configuration plans for SOA composite applications. Task Validation Commands Validate human workflow tasks. SOA Composite Application Compilation Commands Compile SOA composite applications. SOA Composite Application Packaging Commands Package SOA composite applications into archive files to deploy. SOA Composite Application Test Commands Test SOA composite applications prior to deployment in a production environment. SOA Composite Application HTTP Client-Based Export and Import Commands Export and import SOA composite applications based on the HTTP client. SOA Composite Application MBean-Based Export and Import Commands Export and import SOA composite applications on the server-based composite store MBean CompositeStoreMXBean. SOA Composite Application Partition Management Commands Logically group different revisions of your SOA composite applications into separate sections. Table 9–2 Deployment Commands for WLST Configuration Use this command... To... Use with WLST... sca_deployComposite Deploy a SOA composite application. Offline sca_undeployComposite Undeploy a SOA composite application. Offline Table 9–1 Cont. Oracle SOA Suite Command Categories Command category Description Oracle SOA Suite Custom WLST Commands 9-3 SOA Composite Application Packaging Commands for instructions on packaging a SOA composite application.

9.2.1.2 Syntax

sca_deployCompositeserverURL, sarLocation, [overwrite], [user], [password], [forceDefault], [configplan], [partition] Argument Definition serverURL URL of the server that hosts the SOA Infrastructure application for example, http:myhost10:7001. sarLocation Absolute path to one the following: ■ SOA archive SAR file. A SAR file is a special JAR file that requires a prefix of sca_ for example, sca_HelloWorld_rev1.0.jar. The SAR file can be deployed with the deployment commands such as sca_ deployComposite, but a regular .jar file is not treated as a special SAR file. ■ ZIP file that includes multiple SARs, metadata archives MARs, or both. ■ Enterprise archive EAR file that contains a SAR file. overwrite Optional. Indicates whether to overwrite an existing SOA composite application file. ■ 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. forceDefault Optional. Indicates whether to set the new composite as the default. ■ true default: Makes it the default composite. ■ false: Does not make it the default composite. configplan Optional. Absolute path of a configuration plan to be applied to a specified SAR file or to all SAR files included in the ZIP file. 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. 9-4 Oracle Fusion Middleware WebLogic Scripting Tool Command Reference

9.2.1.3 Examples