Using Oracle Enterprise Manager

Verifying Your Installation 3-3 ■ Reports Log Configuration Page ■ Reports Jobs Page FinishedScheduledCurrentLong RunningFailed Use these pages to perform checks and verifications, start a standalone Reports Server, shut down the standalone Reports Server, and run a report using rwservlet and the in-process Reports Server. For more information, see Chapter 7, Administering Oracle Reports Services Using Oracle Enterprise Manager .

3.4 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: ■ Checking Oracle HTTP Server ■ Checking Oracle Reports Servlet ■ Checking Reports Server

3.4.1 Checking Oracle HTTP Server

Before starting Reports Server through Oracle Enterprise Manager, 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: http:server_name.domain:port_number

3.4.2 Checking Oracle Reports Servlet

To verify that Oracle Reports Servlet rwservlet is running, navigate to the following URL: http:host:portreportsrwservlethelp where host is the server that is allotted. port is either the OHS port or the WebLogic Server port. 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.4.3 Checking Reports Server

To verify that Reports Server is running, navigate to the following URL: http:host:portreportsrwservletgetserverinfo?server=server_name where host and port are as described in Section 3.4.2, Checking Oracle Reports Servlet . 3-4 Publishing Reports to the Web with Oracle Reports Services 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.

3.5 Confirming Security with Oracle Portal-Based Security

In Oracle Reports 11g Release 1 11.1.1, by default Reports Server is secure out-of-the-box using Oracle Portal-based Security Services. During installation, you can specify any LDAP server including Oracle Internet Directory to be used as the policy store. Confirm that security is enabled in either of the following ways: ■ Using Oracle Enterprise Manager ■ Using the Command Line

3.5.1 Using Oracle Enterprise Manager

In Oracle Enterprise Manager, select Reports Administration Advanced Configuration to display the Reports Server Advanced Configuration Page: ■ In the Reports Security region, check Enable Security.

3.5.2 Using the Command Line

On the command line, navigate to the following directory to open the in-process Reports Server configuration file to verify it is configured with the RWJAZN security: DOMAIN_HOMEconfigfmwconfigserversWLS_REPORTSapplicationsreports_ versionconfiguration The presence of security id=rwSec class=oracle.reports.server.RWSecurity in the configuration file confirms that RWSecurity is enabled.

3.6 Upgrading from the Prior Release

Upgrading from Oracle Reports 10.1.2.x to 11g Release 1 11.1.1 is fully automated: ■ Integrated with Oracle Fusion Middleware Upgrade framework. ■ Automated configuration reduction mapping. ■ Extensive logging and diagnostics. ■ No loss of functionality.

3.6.1 Backward Compatibility and Interoperability

Oracle Reports 11g Release 1 11.1.1 is fully backward compatible and interoperable with 10.1.2.x: ■ 10.1.2.x serverclient compatible with 11g Release 1 11.1.1 serverclient. Note: For more information about the Oracle Reports Servlet configuration file rwservlet.properties , see Section 8.3, Oracle Reports Servlet Configuration File .