This chapter includes the following sections:
This section covers the following topics:
The number of worker threads can be modified for any of the batch processors. For example, perform the following steps to change the number of worker threads for the import processor. In this example, the thread count is being changed from 10 to 1:
Stop the Capture Managed Server.
In the WebLogic Server Administration Console, click Deployments in the Domain Structure tree on the left. The Summary of Deployments page displays.
In the Deployments table, expand the Capture deployment node.
Expand the Modules node under the Capture deployment node and select oddc-core.jar. The settings page for oddc-core.jar displays.
Select the Configuration tab and then the Workload subtab.
Select ImportProcessorMgr from the list of Application Scoped Work Managers. The settings page for ImportProcessorMgr displays.
Select ImportProcessorMaxThreads from the list of Application Scoped Work Manager Components. The settings page for ImportProcessorMaxThreads displays.
Set the value of the Count field to 1 (from 10).
Click Save.
Perform the following steps to confirm the changes to the thread count setting:
You can use a hash partition of the EBATCTITEMS table to minimize the database wait event enq: HW– contention, which prevents the database from scaling. This event occurs when many threads are trying to update and add new BLOB items to ECBATCHTITEMS, as follows:
table - "UPDATE ECBATCHITEMS SET ECITEMDATA=:1 WHERE ECITEMID=:2"
Creating a hash partition minimizes this contention because different items will be in eight different partitions. See Creating a Hash Partition to Improve Database Performance in Installing and Configuring Oracle WebCenter Content, 11g Release 1 (11.1.1.9).
Note:
The use of a hash partition on an Oracle Database has licensing implications since it requires the purchase of an "Oracle Partitioning" license. Please refer to this document: http://docs.oracle.com/cd/B28359_01/license.111/b28287.pdf.
This section covers troubleshooting topics related to the Commit Processor.
To test the Outside In Technology (OIT) PDF Export utility, it is necessary to supply a TIFF file to test the export. Perform the following steps:
Using Linux
Open a terminal window.
Change to the {Middleware Home}/oit/linux64/lib/contentaccess directory.
Note: The default {Middleware Home} path on Linux is /Oracle/Middleware/Oracle_Home.
Enter the following command, which first sets the LD_LIBRARY_PATH variable to the current directory (".") and then executes the PDFExport64 utility:
env LD_LIBRARY_PATH=. ../../../../wccapture/capture/bin/linux/PDFExport64 -i {TIFF file to read} -o {PDF file to create} -l {log file to create} -f {Path to font folder}
Example:
env LD_LIBRARY_PATH=. ../../../../wccapture/capture/bin/linux/PDFExport64 -i /tmp/sample.tif -o /tmp/test.pdf -l /tmp/pdfexport.log -f /usr/share/X11/fonts
The logging of the OIT PDF Export utility will be captured in the log file specified in the command above (example: /tmp/pdfexport.log).
Using Windows
This section covers the following topics:
Perform the following steps to enable additional Java logging for the Capture client:
Begin modifying the WebCenter Enterprise Capture Client desktop shortcut by right-clicking on the shortcut icon and selecting Properties from the menu.
On the Shortcut tab, click inside the Target field and position the cursor at the end of the line. Type in a space followed by "-showconsole" (without the quotes).
Click OK to save the changes. The next time you start the Capture client using the desktop shortcut, a debug console will display providing additional logging information.
Perform the following steps in the Capture client to activate batch logging:
For issues involving a TWAIN driven scanning device, a TWAIN log is automatically created:
C:\Users\WINDOWS_USER\AppData\Local\Temp\capture_twain.log
When scanning in black/white in the Capture client using the Kofax VRS TWAIN driver, the black and white areas are inverted in the scanned images.
Perform the following steps to resolve this issue:
The above settings may cause performance issues when scanning color images with a large DPI value, for example, a DPI value between 300 and 600.
This section covers the following topics:
The "Image export failed with code 3" error message is a generic error message related to the OIT conversion in Capture. To gather a more detailed error message, you will need to set the CAPTUREOITEXPORTLOG environment variable to generate a log file.
Using Linux
To set the environment variable in Linux, you need to modify the setDomainEnv.sh file which is located in {Oracle Home}/user_projects/domains/{Capture domain}/bin directory.
Add the following two lines to the end of the file:
CAPTUREOITEXPORTLOG="/scratch/captureoit.log"
export CAPTUREOITEXPORTLOG
You can change "/scratch" to any other directory if it exists and is writable. After you add the environmental variable, restart the Capture Managed Server and duplicate the issue. Then examine the captureoit.log file to see the more detailed error message.
Using Windows
To set the environment variable in Windows, you need to modify the setDomainEnv.cmd file which is located in {Oracle Home}\user_projects\domains\{Capture domain}\bin directory.
Add the following line to the end of the file:
set CAPTUREOITEXPORTLOG="C:\temp\captureoit.log"
You can change "C:\temp" to any other directory if it exists and is writable. After you add the environmental variable, restart the Capture Managed Server and duplicate the issue. Then examine the captureoit.log file to see the more detailed error message.
Capture uses OIT libraries for performing the conversion to TIFF. Internally, it uses CaptureOITExport for the conversion. It will create OIT specific logs which can be useful to resolve OIT related errors.
Using Linux
Open a shell prompt and change directories to {Oracle WebCenter Home}/oit/linux64/lib/contentaccess.
For conversions to work on some platforms, certain environment variables must be set. On a Linux operating system running XWindows, when redirecting the display to a system with suitable graphic capabilities, export DISPLAY to a valid X Server before starting the conversion.
Note: On Oracle Linux, the display server is available. On AIX server, it might need to be installed separately.
Create an OIT specific log file. Export the CAPTUREOITEXPORTLOG environment variable to create the log file specified.
Create an input file which contains the parameters for conversion. The name of the input file is /test/testuser/input.txt and contains the following lines:
BEGINSESSION|1|/test/testuser/Test_07.docx|/test/testuser/output/out.tif|FI_TIFF~1|0|0|0|/test/testuser/output/che.lst|300 quit
Run CaptureOITExport64.
Example:
export DISPLAY=:0 export CAPTUREOITEXPORTLOG=/test/testuser/oit.log ../../../../wccapture/capture/bin/linux/CaptureOITExport64 < /test/testuser/input.txt CaptureOITExport Started. ACKSESSION FINISHSESSION INITIATETERMINATE
In the above example:
/test/testuser/Test_07.docx: Input Microsoft Word document file
/test/testuser/output/out.tif: Output TIFF
/test/testuser/output/che.lst: Contains the list of pages for the multi page TIFF
Using Windows
Example: