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.

Setting Up a Cluster<br />

12.2.2 Generating New Public and Private Keys<br />

The server public and private key files aid with message encryption and<br />

au<strong>the</strong>ntication between cluster members. The default files are s<strong>to</strong>red in <strong>the</strong><br />

rwrun.jar file in <strong>the</strong> following path (on both UNIX and Windows):<br />

ORACLE_HOME\reports\jlib\rwrun.jar<br />

Each member of a cluster must have <strong>the</strong> same public and private key files specified in<br />

<strong>the</strong>ir configuration files (server_name.cluster_name.conf). To ensure that your<br />

cluster members share exclusive public and private key files, generate new versions of<br />

<strong>the</strong>m when you set up your cluster. Servers that will not be members of <strong>the</strong> cluster can<br />

go on using <strong>the</strong> default keys provided with <strong>Oracle</strong>AS <strong>Reports</strong> Services.<br />

To generate new public and private key files, at <strong>the</strong> command prompt, enter <strong>the</strong><br />

following command:<br />

rwgenkey.sh public_key_file_name private_key_file_name (UNIX)<br />

rwgenkey.bat public_key_file_name private_key_file_name (Windows)<br />

You can generate <strong>the</strong>se files <strong>to</strong> specific direc<strong>to</strong>ries by specifying <strong>the</strong> desired path in <strong>the</strong><br />

command line along with <strong>the</strong> new public and private key file names. If you just<br />

specify <strong>the</strong> file name in <strong>the</strong> command line, <strong>the</strong> key files will be generated in <strong>the</strong> current<br />

direc<strong>to</strong>ry.<br />

12.2.3 Entering Public and Private Keys in <strong>the</strong> Server Configuration File<br />

Once you generate new public and private key files, you must enter that information<br />

in<strong>to</strong> all cluster members' <strong>Reports</strong> Server configuration files. You'll find each cluster<br />

member's version of this file in <strong>the</strong> following path for both UNIX and Windows on<br />

each server's host machine:<br />

ORACLE_HOME\reports\conf\server_name.cluster_name.conf<br />

To change public and private key files, go <strong>to</strong> <strong>the</strong> connection element in <strong>the</strong> server<br />

configuration file, and change (or add) entries for <strong>the</strong> cluster sub-element as<br />

follows:<br />

<br />

You'll find more information about <strong>the</strong> connection element in Chapter 3,<br />

"Configuring <strong>Oracle</strong>AS <strong>Reports</strong> Services".<br />

12.2.4 Restarting <strong>the</strong> <strong>Reports</strong> Server<br />

Once you have renamed your cluster members and respecified a common public and<br />

private key for each, you may start up your <strong>Reports</strong> Servers <strong>to</strong> activate <strong>the</strong> cluster.<br />

To start up a <strong>Reports</strong> Server:<br />

■ If you're starting <strong>the</strong> <strong>Reports</strong> Server as a Windows service, open <strong>the</strong> Service<br />

control panel, and start <strong>the</strong> service.<br />

■ If you're starting <strong>the</strong> <strong>Reports</strong> Server from a command line, at <strong>the</strong> command<br />

prompt, enter <strong>the</strong> following command:<br />

On Windows:<br />

rwserver server=server_name.cluster_name<br />

12-4 <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!