Publishing Reports to the Web - Downloads - Oracle

Configuring Reports Server
The value JP identifies the environment element created previously in the Reports
Server configuration file. The initial engines will be spawned with the environment
settings specified in this environment element. For more information on the
environment element, refer to engine.
3.2.2.1 Examples
The following examples illustrate the usage of the dynamic environment switching
feature:
Example 1
Suppose that you need to run reports in Japanese from your Reports Server. An
environment conducive to running reports in Japanese would include:
■ NLS_LANG = Japanese_Japan.JA16SJIS
■ The currency unit would be set to Yen (¥), the currency of Japan.
■ If Reports Server is running on UNIX, then DISPLAY would also need to be set.
To begin, you would have to add an environment element to your Reports Server
configuration file that looks something like the following:
Once the environment element is in place, you could request a report with Japanese
output using the following URL:
http://yourWebServer:port/reports/rwservlet?server=yourreportsserver
&report=Japanese.rdf&userid=username/passwd@db&desformat=htmlcss
&destype=cache&envid=jp
When the URL is submitted to Reports Server, it detects the optional ENVID parameter
and matches the specified id (in this case, JP) to the corresponding id in its
configuration file. If Reports Server already has an engine running with these
characteristics, it will reuse the existing engine to process the job. If not, then it spawns
an engine using the current environment plus the three environment variables
specified in the JP environment element. If spawning a new engine would cause
Reports Server to exceed its maxEngines setting, Reports Server shuts down an
engine before starting a new one. An engine may be shut down even though it has not
exceeded its engLife setting.
Once Reports Server has an engine with the correct environment running, the job is
processed by that engine and the output is routed to the specified DESTYPE.
envid is an optional parameter. If you do not pass this parameter with the job,
Reports Server processes the request using an engine started with the defaultEnvId
environment. If defaultEnvId is not specified for the engine element in your
Reports Server configuration file, then the engine will inherit the settings with which
the Reports Server instance was started.
Reports Server may forward the request to another server on the cluster in cases where
it cannot handle the request at that time. Even though the job may be routed to another
server on the cluster, the target server will reuse or spawn an engine with the required
environment to process this job.
3-28 Oracle Application Server Reports Services Publishing Reports to the Web