Publishing Reports to the Web - Downloads - Oracle

Entering Proxy Information
/>
maxEngine="1"
minEngine="0"
engLife="50"
maxIdle="30"
callbackTimeOut="60000"
2. Add a job element that associates the appropriate job types with the URL engine to
the server configuration file. For example, your job element might be as follows:
3. Stop and restart Reports Server.
To learn about sending requests to the URL engine, refer to Chapter 13, "Running
Report Requests".
3.5 Entering Proxy Information
Note: When you restart your Reports Server with these new
elements, you should see the number of engines increase
accordingly in the Reports Server status message box. In the above
example, the number of engines would increase by one (the value
of initEngine) when you restart Reports Server.
Some features of OracleAS Reports Services support retrieving or sending information
through a firewall. For example, the URL engine, the XML data source, the Text data
source, and the mail destination features all retrieve or send information through the
firewall. For these features to function properly, Reports Server requires certain proxy
information. In the interests of simplicity, you store the necessary proxy information in
a single location and point to it from the Reports Server configuration file. To configure
your Reports Server with proxy information, you do the following:
1. Add the pluginParam element to the server configuration file and have it point to
the proxy information file (e.g., proxyinfo.xml). For example, your
pluginParam element might be as follows:
proxyinfo.xml
Note: You can optionally specify a path for the proxy information
file. By default, this file is located in ORACLE_
HOME/reports/conf.
2. Update the proxy information file with the necessary proxy values for your
configuration. For example, proxyinfo.xml might contain the following:
*.abc.com
3-40 Oracle Application Server Reports Services Publishing Reports to the Web