Running a Report with a Paper Layout

18-10 Publishing Reports to the Web with Oracle Reports Services

18.5 Specifying a Report Request from a Web Browser

You can provide the user with the URL syntax needed to make a report request, or you can add the URL syntax to a Web page as a hyperlink. URL syntax can be presented in the following forms: ■ Full URL request, for example: http:your_webserver.domain_ name:portaliasrwservlet?report=myreport.rdfuserid= usernamepasswordmy_dbserver=server_namedesformat=htmldestype=cache If you require additional command line keywords, then refer to Appendix A, Command-Line Keywords for a list of valid rwservlet command line keywords. ■ Simplified URL request using key mapping, for example: http:your_webserver.domain_name:portaliasrwservlet?key1

18.6 Sending a Request to the URL Engine

If you have activated the Reports Servers URL engine, you can send job requests to the URL engine by using the following command line options: ■ urlParameter identifies the URL to be placed in the cache. For example, http:www.oracle.com or a JSP report. ■ jobType is the name of a job type for example, rwurl in the server configuration file that is associated with a URL engine. For example, a request that specifies an external URL for urlParameter might look like the following: http:your_webserver:portnumreportsrwservlet?server= ReportsServer+jobType=rwurl+urlParameter= http:www.oracle.com+destype=mail+desname=foobar.com+desformat=htmlcss Alternatively, a request that specifies a JSP report for urlParameter would look like the following: Note: When you use features like Oracle Portal Security, Portal Destination, and Job Status Repository, the JDBC database connections made by Oracle Reports Services may override the initial NLS_LANG setting. This change may in turn affect the behavior of the running report, such as bidirectional output in PDF. On UNIX platforms, you can work around this issue using the environment switching functionality to dynamically set the environment for reports. Refer to Section 8.2.2, Dynamic Environment Switching for more information. Note: For information on activating the URL engine, refer to Section 8.6, Configuring the URL Engine .