Technical data

Supported Software, Technologies, and Protocols
Oracle iPlanet Web Proxy Server 4.0.25 Release Notes 1-5
1.5.2 URL Mapping
URL mapping was implemented in Oracle iPlanet Web Proxy Server 4.0.8. It enables
Oracle iPlanet Web Proxy Server to act as a reverse proxy. This feature enables Oracle
iPlanet Web Proxy Server to provide a single front-end host name for back-end
application servers. Based on a requester's URI, access is provided to back-end servers.
For more information about URL mapping, see "Reverse Proxy Scenario" in Oracle
iPlanet Web Proxy Server 4.0.14 Configuration File Reference.
For information about Server Application Functions (SAFs) used in URL mapping, see
"Server Application Functions (SAFs)" in Oracle iPlanet Web Proxy Server 4.0.14
Configuration File Reference.
1.5.3 Monitoring Server Parameters
The monitoring capabilities of Oracle iPlanet Web Proxy Server provide a detailed list
of the server parameters that you can monitor at instance level.
From the Proxy Administration Server, you can perform the following actions:
■ View server statistics at an instance level
■ Enable or disable parameters at an instance level
To monitor the server, do the following:
1. Access the Administration Server
2. Click the Instance link from the Manage Servers page
3. Click the Server Status tab
4. Click the Monitor Current Activity tab
5. Set the Monitoring Current Activity to ON to monitor the server
You can also refresh the server in intervals of 5,10, and 15 seconds and view the
statistics of the
DNS , Keep-Alive , Cache , Server Requests, and Work Thread
connections.
1.5.4 Embedded DNS Resolution
The embedded DNS supports the nondefault name resolution. The DNS client
interacts with a DNS server to perform the name resolution. The new SAF
dns-lookup ,
receives the DNS server's IP address as a server argument. This IP address should be
added as a DNS directive in the
obj.conf file.
In the following example, the IP address of the DNS server is specified in the server
parameter:
<object>
....
DNS fn="dns-lookup" server="170.168.10.3"
...
</object>
In the following example, you can add multiple DNS server IPs to dns-lookup-init ,
and it will be used in a round-robin model. In this scenario, do not add DNS server IP
address to
dns-lookup . If DNS server parameters are added to both dns-lookup and
dns-lookup-init , the dns-lookup argument will take precedence.
...
<Object>