Page Comparison

...

Overview

To start the default runtime startup use the following command is used:

java -jar server.jar

a A single-VM instance will be created using the configuration specified in runtimes/vm. Alternative configurations can be used by specifying the runtime name as shown below. The runtime name will map to a configuration contained under the {{runtimes} directory directory:

java -jar server.jar controllernode  -- launches a runtime using the configuration under {{runtimes/controller}} 
java -jar server.jar participant -- launches a runtime using the configuration under {{runtimes/participant}}  
runtimes/node 
java -jar server.jar foo -- launches a custom runtime using the configuration under {{runtimes/foo image}} 

Note it is possible to run multiple runtime instances from a single disk image. In this case, the image will contain multiple configurations under the runtimes directory. Each instance can then be started by specifying the runtime name, for example:

java -jar server.jar foo
java - jar server.jar foo2

Startup Parameters

Clean

...

The clean parameter clears runtime state and removes any persisted information from previous runs. To start the runtime in clean mode, use the clean command parameter:

Code Block
java -jar server.jar clean

Note starting the runtime in clean mode will delete information stored in the data directory, including transaction recovery logs. 

Clone

For high-density clustered topologies such as cloud environments, Fabric3 provides the ability to clone runtimes. This allows new instances to be spawned from a configuration template using a single command without the need for manual setup. The clone parameter makes a copy of a runtime configuration template and boots the runtime using the copied configuration:

java -jar server.jar clone:template1 runtime1

Dir

The dir parameter is used to specify an alternative directory for the runtime configuration:

java -jar server.jar dir:/usr/fabric3/config/runtime1