Publishing Reports to the Web - Downloads - Oracle

Starting and Stopping the Reports Server
■ If the Reports Server running from a command line on Windows or UNIX, at the
command prompt enter the following command:
For Windows and UNIX (on UNIX use rwserver.sh in lieu of rwserver):
The following command line shuts down the server normally (i.e., finishes
pending jobs and then stops):
rwserver server=server shutdown=normal authid=username/password
The following command line shuts down the server immediately (i.e., stops
without finishing pending jobs):
rwserver server=server shutdown=immediate authid=username/password
The following command line shuts down the server without displaying any
related messages:
rwserver server=server shutdown=normal authid=username/password batch=yes
The keywords used with the rwserver command are described in Appendix A,
"Command Line Options".
Note: authid is the Reports Server’s administration user name
and password. For a secure Reports Server, this user must be a
member of the RW_ADMINISTER privilege group in the Oracle
Internet Directory. For a non-secure Reports Server, this user is
defined in the identifier element. The following bullet contains
more information on how to stop a non-secure Reports Server using
the command line.
■ When you stop or shut down a non-secure Reports Server from the command line
using either rwserver.sh or rwrqv.sh, you need to provide a valid authid,
which must match the value set in the identifier element in the server
configuration file. However, the identifier element is set during Reports
configuration while installing Oracle Application Server 10g and encrypted by the
Reports Server. You can reset the identifier element to any value. Then, you also
need to change the corresponding properties in targets.xml for Oracle
Enterprise Manager 10g integration to work. Perform the following steps:
1. In the non-secure Reports Server’s configuration file, server_name.conf,
modify the identifier element to specify the username/password and set the
encrypted attribute to no. For example:
scott/tiger
2. Stop and restart the Reports Server manually for the changes made to the
server_name.conf file to take effect.
Note: You must restart the Reports Server for any configuration
changes to take effect.
The Reports Server will now encrypt the username/password value of the
element. After the Reports Server reads the changes made in
the server_name.conf file, the following commands should execute
successfully (with scott/tiger as the username/password):
Starting and Stopping OracleAS Reports Services 2-5