Skip Headers
Oracle® Application Server Release Notes
10g (9.0.4) for Solaris Operating System (SPARC)
Part No. B10629-15
  Go To Documentation Library
Home
Go To Table Of Contents
Contents

Previous
Previous
Next
Next
 

18 Oracle Reports

This chapter describes issues with Oracle Reports. It includes the following topics:


Note:

Refer to Oracle Reports' documentation page on OTN, (http://www.oracle.com/technology/documentation/reports.html) to download the latest version of the Oracle Reports online help.

18.1 General Issues and Workarounds

This section describes general issues and their workarounds for Oracle Reports. It includes the following topics:

18.1.1 Viewing the rwconverter Help on Oracle Application Server

In an Oracle Application Server-only installation, the Oracle Reports online help system is not installed. If you click Help in the Convert dialog box (the user interface to rwconverter), the following message is displayed:

REP-544: on-line help system is not available

To view the Oracle Reports online help, you can do either of the following:

  • Install Oracle Developer Suite. This installation includes the Oracle Reports online help.

  • Access the Oracle Reports online help on the Oracle Technology Network (OTN):

    1. Navigate to http://otn.oracle.com/reports/help/.

    2. Use the Index and Search tabs to find the information you need. For example, on the Search tab, type Convert dialog box to display the help topic for the Convert dialog box.

18.1.2 Creating an Express Server Query

If you create an Express Server query without installing the appropriate files, you will see the following error message:

REP-0069:Internal Error
XR-3013: The Express xConnect.ini file is missing or incomplete

Workaround

Ensure that you have the required Express Server connection files present on your machine before creating an express query.


Note:

