Pramati Server 4.
Pramati Server 4.1 Installation & Configuration Guide ID 1230-034 April 2004 Pramati Technologies 301 White House, Begumpet Hyderabad 500 016 India info@pramati.com www.pramati.com Communications Design Group, Pramati Technologies. Made in India. Copyright 2002 Pramati Technologies. All rights reserved. Pramati is a registered trademark of Pramati Technologies in United States and India. Java and all Java based marks are trademarks or registered trademarks of Sun Microsystems, Inc.
i 1 Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 Document Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 Contact Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 2 System Requirements for Installing Pramati Server .
ii Pramati Server Management Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 Java Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 Third Party Integration with Apache/IIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 Configuring Components using Pramati Server Administration Service. . . . . . . . . . . . . .
iii Deleting Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 15 Configuring Message Server as a Standalone Node . . . . . . . . . . . . . . . . . 55 Configuring Standalone Message Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 Creating Standalone Message Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
iv 19 Using Pramati Server NodeCreator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81 Using NodeCreator with Command line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81 Using NodeCreator with XMLs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82 Using - configuration flag for custom node configuration . . . . . . . . . . . . . . . . . . . . . . . . . . .
v Starting JMS Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .112 Starting Web Load Balancer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .112 Offline preparation of client.jar. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .112 RemoteShell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
vi
1 Preface The Installation and Configuration Guide to Pramati Server 4.1 provides you with complete and detailed instructions for installing and configuring Pramati Server. It also introduces you to the important feature of the Server. Pramati Server installs with a Deploy Tool, the Console, and an embedded Message Server. Document Conventions The following conventions are commonly used in this guide.
2 Pramati Server 3.
System Requirements for Installing Pramati Server This document provides information about system requirements for installing and configuring Pramati Server 3.5 on Windows and Unix platforms. System Requirements Before you start installing Pramati Server, check for: • Hardware Requirements • Operating System Requirements • Software Requirements • Database Requirements Hardware Requirements The hardware requirements are: • Any hardware platform that supports Java with minimum 128 MB RAM (256 recommended).
2 Pramati Server 3.5 Installation & Configuration Guide • HP-UX 11i Software Requirements The JDK and Browser requirements are provided in the following sections. JDK Pramati Server has been tested on JDK 1.3.1_01 and above, including JDK1.4. Browser Pramati Server can be administered over the web using the Pramati Server Management Console. The Console has been tested with the following browsers that support HTML 3.2: • Internet Explorer 5.5 or above • Netscape 4.7 or above • Opera 5.
Chapter 2 System Requirements for Installing Pramati Server Using JDK If the J2EE application has JSP pages, which need to be compiled at runtime, JDK may be required on the host. This is a common scenario where only the deployment mapping XMLs are required to be in the EAR. If the application provider wants to permit re-mapping or modification of deployment information at the customer site, then JDK must be installed on the host machine.
4 Pramati Server 3.
3 Getting Server Install File Pramati Server can be downloaded as a binary from http://www.pramati.com/products. If you purchase a license with media and documentation, you will receive the product on a product distribution CD along with printed documentation. The Server is available as an executable (EXE) file for Windows users, and as a Java archive (JAR) file for Unix users.
6 Pramati Server 3.5 Installation & Configuration Guide Receiving License Key Normally, after the registration process is complete and the file is downloaded from www.pramati.com, an evaluation license key is send to the e-mail address specified by you during registration. If you have purchased the product and are installing from a product distribution CD, the license key is provided with the CD package in a printed license certificate.
Chapter 3 Getting Server Install File C:\PServer41_1127\server\bin>java.exe -Dinstall.root=C:\PServer41_1127\server -Djava.security.policy=C:\PServer41_1127\s pramati\pramati.java.policy -Djava.security.auth.policy=C:\PServer41_1127\server\lib\pramati\pramati.jaas.policy -Dorg.x ser=org.xml.sax.helpers.XMLReaderAdapter Dorg.xml.sax.driver=org.apache.crimson.parser.XMLReaderImpl com.pramati.
8 Pramati Server 3.
Installing Pramati Server on Unix-based Platforms To install Pramati Server on Unix based platforms: 1 Verify your existing system configuration against the requirements for Pramati Server. 2 Execute java -jar PServer41.jar from the directory where the installation file is downloaded (or from the CD, if you are installing from a product distribution CD). 3 The installation wizard starts and the license agreement appears.
10 Pramati Server 3.5 Installation & Configuration Guide 4 Execute rundeploytool.sh at the command prompt. This opens the ‘Connect to Server’ dialog box. 5 Provide the following information: • Server IP: Specify the Server IP or the host name where the server is running. For example, 192.168.1.36. • Naming Port: Specify the port on which the server is listening. For example, 9191 • User Name: Specify the username provided while configuring the realm.
Chapter 4 Installing Pramati Server on Unix-based Platforms 11
12 Pramati Server 3.
Installing Pramati Server on Windows To install Pramati Server on Windows: 5 Verify your existing system configuration against the requirements for Pramati Server. 6 Execute PServer41.exe from the directory where the installation file is downloaded (or from the CD, if you are installing from a product distribution CD). 7 The installation wizard starts and the license agreement appears. Read the license agreement.
14 Pramati Server 3.5 Installation & Configuration Guide Verifying Server installation 1 Open the command prompt and go to the directory /server/bin. 2 Run runserver.bat. 3 This starts the Server and brings up the j2eeadmin@default:> prompt. This prompt is used for performing Server administration and deployment tasks. 4 To shut down Server, type shutdown at the default prompt. The Server stops, and you return to the command prompt.
Chapter 5 Installing Pramati Server on Windows To exit the Deploy Tool, select Archive > Exit. You can also use the ‘Exit’ button provided. Verifying installation of Message Server 1 If you are verifying Embedded Message Server, open a command prompt and go to the directory /server/bin. Execute runserver command. 2 If you are verifying the Standalone Pramati Message Server, open a command prompt and go to the directory /jms/bin. Execute runjms.bat at the command prompt.
16 Pramati Server 3.
Silent Installation of Pramati Server Using XML To install the server silently, save the file PServer41.jar on your local machine on both Windows and Unix. Silent installation is especially useful in scenarios where the Server is being installed inside another application, and shipped to end users. There are two steps involved in silently installing Server: 1 Generating an XML file (using the PServer41.
18 Pramati Server 3.
Setting up Pramati Server as a Service Pramati Server can be installed as a service on Windows or as a daemon on Unix based systems. This helps the administrators in ensuring that the server is always available on system start. Pramati Server uses the Java Services Wrapper (version 3.0.5) to install Server as service on Windows or a daemon in Unix based systems.
20 Pramati Server 3.5 Installation & Configuration Guide 1 Run setup.bat script present in the /services/bin/ directory. This will set up the necessary environment to install the server as a service. 2 Change directory to /services/j2eeserver/ and run install_server_default.bat. This will install Pramati Server at node default as a service. Make sure the default node is created before executing this setup. > install_server_default.
Chapter 7 Setting up Pramati Server as a Service File Description \j2eeserver\pramati_ser ver_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 are logged here.
22 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. Register proper run levels, so that Pramati Server can be used for all multi-user run levels and 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.
Chapter 7 Setting up Pramati Server as a Service set.ps_root=D:\PServer411082 #Change the node name to install another server instance as a service. #The service will be registered with name PramatiServer (PramatiServerdefault for the following setting) set.node=default # Java Application wrapper.java.command=%JAVA_HOME%/bin/java #wrapper.java.command=C:/jdk1.3.1_03/bin/java.exe wrapper.java.mainclass=org.tanukisoftware.wrapper.WrapperSimpleApp # Application parameters.
24 Pramati Server 3.5 Installation & Configuration Guide from value 1. Make sure that the number parameters are in serial order without any missing numbers. To set the JVM Heap Size values, set values for the following parameters in the configuration files: # Initial Java Heap Size (in MB) equivalent to -Xms wrapper.java.initmemory=16 # Maximum Java Heap Size (in MB) equivalent to -Xmx wrapper.java.
Pramati Server Components Pramati Server is made up of the following configurable components: • Pramati Server Standalone node • Pramati Server Cluster EJB node • Pramati Server Cluster Web node • Pramati Server Cluster BOTH node (refers to a node that is both EJB and Web) • Pramati Server Cluster node • Pramati Server embedded Message Server • Pramati Server Standalone Message Server node • Pramati Server Load Balancer • Pramati Server Administration Service • Console • Java clients • Third Party integrat
26 Pramati Server 3.5 Administration Guide abstraction of a single processing server for operations such as configuration, tuning, deployment and monitoring. A Pramati Server Cluster node can be of three types: EJB, Web and BOTH. Pramati Server can be configured as a Standalone node or a Cluster node.
CHAPTER 8 Pramati Server Components Pramati Server Administration Service Pramati Administration Service can be secured through a username and password. Two services can communicate with each other only if both use identical username and password. Pramati Server Management Console The Console is customizable to suit server administration requirements. Through diagnostic and tuning aids, administrators can optimally deploy resources and extract maximum performance in any scenario.
28 Pramati Server 3.5 Administration Guide For details on using XMLs to configure the various components, read the chapter ‘Creating and Configuring Pramati Server Instances Using XMLs’. Where and how to configure each component Table 6: List of components of Pramati Server that are installed and can be configured Component Where Install Configure Pramati Server Administration Service Server machine Automatically installed as part of Server installation (PServerXX.exe or .
CHAPTER 8 Pramati Server Components Table 6: List of components of Pramati Server that are installed and can be configured Component Where Install Pramati Server Standalone JMS node (or Pramati Message Server) Server machine Installable available only on Configured using the Console. product CD. Run PMsgServerXX.exe or .jar. Pramati High Availability Message Server Server machine Installable available only on Configured from the Console. product CD. Run PMsgServerXX.exe or .jar.
30 Pramati Server 3.
Adding a User and Changing Password After installing the Pramati Server, you may want to add users and change the default password. For information on how to add and configure Groups and Realms, read the chapter ‘Configuring Security for Pramati Server’ in the Pramati Server 4.1 Administration Guide. Adding User To add a user using the Console: 1 Start and connect to Server. 2 Connect to the Administration console using a browser by typing the URL http://:/admin/.
32 Pramati Server 3.5 Security Guide Deleting User A user can be deleted specifically from a group, or can be completely removed from the Server. To delete a user from a specific group: 1 Click the required group. The list of existing users and permissions appears in the Group page. 2 Select the user to be deleted from the list using the checkbox, and click ‘Delete’. This deletes the selected user from just the selected group.
Chapter 9 Adding a User and Changing Password Changing password for User Under the ‘Groups’ section, click ‘All Users’. This takes you to the ‘Security > Realm > Users’ screen. Click ‘Settings’ for the user for which the password is to be changed.
34 Pramati Server 3.
Introduction to Pramati Server Administration Service Pramati Server is configured and started using the Server Administration Service.
36 Pramati Server 3.5 Administration Guide How does Server Administration Service work The Admin Service keeps track of other services running on the LAN using a discovery mechanism, that enables you to manage server configuration from a single administrator host machine. Starting Server Administration Service To start the Server Administration Service: 1 Choose Start > Programs > Pramati 4.1 > Server Administration.
Configuring Standalone Pramati Server Using Admin Service This section talks about starting the Default Server on Unix and Windows, as also configuring a Standalone Pramati Server using the Server Administration Service. Using Default Server When you install the Server, a default configuration is created that appears in the list of managed Servers as default. The Default Server starts if you do not specify another server.
38 Pramati Server 3.5 Administration Guide Creating Standalone Server To create a Standalone Server using the Server Administration Service: 1 Start the Server Administration Service. Read ‘Using Pramati Server Administration Service’ for details. 2 Click Standalone Server in the Explore panel. The ‘Add Standalone Server’ page appears in the Display panel.
CHAPTER 11 Configuring Standalone Pramati Server Using Admin Service Viewing details of added Standalone Server To view the details of the added server, click its name that is provided as a link on the Home page. This takes you to the ‘Home > Server’ screen showing the following details: Configuring Standalone Server To configure (verify or modify) the details for the added server, click on the configure button provided.
40 Pramati Server 3.5 Administration Guide 4 Provide the following details: Table 10: Details needed for starting a Standalone Server Fields Description Realm Provide here the Realm name. By default, this appears as system. This is a mandatory field. Username Provide here the Username for the specified Realm. By default, this appears as root for the system Realm. This is a mandatory field. Password Provide here the password for authenticating the Username.
CHAPTER 11 Configuring Standalone Pramati Server Using Admin Service 41
42 Pramati Server 3.
Adding Web Load Balancer using Administration Service Pramati Server provides a software based load balancing solution. It is implemented as an Interceptor which is a part of the Interceptor stack in the Pramati Web Container. Configuring the Load Balancer is as simple as adding entries into the web-lbconfig.xml file. Pramati Server’s Load Balancer intelligently distributes load among a group of nodes.
44 Pramati Server 3.5 Administration Guide • RD for High Availability • RD for Load Balancer and High Availability Case 2 The node which runs the Request Dispatcher, would also be serving some request. Typical Setup: • The request dispatcher allows plug-ins to be written for Pramati Server • RD with default URI/Failover/Session stickiness plug-in, which allows forwarding requests based upon URI: Case 3 A pure Request Dispatcher for various machines based upon URI.
CHAPTER 12 Adding Web Load Balancer using Administration Service Case 4 Request Dispatcher working along with a Pramati Plug-in for Apache/IIS to enable distribution of the load to backend Pramati Servers. Pramati Server WebGate communicating with the Request Dispatcher, which distributes load and provides failover facility. Adding a Load Balancer node To add a Load Balancer node: 1 Start the Server Administration Service. 2 Click ‘Load Balancer’ in the Explore panel.
46 Pramati Server 3.5 Administration Guide 3 Enter the following details: Table 11: Details needed for configuring a Load Balancer Fields Description Name Name for the Load Balancer, say, Demo_Load Balancer. Host The Host machine name (IP) on which the Load Balancer is to be configured, say, 192.168.1.143. This can be any machine in the LAN where the Server Administration service is running. Lookup Port The Lookup Port on the host machine on which the Load Balancer will start, say 9191.
CHAPTER 12 Adding Web Load Balancer using Administration Service You can modify details for lookup port, HTTP Port, HTTPS Port and Enable HTTPS fields. Save the modifications made. Viewing Load Balancer details To view the details for the Load Balancer, click its name which is provided as a link on the Service page. This takes you to the ‘Home > Load Balancer’ screen. Starting Load Balancer To start the Server: 1 On the Server Administration Service main page, click ‘Start’ against the required server.
48 Pramati Server 3.5 Administration Guide Table 12: Details needed for starting a Server Fields Description Password Provide here the password for authenticating the user name. For the user name ‘root’, the default password is ‘pramati.’ JVM options Provide here the JVM options, if you want to pass any Java options. Connecting to Load Balancer To connect to the Server: 1 Once you have started the Server, the started Server is shown as a blue icon, and ‘Start’ is replaced by a ‘Connect’ button.
Configuring Web Load Balancer Using XML A Load Balancer works as a web-request dispatcher, distributing the web requests across a set of Web/J2EE Cluster nodes. In advanced configurations, it distributes the web requests even across non-cluster server instances and multiple vendor’s servers. Load Balancing for EJB clusters is done at the container level and does not need any external configuration. A Load Balancer is a variant of Web node.
50 Pramati Server 3.
Configuring J2EE Cluster Using Server Administration Service All cluster configuration details are maintained in a database as well as in the configuration files. Pramati Server provides the following ways to configure J2EE Clusters: Using Server Administration Service • Using Command Line (read the chapter) • Modifying XMLs Configuring J2EE Cluster To configure a J2EE Server Cluster using Server Administration Service: 1 Start the Server Administration Service.
52 Pramati Server 3.5 Administration Guide Table 14: Step 1 of adding a J2EE Cluster Fields Options Description Table Provide a table name for the database, say ‘emp’. This is a mandatory field. Click Next>>. ‘Step 2 of 3: Add Nodes’ page appears. Table 15: Step 2 of adding a J2EE Cluster Fields Description EJB, Web Specify the type of the node. This can be EJB or Web. You can also select both the types. Name Specify the name of the node. Say, ‘MyNode’.
CHAPTER 14 Configuring J2EE Cluster Using Server Administration Service • Configure nodes for Lookup, HTTP and HTTPS Port values. • Add new nodes to the cluster by providing values as Name, Type, Host, Lookup, HTTP and HTTPS Port values. • Delete existing nodes. • Edit the failover details for the Cluster. Click ‘Save’. Starting Cluster To start the cluster: 1 On the Server Administration Service, click ‘Start’ against the required cluster under J2EE Server Clusters section.
54 Pramati Server 3.5 Administration Guide 1 Start and connect to the cluster node. 2 Click Start > Programs > Pramati 4.1 > Deploy Tool. The ‘Connect To Server’ window appears, 3 4 5 6 and asks you to enter the password for the realm ‘system’ and user name ‘root’. The default password to be entered is ‘pramati’. Click ‘Connect’. The Deploy Tool UI appears. Click Archive > Open. Browse to the location of the application that is to be deployed.
Configuring Message Server as a Standalone Node The Standalone Message Server can be installed and configured separately from the J2EE Server using the Server Administration Service. Configuring Standalone Message Server This section describes the steps to create, modify and remove a Standalone Message Server using the Server Administration Service.
56 Pramati Server 3.5 Administration Guide You can modify details for the Lookup Port (mandatory field), while the Host address is shown as a non-editable field. Save the modifications made. You can even start the specific Server from this page using the ‘Start’ button. Starting Standalone Message Server To start the Server: 1 On the Server Administration Service Home page, click ‘Start’ against the required Standalone Message Server.
CHAPTER 15 Configuring Message Server as a Standalone Node Stopping Standalone Message Server To stop a connected Standalone Message Server, click ‘Stop Server’ on the Console. To exit from the Console, click ‘Logout’. In the Server Administration Service Home page, the ‘Connect’ option changes back to ‘Start’. Note: You must refresh the main page to verify the status. Removing Standalone Message Server You can remove a Standalone Message Server only if it is not running.
58 Pramati Server 3.5 Administration Guide In the above: • queue: Refers to the name of the queues using the loaded send feature, specified as comma separated values. • minruntimesize: The minimum number of messages maintained in-memory. Messages are loaded from the temporary table when the number of messages go below the minimum size as specified in the loadedsend.props file. • maxruntimesize: The maximum number of messages maintained in-memory.
CHAPTER 15 Configuring Message Server as a Standalone Node The command runserver -node also helps in creation of a new node. Understanding Message Server Configuration All the above operations can be performed by changing the default configurations in the JMS configuration file jms-config.xml. This section provides an overview of how the configuration file can be modified for configuring a standalone Message Server.
60 Pramati Server 3.5 Administration Guide The Server provides a way of configuring this persistence type by exposing certain properties in the jms-config.xml file. If your system does not involve handling any persistent message, you don’t need to configure any value. With the following tags, we can configure persistence in JMS Server. The tag is part of the of the jms-config.
CHAPTER 15 Configuring Message Server as a Standalone Node delivery-mode’, then if the server receives any persistent messages, then it overrides the delivery mode from persistent to non-persistent. If the policy is ‘throw exception’, then for each persistent message that it receives, it will throw the exception indicating that the persistent messages are not allowed when persistence is disabled.
62 Pramati Server 3.5 Administration Guide Table 18: Persistence Framework Default Values Property Default Value Persistence Type File Store Message Dir.
Starting a Server Node Using Command line The command to start Standalone J2EE Server, a J2EE Server Cluster or Message Server node is same. To start a Standalone Message Server using Command line: 1 Open a command window at /server/bin 2 Execute: runserver -node 3 Specify the Server node name in that you have created. Note: For a Message Server node, ensure that JMSService is enabled in server-config.xml, located at [server_install]/server/nodes//config.
64 Pramati Server 3.
Configuring Message Server Cluster Using Server Admin Service Pramati Server provides the following ways to configure Message Server Cluster: • Using the Server Administration Service • Modifying XMLs Before configuring the cluster, the Message Persistence tables should be created. Run the scripts in /jms/templates. You can modify the table names in the scripts to match the names specified for the four message persistence tables.
66 Pramati Server 3.5 Installation & Configuration Guide Table 19: Step 1 of adding a Message Server cluster Fields Options Description User Name This is the username used to access the selected database. For example, if the database selected is Oracle, the user name can be ‘scott’. Password This is the password required to access the selected database. For example, if the database selected is Oracle, the password can be ‘tiger’.
Chapter 17 Configuring Message Server Cluster Using Server Admin Service Table 20: details needed for Adding a Message Server cluster node Fields Description Host This is the name of the machine where the node will be configured (say, ‘localhost’ or ‘192.168.1.12’). The node can be configured on any machine in the local LAN where Administration Service is running. Lookup Port The port on which the node's Naming Service will be started. Say, ‘9191’. Click ‘Next >>’.
68 Pramati Server 3.5 Installation & Configuration Guide Viewing Message Server node details To view details about a Message Server node, click ‘Configure’ against the Message Server Cluster name on the Server Administration Service Home page. This displays the ‘Home > Message Server Cluster’ page, displaying all the nodes of the selected Message Server Cluster. In the Nodes section, click on the name of the selected node whose details are to be viewed.
Chapter 17 Configuring Message Server Cluster Using Server Admin Service To stop a connected node of a Cluster, use the ‘Stop’ option provided after selecting the node on the Console. Deleting Cluster You can delete a cluster only when it's status is stopped. To delete a cluster, select it using the checkbox provided, and click ‘Delete’.
70 Pramati Server 3.5 Installation & Configuration Guide Table 21: Cluster types supported by Pramati Server Node Type Description Web If a cluster node is defined as Web, only the Web container is started. EJB components are not available on this node. Select this option when the application has only JSPs and other Web components. A standalone Web node can act as a EJB Load Balancer. EJB If a cluster node is defined as EJB, only the EJB container is started.
Creating and Configuring Pramati Server Nodes Using XML Overview Pramati Server instances can be configured manually by modifying the configuration XML files. Server instances of type J2EE, Message Server and Cluster can be manually created with simple configuration in the XML files. This section describes the structure of a Server instance and discusses the procedure to create different types of Server instances in Standalone and Cluster scenarios.
72 Pramati Server 3.5 Administration Guide Table 22: Terminology Term Description Cluster A logical server comprising a group of underlying nodes forming a single entity that internally works with a collection of nodes. Cluster Node Server instance that serves as a node of a cluster J2EE Cluster A cluster with both EJB and WEB Nodes J2EE Node A Server instance that serves as a node serving both Web and EJB requests.
CHAPTER 18 Creating and Configuring Pramati Server Nodes Using XML Table 23: Pramati Server configuration files Configuration File Description logging-config.xml Logging parameters like rotation type, max file size and rotation time are configured here. security-config.xml Contains information about security providers, security policy, certification manager and realm. web-cache.xml Contains dynamic cache configuration.
74 Pramati Server 3.5 Administration Guide • EJB Node • Load Balancer Node The Server Cluster J2EE Node has both Web and EJB services enabled in server-config.xml file. A node can be configured to as a Standalone Message Server by disabling other services like EJB and Web—as long as there are no inter-service dependencies. The type of server instance is determined based on the specific services that are enabled through the Pramati Services Framework. Details are discussed in the following sections.
CHAPTER 18 Creating and Configuring Pramati Server Nodes Using XML -logs (Stack traces and log messages for the node are stored here) -archives (This directory holds all extracted application archives -temp (A temporary directory) Procedure for creating Pramati Server Instances Server instances are created in the ‘nodes’ directory of a Pramati Server installation. There will be one DIR for each server instance (in case of Standalone servers) and one for each cluster-node in case of Cluster.
76 Pramati Server 3.5 Administration Guide Configuration File Dependency Table 24: Configuration files needed for Server Instances Configuration HA Standalone File Standalone J2EE (BOTH) Web Cluster Message Message Cluster Node Node Server Server Server Node EJB Cluster Node Load Balancer serverconfig.xml Required Required Required Required Required Required Required resourceconfig.xml Required Required Can Have Required Required Can Have - webconfig.
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 INSTALLDIR/server/templates to the configuration directory created above. The specific files needed are listed in Table 2 provided in the following section.
78 Pramati Server 3.5 Administration Guide name="default-mdb-max-pool-size" value="1000" /> name="default-low-activity-interval" value="60" /> name="default-session-timeout" value="1000" /> name="smart-code-generation" value="true" /> Enabling embedded Message Server in a Standalone Server For enabling embedded Message Server for a Standalone Server follow the general instructions as given above for creating a Standalone Server.
CHAPTER 18 Creating and Configuring Pramati Server Nodes Using XML class-name="com.pramati.web.WebServer"> Creating Standalone Message Server For a Standalone Message Server, enable the JMS Service in the server-config.xml: jms-config.
80 Pramati Server 3.
Using Pramati Server NodeCreator The NodeCreator is a utility for creating or removing nodes and clusters. You can configure and use the NodeCreator with both the command line and XMLs. Using NodeCreator with Command line To run the NodeCreator: Run NodeCreator.bat (for Windows) or NodeCreator.sh (for Unix) located at / server/bin/. Execute java com.pramati.
82 Pramati Server 3.5 Administration Guide Example for creating a J2EE cluster java -Dinstall.root=. com.pramati.NodeCreator -createj2eecluster -name my node1,mynode2 -namingport 9191,9292 -httpport 8181,8282 -clustername mycluster The help snippet that shows up on the command shell is as follows: Usage: java com.pramati.NodeCreator [operation] [option value] [flag] Using NodeCreator with XMLs You can create a node or cluster using the config-topology-standalone-template.
CHAPTER 19 Using Pramati Server NodeCreator If you wish to create a J2EE Cluster, locate the tag in the config-topologycluster-template.
84 Pramati Server 3.5 Administration Guide
