Using the BI Publisher Java APIs 7-3
In addition, the following libraries are required:
■
aolj.jar - version information for Oracle E-Business Suite
■
collections.jar - you only need this if you are working with the delivery APIs or bursting engine.
■
dvt-jclient.jar - a charting library
■
dvt-utils.jar - a charting library
■
groovy-all-1.6.3.jar - Groovy
■
i18nAPI_v3.jar - the i18n library used for localization functions
■
jewt4.jar - a charting support library
■
mail.jar - used for SMTP delivery
■
ojdl.jar - used for Oracle Diagnostic Logging
■
orai18n-collation.jar - used by XDK
■
orai18n-mapping.jar - used by XDK
■
orai18n.jar - contains character set and globalization support files used by XDK
■
osdt_cert.jar - security library for SMIME support
■
osdt_cms.jar - security library for SMIME support
■
osdt_core.jar - security library for SMIME support
■
osdt_smime.jar - security library for SMIME support
■
share.jar - a charting support library
■
xdoparser.jar - the scalable XML parser and XSLT 2.0 engine 10g
■
xdoparser11g.jar - the scalable XML parser and XSLT 2.0 engine 11g
■
xmlparserv2.jar - 11g XDK SAX and DOM
7.3 Obtaining the Libraries
If you are using Oracle JDeveloper, then the charting and XML Parser libraries are available to you. However, it is recommended that you create a directory with all of
the required JAR files to use as a custom library in your project. This will help prevent unexpected errors after deployment.
The easiest method to obtain the libraries is to download and install the Template Builder for Microsoft Word Add-in. Download the Template Builder for Word from the
Home page, under Get Started, click Download BI Publisher Tools, then click Template Builder for Word
. The JAR files are packaged with the Template Builder in the jlib library under the
install directory. A sample path to the jlib would be:
C:\Program Files\Oracle\BI Publisher\BI Publisher Desktop\Template Builder for Word\jlib
Note that the Template Builder includes the aolj.jar. You must use the versioninfo.jar instead.
7-4 Developers Guide for Oracle Business Intelligence Publisher
7.4 PDF Form Processing Engine
This section discusses how to use the RTP Processor Engine, and includes the following topics:
■
Section 7.4.1, Overview of the PDF Form Processing Engine
■
Section 7.4.2, Merging a PDF Template with XML Data
■
Section 7.4.3, Merging XML Data with a PDF Template Using InputOutput File Name
■
Section 7.4.4, Merging XML Data with a PDF Template Using InputOutput Streams
■
Section 7.4.5, Merging an XML Data String with a PDF Template
■
Section 7.4.6, Retrieving a List of Field Names
7.4.1 Overview of the PDF Form Processing Engine
The PDF Form Processing Engine creates a PDF document by merging a PDF template with an XML data file. This can be done using file names, streams, or an XML data
string.
As input to the PDF Processing Engine you can optionally include an XML-based Template MetaInfo .xtm file. This is a supplemental template to define the placement
of overflow data.
The FO Processing Engine also includes utilities to provide information about your PDF template. You can:
■
Retrieve a list of field names from a PDF template
■
Convert XML data into XFDF using XSLT
7.4.2 Merging a PDF Template with XML Data
XML data can be merged with a PDF template to produce a PDF output document in three ways:
■
Using inputoutput file names
■
Using inputoutput streams
■
Using an input XML data string
7.4.3 Merging XML Data with a PDF Template Using InputOutput File Name
Input:
■
Template file name String
■
XML file name String Output:
■
PDF file name String
Example 7–1 Sample Code for Merging XML Data with PDF Templates Using
InputOutput File Names
import oracle.xdo.template.FormProcessor; .
.
