Installation guide

114
Pramati Server 3.5 Installation & Configuration Guide
The command list_system_properties from j2eeshell lists all properties with values. Running “help”
or “shelp” gets more information in Shell.
Starting RemoteShell
The remote shell for Server can be started using one of the following commands:
• java com.pramati.RemoteShell -ip <ip> -port <port> -realm <realm> -user <user> -password
<password>
• java com.pramati.RemoteShell -file <fileName> filecontents connect -ip <ip> -port <port> -realm
<realm> -user <user> -password <password>
List of all start up options to start Pramati Server
These startup options apply for both Server versions.
-Dcom.pramati.rmi.enablepassbyreference=true (enable pass by
reference for intra VM calls)
-Dcom.pramati.application.preferdeployedclasses=application
-Dcom.pramati.application.preferdeployedclasses=web-module
-Drunning_in_tomcat_mode=true (Tomcat spec-deviation toler-
ance)
-Dcom.pramati.web.logging=true(enable web logging)
Table 9: Startup options
Option Purpose
-verbose runs Server in verbose mode
-startapps starts all applications deployed
-redirect redirects standard output
-noshell does not start the shell, starts by default. This is new in Version 4.1.
-user user name to start Server
-password password to start Server
-realm realm to start Server
-cleanupapps cleans up corrupt app directories, if any
-traceprops properties to enable tracing for Server start, argument the trace props file
-testJDBCResources tests all JDBC resources during Server startup
-nodedir(argument) directory of Server node, to be used if the default directory is not used
-uploadconfig relevant only for a cluster node.uploads the configuration of the node to the database.
Table 8: System Properties
3.0 4.1