Refer to the Express PDS help on OTN (http://otn.oracle.com/reports/help/), for more information on configuring and using the Oracle Express Pluggable Data Source.

18.1.3 Inserting a Graph in the Paper Design View for a Matrix-with-Group Report

In the Paper Design view of a Matrix-with-Group report, inserting a graph with a once-per-group position causes Reports Builder to fail.

Workaround

Insert the graph in the Paper Layout view rather than in the Paper Design view.

18.1.4 Using the Report Wizard or Data Wizard on Solaris 2.9 Solaris

On Solaris 2.9, Reports Builder stops responding if you invoke either the Report Wizard or the Data Wizard after accessing any of the following:

  • Oracle Reports online help

  • Data Model Editor

  • Text Query Editor

  • JDBC Query Editor

  • OLAP Query Editor

Reports Builder may stop responding when you use the query editor from the Report Wizard's data panel.

To fix this issue, you must download the patch at the following location: http://metalink.oracle.com. The ARU patch number is: 5188895.

To enable the fix, you must set the REPORTS_SOLARIS_9 environment variable to YES after you install the patch.

18.1.5 Running a Report to DelimitedData on OracleAS Portal

If you have registered your Reports Server in OracleAS Portal, then you cannot run a report to DESFORMAT=DELIMITEDDATA using that Reports Server.

To work around this issue, you must either unregister your Reports Server from OracleAS Portal or use a standalone Reports Server to run the report to DESFORMAT=DELIMITEDDATA.

18.1.6 Running a Simple Matrix Report to the Web

A simple matrix report created and run to the Web by using the Run Web Layout functionality does not display correctly.

To fix this issue, you must download the patch from the following location: http://metalink.oracle.com.

  • The ARU patch number for Solaris is 5147755.

18.1.7 FTP and WebDaV Destinations Not Supported from Reports Builder

Currently there is no support for FTP and WebDaV destinations from the Reports Builder environment. However, they are supported from the Reports Runtime and the Reports Server environments.

18.1.8 Oracle JDeveloper Integration

This section describes issues with Oracle JDeveloper integration. It includes the following topics:

18.1.8.1 Deadlock When Debugging JSP Reports in Oracle JDeveloper

When debugging an OracleAS Reports Services JSP in Oracle JDeveloper, you must disable any breakpoints that are not of source type. If you do not disable these breakpoints, a deadlock is detected. You can disable breakpoints that are not of source type in the Breakpoints window.

18.1.8.2 Graph Not Appearing in Oracle JDeveloper

When running a JSP report with the rw:graph tag in Oracle JDeveloper, the image is not visible in the browser. To fix this problem, set the IMAGEURL parameter in the rwservlet.properties file in ORACLE_HOME/reports/conf:

IMAGEURL=http://host:port/Workspace-Project-context-root/servlet/ oracle.reports.rwclient.RWClient

18.1.8.3 Reports In-process Server

If the Java Virtual Machine (JVM) is set to ojvm, minimal, or vanilla in Oracle JDeveloper's Virtual Machine settings (Project Settings > Runner > Virtual Machine), the rwservlet's in-process server is not stopped when JDeveloper's embedded OC4J server is terminated. As a result, a port conflict occurs the next time OC4J is started. To avoid this problem, do one of the following:

  • Set the JVM to hotspot.

  • Disable the in-process server in ORACLE_HOME/reports/conf/rwservlet.properties by setting:

    server_in_process=no
    
    
  • Use the standalone Reports Server instead.

18.1.9 OracleAS Reports Services Demos Will Not Work if JServ is Configured

If you configure JServ and OracleAS Reports Services in the same application server instance, you will not be able to run OracleAS Reports Services demos.

18.2 Configuration Issues and Workarounds

This section describes configuration issues and their workarounds for Oracle Reports. It includes the following topics:

18.2.1 Implementing Removal of DISPLAY and Printer Dependencies

With Oracle Reports 10g (9.0.4), it is no longer necessary to have the DISPLAY environment variable or a valid printer defined at runtime (PRINTER or TK_PRINTER).

Even if the environment variable DISPLAY is defined, the X-Windows display surface will not be used by default.

For existing customers upgrading to Oracle Reports 10g (9.0.4), this change may impact the appearance, number of pages, output file size, or performance of existing reports. If necessary, the previous behavior can be restored by setting the environment variables DISPLAY to the active X-Windows display surface and REPORTS_DEFAULT_DISPLAY to NO.


See Also:

  • Oracle Application Server Reports Services Publishing Reports to the Web and the Reports Builder Online Help for more information on the REPORTS_DEFAULT_DISPLAY environment variable and screenprinter.ppd.

  • Section "Fonts in Report Output" in the chapter "Managing Fonts in Oracle Reports" in Oracle Application Server Reports Services Publishing Reports to the Web.


18.2.2 Printing on Solaris Version 2.9

If you print a report using the destype=printer and the desname=printer_name command line options on Solaris 2.9, you may encounter the following errors:

REP-0069: Internal error
REP-57054: Inprocess job terminated with error
REP-50157: Error while sending file to printer 2op837a.Exit with error code 1

To resolve this issue, you must do the following:


Note:

Create a backup of the rwlpr.sh file before proceeding. On Solaris, rwlpr.sh is the printing script file located in the ORACLE_HOME/bin/ directory. This script file supports lp and lpr commands by default.

  1. Navigate to the following line at the end of the file:

    #either LPR or LP Command was found
    
    
  2. Add an OR operator to the existing if...else condition.

    if [ `uname -r` = "5.8" ] || [ `uname -r` = "5.9" ] # If Solaris Release 5.8 / 5.9
       ...
       else
       # parse and Fix the command Line as Required by lp
       					...
         if [ `uname -r` = "5.8" ] || [ `uname -r` = "5.9" ]# If Solaris Release   
         5.8/ 5.9 
    
    

    The if...else if condition checks for the Solaris Release version. Based on the version number, it strips the quotes from the printer name and passes it to the print command.

18.2.3 Using the Graph Wizard in a Multibyte Environment

On Solaris, invoking the Graph Wizard in a multibyte (Japanese, Simplified Chinese, and Korean) environment causes Reports Builder to stop responding.

To work around this issue, you must:

  1. Install J2SE Version 1.4.2 on your machine. J2SE 1.4.2 is downloadable at Sun's site.

  2. Set the path to the J2SE home in the reports.sh file:

    PATH=$J2SEHOME/bin:$ORACLE_HOME/jdk/bin:$ORACLE_HOME/bin:${PATH};
    export PATH
    
    
  3. Modify LD_LIBRARY_PATH in reports.sh to point to the location of the J2SE home:

    LD_LIBRARY_PATH=$J2SEHOME/lib/sparc:$ORACLE_HOME/jdk/jre/lib/sparc:
    $ORACLE_HOME/lib:${LD_LIBRARY_PATH}; export LD_LIBRARY_PATH 
    

18.2.4 Repairing Fonts Not Appearing Correctly in Web Source View

Text in the user interface of Reports Builder, such as the window title, uses fonts taken from the system resource files for the current language. These system resource files are supplied with the Oracle Reports installation. In Oracle Reports, you can map these fonts in the [RWBUILDER] section of uifont.ali. If found, the mapped font is used instead of the original font; if not, Oracle Reports uses the original font.


Note:

The mapped font needs to be a fixed-width font.

In the Web Source view of the Report Editor, the following languages may appear garbled: Arabic, Central European languages, Cyrillic, Greek, Hebrew, Japanese, Thai, and Turkish. To work around this issue, you can set the font names for Reports Builder in uifont.ali as follows:

[rwbuilder]
.....AR8MSWIN1256="Courier New"
.....CL8MSWIN1251="Courier New"
.....EE8MSWIN1250="Courier New"
.....EL8MSWIN1253="Courier New"
.....IW8MSWIN1255="Courier New"
.....JA16SJIS="MS Gothic"
.....TH8TISASCII="Andale Duospace WT"
.....TR8MSWIN1254="Courier New"

You can download a copy of the Andale Duospace WT (fixed-width) font from Oracle Metalink, (http://metalink.oracle.com). The ARU number is 2638552.

18.2.5 Configuring Reports Server for a Heavily Loaded Machine

Before you deploy a report on a machine that is either slow or heavily loaded, you may want to configure the following:

  • Ping timeout (OPMN-side): Ping timeout is the measure that OPMN uses to determine the time that it must wait for a callback from an in-process Reports Server (in OC4J_BI_FORMS), before considering it as a timeout.

    The default timeout period is 150.  This period is calculated from: ping timeout, ping interval, and number of retries. The default values for these are:

    ping timeout = 30 seconds

    ping interval = 20 seconds

    number of retries = 3


    Note:

    The number of retries is applicable only when OPMN successfully connects to OC4J and receives regular ONS notifications from the process.

    Based on these values, there will be three ping attempts with a timeout of 30 seconds each at 20 second intervals. The first ping is done after the specified ping interval. Thus, from the time OC4J is started by OPMN, approximately 150 (20 + 3*30 + 2*20) seconds will elapse before the process is considered unresponsive and restarted. If OPMN connects to OC4J but OC4J is too slow in sending regular ONS notifications, then the 30 second timeout is applicable.


    See Also:

    Oracle Application Server Reports Services Publishing Reports to the Web for more information on the opmn.xml file.

  • Callback timeout (Reports Server-side): Callback timeout is the measure that Reports Server uses to determine the time that it must wait for a response from the engine before timing out. You can specify this value in the Reports Server configuration file, server_name.conf. This time out period is in milliseconds.

    For example:

    <engine id="rwEng" class="oracle.reports.engine.EngineImpl" initEngine="1" maxEngine="1" minEngine="0" engLife="50" maxIdle="30" callbackTimeOut="80000">
    

Note:

Increase the timeout when the machine is very slow.

18.2.6 Changing the Administrator Login by Using Reports Queue Manager

In Oracle Reports, if you use the Reports Queue Manager to change the administrator password, you will be unable to perform the following actions from Oracle Enterprise Manager/OPMN:

  • Start or stop the Reports Server.

  • View the Reports Server's metrics.

Recommendation

The recommended way of managing a Reports Server is through Oracle Enterprise Manager/OPMN.

However, if you change the administrator password by using Reports Queue Manager, you must do the following:

  1. Add the modified username and password to the targets.xml file under the specified Reports Server entry.

  2. Set ENCRYPTED=FALSE.

    For example:

    <Property NAME="UserName" VALUE="foo" ENCRYPTED="FALSE"/>
    ...
    ...
    <Property NAME="Password" VALUE="hello123" ENCRYPTED="FALSE"/>
    
    
  3. Restart Oracle Enterprise Manager. When Oracle Enterprise Manager restarts, it will encrypt the username and password and set ENCRYPTED=TRUE.

18.2.7 Improving Image Resolution of Graphs Output to a PDF File or a Printer

The REPORTS_GRAPH_IMAGE_DPI environment variable specifies a dots per inch (DPI) value for graphs output to a a PDF file or a printer. The default value for this environment variable is set at 72 DPI to minimize the time taken to generate the report as well as to reduce the report file size.

If you specify a value higher than 72 DPI, you will see an improvement in the image resolution for graphs sent to a PDF file or a printer. However, this affects the time taken to generate the report output as well as the file size.


Note:

With the value of 250:
  • The time taken to generate a report with an Oracle Reports graph increases 5 to 6 times when compared to the time taken to generate the same report with the value set to 72 DPI.

  • The PDF file size also increases 5 to 6 times.


Valid Values  

72 through 300

Default  

72

Usage Notes

18.2.8 Specifying the Values for Oracle Reports' Java Virtual Machine

You may want to set the JVM options explicitly to get certain, specific functionality from the JVM that aren't enabled, by default. To do so, use the command line keyword JVMOPTIONS to set options for either Reports Runtime, Reports Builder, or Reports Converter's Java Virtual Machine (JVM).

For example, you could use the following command line to start Reports Builder with a 512 MB heap space:

rwbuilder jvmoptions=-Xmx512M

Multiple options can be passed, in which case the options must be enclosed in quotes:

rwbuilder jvmoptions="-Xmx256M -Xms=128M"

Syntax 

JVMOPTIONS={options in reports runtime, reports builder, reports converter JVM}

Default 

-Xmx256M

Note:

The value set using the jvmoptions keyword will override the value in the REPORTS_JVM_OPTIONS environment variable, if set.

18.2.9 Resolving Reports-Portal Integration Error in a Mixed Version Environment

In OracleAS Portal, when configuring Oracle Reports Security settings for Reports Definition File Access, you may encounter an error when editing a reports definition file, when you click Run or Run as Portlet.

500 Internal Server Error 
Unexpected Error. Please contact Administrator

This error occurs when all of the following conditions are true:

  • Running in a mixed 9.0.2/9.0.4 environment, with the middle-tier (MT) and Identity Management (IM) using version 9.0.4, and with the metadata repository (MR) using version 9.0.2.

  • Running Oracle Reports within OracleAS Portal, using the SSOCONN parameter.

  • The connection resource specified in the SSOCONN parameter has not been created in the Oracle Internet Directory server.

To implement the workaround, perform the following steps:

  1. In the 9.0.4 IM ORACLE_HOME, open the following file in a text editor:

    ORACLE_HOME/Apache/Apache/conf/mod_osso.conf 
    
    
  2. Add the following flag:

    OssoRedirectByForm on
    
    

    For example:

    <IfModule mod_osso.c> 
    OssoIpCheck off 
    OssoIdleTimeout off 
    OssoConfigFile 
    /private1/iasinst/install_set1/904infra/Apache/Apache/conf/osso/osso.conf
    OssoRedirectByForm on 
    </IfModule>
    

18.3 Administration Issues and Workarounds

This section describes administration issues and their workarounds for Oracle Reports. It includes the following topics:

18.3.1 Authenticating Enterprise Manager Access to Reports Server Information

The identifier element in server_name.conf contains a new value, SERVERACCESSKEY. This value is used to ensure that the Reports Server information in Enterprise Manager is secure.

The following authentication is implemented:

  • The value of the identifier element in the server_name.conf file is encrypted and is of the form %SERVERACCESSKEY_USER%/%SERVERACCESSKEY_PASSWORD%. For example:

    <identifier confidential="yes" encrypted="no">
    %SERVERACCESSKEY_USER%/%SERVERACCESSKEY_PASSWORD%</identifier>
    

  • The corresponding entries in the targets.xml file are:

    <Property NAME="UserName" VALUE="%SERVERACCESSKEY_USER%" ENCRYPTED="FALSE"/>
    <Property NAME="Password" VALUE="%SERVERACCESSKEY_PASSWORD%" ENCRYPTED="FALSE"/>
    

The default installation ensures that the install time values of %SERVERACCESSKEY_USER% and %SERVERACCESSKEY_PASSWORD% match those in targets.xml.


Note:

%SERVERACCESSKEY_USER% and %SERVERACCESSKEY_PASSWORD% in server_name.conf and targets.xml must match for the Reports Server pages in Enterprise Manager to display data correctly.

To change the user name and password:

  1. Edit the ORACLE_HOME/reports/conf/server_name.conf file, as follows:

    <identifier confidential="yes" encrypted="no">new_username/new_password</identifier>

  2. Edit the ORACLE_HOME/sysman/emd/targets.xml file, as follows:

    <Property NAME="UserName" VALUE="new_username" ENCRYPTED="FALSE"/>
    <Property NAME="Password" VALUE="new_password" ENCRYPTED="FALSE"/>
    
    
  3. Restart Enterprise Manager and Reports Server. The user name and password in server_name.conf and targets.xml will be encrypted after the restart.


Note:

Beginning with Oracle Reports 10g (9.0.4), Oracle Enterprise Manager (Enterprise Manager) will not use Oracle Internet Directory authentication to access Reports Server information. It will use the SERVERACCESSKEY value to implement the authentication.

18.3.2 Running Reports on OracleAS Portal as an Item Link

When you install OracleAS Portal with a non-default language setting, some entries required to publish a report as an item link on a portal page are not installed automatically. You must install the language of your choice by using the rwlang.sql script.

Thus, you must run the script rwlang.sql (ORACLE_HOME/portal/admin/plsql/wwd/) if:

  • You have selected at least one language in addition to the default ("US") at the time of installing OracleAS Portal.

    AND

  • You want to publish a report as an item link in OracleAS Portal.


    Note:

    This is a one time post-installation task and will ensure that you can publish a report as an item link on OracleAS Portal.

To run the script:

  1. Change the directory to ORACLE_HOME/portal/admin/plsql/wwd/.

  2. Run sqlplus.

  3. Log on to OracleAS Portal using the portal schema.


    Note:

    This is the portal schema used to install OracleAS Portal PL/SQL packages.

  4. Run the rwlang.sql script with the following parameters:

    @rwlang.sql language_list
    
    

    where

    language_list is the list of languages separated by commas.

    For example, to install French and Japanese:

    @rwlang.sql f,ja
    

Usage Notes

  • There should be no space before or after the comma (,) because sqlplus treats the language list as two parameters, instead of one parameter separated by a comma (,).

  • The header of the rwlang.sql script contains the complete list of all language abbreviations. Edit the script file using any text editor to find out the various abbreviations.

18.4 NLS-Specific Issues and Workarounds

This section describes NLS-specific issues and their workarounds for Oracle Reports. It includes the following topics:

18.4.1 Opening/Running an Encoded JSP Report

If your JSP report's character encoding (for example, EUC-JP) differs from the character set portion of the NLS_LANG environment variable (for example, JA16SJIS), you will get the following errors:

  • When running the JSP file

    REP-6106 or 6104 with javax.servlet.jsp.JspException  (multibyte)
    REP-0495 Unable to tokenize the query (singlebyte)
    
    
  • When opening the JSP file using Reports Builder

    REP-0069 Internal Error or REP-6106
    
    

To work around this issue, you must ensure that your JSP report's character encoding matches the IANA encoding corresponding to Reports Builder's character set portion of the NLS_LANG variable.

For example:

JSP Report encoding:

<%@ page contentType="text/html;charset=EUC-JP" %>
<META http-equiv="Content-Type" content="text/html;charset=EUC-JP">

This JSP file needs to be encoded in the character set (EUC-JP).

Reports Builder encoding:

NLS_LANG=JAPANESE_JAPAN.JA16EUC

In this example, the JSP report's encoding (EUC-JP) matches Reports Builder's character set portion of NLS_LANG, that is, JA16EUC.

18.4.2 Embedding a Character Set in a JSP file Dynamically

In Oracle Reports, Web-report templates are configured for Western European character encoding by default. However, for other languages, you can specify the character encoding for every JSP file by using both the charset attribute of the <Meta> tag and the <%@page%> page directive.

To dynamically associate the appropriate character encoding with the JSP file, you can make the following modifications:

  1. Edit the rw*.html files and the blank_template.jsp file:

    1. Modify the page directive to read

      <%@ page contentType="text/html;charset=yourIANAencoding" %>
      
      

      where:

      yourIANAencoding is the IANA encoding name that corresponds to the NLS_CHARACTERSET portion of the NLS_LANG variable.

    2. Modify the <Meta> tag inside the <Head> tag to read:

      <meta http-equiv="Content-Type" content="text/html;charset=yourIANAencoding" />
      

    Note:

    The template files, i.e., rw*.html, and blank_template.jsp, are located in the ORACLE_HOME/reports/templates/ directory.

  2. Edit the template.xsl (ORACLE_HOME/reports/templates/) file:

    1. Modify the <xsl:output> tag to read:

      <xsl:output
           method="jsp"
           indent="yes"
           encoding="yourIANAencoding"
         />
      
      

      where:

      yourIANAencoding is the IANA encoding name that corresponds to the NLS_CHARACTERSET portion of the NLS_LANG variable.

    2. Add the page directive to the file:

      <%@ page contentType="text/html;charset=yourIANAencoding" %>
      
      
    3. Add or modify the <META> tag inside the <HEAD> tag:

      <meta http-equiv="Content-Type" content="text/html;charset=yourIANAencoding" />
      
      

      where:

      yourIANAencoding is the IANA encoding name that corresponds to the NLS_CHARACTERSET portion of the NLS_LANG variable.

18.4.3 Running a Multibyte Report Containing an Embedded Oracle Object

Reports Builder stops responding when you run a multibyte report containing an embedded Oracle Object type. This issue is known to occur on Windows and LINUX platforms.

18.4.4 Providing the location to a characterset-specific Tk2Motif.rgb file

Oracle Reports locates the Tk2Motif.rgb file based on the language portion of the NLS_LANG environment variable, by default. This file location varies based on the language setting: ORACLE_HOME/guicommon9/tk90/admin/<language>


Note:

The Tk2Motif.rgb file contains resource settings for the Motif version of the Oracle Toolkit, for example, the font mapping between Oracle Reports NLS_CHARACTERSET and X fonts.

If Oracle Reports locates a Tk2Motif.rgb file whose character set setting differs from the character set portion of your NLS_LANG, then you may get the REP-3000 error.

For example:

If you have set NLS_LANG=AMERICAN_AMERICA.JA16EUC, then Oracle Reports locates the file from the following directory:

ORACLE_HOME/guicmmon9/tk90/admin/Tk2Motif.rgb

This causes the REP-3000 error, as this Tk2Motif.rgb file is designed for the WE8ISO8859P1 character set and not for the JA16EUC character set.

You can set the value of the TK90_UNKNOWN to the location of your characterset-specific Tk2Motif.rgb file.

Valid Values The location to the valid TK2Motif.rgb file.

Example 

$ORACLE_HOME/guicommon9/tk90/admin/JA
(NLS_LANG=AMERICAN_AMERICA.JA16EUC)

18.4.5 Viewing Oracle Enterprise Manager Screens in Non-European Languages

In Oracle Enterprise Manager Application Server Control, you may see garbled titles on the following Reports Server pages for non-Western-European languages:

  • Engine

  • Configuration

  • Edit Configuration File

18.4.6 Running Oracle Reports in a Japanese Environment on HP-UX

If you want to use Oracle Reports in the HP-UX Japanese environment with NLS_LANG=JAPANESE_JAPAN.JA16SJIS, you will need to modify the appropriate Tk2Motif.rgb file before using Oracle Reports because this file contains EUC encoded Japanese resources.

Convert the Tk2Motif.rgb file to EUC encoding, or remove the last seven entries from this file. Otherwise, Oracle Reports may fail.


Note:

The Tk2Motif.rgb file for the Japanese environment is: $ORACLE_HOME/guicommon9/tk90/admin/JA/Tk2Motif.rgb.

18.4.7 Specifying the Encoding of an XML PDS Report

The Tk2Motif.rgb file for the Japanese environment is: $ORACLE_HOME/guicommon9/tk90/admin/JA/Tk2Motif.rgb.

When you create a report against an XML data source, you must ensure that the encoding of both the XML file (data source) as well as the DTD matches the encoding of Reports Builder.

When you create an XML report against a table -- for example, a Japanese table-- the group element name is in the table's language that is Japanese. To match the data source, you should set the group's element name in the DTD to Japanese. The XML and DTD files can be in any encoding that supports Japanese, for example, Shift_JIS, EUC-JP, or UTF-8. However, when the encoding of the XML data source as well as the DTD differs from Reports Builder, you will see the following error:

ERR-063001 xxx.dtd null


Note:

This error is not displayed if you use an XML schema to define the rules.

To work around this issue, you must ensure that both the data source XML files as well as the DTD file for an XML report is encoded in the character set portion of Reports Runtime NLS_LANG.

For example, if your NLS_LANG=JAPANESE_JAPAN.JA16SJIS, then both your data source XML file as well as your DTD file should be encoded in Shift_JIS.

18.5 Documentation Errata

This section describes known errors in the documentation.

18.5.1 Deploying an Oracle Reports JSP to an OC4J_BI_FORMS Instance

This section outlines the updated steps needed to deploy an Oracle Reports JSP file to either an existing or a new instance of OC4J_BI_FORMS.

18.5.1.1 Using an Existing Instance

  1. Ensure that you have created the J2EE application. Refer to Oracle Application Server Reports Services Publishing Reports to the Web for more information on creating a J2EE application for Oracle Reports.

  2. In Oracle Enterprise Manager, display the detail page for your middle-tier.

  3. Under System Components, click OC4J_BI_Forms.

  4. In the OC4J_BI_FORMS page, click Administration.

  5. Under Deployed Applications, click Deploy EAR file to deploy the EAR file you created.

  6. On the first page of the Deploy Application wizard, click Browse to select the J2EE application (EAR file) to be deployed or enter the location of the EAR file you created.

  7. Under Application Name, specify a unique application name for this application. For example, MyReportApp.

  8. From the Parent Application list, select the parent application and click Continue.

  9. On the URL Mapping page, note that the text in the URL Mapping field is the name your users will enter to access the new application.

  10. In the URL Mapping field, add a forward slash (/) to the beginning of the application name, since it is part of a URL address. For example:

    /MyReportApp
    
    
  11. Click Finish.

  12. On the next page, click Deploy.

  13. On the OC4J_BI_Forms detail page that displays, you should now see your application (MyReportApp) listed under Deployed Applications.

  14. Click your application name (MyReportApp).

  15. On the Application page, under Properties, click General.

  16. Under Library Paths, click Add Another Row, then add the following path to the rwrun.jar library:

    $ORACLE_HOME\reports\jlib\rwrun.jar
    
    
  17. Add another row with the following path to the zrclient.jar library:

    $ORACLE_HOME\jlib\zrclient.jar
    
    
  18. Click Apply, then click OK.

  19. Click Stop, then Start to restart your application so that the new library paths take effect.

18.5.1.2 Using a New Instance

  1. Ensure that you have created the J2EE application. Refer to Oracle Application Server Reports Services Publishing Reports to the Web for more information on creating a J2EE application for Oracle Reports.

  2. In Oracle Enterprise Manager, display the detail page for your middle-tier.

  3. Click Create OC4J Instance.

  4. Type the name of your OC4J instance.

  5. Click Create.

  6. Once the OC4J instance is created, click OK.

  7. On Application Server page, under System Components, you should now see the new OC4J instance.

    Now, you must manually configure the OC4J to support connection to a Reports Server and the security integration.

  8. Copy the following properties and their definitions in the oc4j.properties file from an existing OC4J instance, for example the OC4J_BI_FORMS instance ($ORACLE_HOME/j2ee/OC4J_BI_FORM/config/oc4j.properties), into the oc4j.properties file of your new OC4J instance ($ORACLE_HOME/j2ee/your application/config/oc4j.properties):

    • oracle.home

    • oracle.path

  9. In the opmn.xml file in your $ORACLE_HOME/opmn/conf directory, add the PATH (Windows) or LD_LIBRARY_PATH (UNIX) to your new OC4J instance:

    1. In $ORACLE_HOME/opmn/conf/opmn.xml, find the XML element that describes your new OC4J instance:

              <process-type id="<your application>" module-id="OC4J">
               <module-data>
                        <category id="start-parameters">
                           <data id="java-options" value="-server
       -Djava.security.policy=$ORACLE_HOME/j2ee/MyOC4JInst/config/java2.policy
       -Djava.awt.headless=true"/>
                           <data id="oc4j-options" value="-properties"/>
                        </category>
                        <category id="stop-parameters">
                           <data id="java-options"
       value="-Djava.security.policy=$ORACLE_
      HOME/j2ee/MyOC4JInst/config/java2.policy -Djava.awt.headless=true"/>
                        </category>
                     </module-data>
                     <start timeout="900" retry="2"/>
                     <stop timeout="120"/>
                     <restart timeout="720" retry="2"/>
                     <port id="ajp" range="3301-3400"/>
                     <port id="rmi" range="3201-3300"/>
                     <port id="jms" range="3701-3800"/>
                     <process-set id="default_island" numprocs="1"/>
                  </process-type>
      
      
    2. Add the PATH (Windows) or LD_LIBRARY_PATH (UNIX), module data properties by copying them from the OC4J_BI_FORMS instance in the same opmn.xml file, for example:

                     <environment>
                        <variable id="LD_LIBRARY_PATH" value="$ORACLE_
      HOME/lib:$ORACLE_HOME/network/lib:$ORACLE_HOME/jdk/jre/lib/sparc"/>
                     </environment>
                    <category id="start-parameters">
                           <data id="java-options" value="-server
       -Djava.security.policy=$ORACLE_HOME/j2ee/OC4J_BI
      _Forms/config/java2.policy -Djava.awt.headless=true -Xmx512M
       -Xbootclasspath/p:$ORACLE_HOME/vbroker4/lib/vbjboot.jar "/>
                           <data id="oc4j-options" value="-properties
       -userThreads "/>
                        </category>
                        <category id="urlping-parameters">
                           <data
       id="/MyReportsApp*/rwservlet/pingserver?start=auto" value="200"/>
                        </category>
                     <dependencies>
                        <database infrastructure-key="portal"/>
                        <managed-process process-type="HTTP_Server"
       process-set="HTTP_Server" ias-component="HTTP_Server" autostart="true"/>
                     </dependencies>
      

      *where MyReportsApp is your newly created Web application name for Oracle Reports.

    3. Restart the OC4J instance.