Search for the
aolj.jar,collections.jar,xdocore.jar, andxmlparserv2-904.jarfiles on your computer at the location provided in the following URL:C:\OraHome_1\oc4j_bi\j2ee\home\applications\xmlpserver\xmlpserver\WEB-INF\libYou may also find these libraries, or the corresponding classes, under
JAVA_TOP(this is a folder on the Oracle Application middle-tier machine) if you are using Oracle EBS.Copy the files mentioned before to a location of your choice. In this example, the
C:\oracle\convertfolder is used, which is shown in the following screenshot:
Copy the Oracle Reports that have to be converted into the
sourcefolder.Run Oracle Reports Builder and go to the File Conversion tool. Skip this step if your reports are already in the XML format, as shown in the following screenshot:
Browse for your
.rdffile in the Source field and choose Report XML File (XML) as the Destination Type, as shown in the following screenshot:
Once done, a Conversion successful message is displayed, as shown in the preceding screenshot.
Now, run the conversion utility.
BIPBatchConversion is the utility to migrate reports from Oracle Reports to BI Publisher. It takes the following parameters:
source(required): Source directory for Oracle Reports files. All reports must be in the same format, that is, either RDF or XML.target(required): Target directory to create Oracle BI Publisher report objects. This includes the Oracle BI Publisher Report file (.xdo), the layout template file (.rtf), the PL/SQL package, and the log file.oraclehome(optional): If your reports are in Oracle Reports XML format, do not specify this parameter. If your reports are not in Oracle Reports XML format, specify the Oracle home path where Oracle Report Designer (9i or later version) is installed. Refer to the Install Oracle Reports Designer section for this. BIPBatchMigration assumes thatrwconverteris contained in thebindirectory beneath the Oracle Home path.debug(optional): To run the utility in debug mode and write debug statements to the log file.
We already converted our reports to XML format, so the
oraclehomeparameter won't be needed in this case.The command line in our example is:
C:\"Program files"\Java\jre6\bin\java -classpath C:\oracle\convert\xdocore.jar; C:\oracle\convert \collections.zip; C:\oracle\convert\aolj.jar; C:\oracle\convert \xmlparserv2-904.jar oracle.apps.xdo.rdfparser.BIPBatchConversion -source C:\oracle\convert\source -target C:\oracle\convert\target
Output files are generated in a folder for each report. In our case, the folder
Sales600contains these files, as shown in the following screenshot:
Sales600.xdo: Report definition file that includes the Data Model. This file is not needed for EBS users.Sales600_template.xml: It is a Data Template. This is not required for Oracle BI Publisher Enterprise users because the data template is embedded in the.xdofile.Sales600S.pls: This is the default PL/SQL package.Sales600B.pls: This is the default PL/SQL package body.Sales600.rtf: This is the RTF Layout Template.Sales600.log: This is a log file.Sales600_LOV.xml: This is a list of values file.
Load the PL/SQL package into the database.
Create the package and the package body from the
.plsfiles, as shown in the following command lines:SQL> @C:\oracle\convert]target\Sales600\Sales600S.pls
SQL> @C:\oracle\convert]target\Sales600\Sales600B.pls
Upload the report to the Oracle BI Publisher repository.
First copy the files to the repository and then refresh the repository metadata. For this, log on to Oracle BI Publisher with administrator privileges, go to the Admin page, and select Refresh Metadata from the System Maintenance section, as shown in the following screenshot:
Test the report and check the conversion log files to identify any manual modifications needed to complete the conversion.
When converting a complex Oracle Reports report, the Data Template or PL/SQL may contain minor errors and require manual correction. For example, the conversion utility does not convert any PL/SQL format trigger logic present in the report. Instead the conversion utility writes all the format trigger code to a log file. You will need to implement any corresponding PL/SQL logic as XSL code. Refer to Appendix C, Debugging Oracle Reports to BIP Migration, for a more comprehensive example.