Fabric3 for WebLogic

Fabric3 has direct integration with Oracle WebLogic Server (WLS). When hosted on WLS, Fabric3 will use its native clustering, transaction management, datasource pooling, JMS, JMX, and thread pooling services.

Deployment Topologies

Fabric3 can be setup to run on a single WLS instance or on a WLS cluster. When run on a cluster, the Fabric3 controller is installed on the WLS Admin Server while participant runtimes are hosted on WLS managed servers:

Contributions are deployed using either the The Admin CLI (recommended for production) or by copying them to the runtime deploy directory (for development). Note that contributions cannot be deployed using the WLS management console or deployment tool.  

Installation

To install Fabric3 on WebLogic, download the Fabric3 WebLogic runtime and Fabric3 bootstrap .WAR from the Downloads sections. then, and complete the following steps:

1. Setup your WebLogic cluster (or single instance).
2. Extract the runtime image.
3. Place the fabric3-weblogic-cluster1-1.9.jar in the WLS domain lib/ directory. 

4. On the admin server machine, set the fabric3.home and fabric3.mode as part of the WLS JAVA_OPTIONS environment variable. On *nix:

   export 'JAVA_OPTIONS=-Dfabric3.home=<path to the extracted Fabric3 image> -Dfabric3.mode=controller 
                -Djavax.xml.soap.MetaFactory=com.sun.xml.messaging.saaj.soap.SAAJMetaFactoryImpl'

5. On each managed server, set the fabric3.home and fabric3.mode as part of the WLS JAVA_OPTIONS environment variable. On *nix:

   export 'JAVA_OPTIONS=-Dfabric3.home=<path to the extracted Fabric3 image> -Dfabric3.mode=participant 
                -Djavax.xml.soap.MetaFactory=com.sun.xml.messaging.saaj.soap.SAAJMetaFactoryImpl'

   Alternatively, a single instance WLS installation can be started using:

   export 'JAVA_OPTIONS-Dfabric3.home=<path to the extracted Fabric3 image> -Dfabric3.mode=vm 
                -Djavax.xml.soap.MetaFactory=com.sun.xml.messaging.saaj.soap.SAAJMetaFactoryImpl' 

6.  When running cluster on more than one machine, admin server address must be set in systemConfig.xml on runtimes running in PARTICIPANT mode. Otherwise the default value (t3://localhost:7001) will be used:

   <weblogic adminServerUrl="t3://your.admin.server.ip:port"/>

7. Launch the WebLogic domain and deploy the Fabric3 bootstrap WAR located in the war directory of the distribution. The WAR will replicate to the cluster and initialize the Fabric3 runtime
8. SCA applications are deployed to the controller (or vm) deploy directories in the runtime image. This process will be exactly the same as for the Fabric3 standalone and Tomcat runtimes.