You can separately package all required artifact files within the project of a SOA composite application into a SOA archive (SAR) JAR file though use of the following tools:

• Oracle JDeveloper

  During deployment on the Deployment Action page, you select the Generate SAR File option. For more information, see Deploying the Profile.

• ant scripts

  Use the ant-sca-package script to package your artifacts. For more information, see How to Use ant to Package a SOA Composite Application into a Composite SAR File.

• WLST commands

  Use the sca_package script to package your artifacts. For more information, see WLST Command Reference for SOA Suite.

• Maven plug-in

  Use the Maven plug-in to compile, package, deploy, test, and undeploy a SOA composite application in a Maven environment. For more information, see Using the Oracle SOA Suite Development Maven Plug-In.

A SAR file is a special JAR file that requires a prefix of sca_ (for example, sca_HelloWorld_rev1.0.jar).

In addition, when you deploy a SOA composite application with the Deploy to Application Server option on the Deployment Action page in Oracle JDeveloper, all required artifact files within a project are automatically packaged into one of the following files:

• A self-contained JAR file (for single SOA composite applications)

  For more information about self-contained composites, see How to Deploy a Single SOA Composite in Oracle JDeveloper and How to Deploy Multiple SOA Composite Applications in Oracle JDeveloper.

• A ZIP file of multiple SOA composite applications that share metadata with one another

  You can deploy and use shared data across SOA composite applications. Shared data is deployed to the SOA Infrastructure on the application server as an Oracle Metadata Services (MDS) Repository archive JAR file. The archive file contains all shared resources. For more information, see How to Deploy and Use Shared Data Across Multiple SOA Composite Applications in Oracle JDeveloper.