Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Copy bigbank-loan-XXXX.jar to the severs/vm/target/image/runtimes/vm/deploy directory. Next, copy the two war archives to the deploy directory. Copy bigbank-web-1.7.jar and bigbank-backoffice-1.7.jar to the runtimes/vm/deploy directory.

Deploying

...

to a Distributed Domain

The samples distribution also contains an automated build process for producing a set of clustered servers. To create the clustered servers, execute the following from the servers/cluster directory:
mvn clean install
The install.
 The build will create three server images located in the target directory of each module under /servers/cluster: controller, zone1, and zone2. 
Follow the steps in the previous section to build the BigBank application. When the build completes, launch the H2 database, controller and zone runtimes:

  1.  

...

#  Launch the shared H2 database process from cluster/database:

...

 java -jar target/h2-1.2.140.jar

 jar

 
# From the controller/target/image/bin directory:

...

 java -jar server.jar controller
 controller
 
# From the zone1/target/image/bin directory:

...

 java -jar server.jar participant
participant

  1.  

# From the zone2/target/image/bin directory:

...

 java -jar server.jar participant
 participant
 

After booting, the runtimes will discover each other and form a distributed domain consisting of two cluster clusters (zones). Note the runtimes may be on the same machine or different machines.
Copy bigbank-loan-1.7.jar  Copy the BigBank archives to the controller/target/image/runtimes/controller/deploy directory. The controller will provision the loan service and web UIs to zone1 and the backend services to zone2.
To run additional zone participants, copy one of the images and follow the instructions above for launching the servers. If more than one server is run on the same machine, you will need to modify the HTTP and HTTPS ports in config/participant/systemConfig.xml.

...

 

Getting Help


At some point you may require help with Fabric3. The best place to obtain pointers, advice or assistance troubleshooting a problem is the user mailing list, which can be accessed at {+}http://xircles.codehaus.org/projects/fabric3/lists+. There are several mailing lists for Fabric3. Please post questions to the user list. The developer list is intended for topics related to ongoing Fabric3 development and is not a general forum for questions. However, if you are interested in Fabric3 development, we encourage you to participate in discussions.
Should you encounter a bug, we encourage you to file a report in the online JIRA system at {+}http://jira.codehaus.org/browse/FABRICTHREE+. If possible, please include a detailed description and failing testcase (or other appropriate means) to reproduce the problem. Assisting Fabric3 developers in reproducing the problem generally leads to faster resolution.