Migrating from Pramati Server 3.0 to Pramati Server 3.5
Overview
Pramati Server 3.5 has provided a number of new features and enhanced functionality. There have been a number of changes in the internal architecture between the Pramati Server 3.0 and Pramati Server 3.5. Specifically, configuration of the server has been more improved and provides different configuration files for configuring parts of the server. The deployment of applications, however, hasn't changed much. In this chapter we will list the specific areas that have changed and that will help in migrating from Pramati Server 3.0 to Pramati Server 3.5. In particular, we will discusses the following:
- Command line changes for starting various servers
- Offline preparation in creating client jars
- Remote Shell
- Command Line Operations
- Shell Commands
- System Properties
- Starting Remote Shell
- Startup Options
- Server Configuration XMLs
- Handling RARs
Starting the Servers
Starting J2EE Server
Table 1:
|
3.0
|
3.5
|
|
com.pramati.J2eeServer
|
com.pramati.Server -node <j2ee_node_name>
(J2EE node is also the default node, with no -node argument)
|
Starting JMS Server
Table 2:
|
3.0
|
3.5
|
|
com.pramti.JMSServer
|
com.pramati.Server -node <jms_node_name>
|
Starting Web Load Balancer (introduced in Version 3.5)
Table 3:
|
3.0
|
3.5
|
|
Not Available.
|
com.pramati.Server -node <lb_node_name>
|
Offline preparation of client.jar (introduced in Version 3.5)
Table 4:
|
3.0
|
3.5
|
|
|
com.pramti.ejb.gen.ClientJar <path of app>
|
RemoteShell
Table 5:
|
3.0
|
3.5
|
|
com.pramati.RemoteShell
|
com.pramati.RemoteShell
|
Command Line Operations
Table 6:
|
3.0
|
3.5
|
|
- shell
|
-shell is default. Use -noshell for disabling shell
|
|
-config %APPSERVER_HOME%\nodes\StandAlone\
<nodeName>\config\server-config.xml
|
-node <nodeName>
|
|
-nojms
|
This option has been moved to server-config.xml.[ <service name="JMSService" enable="false">]
|
|
-keep
|
This has been moved to deploy-config.xml [<retain-generated-java-files>true<</retain-generated-java-files>]
|
|
|
com.pramati.Launcher (Server launcher)
|
|
|
com.pramati.NodeCreator (creates nodes for a Cluster)
|
Shell Commands
Table 7:
|
Shell
|
3.0
|
3.5
|
|
j2eeshell
|
shutdown
|
shutdown, shutdown <time_to_wait> [after this time system.exit will be called]
|
|
ressh
|
adddatasource
|
add_datasource
|
|
|
removedatasource
|
remove_datasource
|
|
|
addjmsserver
|
add_jmsadapter
|
|
|
removejmsserver
|
remove_jmsadapter
|
|
|
addconnfactory
|
add_jca_cf
|
|
|
removeconnfactory
|
remove_jca_cf
|
|
|
addmailresouce
|
add_mailresource
|
|
|
removemailresource
|
remove_mailresource
|
|
|
|
add_jdbc_cf
|
|
|
|
remove_jdbc_cf
|
|
|
|
add_urlresource
|
|
|
|
remove_urlresource
|
System Properties
Table 8:
|
3.0
|
.35
|
|
-Dcom.pramati.ejb.nolockbmp=true
|
-Dcom.pramati.ejb.nolockbmp=true
|
|
-Dcom.pramati.useMultipleClassLoaders=true
|
Moved to deploy-config.xml [ <classloader-for-multiple-apps enabled="false">]
|
|
|
-Dcom.pramati.naming.uselocalcontextfactory=true (to use local context factory for intra VM calls)
|
|
|
-Dcom.pramati.ejb.poolwaittimeoutseconds=20 (maximum time a request would wait for an EJB instance)
|
|
|
-Dcom.pramati.ejb.enablefreepool=true (use free pool for EJBs)
|
|
|
-Dcom.pramati.ejb.loadfromdbatstart=true (loads bean with transaction)
|
|
|
-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 tolerance)
|
|
|
-Dcom.pramati.web.logging=true(enable web logging)
|
The command list_system_properties from j2eeshell lists all properties with values. Running "help" or "shelp" gets more information in Shell.
Starting RemoteShell
- 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 (3.0 & 3.5)
Table 9:
|
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 3.5.
|
|
-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.
|
New Server Configuration XMLs in Version 3.5
The server-config.xml in Version 3.0 has been split up into the following sub-configuration files:
- server-config.xml for configuring the service information.
- individual service config XMLs for configuring individual services.
All types of Server nodes always run off server-config.xml instead of the earlier separate central configurations. To recall, in Version 3.0 the embedded JMS server had emb-jms-config.xml, the cluster node had cluster-config.xml as the central configuration stores.
New Service Configurators and other XMLs in Version 3.5
- deploy-config.xml
- jms-config.xml
- ejb-cache.xml
- resource-config.xml
- web-config.xml
- management-config.xml
- dashboard.xml
- history-collector.xml
- alerts-config.xml
- logging-config.xml
- web-cache.xml
- web-lbconfig.xml
New configuration tags in deploy-config.xml
Table 10:
|
New Tag
|
Purpose
|
|
<application-hooks>
|
for per application hooks
|
|
<classloader-for-multiple-apps enabled="false">
|
for using single classloader for group of applications
|
|
<application-properties versioning-enabled="true">
|
for versioning of applications
|
|
<out-of-process-compilation enabled="false">
|
for out of the process compilation
|
|
<auto-deploy>
|
the path of the auto deploy directory
|
|
<startup-hooks>
|
for Server hooks
|
Handling of RARs
- connector-config.xml has been removed. The contents are now in pramati-j2ee-server.xml.
- You can now configure test parameters through Shell while creating a JCA connection factory. You can also configure test parameters through pramati-j2ee-server.xml.
