Inbound refinery is one of the key components of the WebCenter Content suite. It enables users to convert a wide variety of document based file formats to PDF. For WebCenter Content this is highly desired functionality as it ensures that Microsoft Office based content items are able to be rendered directly in the browser when selecting the web viewable link.
In this blog post we will go over the most common problems that can cause the PDF conversion process to fail.
IBR in Cluster Mode
This is one of the most common causes of issues during conversions. Multiple nodes of Inbound Refinery try to process (Submit and release to Content Server) the same content item. This causes a file lock and neither of the nodes are able to process the conversion.
An example of this error is:
Event generated by user ‘sysadmin’ at host ”. Error extracting data from the zip file
‘<domain_home>/ibr/vault/~temp/xyz.zip’. Unable to extract the file
‘<domain_home>/ibr/vault/~temp/xyz..jpg’.java.io.EOFException: Unexpected end of ZLIB input stream
It is suggested by Oracle that Inbound Refinery not be set up in a clustered configuration. Multiple individual Inbound Refineries can be installed and providers can be created in WebCenter Content so that multiple content items can be processed at the same time.
IBR Pre-Requisites Not Installed
Inbound Refinery uses the Outside In module for the PDF conversion engine. OIT is dependent on certain file system libraries. There can be cases when the following error is received when conversions fail in IBR:
>log/3 12.20 15:48:32.556 Job_10_idc !csLogJobIdPrefix,10!csLinefeed!csConversionForceFailureByStep,PDFExport,no export module available for selected graphic outputid (0x01C6)!$no export module available for selected graphic outputid (0x01C6)
One of the ways to check that all the libraries needed for the PDF conversion are preset is by using the native Unix command ‘ldd’. This will list all the libraries being referenced by the module being checked. This guides administrators to install specific libraries which show up as ‘Not Found’.
As an example, in WebCenter Content 11g the location of the pdfexport module is:
An example of how ldd would be used:
[oracle@test contentaccess]$ ldd pdfexport
linux-gate.so.1 => (0xf7753000)
libsc_da.so => /u01/product/fmw/Oracle_ECM1/oit/linux/lib/contentaccess/./libsc_da.so (0xf7732000)
libsc_ex.so => /u01/product/fmw/Oracle_ECM1/oit/linux/lib/contentaccess/./libsc_ex.so (0xf7728000)
libc.so.6 => /lib/libc.so.6 (0x475b2000)
libsc_ch.so => /u01/product/fmw/Oracle_ECM1/oit/linux/lib/contentaccess/./libsc_ch.so (0xf76f4000)
libsc_fa.so => /u01/product/fmw/Oracle_ECM1/oit/linux/lib/contentaccess/./libsc_fa.so (0xf76e0000)
libsc_fi.so => /u01/product/fmw/Oracle_ECM1/oit/linux/lib/contentaccess/./libsc_fi.so (0xf76c1000)
libsc_ut.so => /u01/product/fmw/Oracle_ECM1/oit/linux/lib/contentaccess/./libsc_ut.so (0xf7511000)
libwv_core.so => /u01/product/fmw/Oracle_ECM1/oit/linux/lib/contentaccess/./libwv_core.so (0xf6f83000)
libstdc++.so.5 => /usr/lib/libstdc++.so.5 (0xf6ec9000)
libm.so.6 => /lib/libm.so.6 (0xf6e9f000)
libgcc_s.so.1 => /lib/libgcc_s.so.1 (0xf6e81000)
libdl.so.2 => /lib/libdl.so.2 (0xf6e7c000)
libsc_fut.so => /u01/product/fmw/Oracle_ECM1/oit/linux/lib/contentaccess/./libsc_fut.so (0xf6df8000)
libsc_lo.so => /u01/product/fmw/Oracle_ECM1/oit/linux/lib/contentaccess/./libsc_lo.so (0xf6ddb000)
librt.so.1 => /lib/librt.so.1 (0xf6dd2000)
libpthread.so.0 => /lib/libpthread.so.0 (0xf6db7000)
In this particular output, all the dependent libraries for pdfexport are installed. For any library that shows as ‘Not Found’ administrators should install the 32 bit version of those libraries.
If you need further assistance please feel free to contact us directly.