Red Hat NETSCAPE DIRECTORY SERVER 6.01 - DEPLOYMENT Installation Guide download pdf (Page 133)

123

CHAPTER 28

Configuration Layouts

Third-party HTTP server + servlet engine

Third-party HTTP server with servlet engine serves HTTP requests from the DMZ, while Pramati

EJB Server serves EJBs from the host machine. In this scenario, Pramati Server-specific client.jar

must be in the classpath of the Servlet engine.

Independent Pramati Servers on the network

Hosting applications on multiple independent servers is the simplest of all Server configurations.

Suppose, Pramati Server is installed on the local host and remote host. In this scenario, you deploy

the complete application on each Server using the Deploy Tool.

Alternatively, you can prepare the application using the Deploy Tool, and distribute the prepared

archive (.par) to multiple Server instances using Pramati Server Management Console. However,

sessions are neither backed up nor shared among these Servers, and so load balancing and failover are

not available to such an application.

Configure the multiple Pramati Servers as Pramati Server Cluster Nodes for load balancing and

failover of the application.

To deploy applications across multiple Pramati Servers that are sharing a common external HTTP

server, install Pramati WebGate, the third-party HTTP server plug-in.

Java Client

Browser

Firewall

DMZ

Host

Internet

Http

Web

Server

JServer

Client.jar

EJB Container

Pramati Server

1 2 ... 128 129 130 131 132 133 134 135 136 137 138 ... 142 143

No comments

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