Red Hat NETSCAPE DIRECTORY SERVER 6.01 - DEPLOYMENT Installation Guide Page 87

  • Download
  • Add to my manuals
  • Print
  • Page
    / 143
  • Table of contents
  • TROUBLESHOOTING
  • BOOKMARKS
  • Rated. / 5. Based on customer reviews
Page view 86
77
CHAPTER 18
Creating and Configuring Pramati Server Nodes Using XML
- config
- the other directories described in the ‘Structure of Nodes Directory’ above will be automatically
created after the instance starts up.
Depending on the type of instance needed, copy the required config files from the INSTALL-
DIR/server/templates to the configuration directory created above. The specific files needed are
listed in Table 2 provided in the following section.
Edit the configuration XML to setup the information as described in the following sections.
Make sure that the cluster service is disabled in server-config.xml
<service name="ClusterService" enabled="false"
class-name="com.pramati.cluster.PramatiClusterService">
The instance can be started using -node option.
A Instance can be created by just creating a directory with an unique name under server/nodes
directory. Once the directory is created, create another directory called config and copy
server-
config.xml and other configuration files required for the Standalone Server (as described in
Tab le 2) from the templates directory to config. Once the node directory is created, you can activate
the Instance using -node command.
The same process can be followed for all the instance types including Message Server instances.
Once the Standalone J2EE Server is setup, based on the type selected, setup the basic attributes of
the Web and EJB Containers. In the
server-config.xml, change the values as needed:
<service name="WebContainer" enabled="true"
class-name="com.pramati.web.WebServer">
<config-file>web-config.xml</config-file>
<requires always="NamingService,DeployService" />
<property name="http-port" value="8181" />
<property name="https-port" value="443" />
<property name="ssl-enabled" value="false" />
</service>
Default value of HTTP port, and HTTPS port can be set now.
For EJB, in server-config.xml, the default pool size and session time-out value can be modified.
<service name="EJBContainer" enabled="true"
class-name="com.pramati.ejb.EJBContainer">
<requires always="NamingService,TransactionService,
DeployService" />
<property name="default-entity-min-pool-size" value="40" />
<property name="default-entity-max-pool-size" value="1000" />
<property name="default-session-min-pool-size" value="40" />
<property name="default-session-max-pool-size" value="1000" />
<property name="default-mdb-min-pool-size" value="40" />
Page view 86
1 2 ... 82 83 84 85 86 87 88 89 90 91 92 ... 142 143

Comments to this Manuals

No comments