|
Oracle® Application Server Release Notes
10g (9.0.4) for Microsoft Windows Part No. B13749-11 |
|
 Previous |
 Next |
|
Oracle® Application Server Release Notes
10g (9.0.4) for Microsoft Windows Part No. B13749-11 |
|
|
Previous |
Next |
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.
|
This section describes general issues and their workarounds for Oracle Reports. It includes the following topics:
Section 18.1.1, "Viewing the rwconverter Help on Oracle Application Server"
Section 18.1.3, "Inserting a Graph in the Paper Design View for a Matrix-with-Group Report"
Section 18.1.4, "Running a Report with an Embedded 6i Graphic on an OPMN-Managed Reports Server"
Section 18.1.6, "FTP and WebDaV Destinations Not Supported from Reports Builder"
Section 18.1.8, "OracleAS Reports Services Demos Will Not Work if JServ is Configured"
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):
Navigate to http://otn.oracle.com/reports/help/.
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.
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.
|
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.
If you are managing a Reports Server using Oracle Enterprise Manager/OPMN, you cannot run a report containing an embedded 6i graphic on that Reports Server as it will fail.
However, you can run the same report (containing an embedded 6i graphic) on a Reports Server that is started as a Windows service, after applying the workarounds specified in Section 2.1.3.1 and Section 3.8 of the Oracle Application Server Reports Services Publishing Reports to the Web manual.
Recommendation
Run the report containing the embedded 6i graphic on a standalone Reports Server that is started using the command prompt.
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 Windows is 5147374.
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.
This section describes issues with Oracle JDeveloper integration. It includes the following topics:
Section 18.1.7.1, "Deadlock When Debugging JSP Reports in Oracle JDeveloper"
Section 18.1.7.2, "Graph Not Appearing 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.
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
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.
This section describes configuration issues and their workarounds for Oracle Reports. It includes the following topics:
Section 18.2.1, "Invoking the Getting Started Page from Reports Builder"
Section 18.2.2, "Repairing Fonts Not Appearing Correctly in Web Source View"
Section 18.2.3, "Configuring Reports Server for a Heavily Loaded Machine"
Section 18.2.5, "Changing the Administrator Login by Using Reports Queue Manager"
Section 18.2.6, "Improving Image Resolution of Graphs Output to a PDF File or a Printer"
Section 18.2.7, "Specifying the Values for Oracle Reports' Java Virtual Machine"
Section 18.2.8, "Resolving Reports-Portal Integration Error in a Mixed Version Environment"
If you invoke the Getting Started page from Reports Builder, you may encounter either of the following error messages:
Error: REP-0911: The Quick Tour cannot be found. Please reinstall the Quick Tour and Try again.
Failed to locate browser (Netscape 7.0).
Workaround
To rectify this issue, you must:
Edit the Windows registry using a registry editor (for example, regedit.exe).
|
Note: Before you edit the registry, back it up. |
Navigate to the following key:
HKEY_CURRENT_USER\Software\Oracle\Toolkit\Tkbrowser
Verify the TKBrowser settings in your registry.
Ensure that the BrowserName and the BrowserPath keys reflect the correct values.
For example:
Value data (BrowserName)= Netscape 7
Value data (BrowserPath)= C:\Program Files\Netscape\Netscape\Netscp.exe
Run Reports Builder and select Getting Started.
Click OK. The Information Navigator Preferences dialog box appears.
Select Netscape Navigator 7.0+ as the browser.
Ensure that the path and the browser program name are accurate. To change the browser location (if the path or the program name is incorrect):
Click Browse.
Navigate to the location.
Click OK.
In the Information Navigator Preferences dialog box, click OK.
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.
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 theopmn.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. |
It is not recommended to start or stop a Reports Server that is managed by Oracle Enterprise Manager/OPMN as a Windows service or through the command line. If you do, you may face the following issues:
The status of the Reports Server will not be reflected accurately.
Oracle Enterprise Manager may display errors when starting or stopping the Reports Server.
Workaround
You must start or stop a Reports Server that is registered with Oracle Enterprise Manager only through Oracle Enterprise Manager/OPMN.
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:
Add the modified username and password to the targets.xml file under the specified Reports Server entry.
Set ENCRYPTED=FALSE.
For example:
<Property NAME="UserName" VALUE="foo" ENCRYPTED="FALSE"/> ... ... <Property NAME="Password" VALUE="hello123" ENCRYPTED="FALSE"/>
Restart Oracle Enterprise Manager. When Oracle Enterprise Manager restarts, it will encrypt the username and password and set ENCRYPTED=TRUE.
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:
|
Valid Values
72 through 300
Default
72
Usage Notes
On Windows, use the registry to specify the value.
When you set a DPI value greater than 250 and your chart is bigger than 5"x5" (approximately), you may also need to change the JVM heap size value via REPORTS_JVM_OPTIONS to avoid the Out Of Memory error for the JVM.
|
See Also: Oracle Application Server Reports Services Publishing Reports to the Web for more information on setting the JVM options. |
This variable is currently not supported in Oracle Reports distribution functionality as this is specific to PDF and printer outputs only.
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 thejvmoptions keyword will override the value in the REPORTS_JVM_OPTIONS environment variable, if set.
|
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:
In the 9.0.4 IM ORACLE_HOME, open the following file in a text editor:
ORACLE_HOME/Apache/Apache/conf/mod_osso.conf
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>
This section describes administration issues and their workarounds for Oracle Reports. It includes the following topics:
Section 18.3.1, "Authenticating Enterprise Manager Access to Reports Server Information"
Section 18.3.2, "Running Reports on OracleAS Portal as an Item Link"
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:
Edit the ORACLE_HOME/reports/conf/server_name.conf file, as follows:
<identifier confidential="yes" encrypted="no">new_username/new_password</identifier>
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"/>
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 theSERVERACCESSKEY value to implement the authentication.
|
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:
Change the directory to ORACLE_HOME/portal/admin/plsql/wwd/.
Run sqlplus.
Log on to OracleAS Portal using the portal schema.
|
Note: This is the portal schema used to install OracleAS Portal PL/SQL packages. |
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.
This section describes NLS-specific issues and their workarounds for Oracle Reports. It includes the following topics:
Section 18.4.2, "Embedding a Character Set in a JSP file Dynamically"
Section 18.4.3, "Running a Multibyte Report Containing an Embedded Oracle Object"
Section 18.4.4, "Viewing Oracle Enterprise Manager Screens in Non-European Languages"
Section 18.4.5, "Specifying the Encoding of an XML PDS 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.
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:
Edit the rw*.html files and the blank_template.jsp file:
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.
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.
|
Edit the template.xsl (ORACLE_HOME/reports/templates/) file:
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.
Add the page directive to the file:
<%@ page contentType="text/html;charset=yourIANAencoding" %>
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.
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.
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
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.
This section describes known errors in the documentation.
Chapter 19, "Managing and Monitoring OracleAS Reports Services", of the Oracle Application Server Reports Services Publishing Reports to the Web manual may show screenshots that do not reflect the latest updates to the Oracle Enterprise Manager user interface.
Due to improvements on OTN, the URL that directly accesses the Oracle Reports Documentation page is incorrect in the documentation. Instead of http://otn.oracle.com/docs/products/reports/content.html, the revised URL is http://otn.oracle.com/documentation/reports.html.
Chapter 13, section 13.3.3.2, of the Oracle Application Server Reports Services Publishing Reports to the Web manual contains certain steps that have not been updated. The section, Section 18.5.1, "Deploying an Oracle Reports JSP to an OC4J_BI_FORMS Instance", outlines the entire section with the updated steps for your convenience.
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.
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.
In Oracle Enterprise Manager, display the detail page for your middle-tier.
Under System Components, click OC4J_BI_Forms.
In the OC4J_BI_FORMS page, click Administration.
Under Deployed Applications, click Deploy EAR file to deploy the EAR file you created.
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.
Under Application Name, specify a unique application name for this application. For example, MyReportApp.
From the Parent Application list, select the parent application and click Continue.
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.
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
Click Finish.
On the next page, click Deploy.
On the OC4J_BI_Forms detail page that displays, you should now see your application (MyReportApp) listed under Deployed Applications.
Click your application name (MyReportApp).
On the Application page, under Properties, click General.
Under Library Paths, click Add Another Row, then add the following path to the rwrun.jar library:
$ORACLE_HOME\reports\jlib\rwrun.jar
Add another row with the following path to the zrclient.jar library:
$ORACLE_HOME\jlib\zrclient.jar
Click Apply, then click OK.
Click Stop, then Start to restart your application so that the new library paths take effect.
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.
In Oracle Enterprise Manager, display the detail page for your middle-tier.
Click Create OC4J Instance.
Type the name of your OC4J instance.
Click Create.
Once the OC4J instance is created, click OK.
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.
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
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:
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>
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.
Restart the OC4J instance.
