| Oracle9iAS Reports Services Publishing Reports to the Web
Release 2 (9.0.2)
Part Number A92102-01
This chapter provides information on starting and stopping Oracle9iAS Reports Services. It includes the following main sections:
If you plan to run reports on the Web, you must first start the Oracle HTTP Server. You'll find information on doing this in your Oracle9iAS documentation. When you follow any of the procedures in this chapter, we assume you have already started the Oracle HTTP Server.
You have these options for running the Reports Server:
The following subsections tell you how to set up each of these options.
By default, the Reports Server is installed as an in-process server, but, if you wish, you can install the Reports Server as a service on a Windows NT/2000 machine. To do so, at the command prompt enter:
For batch, the default is no. Enter yes if you don't want to be prompted for confirmation during installation. For autostart, the default is no. Enter yes if you want the service to start automatically at reboot without requiring a user to logon and manually start the Reports Server.
Add the cluster name to this command if this server will be a member of a cluster. For example:
To learn more about clustering servers together, see Chapter 6, "Reports Server Clusters".
To remove the Reports Server NT/2000 service, at a command prompt enter: r
To start your Reports Server on Windows NT/2000:
>is the name of the Reports Server instance, and click Startup. The Services dialog window displays.
If you want to output to Postscript or to a printer, then ensure the user running the Reports Server service has access to a default printer. Do this by using a specific, real user who has printer access when you set up the Log On As section of your NT/2000 service. Typically, the System Account does not have access to printers.
For that matter, the user running the Reports Server service must have access to anything the server may need. For example, the server may need write access to another drive.
A Service Control message box indicates when your Reports Server has started.
If you are using the Reports Server as an in-process server (the default configuration), just sending a request starts up the servlet; however, if you are sending a request via a command line, the servlet must be invoked via a URL first. When you have successfully started the servlet, this also means you have successfully started the HTTP Server.
To start the Reports Servlet from a URL, enter the following from your Web browser:
You can also start the Reports Server as a stand-alone server on Windows NT/2000 using the following command:
BATCH command line keyword to start up the server without displaying dialog boxes or messages.
You can run this command on UNIX using the following syntax:
You can run this command from any directory as long as the executable can be reached in your PATH environment variable.
To verify that the Oracle9iAS Reports Servlet is running, navigate to the following URL:
Note that the URL is case sensitive. If this URL executes successfully, you should get a help page describing the rwservlet command line arguments.
To verify that the Reports Server is running, navigate to the following URL:
http://< your_machine_name>.< domain_name>:< your_port_ number>/reports/rwservlet/showjobs?server=< server_name>
> argument is not required if you are using the default Reports Server name (
>) or the Reports Server specified in the servlet configuration file, rwservlet.properties (
\reports\conf\). If this URL executes successfully, you should see a listing of the job queue for the specified Reports Server.
You'll find more information about the servlet configuration file in Chapter 3, "Configuring Oracle9iAS Reports Services".
To verify that the Oracle HTTP Server is running, in your browser, navigate to the following URL:
This section discusses how to stop the Reports Server on Windows NT/2000 and UNIX.
For Windows NT/2000 and UNIX (on UNIX use rwserver.sh in lieu of rwserver):
This shuts down the server normally (i.e., finishes pending jobs and then stops):
This shuts down the server immediately (i.e., stops without finishing pending jobs):
This shuts down the server without displaying any related messages:
The keywords used with the
rwserver command are described in
Appendix A, "Command Line Arguments".