What are the Various Hosting Scenarios?
Following are some typical client-server hosting scenarios:
- All installations on the host machine.
- Pramati Web Container in DMZ.
- Third party HTTP server replacing Pramati HTTP Server.
- Third party HTTP server and Servlet engine.
- Independent Pramati Servers on the network.
All Installations on Host Machine
In this scenario:
- Nothing exists in the De-militarized Zone (DMZ) behind the firewall.
- Pramati Server is on the host machine.
- Pramati Web Container handles all HTTP requests.
Pramati Web Container in DMZ
In this scenario, Pramati Web and EJB Servers are configured in two different zones:
- The Web container is in the DMZ and handles all the HTTP requests.
- The EJB container is on the host machine and serves EJBs.
Third-party HTTP Server Configured With Pramati Server
In this scenario, an existing third-party HTTP server is configured with Pramati Server. While Pramati Server serves dynamic content through EJBs and JSP pages, the HTTP server serves static HTML content.
The Administrators must install Pramati WebGate, the HTTP server plug-in facility, for Pramati Server to work with other HTTP servers.
Third-party HTTP Server and Servlet Engine
In this scenario, a third-party HTTP server with servlet engine serves HTTP requests from the DMZ, while Pramati EJB Container serves EJBs from the host machine. The administrators must place Pramati Server-specific client.jar in the classpath of the Servlet engine.
Independent Pramati Servers on Network
Hosting applications on multiple independent servers is the simplest of all Server configurations. Each Server is installed on the local host or a remote host. Say, 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 that ships with the Server.
Related Topics:
