Offline Deployment Configuration File

The offline deployment configuration file specifies the following elements for offline deployments.

• Partitions are created, as necessary, before the SOA composite applications and shared resources are deployed. Note the following order of precedence for partition use:

  • The partition specified in the <partition> element is created.

  • If a partition used in <composite-deployment> is not specified in the <partition> element, it is created implicitly.

  • If the partition attribute is not specified in the <composite-deployment> element, the composite is deployed into the default partition.

• Shared resources

  Shared resources are deployed before the SOA composite applications.

• SOA composite applications

  You can list multiple SOA composite applications in the file. However, they are not deployed in the order in which they are listed in the file.

The file naming convention is composite-offline-deployments-version_number.xml, where version_number can be any value, but the composite-offline-deployments- part is fixed and required.

The following example shows the structure of the offline deployment file. The file is divided into the three sections to represent partitions, SOA composite applications, and shared data.

<offline-configuration>
    <partitions>?
        <partition name="partition_name"/>*
    </partitions>
    <composite-deployments>?
        <composite-deployment location="/some/path" partition="partition_name"?>*
    </composite-deployments>
    <shared-resources>?
        <shared-resource location="/some/path"/>*
    </shared-resources>
</offline-configuration>

The following example shows an offline deployment configuration file in which the following is defined:

• Partition one and two are created.

• The composite SAR file /some/path/sca_composite1.jar is deployed into partition one.

• The composite SAR file /another/path/sca_composite2.jar is deployed into partition two.

• The composite SAR file /yet/another/path/sca_composite3.jar is deployed into the default partition.

• The shared data JAR files /some/path/shareddata1.jar and /another/path/shareddata2.jar are deployed into the shared data location.

<offline-configuration>
    <composite-deployments>
        <composite-deployment location="/some/path/sca_composite1.jar"
 partition="one">
        <composite-deployment location="/another/path/sca_composite2.jar"/
 partition="two">
        <composite-deployment location="/yet/another/path/sca_composite3.jar"/>
    </composite-deployments>
    <shared-resources>
        <shared-resource location="/some/path/shareddata1.jar"/>
        <shared-resource location="/another/path/shareddata2.jar"/>
    </shared-resources>
</offline-configuration>

The following example shows an offline configuration deployment file in which the following occurs:

• The shared data JAR file named shareddata.jar is deployed.

• The composite SAR file named sca_soaApp1.jar is deployed into the myPartition partition.

• The composite SAR file named sca_soaApp2.jar is deployed by default into the default partition because no partition is explicitly defined.

<offline-configuration>
    <composite-deployments> 
        <composite-deployment
            location="/scratch/aime/appTop/soa1/sca_soaApp1.jar“ 
            partition=“myPartition“/>
        <composite-deployment
            location="/scratch/aime/appTop/soa1/sca_soaApp2.jar“/>
           </composite-deployments> 
    <shared-resources> 
        <shared-resource location="/scratch/aime/appTop/soa1/shareddata.jar"/> 
    </shared-resources> 
</offline-configuration>

The following example shows an offline deployment configuration file in which only shared data located in the two defined directories is deployed:

<offline-configuration>
    <shared-resources>
        <shared-resource location="/some/path/shareddata1.jar"/>
        <shared-resource location= "/another/path/shareddata2.jar"/>
    </shared-resources>
</offline-configuration>

The following example shows an offline deployment file in which partition one and two are created. No SOA composite applications or shared data are deployed:

<offline-configuration>
    <partitions>
        <partition name="one"/>
        <partition name="two"/>
    </partitions>
</offline-configuration>