|Oracle® Fusion Middleware Oracle Reports User's Guide to Building Reports
11g Release 1 (11.1.1)
Part Number B32122-02
|PDF · Mobi · ePub|
This section provides procedures for the following tasks that you may perform as you integrate your reports with other products:
Oracle Portal is integrated with Oracle Reports. This integration enables you to quickly publish a report as a portlet (that is, a small, dynamic region) or an item on a page, so that end users can easily access dynamic reports.
For general information, refer to the Oracle Technology Network (OTN): on the Oracle Reports page (
http://www.oracle.com/technology/products/reports/index.html), click Getting Started to display the Getting Started with Oracle Reports home page. In the list of topic sections on the left, click Any Format, then select Integration with Oracle Portal.
For detailed information and tasks to publish a report as a portlet in Oracle Portal, see the chapter "Deploying Reports in Oracle Portal" in the Oracle Fusion Middleware Publishing Reports to the Web with Oracle Reports Services manual.
When you install Oracle Portal with a nondefault 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
Thus, you must run
You have selected at least one language in addition to the default (
US) at the time of installing Oracle Portal.
You want to publish a report as an item link in Oracle Portal.
Note:By default, a report is defined in the Main section.
To run the script:
Change the directory to
Log on to Oracle Portal using the portal schema.
rwlang.sql script with the following parameters:
language_list is the list of languages separated by commas.
For example, to install French and Japanese:
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.
Oracle Reports enables you to access any data source. The pluggable data source (PDS) architecture replaces Oracle Open Client Adapter (OCA) and the Open Database Connectivity (ODBC) drivers, which are no longer supported in Oracle Reports. However, Java Database Connectivity (JDBC) is one of the pluggable data sources available that can utilize the JDBC-ODBC bridge, allowing access to other data sources.
Use the following steps to determine the easiest method for accessing your data source:
Does your data source have Java Database Connectivity (JDBC)?
A pluggable data source (PDS) has already been set up. All you have to do is select JDBC as your data type.
Does your data source have ODBC?
If so, make sure that you have downloaded the JDBC-ODBC bridge from Sun Microsystems. This lets you use the JDBC connection mentioned in Step 1. If you do not know if there is an ODBC driver for your data source, check the company Web site. For example, Microsoft has a downloadable ODBC driver for Excel.
Is the file in XML?
Oracle Reports includes an XML PDS. If the DTD file is available, all you have to do is select XML as your data type. If the DTD file is not available, you will have to create one.
Is the file comma-delimited?
You can use the Text PDS included with Oracle Reports to query the data source.
Has someone in your company built a PDS for your data type?
If the PDS exists, it will probably be on the Reports Server. Ask your administrator if such a file exists. If the PDS exists, add it to the classpath for your copy of Oracle Reports Builder. If the PDS does not exist, use the API Reference to help you build one.
Oracle Reports ships with XML data source sample files.
The Pluggable Data Sources section of the Oracle Reports online Help, including the topics:
About pluggable data sources
Adding a pluggable data source
Connecting to a pluggable data source
Adding online Help to a pluggable data source
Pluggable data source interface definition
Troubleshooting PDS problems