3.3 Verifying the Reports Server Environment

Oracle Reports Services report requests flow from the Oracle HTTP Server component, to Oracle Reports Servlet, to Reports Server. Before sending report requests to Reports Server, verify that the environment is up and running:

3.3.1 Checking Oracle HTTP Server

Before starting Reports Server, you must verify that your Oracle HTTP Server is running. For more information about performing this task in Oracle Enterprise Manager, refer to your Oracle Enterprise Manager documentation.

Alternatively, you can verify that the Oracle HTTP Server is running by navigating to the following URL:


3.3.2 Checking Oracle Reports Servlet

To verify that Oracle Reports Servlet (rwservlet) is running, navigate to the following URL:



host is the server that is allotted.

port is either the OHS port or the WebLogic Server port.

In a Single Sign-On environment, when using Oracle Access Manager 11g (OAM) as the authentication server, if AUTHID is passed in the Reports URL, then OAM authentication page is displayed.

Note that the URL is case-sensitive. If this URL executes successfully, you should get a help page describing the rwservlet command line arguments

3.3.3 Checking Reports Server

To verify that Reports Server is running, navigate to the following URL:



host and port are as described in Section 3.3.2, "Checking Oracle Reports Servlet".

server=server_name is not required if you are using the default Reports Server name (rep_machine_name) or the Reports Server specified in the Oracle Reports Servlet configuration file (rwservlet.properties).

If this URL executes successfully, you should see a listing of the job queue for the specified Reports Server.


For more information about the Oracle Reports Servlet configuration file (rwservlet.properties), see Section 7.3, "Oracle Reports Servlet Configuration File".