Working with XML Conversions 5-3
on. Inbound Refinery will attempt to convert the file using the first selected method that supports the conversion of the format.
For example, consider that you select both the Convert to PDF using third-party applications
option and the Convert to XML option. The refinery will attempt to convert any supported formats to PDF using the Convert to PDF using
third-party applications method. Whether or not this method fails, Inbound
Refinery will not attempt another conversion method for these formats. Therefore, you should typically select only the Convert to XML option if you want to create
XML files as the primary web-viewable rendition.
5. Click Update to save your changes.
6. Click the XML Options button. The
XML Options Page is displayed.
7. Set your XML options, and click Update to save your changes.
8.
Note the following important considerations:
■
If you want to adjust the default settings for the Flexiondoc and SearchML options, you can specify option settings in the intradoc.cfg file located in the
refinery DomainDirucmibrbin directory. For a complete description of available Flexiondoc and SearchML options, refer to the xx.cfg file located in
the refinery IdcHomeDircomponentsXMLConverterresources directory. You must restart your refinery after making changes to the intradoc.cfg file.
■
FlexionDoc and SearchML schema code and documentation files are installed with the XMLConverter component into the refinery
IdcHomeDircomponentsXMLConverter directory.
5.1.4 Setting XML Files as an Additional Rendition
To set XML files as an additional rendition, complete the following steps:
1.
Log into the refinery.
2. From Conversion Settings, select Additional Renditions. The Additional
Renditions page is displayed.
3. Select the Create XML renditions for all supported formats option. Inbound
Refinery will generate an XML file in addition to other renditions such as PDF files.
When the generated XML files are delivered back to a content server, the XML files are included in the full-text index. However, if other web-viewable files are
generated in addition to the XML file, the XML file is not used as the primary web-viewable rendition. For example, if Inbound Refinery generates both a PDF
file and an XML file, the PDF file would be used as the primary web-viewable rendition. XML renditions stored in the content server weblayout directory can be
recognized by the characters x in their filenames. For example, the file Report2001x~2.xml would be an XML rendition.
4. Click Update to save your changes.
5. Click the XML Options button. The
XML Options Page is displayed.
6. Set your XML options, and click Update to save your changes.
7.
Note the following important considerations:
■
If you want to adjust the default settings for the Flexiondoc and SearchML options, you can specify option settings in the intradoc.cfg file located in the
refinery DomainDirucmibrbin directory. For a complete description of
5-4 Administrators Guide for Conversion
available Flexiondoc and SearchML options, refer to the xx.cfg file located in the refinery IdcHomeDircomponentsXMLConverterresources directory.
You must restart your refinery after making changes to the intradoc.cfg file.
■
FlexionDoc and SearchML schema code and documentation files are installed with the XMLConverter component into the refinery
IdcHomeDircomponentsXMLConverter directory.
5.1.5 Setting Up XSL Transformation
Inbound Refinery uses the Xalan XSLT processor and the SAX validator built into the Java virtual machine running Inbound Refinery. To enable transformation, the
XMLConverter component must be installed and enabled on the refinery server and the XMLConverterSupport must be installed and enabled on the content server.
To turn on XSL Transformation do the following:
1.
Log into the refinery server.
2.
Do one of the following:
■
If the XML rendition is to be the primary web-viewable file, click Conversion Settings
then Primary Web Rendition. Enable Convert to XML on the
Primary Web-Viewable Rendition Page when it is displayed.
■
If the XML is to be an additional rendition, click Conversion Settings then Additional Renditions
. Enable Create XML renditions for all supported formats
on the Additional Renditions Page
when it is displayed.
3. Click XML Options. The
XML Options Page is displayed.
4. Enable Process XSLT Transformation and select the XML schema to use from the
following options:
■
Produce FlexionDoc XML
■
Produce SearchML
5. Click Update to save your changes or Reset to revert to the last saved settings.
In order to preform XSL transformations Inbound Refinery must have an XSL template to apply during the transformation checked into Oracle Content Server. To
check in an XSL template to Oracle Content Server, do the following:
1.
Create an XSL file. The XSL file specifies how an XML file with a specific Content Type will be transformed to a new XML file. You can specify a DTD or schema for
validation, but you do not have to. You can store DTD or schema in the content server, but you do not have to.
2. Check the XSL file into the content server; associating it to a Content Type.
Note: It is critical that the DTDs and schemas used for XSL
transformation are accessible without a login they cannot require authentication for read access. For example, if a DTD file is stored in
Oracle Content Server, it must be in a Security Group that gives read access to anonymous users.
The XSL file and Native file must both reside in the same Security Group for XSL transformation to be successful.
Working with XML Conversions 5-5
a. In the Content Check In Form, select the Content Type from the Type
