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

  • Download
  • Add to my manuals
  • Print
  • Page
    / 143
  • Table of contents
  • TROUBLESHOOTING
  • BOOKMARKS
  • Rated. / 5. Based on customer reviews
Page view 114
23
Configuring Pramati Server For Firewalls
In typical deployment scenarios, servers are located behind firewalls and any RMI transport
layer that attempts to open direct sockets to hosts on the Internet will not be allowed to do
so. The default RMI transport provides two alternate HTTP–based mechanisms that
enable a client to invoke a method on a remote object residing across the firewall. These are:
HTTP tunneling when the RMI call is within the HTTP protocol
Using the default socket factory
This section contains information about:
HTTP tunneling (Port Filtering firewalls)
•Configuring the client
Configuring the RMI Server
Working with NAT firewalls
Default Socket Factory
Configuring Server for firewalls
•Hosting Scenarios
HTTP tunneling (Port Filtering firewalls)
To get across a firewall, the transport layer embeds an RMI call within the firewall–trusted
HTTP protocol. The RMI call data is sent outside as the body of an HTTP POST request,
and the information returned is sent back in the body of the HTTP response.
The transport layer formulates the POST request in two ways.
6 If the firewall proxy forwards an HTTP request to an arbitrary port on the host
machine, then it is forwarded directly to the port on which the RMI service is listening.
The default RMI transport layer listens on a server socket that understands and decodes
RMI calls inside POST requests.
7 If the firewall proxy forwards HTTP requests to well-known HTTP ports, then it is
forwarded to the HTTP server listening on port 80 of the host machine, and a CGI
script forwards the request to the target RMI server port on the same machine.
Configuring client
While there is no special configuration necessary to enable the client to send RMI calls
through a firewall, the client can disable the packaging of RMI calls as HTTP requests. To
do this, set the boolean value of
java.rmi.server.disableHttp property to ‘true.’
Page view 114
1 2 ... 110 111 112 113 114 115 116 117 118 119 120 ... 142 143

Comments to this Manuals

No comments