Mcneill 01


Published on

Mcneill 01

Published in: Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Mcneill 01

  1. 1. Converting Oracle Reports to BI Publisher RMOUG Training Days February 24, 2010 Jennifer McNeill Unify/CipherSoft
  2. 2. AgendaChallenges of Reporting within the EnterpriseBenefits of Utilizing BI-PublisherStep by Step Approach to Converting OracleReportsIntegrating Oracle Forms 10g with BI PublisherTechnical IssuesCreating the Project PlanBest PracticesLessons LearnedQ&A
  3. 3. Challenges of Reporting in an Enterprise EnvironmentHigh Fidelity ReportsPartner ReportsFinancial StatementsGovernment formsMarketing materialsContractsChecks, LabelsXMLEFT / EDIMultiple destinations
  4. 4. Challenges of Reporting in an Enterprise EnvironmentMultiple reporting solutionsHighly-skilled engineers required tomaintain servers and report formats◦ Costly◦ Time consuming◦ Complex systems◦ Expensive maintenance◦ Labor intensive
  5. 5. Benefits of BI-PublisherSimplifies Report Maintenance◦ Separate query, layout, and translationReport output provided is:◦ Flexible◦ Reduces maintenance◦ Business users create layouts with familiar desktop toolsRapid DevelopmentExtract Data Once, Publish Many Docs
  6. 6. BI Publisher Benefits - Hot- PluggablePure Java application – Use any J2EE application serverRich set of Java APIs for custom application developmentWeb Services for SOA developmentAny data source: JDBC and Web services XML data sourcesStandard W3C XSL-FO stylesheetsOutput formats in PDF, PS, RTF, HTML…Delivery Support for:◦ Internet Printing Protocol, CUPS◦ Internet Fax Protocol◦ SMTP email protocol◦ WebDAV, FTP, SFTP
  7. 7. First Conversion StepsDuring the conversion process, the source reports musteventually be in Oracle Reports XML formatOracle Reports XML format is supported in OracleReports 9i and aboveIf your source reports are not in Oracle Reports XMLformat, the conversion utility will do this conversionautomaticallyRequires Oracle Reports Designer 9i or later on thesame machine where you will do the conversion so thatOracle BI Publisher conversion utility can call therwconverter executable to get the reports into OracleReports XML format
  8. 8. What will the Converter do? Use rwconverter from Data Oracle Reports to go Template from RDF to RDF XML RDF XML file will beOracle Reports converted to BIPRDF XML PL/SQL objects Data ◦ Data Template ◦ Supporting pl/sql Layout RTF ◦ RTF template Templates Enabled for batch mode processing
  9. 9. Running the Conversion UtilityEnsure the following jar files are in yourclasspath:◦ l -◦ l xmlparserv2-904.jar -◦ l xdocore.jar◦ l aolj.jarThe conversion utility requires JDKversion 1.1.8 or later
  10. 10. Running the Conversion UtilityBIPBatchConversion is the utility to migrate reports from Oracle Reports toBI Publisher.It takes the following parameters:l -source — (required) Source directory for Oracle Reports files. All reportsmust be in the same format - either RDF or XML.l -target — (required) Target directory to create Oracle BI Publisher reportobjects. This includes the Oracle BI Publisher Report file (.xdo), the layouttemplate file (.rtf), the PL/SQL package, and log file.l -oraclehome — (optional) If your reports are in Oracle Reports XMLformat do not specify this parameter. If your reports are not in OracleReports XML format, specify the Oracle home path where Oracle ReportDesigner (9i or later version) is installed.BIPBatchMigration assumes that rwconverter is contained in the bindirectory beneath the Oracle home path.BIPBatchConversion requires rwconverter from Oracle Reports to convertthe report from RDF format to XML format.l -debug — (optional) To run the utility in debug mode and write debugstatements to the log file.
  11. 11. Running the Conversion UtilityCommand Line Usage:◦ java ... BIPBatchConversion [-debug] -source SourceDirectory -target◦ TargetDirectory [-oraclehome OracleHomePath]
  12. 12. Output Files CreatedThe conversion utility will generate the following output filesfor each report:◦ l Report definition file that includes the Data Model (for example: REPORT.xdo)◦ (Note: This file is not needed for E-Business Suite users; see the following note under DataTemplate.) l DataTemplate (for example: REPORT_template.xml) (Note: this is not required for Oracle BI Publisher Enterprise users because the data template is embedded in REPORT.xdo.)◦ l Default PL/SQL package specification (for example: REPORTS.pls)◦ l Default PL/SQL package body (for example: REPORTB.pls)◦ l RTF Layout Template (for example: REPORT.rtf)◦ l Log file (for example: REPORT.log)
  13. 13. Running the Conversion UtilityUpload PL/SQL Package to the Database◦ Many converted Oracle Reports will generate a PL/SQL package specification file and a PL/SQL package body file as follows: l <report_name>S.pls l <report_name>B.pls◦ Run the PL/SQL package files against your Oracle Database as follows. This will create the PL/SQL package specification and body. SQL> @C:BIPublisher_reports raxinvraxinvS.pls SQL> @C:BIPublisher_reports raxinvraxinvB.pls
  14. 14. Running the Conversion UtilityPutting Converted Reports into the Oracle BI PublisherRepository◦ Make your reports visible in the Oracle BI Publisher repository is a two-step process: 1. Copy the report folders into the repository. 2. Refresh the repository metadata.◦ If you have a file-based repository, copy the report folder structure to the file system.Example, suppose your repository path was set to:◦ C:oraclebixmlpXMLPFor the report in the previous example, simply copy thereport directory and all its files to the desired folder structurein the existing report repository
  15. 15. Conversion IssuesOccasionally when converting a more complex Oracle Reportsreport, the Data Template or PL/SQL may contain minorerrors and require manual correction.The conversion utility will move all formula columns to theselect clause of the SQL query in the data model. In mostcases this will not cause a problem. However, if any of thearguments to the formula is a summary column, this will notwork because the summary column will not be calculated atthe time the query is executed.To correct this problem you will need to remove this formulafrom the select clause and implement the formula as XSL inyour layout template. Most of these formulas are used eitherfor simple addition or summation or currency conversion,formatting, and rounding.
  16. 16. Running the Conversion UtilityRTF Layout Template File◦ The majority of Oracle Reports reports use simple if formatting logic that is automatically converted to equivalent XSL-FO and inserted into form fields in the RTF layout template.◦ There is no support for PL/SQL in RTF layout templates.◦ 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.◦ To aid in this process, the resulting RTF template will contain form fields that hold the format trigger names that are called; these fields will be highlighted in red. You can then refer to the log to find the actual PL/SQL code used in the original Oracle Report. You will need to rewrite these PL/SQL triggers as XSL- FO
  17. 17. Standalone Reports ConversionRDF Converter extracts 9i+ rwconverter 9i+ RDF layout and data XML information Enabled for batch mode processing Generates BIP report RTF objects RDF2RTFTemplates Converter Data ◦ Data Template ◦ Supporting pl/sql PL/SQL Layout ◦ RTF templateData These can be loadedTemplate to the BIP server
  18. 18. What will the converter not do?Simple wire frame layout will be created, users need toaddress:◦ Sanity Check – does the template work◦ Fonts◦ Shading◦ BordersFormat triggers on report objects will not be convertedfrom plsql to xsl-fo◦ Observations have noted that the majority of format triggers are of the ‘if’ type i.e. if x=y then zzzzzz◦ These can be very simply converted to Publisher’s XSL format
  19. 19. Integrating Oracle Forms with Bi Publisher Creating a client for the Web Services with Oracle JDeveloper
  20. 20. Integrating Oracle Forms with BI Publisher Select No Template as Application Template
  21. 21. Integrating Oracle Forms with BI Publisher Use BIP_WebService as Project Name When choosing another name pay attention in the document. There are several code pieces using this project name
  22. 22. Integrating Oracle Forms with BI Publisher Select the created Project BIP_WebService.jpr in the Navigator and choose the Project Properties with a right click. Select the Compiler node and set the Source and Target dropdown lists to 1.4. (That’s because of the used JRE of Forms 10.1.2)
  23. 23. Integrating Oracle Forms with BI PublisherWhen working with Oracle Forms you have to replace the version of JDK which is used in the project.Select the Libraries node in the Project Properties and press the button to Change the J2SE version.
  24. 24. Integrating Oracle Forms with Bi Publisher In the Edit J2SE Definition Window go to the left pane and select the node Project.
  25. 25. Integrating Oracle Forms with Bi PublisherBy pressing the button New a window Create J2SE opens where you can reference the necessary J2SE Press the button Browse and select the file java.exe from the directory jdkjrebin in the Oracle Home of your Developer Suite. If you submit your selection with OK you will see that several jar- Files were added to the classpath. In the window Project Properties the version of J2SE should now be set to 1.4.2_14
  26. 26. Integrating Oracle Forms with Bi Publisher After saved the project, right-click the project, choose New and select the Item Web Services Proxy in the Category Business Tier – Web Services
  27. 27. Integrating Oracle Forms with Bi Publisher Choose as your WSDL Document URL the appropriate URL of your BI Publisher Server:http://<machine>:<port>/<yourappname>/services/PublicReportService?wsdl (Default for <yourappname> is xmlpserver)If you run into problems when generating the WSDL from the above URL you could manually create a WSDL file and use it with the second option Mapping File. A complete definition of the WSDL can be found in the documentation at: BHEHEJ. Just copy the text in a file and add it to the content of your project.
  28. 28. Integrating Oracle Forms with Bi Publisher Accept the following two screens and than set your wished Package Name (here bip_webservice.proxy).
  29. 29. Integrating Oracle Forms with Bi Publisher Accept again the two following screens. Check that in the Finish screen the method runReport is available in the service endpoint.
  30. 30. Integrating Oracle Forms with Bi Publisher Finally you’ve created the proxy stub.
  31. 31. Challenges of a Conversion ProjectLimited ResourcesLack of knowledge within staffLack of understanding of future directionNeed to “hang on” to previousenvironmentUnderstanding of Business RequirementsIntegration with present and futureenvironment
  32. 32. Challenges of a Conversion ProjectUtilization of new technology in the mostefficient mannerProject planning for present and futureUtilization of Testing Resources
  33. 33. Thank you for attending! Jennifer McNeill Unify/CipherSoft Office: 403.256.5699 ext 228 Cell: 916-865-6049