Installation guide

Pramati Server 3.5 Installation & Configuration Guide

require a symbolic link that is used to locate the rest of the application files without modifying the

script.

stopped for the halt, single-user, and reboot runlevels.

Configuring more than one Pramati Server Nodes

In the previous section we saw how to setup the Default Server as a service. We can also setup

multiple nodes as services. Setting up multiple nodes as services/daemon on Windows/Unix requires

editing the files in the

j2eeserver directory. Ensure that the node you want to configure as a

service is created first. A normal convention followed is to append the node name to the name of the

batch scripts.

For example, to install a node, myNode and run it as a service, rename the files as follows:

• install_server_MyNode.bat for Windows. For Unix based systems it would be the

pramatiserver.sh shell script

• remove_server_MyNode.bat, (only available for Windows). For Unix based systems, the

pramatiserver.sh shell script can be used to stop the daemon service using the stop switch.

• pramati_server_MyNode.conf.

The files form a set and are required to setup/remove the services. You should have all these files

separately available for different configurations of nodes hence, the convention of having the node

name at the end of the filename. Edit the

pramti_server_MyNode.conf by changing the

environment variable

set.node to the name of the node you wish to be installed as a service. In the

batch scripts above edit the environment variable

_WRAPPER.CONF to point to the correct

configuration file (in this case

pramati_server_MyNode.conf ). Here is the entry in the install

service batch script:

set _WRAPPER_CONF="%_APP_HOME%\j2eeserver\pramati_server_default.conf"

Note: Make sure you resolve all the conflicts that may arise due to communication ports such as the

naming port, etc., before installing a new service. Also, the naming convention of appending the node

name to the various files is not mandatory but recommended to avoid confusion.

Customizing Default Parameters

In the previous section we discussed setting up the server as a service. The service is started using

default parameters that are picked up from the configuration file

pramat_server_default.conf

which is present in the

j2eeserver directory. The file looks as below:

#********************************************************************

# Wrapper Properties

#********************************************************************

#EDIT following environment variables to suit local settings

set.JAVA_HOME=d:\jdk1.4.1\