Transfer the report file RDF, REP, XML, or JSP and its associated files for

Running Report Requests 18-9 ■ Replace the report in this location. ■ Re-create the WAR file with the modified JSP-based Web report, then redeploy the application. For more information, refer to Section 18.3.3.1, Creating a New Java EE Application . For more information on running a report from a browser, refer to Section 18.5, Specifying a Report Request from a Web Browser .

18.3.5 Running a JSP report with a Paper Layout

If your JSP report has a paper layout, you can run your JSP report from a browser using the following URL: http:your_web_server:portnumMyReportApprwservlet?report=myreport.jspuserid= usernamepasswordmy_dbserver=server_namedesformat=pdfdestype=cache In this example, your report displays as a PDF desformat=PDF in the browser. For more information on running a report from a browser, refer to Section 18.5, Specifying a Report Request from a Web Browser .

18.3.6 Running with the WE8MSWIN1252 Character Set on UNIX

There are no UNIX fonts built into the WE8MSWIN1252 character set. This may cause Oracle Reports to fail when NLS_LANG=AMERICAN_AMERICA.WE8MSWIN1252. Therefore, you must map the code page of the installed fonts defined in the Tk2Motif.rgb file to the WE8MSWIN1252 character set. TK2Motif.rgb is located in the ORACLE_ INSTANCEconfigFRComponentfrcommonguicommontkadmin directory. Example1 Tk2MotiffontMapCs: ISO8859-1=WE8MSWIN1252 if there are ISO8859-1 fonts installed.

18.4 Publishing a Report in Oracle Portal

One of the best ways to publish your report is through the declarative, secure interface of Oracle Portal. To publish a report in Oracle Portal, refer to Chapter 16, Deploying Reports in Oracle Portal . Specifically, you must first register your Oracle Reports components in Oracle Portal see Section 16.2, Registering Oracle Reports Components , then expose your report in a portal see Section 16.3, Publishing Your Report as a Portlet . Note: This mapping is required for Oracle Reports Builder, Reports Converter in non-batch mode BATCH=NO, Reports Server and Reports Runtime with REPORTS_DEFAULT_DISPLAY=NO. Reports Server and Reports Runtime uses REPORTS_DEFAULT_DISPLAY to determine the fonts needed. 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 .