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

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

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

Description<br />

The persistFile element identifies <strong>the</strong> file that records all job status. It is used by<br />

<strong>Reports</strong> Server <strong>to</strong> res<strong>to</strong>re <strong>the</strong> server <strong>to</strong> <strong>the</strong> status it held before shutdown.<br />

It is named persistFile because <strong>the</strong> file remains intact, or persists, even when <strong>the</strong><br />

server is brought down and restarted.<br />

The server persistent file is created au<strong>to</strong>matically <strong>the</strong> first time you start <strong>the</strong> server or<br />

<strong>the</strong> first time you start <strong>the</strong> server after <strong>the</strong> current server persistent file has been<br />

deleted or renamed. If you want <strong>to</strong> rename this file but continue using it, enter <strong>the</strong> new<br />

name in <strong>the</strong> server configuration file before you actually rename <strong>the</strong> file, <strong>the</strong>n restart<br />

<strong>the</strong> server.<br />

The persistFile element has one attribute, fileName, described in Table 3–16.<br />

Table 3–16 Attributes of <strong>the</strong> persistFile element<br />

Attribute Valid values Description<br />

fileName string Default: server_name.dat<br />

The name and, optionally, <strong>the</strong> path of <strong>the</strong> server<br />

persistent file. You can leave <strong>the</strong> path off if <strong>the</strong> file is<br />

kept in its default direc<strong>to</strong>ry:<br />

ORACLE_HOME\reports\server\<br />

The path is <strong>the</strong> same for Windows or UNIX.<br />

3.2.1.15 identifier<br />

Example<br />

fpoiVNFvnlkjRPortn+sneU88=NnN<br />

Required/Optional<br />

Optional. You can have a maximum of one identifier element in your server<br />

configuration file.<br />

Description<br />

The identifier element is au<strong>to</strong>matically written <strong>to</strong> <strong>the</strong> configuration file when you<br />

first log in <strong>to</strong> <strong>Reports</strong> Queue Manager as an administra<strong>to</strong>r. The first login sets <strong>the</strong><br />

<strong>Reports</strong> Queue Manager's administra<strong>to</strong>r user ID and password. That information is<br />

encrypted and written <strong>to</strong> <strong>the</strong> server configuration file, <strong>the</strong>n used for au<strong>the</strong>ntication for<br />

all future Queue Manager logins.<br />

If you forget <strong>the</strong> Queue Manager login or need <strong>to</strong> change it, delete it and reenter it in<br />

<strong>Reports</strong> Server configuration file in <strong>the</strong> following format:<br />

username/password<br />

You should immediately start <strong>Reports</strong> Server after making this change. Doing so<br />

au<strong>to</strong>matically encrypts <strong>the</strong> user name and password and resets encrypted <strong>to</strong> yes. It<br />

will look something like this:<br />

fpoiVNFvnlkjRPortn+sneU88=NnN<br />

3-24 <strong>Oracle</strong> Application Server <strong>Reports</strong> Services <strong>Publishing</strong> <strong>Reports</strong> <strong>to</strong> <strong>the</strong> <strong>Web</strong>

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

Saved successfully!

Ooh no, something went wrong!