InfoCenter Home > 7.3.1: OSE and remote OSEOSEOpen Servlet Engine (OSE) is a lightweight, proprietary protocol for transporting data. It is used by WebSphere to forward requests from the Web server to an application server for processing. OSE is configured though the Web server plug-in. It associates a uniform resource locator (URL) with one or more data queues. Each data queue is associated with an application server (and its clones) that is designated to service requests from that URL. Data can be sent through a variety of protocols, including pipes, Unix domain sockets, and TCP/IP sockets. OSE does not support data encryption between the Web server and the application server, although HTTPS requests can be used between a browser and the Web server. OSE (or local OSE) was originally designed to be used for transporting data on a single machine. It is the default mechanism for transporting data between between a Web server and an application server running on the same machine. Remote OSEAn extension to OSE enables it to be used to transport data remotely. Remote OSE can be used to enable communication between a Web server on one machine and application server clones that are running on one or more other machines in the system. Remote OSE uses only the TCP/IP protocol for transporting data between machines. All other OSE characteristics remain the same as in the local case, including the ability to route URLs to different application servers. Remote OSE supports WebSphere security. In a Remote OSE configuration, the Web server is physically separated from the application servers. The Web server sends requests that require intensive processing to other machines, enabling it to process more requests. There are no application server instances running on the machine that hosts the Web server, although Remote OSE currently requires the WebSphere Application Server software to be installed on the Web server machine. The OSERemoteConfig script is used to configure the Web server plug-in to enable Remote OSE. Remote OSE is the preferred method for redirecting client requests to servlet engine clones. It provides better performance than the servlet redirector. Remote OSE supports firewalls with Network Address Translation (NAT) and can be used in demilitarized zone (DMZ) configurations where the Web server runs on a secure server. It does not require database access through a firewall. Because the OSE transport does not support data encryption, Remote OSE is not suitable for configurations where data encryption is required between the Web server and the application server. Unlike other WebSphere Application Server internal IIOP traffic, Remote OSE does not implicitly use Secure Sockets Layer (SSL) when security is enabled. Article 7.1.3.6.1, Remote OSE sample topology, describes the Remote OSE configuration in more detail. Semi-remote OSE is a variant on the Remote OSE configuration. An application server instance runs on the same machine as the Web server; other application server instances run on remote machines. It is generally used when hardware limitations prevent the full Remote OSE configuration from being used. Article 7.1.3.6.2, Semi-remote OSE sample topology, describes the semi-remote OSE configuration in more detail. |
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|