Table of Contents
Oracle Fusion Middleware Publishing Reports to the Web with Oracle Reports Services
PrefaceIntroductionUnderstanding the Oracle Reports Services ArchitectureVerifying Your InstallationInteroperability Scenarios and ConsiderationsStarting and Stopping Oracle Reports ServicesStarting and Stopping Reports ServerStarting, Stopping Reports Bridges from the Node Manager using scriptStarting Reports Components After Shutting Down an InstanceAdministering Oracle Reports Services Using Oracle Enterprise ManagerConfiguring Oracle Reports ComponentsAdministering and Scheduling JobsSecuring Oracle Reports ServicesManaging FontsManaging Log FilesManaging and Monitoring a Reports High Availability (HA) SolutionAbout the Oracle Fusion Middleware System MBean BrowserDiagnosing IssuesConfiguring Oracle Reports ServicesOracle Reports Services Configuration FilesReports Server Configuration FileOracle Reports Servlet Configuration FileOracle Reports Bridge Configuration FileNetwork Configuration FileEntering Proxy InformationConfiguring Reports Server with the Node Manager Reports Process ManagementOverview of SOA IntegrationConfiguring Oracle Reports to Communicate with Oracle BPEL Process ManagerManaging Fonts in Oracle ReportsPrinting on UNIX with Oracle ReportsUsing PDF in Oracle ReportsFont Model and Cross-Platform DeploymentConfiguring Destinations for Oracle Reports ServicesConfiguring and Using the Pluggable Data sourcesSecuring Oracle Reports ServicesIntroduction to Oracle Reports SecurityAuthentication in Oracle ReportsAuthorization in Oracle ReportsManaging Users and Security PoliciesConfiguring External Oracle Internet Directory and Reassociating ReportsDatabase Proxy AuthenticationOracle Portal-Based Security for Backward CompatibilityDeploying Reports in Oracle PortalConfiguring and Administering Oracle Single Sign-OnRunning Report RequestsThe Reports URL SyntaxDeploying Your ReportsCalling Oracle Reports from Oracle Forms ServicesReusing Report Output from CacheUsing a Key Map FileUsing the Oracle Reports Web ServiceCreating Advanced DistributionsUsing Event-Driven PublishingCustomizing Reports with XMLImplementing Globalization and Bidirectional SupportDiagnosing and Tuning Oracle ReportsCommand-Line KeywordsUsing the Command LineOverview of Oracle Reports ComponentsCommand Line Keywords (ACCESSIBLE to DESTYPE)Command Line Keywords (DISTRIBUTE to ORIENTATION)Command Line Keywords (OUTPUTFOLDER to ROLE)Command Line Keywords (RUNDEBUG to WEBSERVER_PORT)Environment VariablesEnvironment VariablesBatch Registering Reports in Oracle PortalTroubleshooting Oracle Reports ServicesProblems and SolutionsReports Server and Bridge Diagnostic Utility
Thank you for your feedback!Categories
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:
Table 18-4 Additional Parameters Passed With a Report Request
| Name | Description |
|---|---|
|
|
The comma separated list of languages accepted by the browser/user. |
|
|
The remote IP address from which the user is making the request. |
|
|
The remote host name from which the user is making the request. |
|
|
The virtual path of the script being executed. |
|
|
The host name or IP address of the server on which Oracle Reports Servlet ( |
|
|
The port number of the server on which Oracle Reports Servlet ( |
|
|
The name and revision of the information protocol with which the request was sent. |
|
|
The description of the remote client's browser. |
Sign In