Fabric3 supports
Deploying to a domain comprised of multiple VMs (runtimes) follows the same basic model as a single-VM deployment with the additional requirement of specifying a target zone (the Fabric3 term for cluster partition; see The Domain).
Deployment Plan
Packaging for a clustered environment is nearly identical to packaging for a single-VM environment, except for the additional requirement of including a plan file {{.xml file in the contribution META-INF/plan directory. xml). The plan file maps deployable composites (i.e. composites specified for deployment in the sca-contribution.xml manifest) to a zone . The following is an example of a plan fileas shown below:
| Code Block | ||||
|---|---|---|---|---|
| ||||
<plan xmlns:test="urn:org.fabric3.test" name="testPlan">
<mappings>
<mapping deployable="test:Composite1" zone="zone1"/>
<mapping deployable="test:Composite2" zone="zone2"/>
</mappings>
</plan>
|
Single Contribution Deployment
A single contribution can be deployed to one zone or multiple zones. It is important to note that zones in Fabric3 are homogenous. That is, each runtime in the zone acts as a replica running with the same configuration and hosting the same services. Consequently, If a contribution is deployed to one zone, it will be horizontally scaled as a single unit as illustrated in the following diagram:
All services will run