Publishing a Report in Oracle Portal

Running Report Requests 18-13 ■ Instance.oracle_home with the path to the ORACLE_HOME directory If Forms and Reports are configured on different OHS Servers, you must route the web requests from OHS instance where Forms is configured to the Reports Servlet as follows: 1. Copy the reports_ohs.conf file as follows: cp ORACLE_HOMEreportsconfreports_ohs.conf FORMS_ORACLE_ INSTANCEconfigOHSohs1moduleconf. 2. Replace the macros managedserverhost and managaerserverport with host and port of the WLS_REPORTS managed server. 3. Restart the OHS that is running in FORMS_ORACLE_INSTANCE.

18.8.2 Generating Random and Non-Sequential Job IDs

With 11g Release 1 11.1.1, Oracle Reports allows you to generate random and non-sequential job IDs to make it impossible to predict the job ID for a particular job. To generate random and non-sequential job IDs for in-process servers, you must pass -Djobid=random via JVM options to Oracle WebLogic Server. For standalone servers, you can generate random and non-sequential job IDs by passing the -Djobid=random via JVM options in the command line or by setting the REPORTS_JVM_OPTIONS variable. For more information, see Section B.1.53, REPORTS_JVM_OPTIONS . This prevents malicious users from viewing non-secure report output by typing the job id in a URL.

18.9 Running Reports Using Oracle BPEL Process Manager

With 11g Release 1 11.1.1, Oracle Reports is integrated with the Oracle Service-Oriented Architecture SOA suite, which includes Oracle BPEL Process Manager to automate and monitor reporting requirements. You can submit Oracle Reports jobs from the Oracle BPEL Process Manager business process, get the status of report execution, and also invoke an Oracle BPEL Process Manager business process from your reports. This makes it easy to include reporting requirements in the business process; for example, submit a report request when an order gets approved. For more information, see Section 8.10, Configuring Oracle Reports to Communicate with Oracle BPEL Process Manager , and also Oracle Fusion Middleware Developers Guide for Oracle SOA Suite.

18.10 Scheduling Reports to Run Automatically

You can use the server to run reports automatically from Reports Queue Manager rwrqm on Windows, or rwrqv.sh on Solaris, Oracle Portal, or with the SCHEDULE command line keyword. The scheduling feature enables you to specify a time and frequency for the report to run. Refer to the Reports Queue Manager online Help for more information about scheduling your reports. 18-14 Publishing Reports to the Web with Oracle Reports Services If you publish a report as a portal component on an Oracle Portal page, then you can schedule the report request to run automatically and push the resulting report output to specified pages. Refer to the Oracle Portal online Help for more information. The SCHEDULE command line keyword is available for use with the rwclient and rwservlet commands. See Section A.8.3, SCHEDULE for more information.

18.11 Additional Parameters

When you send a request to the Reports Server through rwcgi ,the following additional parameters, the values of which you cannot change, are implicitly passed along with your request:

18.12 Reusing Report Output from Cache

When you run a report, a copy of the report output is saved in the Oracle Reports Services cache. Subsequently, if an identical report is run that is, with the same cache key, then the current request is recognized as a duplicate job. There are several scenarios where reports caching takes effect: ■ When a new job request A comes to the Reports Server, and there is another job B that has the same cache key in the Current Jobs Queue where it is waiting for an available engine or is in the middle of execution, then job A will use the output from job B. The job cache key excludes the destype, desname, server, and tolerance parameters, and includes almost all other parameters. This level of cache happens automatically. You need not specify any other parameters in the command line for it to work. ■ If the user specifies TOLERANCE=n where n is a number in units of minutes in the new job request A, then Reports Server will try to find a job in the Finished Jobs Queue than was successfully completed within n minutes. If Reports Server finds such a job, then the new job request A will return the output of job B. Table 18–4 Additional Parameters Passed With a Report Request Name Description ACCEPT_LANGUAGE The comma separated list of languages accepted by the browseruser. REMOTE_ADDR The remote IP address from which the user is making the request. REMOTE_HOST The remote host name from which the user is making the request. SCRIPT_NAME The virtual path of the script being executed. SERVER_NAME The host name or IP address of the server on which Oracle Reports Servlet rwservlet is running. SERVER_PORT The port number of the server on which Oracle Reports Servlet rwservlet is running. SERVER_PROTOCOL The name and revision of the information protocol with which the request was sent. USER_AGENT The description of the remote clients browser.