Oracle9iAS Portal can be configured to use proxy server when making requests. Proxy servers intercept requests to another server and forward the requests to the real server as needed. They are generally used for forwarding requests through a firewall, filtering content and caching content.
This article describes the key features of proxy support within Oracle Portal and also how to configure Web providers (registered with Oracle Portal) to use proxy servers.
Key Features
These are the key features of proxy support within Portal:
Only Portal Administrators can add Proxy Server Settings as follows:
How to use Proxy Servers for Web Providers
Some of the Oracle Portal calls to Web providers originate from the Portal repository (database-tier). The calls to a Web provider's Show method originate from the Portal middle-tier. During Web provider registration, proxy servers for both middle-tier and database-tier communications can be specified individually. The choice of Proxy servers depends on the configuration of the Portal middle-tier and the repository.
In this article, we consider three sample configurations of the Portal repository and middle-tier with firewall and discuss how to specify the proxy servers based on these configurations during provider registration. Lets assume that the Proxy servers used in this example are primarily used to connect to servers outside of firewall and that have been specified within Oracle Portal via the Proxy Settings page.
Sample Configuration 1 - Portal Repository and Middle-Tier within the Same Firewall
Figure 1 shows both the Portal middle-tier and repository behind the same firewall.
They require a proxy server (P1) to connect to Web provider WP1 outside this
firewall. In this case, the same proxy can be selected for both middle-tier
and database-tier in the Provider registration screen. Figure 1 shows Proxy
P1 is used by both the Portal repository and Portal middle-tier.
Sample Configuration 2 - Portal Repository and Middle-Tier
are Separated by a Firewall and both are Surrounded by another Firewall
Figure 2 shows the Portal middle-tier behind a firewall and that it requires a proxy to connect to the Portal. This Proxy needs to be specified in the middle-tier. For details on how to specify proxy setting in the middle-tier to connect to the Portal repository, refer to the Oracle9iAS Portal Configuration Guide.
In the Provider Registration screen for Web provider WP1, Proxy P1 must be
selected as the middle-tier proxy and Proxy P3 as the database-tier proxy.
Sample Configuration 3 - Portal Repository and Middle-Tier are Separated by a Firewall and Web Provider is Outside the Firewall
Figure 3 shows the Portal repository within a firewall and both the Web provider and Portal middle-tier outside this firewall. The middle-tier uses proxy server P1 to connect to the database and this must be specified in the Portal middle-tier. For details on how to specify proxy setting in the middle-tier to connect to the Portal repository, refer to the Oracle9iAS Portal Configuration Guide.
The Portal database uses proxy server P2 to connect to Web provider WP1 outside of the firewall. No proxy server is specified for the middle-tier during Web provider registration.

Proxy Servers and Database Providers
There are no proxy servers involved in calls from the Portal repository to database providers. However, if the configuration is such that the Portal middle-tier requires a proxy server to connect to the database (see samples 2 and 3 above), the proxy server needs to be specified in the middle-tier. For details on how to specify proxy setting in the middle-tier, refer to the Oracle9iAS Portal Configuration Guide.
Revision History: