This chapter contains information about troubleshooting Oracle WebCenter Enterprise Capture.
This chapter includes the following sections:
This section covers the general troubleshooting 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:
Start the Capture Managed Server.
In the WebLogic Server Administration Console, expand the Services node in the Domain Structure tree on the left.
Expand the Messaging node under Services and click JMS Modules. The JMS Modules page displays.
In the JMS Modules table, select capture-jms-module. The settings page for capture-jms-module displays.
In the Summary of Resources table, select capture-batchinput-queue. The settings page for capture-batchinput-queue displays.
Select the Monitoring tab. In the Destinations table, the values in the Consumers Current and the Consumers High columns should be 1.
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:
Open a terminal window.
Change to the /oit/linux/lib/contentaccess directory.
Note: To find this directory, the default path on Windows is Oracle\Middleware\Oracle_ECM1 and on Linux is /Oracle/Middleware/Oracle_ECM1.
Enter the following command, which first sets the LD_LIBRARY_PATH variable to the current directory (".") and then executes the PDFExport32 utility:
env LD_LIBRARY_PATH=. ../../../../capture/bin/linux/PDFExport32 -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=. ../../../../capture/bin/linux/PDFExport32 -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).
Open a terminal window.
Change to the oit\win32\lib\contentaccess directory.
Note: To find this directory, the default path on Windows is C:\Oracle\Middleware\Oracle_ECM1.
Enter the following command, which executes the PDFExport32 utility:
..\..\..\..\capture\bin\win32\PDFExport32 -i {TIFF file to read} -o {PDF file to create} -l {log file to create}
Example:
..\..\..\..\capture\bin\win32\PDFExport32 -i C:\tmp\sample.tif -o C:\tmp\test.pdf -l C:\tmp\pdfexport.log
The logging of the OIT PDF Export utility will be captured in the log file specified in the command above (example: C:\tmp\pdfexport.log).
This section covers the following topics:
Perform the following steps to set a Java console log by enabling logging in the Java Control Panel applet:
Open the Java Control Panel applet: Click Start, click Control Panel, and then click Java.
Select the Advanced tab.
Select Show console under Java Console and also select the appropriate debugging levels under Debugging (For example, Enable tracing and/or Enable logging).
Click OK to save the changes.
The next time you open the Capture client console, the Java console will appear and provide logging information in the console page.
Note: Java console logging contains useful information about the JVM, the start-up of the Capture client, and will show any exceptions that were not caught by the Capture client logging (set using the Preferences window).
Perform the following steps in the Capture client to activate batch logging:
Click the Preferences link in the upper right area of the client window.
In the Logging Level field, select a new level.
By default, logging is set to Off. Other values include Severe, Warning, Info, Config, Fine, Finer, Finest, and All.
Log files are stored locally in the .oracle_capture\Log directory in your home directory. A log file is named as follows: WC{date} where date is in the format of MMddyyyy.
Click Save.
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:
Login to the Capture client.
Click the Preferences link in the upper right area of the client window.
Select the Prevent File Mode Transfer field.
Click Save.
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:
Section 6.4.1, ""Image export failed with code 3" error in Conversion Processor (OIT conversion)"
Section 6.4.2, "Running CaptureOITExport32 to debug issues related to converting to TIFF"
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.
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.
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 CaptureOITExport32 for the conversion. It will create OIT specific logs which can be useful to resolve OIT related errors.
Go to {Oracle WebCenter Home}/oit/linux/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 CaptureOITExport32.
Example:
export DISPLAY=:0 export CAPTUREOITEXPORTLOG=/test/testuser/oit.log ../../../../capture/bin/linux/CaptureOITExport32 < /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
In Windows, only CAPTUREOITEXPORTLOG needs to be set.
Example:
The input file in this example is input.txt (C:\OIT\convtest\input.txt). The input file contains the parameters required for the conversion. It includes the file to be converted (C:\OIT\convtest\Test_07.docx), the output TIFF file (C:\OIT\convtest\output\out.tif) and the following two lines:
BEGINSESSION|1|C:\OIT\convtest\Test_07.docx|C:\OIT\convtest\output\out.tif|FI_TIFF~1|0|0|0|C:\OIT\convtest\output\che.lst|300
quit
Setting CAPTUREOITEXPORTLOG in the command prompt:
C:\Users\odc>set CAPTUREOITEXPORTLOG=C:\OIT\convtest\oit.log
Invoking the conversion using the input file:
C:\Oracle\Middleware\Oracle_ECM1\oit\win32\lib\contentaccess>C:\Oracle\Middleware\Oracle_ECM1\capture\bin\win32\CaptureOITExport.exe < C:\OIT\convtest\input.txt
CaptureOITExport Started.
ACKSESSION
FINISHSESSION
INITIATETERMINATE
C:\Oracle\Middleware\Oracle_ECM1\oit\win32\lib\contentaccess>