How do I set up Pramati Server as Daemon on Unix?

To setup Server as a daemon on Unix, execute the shell script ./pramatiserver.sh. Confirm you have the following files that are shipped with the distribution:

Table 1: List of files that are shipped with the distribution

File Description

\bin\license.txt A text file describing the copyrights of the use of the Wrapper Service. This is provided by TanukiSoftware.org.

\bin\libwrapper.so A library file.

\bin\Wrapper An executable file that is invoked to install the Java application as a service.

\bin\wrapper.jar The Java Services Wrapper classes are present in this executable *.jar file.

\j2eeserver\pramatiserver A shell script that starts the Server as a Daemon.

\j2eeserver\pramati_server_default.conf A configuration file used to launch the Server with pre-defined startup parameters like setting classpath, JVM options etc.

\j2eeserver\wrapper.log A log file for the Java services wrapper. All communication between the services wrapper classes and Pramati Server is logged here.

To start the Server as a daemon, run the shell script pramatiserver located at <install_dir>\services\j2eeserver\ directory.

$./pramatiserver start Starting @Pramati J2EE Server V 5.0@...

The script pramatiserver can be run in the following modes:

Table 2: List of modes in which pramatiserver script can be run

Mode Description

console When a wrapper is started in console mode, the server starts as the child process of console. You cannot exit from the console until the Server is stopped using wrapper stop command. You can see the output of the wrapper program on the console in this mode, and hence should use it to debug setup problems.

start When wrapper is started in ''start'' mode, the Server is launched as a detached process. When running as a detached process, you will immediately regain control of the Console used to launch the wrapper. You can also close the Console while the Console and the wrapper keep running. In this mode the wrapper's output is in wrapper.log located at bin/ dir. In both modes Pramati Server's output is redirected to stdOut.log in logs/ dir.

dump Irrespective of the mode server is started in you can request for a "Thread Dump" by adding the dump attributes.

The shell script looks for the wrapper program in the bin directory and for pramati_server_default.conf in the current directory and starts the Server.

To stop the Server, click Stop.

To know more about other parameters for this script, use the help command: $ ./pramatiserver help Usage: ./pramatiserver {console | start | stop | restart | dump}

File	Description

\bin\license.txt	A text file describing the copyrights of the use of the Wrapper Service. This is provided by TanukiSoftware.org.
\bin\libwrapper.so	A library file.
\bin\Wrapper	An executable file that is invoked to install the Java application as a service.
\bin\wrapper.jar	The Java Services Wrapper classes are present in this executable *.jar file.
\j2eeserver\pramatiserver	A shell script that starts the Server as a Daemon.
\j2eeserver\pramati_server_default.conf	A configuration file used to launch the Server with pre-defined startup parameters like setting classpath, JVM options etc.
\j2eeserver\wrapper.log	A log file for the Java services wrapper. All communication between the services wrapper classes and Pramati Server is logged here.

Mode	Description

console	When a wrapper is started in console mode, the server starts as the child process of console. You cannot exit from the console until the Server is stopped using wrapper stop command. You can see the output of the wrapper program on the console in this mode, and hence should use it to debug setup problems.
start	When wrapper is started in ''start'' mode, the Server is launched as a detached process. When running as a detached process, you will immediately regain control of the Console used to launch the wrapper. You can also close the Console while the Console and the wrapper keep running. In this mode the wrapper's output is in wrapper.log located at bin/ dir. In both modes Pramati Server's output is redirected to stdOut.log in logs/ dir.
dump	Irrespective of the mode server is started in you can request for a "Thread Dump" by adding the dump attributes.


© Pramati Technologies 2007	Runs on Pramati Server \| Feedback \| Legal