 |
 |
 |
 |
|
|
 |
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.
Table 1: Terminology
| Term | Description |
| Installation | Pramati Server product installation. |
| Install-Dir | The directory under which Pramati Server is installed. |
| Nodes Directory | The directory under which all configured server instances exist. |
| Server | The installed server with default settings. |
| Server Instance | An instance of a Pramati Server- of any type (J2EE, Web cluster node, EJB cluster node, Message Server) will normally run in one VM. |
| Standalone Server | An instance that is a self contained J2EE Server running in a single VM. |
| Instance Directory | The directory under the Nodes Directory that holds the configuration and other files/information for a Server Instance. |
| Message Server | An instance which functions as a Standalone Message Server. |
| Embedded Message Server | Full featured Message Server that runs inside a Standalone Server instance. |
| JMS Adapter | JMS Adapter is setup in a J2EE Server instance determining the connectivity to a Message Server (Embedded or external Standalone Message Server or HA-Message Server). |
| Cluster | A logical server comprising a group of underlying nodes forming a single entity that internally works with a collection of nodes. |
| Cluster Node | A 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. It can exist as a part of a J2EE Cluster. |
| BOTH Node | Same as J2EE node. |
| Web Cluster | A cluster of Web nodes. |
| Web Node | A Server instance that serves as a node serving Web requests alone. It can either exist as part of a J2EE Cluster or a Web cluster. |
| EJB Cluster | A cluster of EJB nodes. |
| EJB node | Server instance that serves as a node serving EJB requests alone. It can either exist as part of a J2EE Cluster or a Web cluster. |
| Message Server Cluster | A cluster of Message Server Nodes. |
| HA Message Server | Message Server Cluster that only supports failover, and not Load Balancing (as of 4.1, Message Server Cluster is only HA Message Server). |
| Message Server Node | A Server instance that serves as a node serving Message Server requests alone. |
| Load Balancer | A request dispatcher for managing requests. |
| Configuration | Modifying the default settings for the Server. |
Each Pramati Server node starts in its own JVM. Attributes of the node -sizing, runtime behavior, and performance -are defined by the configuration of the server and specified in a set of server configuration files (XMLs).
<install_dir>\server\bin and execute runserver.bat -node <node_name> on Windows or runserver.sh -node <node_name> on Unix.
In case a node does not exist with the given name, the following message is displayed:
Node [node_name] does not exist,
Press enter to create node [sa2] 'q' to exit #
Enter the values prompted for, such as:
Enter naming port:
Press enter for default value [9191] #9292
Enter http port:
Press enter for default value [8181] #8282
<install_dir>\server\bin and execute runserver.bat -type jms on Windows or runserver.sh -type jms on Unix. A JMS node with the name jmsdefault is created and gets started.
Related Topics:
 |
|
| © Pramati Technologies 2007 | Runs on Pramati Server | Feedback | Legal |