Working with XML Conversions 5-5
a. In the Content Check In Form, select the Content Type from the Type
drop-down list.
b.
Enter the Content ID according to the following convention: Content Type.xsl.
For example, if the Content Type is ADACCT, you would enter adacct.xsl.
c.
Enter your XSL file as the Primary File.
d.
Make sure the Security Group matches any DTDschema files in the content server associated with your XSL file and the native files that will be checked
into the content server.
e. Click Check In.
Now, when files are checked in with this Content Type, and a FlexionDocSearchML XML file is generated by XML Converter or the checked-in
file is XML, this XSL file will be used for XSL transformation to a new XML document.
3.
Repeat steps 1 and 2 for each Content Type that you want to post-process to XML.
5.1.5.1 XSLT Errors
When a validation fails, Inbound Refinery collects the errors from the SAX Validation engine, creates an hcsp error page and attempts to check in the page to Oracle Content
Server. In order for the refinery to be able to check in an error page you must manually setup in outgoing providers on Inbound Refinery to the content server. The name of
Inbound Refinery provide must match the agent name. For example if Inbound Refinery is named production_ibr and it is converting files for a content server named
production_cs, then an outgoing provider named production_cs must be created on the production_ibr Inbound Refinery.
If you want to be notified when there are XSL transformation failures, it is recommended that you complete the following steps to set up a criteria workflow in
the content server:
1. Access the Workflow Admin applet for the content server.
2.
Add a criteria workflow for notification of XSLT transformation failures.
3.
Add a workflow step with the following properties:
■
Users : specify the users that should be notified.
■
Exit Conditions : select At least this many reviewers, and set the value to 0.
■
Events : For the Entry event, add the following Custom Script Expression:
if dDocTitle like XSLT Error else
wfSetwfJumpEntryNotifyOff, 1 wfExit0,0
endif
5.1.5.2 Support for Unmanaged Files
When a document containing graphics are submitted for XML transformation, the graphics are ignored by default. If you want to have submitted graphics exported, you
must manually turn this on by setting xx-graphictype to one of the following values:
■
gif : to export all graphics to GIF format
5-6 Administrators Guide for Conversion
■
jpeg : to export all graphics to JPEG format
■
png : to export all graphics to PNG format
When xx-graphictype is set, Inbound Refinery can copy the graphics to a specified directory. By default the Inbound Refinery will ignore the extra files. To use the
graphics, do the following:
1.
In the Inbound Refinery intradoc.cfg file, set the following variables, where the value for xx_graphictype is the desired format:
xx_graphictype=jpeg AllowXmlConverterCopyUnmanagedFiles=true
2.
Also in the Inbound Refinery intradoc.cfg file, set XmlUnmanagedPhysicalDir-AgentName to the directory you want the
unmanaged files copied for each agent. Typically, this will be the weblayout directory of the content server.
For example, if the refinery server has an agent named production_cs and the weblayout directory is located at c:oracleproduction_csweblayout, you
would specify the following in the refinery intradoc.cfg file:
XmlUnmanagedPhysicalDir-production_cs=c:oracleproduction_csweblayout Inbound Refinery appends the following to the path when computing the complete
location of the unmanaged files: groupsdSecurityGroupdocumentsdDocType
The file name of the unmanaged files are of the form: dDocName.increasingNumber.jpg
An example of the complete path to an unmanaged file then would be: c:oracleproduction_csweblayoutgroupspublicdocumentsadacct001166.2.jpg
5.2 Troubleshooting XML Converter Problems
Kategori