01.02.2013 Views

Publishing Reports to the Web - Downloads - Oracle

Publishing Reports to the Web - Downloads - Oracle

Publishing Reports to the Web - Downloads - Oracle

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Configuring <strong>Reports</strong> Server<br />

■ The command line option, ENVID, of your report’s job request, which makes <strong>the</strong><br />

environment settings only effective for that particular report job request.<br />

The environment attributes are listed and described in Table 3–18.<br />

Table 3–18 Attributes of <strong>the</strong> environment element<br />

Attribute Valid values Description<br />

id string The name of <strong>the</strong> environment.<br />

The environment element has one sub-element, envVariable. Each envVariable is<br />

specified as a name–value pair. They can be ei<strong>the</strong>r standard environment variables or<br />

user-defined environment variables.<br />

The envVariable element attributes are listed and described in Table 3–19.<br />

Table 3–19 Attributes of <strong>the</strong> envVariable element<br />

Attribute Valid values Description<br />

name string Is <strong>the</strong> name of <strong>the</strong> environment you wish <strong>to</strong> use<br />

(e.g., NLS_LANG).<br />

value string Is <strong>the</strong> value you want <strong>to</strong> assign <strong>to</strong> <strong>the</strong> environment<br />

variable identified with <strong>the</strong> name attribute.<br />

3.2.2 Dynamic Environment Switching<br />

In <strong>the</strong> past, <strong>Reports</strong> Server could only serve reports that were compatible with <strong>the</strong><br />

environment in place when <strong>Reports</strong> Server was started. For example, reports had <strong>to</strong> be<br />

compatible with <strong>the</strong> value of <strong>the</strong> NLS_LANG parameter at <strong>the</strong> time <strong>Reports</strong> Server was<br />

started. This restriction meant that you needed <strong>to</strong> have one <strong>Reports</strong> Server running for<br />

each language you wanted <strong>to</strong> process. The new environment switching feature<br />

eliminates this restriction by enabling one instance of <strong>Reports</strong> Server <strong>to</strong> serve reports<br />

with any arbitrary environment settings, including language.<br />

To use this feature, you first need <strong>to</strong> add an environment element <strong>to</strong> your <strong>Reports</strong><br />

Server configuration file <strong>to</strong> establish a particular runtime environment. Once you have<br />

an environment element established, you can switch <strong>to</strong> its settings in ei<strong>the</strong>r one of <strong>the</strong><br />

following ways:<br />

■ The defaultEnvId attribute of <strong>the</strong> engine element in <strong>the</strong> <strong>Reports</strong> Server<br />

configuration file applies <strong>the</strong> specified environment element <strong>to</strong> <strong>the</strong> engine when it<br />

starts up. For more information, refer <strong>to</strong> engine.<br />

■ The command line option, ENVID, of your report’s job request, which makes <strong>the</strong><br />

environment settings only effective for that particular report job request. Refer <strong>to</strong><br />

Examples.<br />

Below is an example of an environment element:<br />

<br />

<br />

<br />

<br />

<br />

You could invoke this environment element from an engine element as follows:<br />

<br />

Configuring <strong>Oracle</strong>AS <strong>Reports</strong> Services 3-27

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!