CloudTran Home

 
  
<< Back Contents  >  5.  Running CloudTran Forward >>

5.2 Running

 5.2.1  Jars
 5.2.2  Module Order
 5.2.3  Running
 5.2.4  Custom Initialization

5.2.1  Jars
The CloudTran shipment includes a lib/ directory with a number of required jars. The bare minimum are the cloudTran*.jar files. There are other jars in the lib/ directory which may not be relevant to your deployment or may need upgrading.

The CloudTran jars need to be in the classpath of all types of nodes - client, manager and isolator.


5.2.2  Module Order
You must start the Isolator nodes first, then the Manager nodes (or at least a quorum of them), and finally the client nodes.

Even in debug deployments, starting the first isolator takes 20-30 seconds. When the isolator is ready to service the grid, it prints the message
    CloudTran ISOLATOR node started
It is best to start managers with at least some delay between them - 2 seconds is enough on standard server processors.


5.2.3  Running
To run the different types of node, you call classes in CloudTran. For the isolator and managers, main() classes are provided, and you would normally use these to start the nodes rather than Coherence's DefaultCacheServer:
java -classpath ... cloudtran.start.StartManager
java -classpath ... cloudtran.start.StartIsolator
You can also call these as normal "main()" methods from other classes.

The client is different because it will be running its own application. So the client application must call the method
cloudtran.start.StartClient.init()


5.2.4  Custom Initialization
You can provide a class to do application-specific initialization across all three tiers (Client, Manager and Isolator).

To invoke this class, you specify the class name in the ct.init.user.class config property.

Copyright (c) 2008-2013 CloudTran Inc.