Installation guide

Pramati Server 3.5 Administration Guide

<node-id>001</node-id>

</node>

Here, when node-type is J2EE, enabling the cluster service would make it a J2EE Cluster. A J2EE

Cluster can be of type BOTH (both ejb and web) or just EJB/Web.

J2EE Cluster cannot start with Message Server in an embedded mode and a Message Server cluster

cannot have EJB or Web Containers enabled. If node-type is "JMS", then it becomes a HA Message

Server cluster.

Once cluster is enabled in server-config.xml, define the cluster topology and properties in the

cluster-config.xml. Specify cluster nodes, topology, persistence (EJB/Web) and Load Balancer

here.

J2EE clustering can involve both EJB and Web clustering. However, Web and Message Server

instances cannot exist in a single cluster. The cluster solution is based on a common cluster

backbone called Cluster service, which also runs on the Pramati Services framework.

Pramati Cluster being a self-organizing, non master-slave homogeneous cluster, does not have a

separate entity for cluster housekeeping or processing. Based on the shared persistence store, the

cluster runtime in each cluster node jointly perform all the housekeeping and operational tasks.

Uploading Configuration to DB when DB is used for Configuration Persistence

To upload the configuration into the database in case of DB persistence for cluster configuration,

start the node for the first time using the following command:

com.pramati.Server -node <NODENAME> -uploadconfig

The rest of the nodes would automatically pick up the configuration and do not need to be started

with this option. To update the database after making changes in the configuration, start the cluster

node with the following startup option:

com.pramati.Server -node <NODENAME> -updatelocalconfig

This option would update all of the configuration files. Only this node needs this option and the

rest would automatically use updated configuration. To update specific configuration changed

manually, start cluster node with the following startup option:

com.pramati.Server -node <NODENAME> -updatelocalconfigfor

<SERVICENAME>[,<SERVICENAME>]

Only this node needs this option and the rest would automatically use updated configuration.

Creating a Cluster Instance

The cluster definition is essentially defined along with the first cluster node, and the same common

persistence information and cluster details should be setup in all the other nodes that form a part of

this cluster. The steps involved in creating a cluster are:

1 The DIR and the config files should be setup just as one would setup a Standalone instance.