Accessing IBM FileNet
documentation and fix packs
Installation, migration, upgrade, and
configuration
This document provides information about the IBM® FileNet® CAP-5.2.1-004 fix pack, which upgrades an existing Capture 5.2.1 system.
NOTE IBM recommends that all Capture client stations have the latest Capture fix pack level.
Documentation
To access documentation for IBM FileNet Capture, go to http://www.ibm.com/support/docview.wss?rs=3276&context=SSNVMX&uid=swg27010327.
Fix packs
To access fix packs for IBM FileNet Capture, go to
IBM Fix Central.
(http://www.ibm.com/support/fixcentral/)
For compatibility information, see IBM FileNet Capture Hardware and Software Requirements.
Certain compression types work better with different image types and provide
better performance to s
1.
Create or edit the CapConfig.ini
file in the same default location as the Local Repository. (For example,
C:\Documents and Settings\All Users\Application
Data\IBM\Capture\CapConfig.ini in Windows XP).
2.
Add these entries to the
CapConfig.ini:
[FullTextOCR]
PDFCompressionType= <0,1,2, or 3>
Specify 0 is the recommended compression using JBIG2 and FLATE compression
Specify 1 using TIFF Group 4 with FLATE compression
Specify 2 using JBIG2 with LZW compression
Specify 3 using TIFF Group 4 with LZW compression
The default for PDFCompressionType is 0.
This option allows the user to select the preferred OCR engine to fit their requirements.
1.
Create or edit the CapConfig.ini
file in the same default location as the Local Repository. (For example,
C:\Documents and Settings\All Users\Application
Data\IBM\Capture\CapConfig.ini in Windows XP).
2.
Add these entries to the
CapConfig.ini:
[FullTextOCR]
EngineTradeOff= <1,2, or 3>
The "EngineTradeOff" value can be set to 1=accurate, 2=balanced or 3=speed.
Specify 1 for documents that consists of mostly text.
Specify 2 or 3 when processing documents that are graphics intensive.
The default is 2.
This option allows the user to select the preferred OCR engine to fit their requirements.
1.
Create or edit the CapConfig.ini
file in the same default location as the Local Repository. (For example,
C:\Documents and Settings\All Users\Application
Data\IBM\Capture\CapConfig.ini in Windows XP).
2.
Add these entries to the
CapConfig.ini:
[ZonalOCR]
EngineTradeOff= <1,2, or 3>
The "EngineTradeOff" value can be set to 1=accurate, 2=balanced or 3=speed.
Specify 1 for documents that consist of mostly text.
Specify 2 or 3 when processing documents that are graphics intensive.
The default is 2.
If you have a layout issue, use this option to force Capture Professional to reset its layout to the default state.
1. Shut down all instances of Capture Professional
2. Create or edit the CapConfig.ini file in the same default location as the Local Repository. (For example, C:\Documents and Settings\All Users\Application Data\IBM\Capture\CapConfig.ini in Windows XP).
3. Add these entries to the CapConfig.ini:
[CaptureProfessional]
ResetLayout=1
Specify 0 to hide the menu item
Specify 1 to display the menu item
4. Start Capture Professional
5. In the "Window" menu, the "Reset Layout & Exit" should appear
6. Select this item to reset Capture Professional its default layout state and exit the current session
The default for this option is 0.
Note: If there is no entry then Capture Professional hides the menu item
Before installing Capture 5.2.1 on a machine with Windows 7-x86 (32 bit version) and Office 2010 follow these steps:
1. Create Capture's Programs directory (for example c:\Program Files\Filenet\Capture\Programs for Windows 7-x86)
2. Copy cpengine.ocx from the fix pack to the Programs directory
3. Install Capture 5.2.1
Note: The fix pack will also update the cpengine.ocx to correct version if the installer is run.
For Content Engine customers, the IBM FileNet Capture fix pack installer updates the Capture Viewer files. Customers who installed IDM Desktop separately must download the latest IDM fix pack (IDM 4.0.3-002 or later).
CAP-5.2.1-004 is qualified for use with:
·
IDM 4.0.2-014
·
IDM 4.0.3-002
·
IS 4.2.0-004
·
CE 5.1.0-001
·
IER 5.1.0.2
·
MS SQL 2012
For information about the resolved defects in this fix pack, see "Product fix history".
For information about FileNet Capture new features
and known issues, see the
Capture Release Notes.
Under some circumstances, it might be necessary to suppress Zonal OCR errors.
To suppress Zonal OCR errors:
1.
Create or edit the CapConfig.ini
file in the same default location as the Local Repository. (For example,
C:\Documents and Settings\All Users\Application
Data\IBM\Capture\CapConfig.ini).
2.
Add these entries to the
CapConfig.ini:
[ZonalOCR]
SuppressErrors=1
The default value for SuppressErrors is 0.
When AutoRotate is enabled by default, ZonalOCR might produce an error. To disable auto rotation:
1.
Create or edit the CapConfig.ini
file in the same default location as the Local Repository. (For example,
C:\Documents and Settings\All Users\Application Data\IBM\Capture\CapConfig.ini).
2.
Add these entries to the
CapConfig.ini:
[ZonalOCR]
AutoRotation=0
The default value for AutoRotation is 1.
After installing PICN20.dll from an interim fix, some customers could not use ADR Scripted Export to export multi-page TIFF images. Capture 5.2.0-003 is releasing the Picn20.dll file as Picn20.zip, and installs it in ..\Capture\Programs. This is a resolution to an independent software vendor conflict that affects ADR Scripted Export. Customers who are experiencing problems with exporting multi-page TIFF images need to manually install the PICN20.dll in C:\WINDOWS\SYSTEM32.
For Content Engine customers, the IBM FileNet Capture fix pack installer updates the Capture Viewer files. Customers who installed IDM separately must download the latest IDM fix pack (IDM 4.0.3-001 or later).
CAP-5.2.1-003 is qualified for use with:
·
IDM 4.0.2-012
·
IDM 4.0.3-001
·
IS 4.2.0-001
·
CE 5.1
·
IER 5.1
For information about the resolved defects in this fix pack, see "Product fix history".
For information about FileNet Capture new features and known issues, see the Capture Release Notes.
FileNet Capture now provides the ability to store Content Engine index properties that are defined as binary. Previous versions of FileNet Capture ignored P8 Content Engine document classes that a user defined with a binary property type. You must programmatically assign this type of index property because, when a user attempts to index a document by using the indexing component, the binary document properties are grayed out.
The current date policy is that a user must enter a time when entering a date value in a Content Engine property field. FileNet Capture adjusts the time for daylight saving time.
To disable the adjustment for daylight saving time, complete the following steps:
1.
Create or edit the CapConfig.ini
file in the same default location as the Local Repository. (For example,
C:\Documents and Settings\All Users\Application
Data\IBM\Capture\CapConfig.ini).
2.
Add these entries to the
CapConfig.ini:
[RilCE]
IgnoreDST=1
[RilSharedCE]
IgnoreDST=1
When a user enables auto-indexing but does not enter values for all of the required fields, the user is unable to enter index data and proceed to the commit operation.
To workaround this issue, complete the following steps:
1.
Create or edit the CapConfig.ini
file in the same default location as the Local Repository (For example,
C:\Documents and Settings\All Users\Application
Data\IBM\Capture\CapConfig.ini).
2.
Add this entry to the CapConfig.ini:
[Index]
ProcessOnError=1
Setting this flag equal to 1 allows a user to manually enter the required index values and proceed to committal.
The FileNet Capture trace log is enhanced to include the following information:
·
Batch Name
·
IP address
·
Commit status
·
Save Batch call status/error
·
Date/Time stamps.
To enable enhanced logging for failed Content Engine batches:
1.
Create or edit the CapConfig.ini
file in the same default location as the Local Repository (For example,
C:\Documents and Settings\All Users\Application
Data\IBM\Capture\CapConfig.ini).
2.
Add the following entries to
CapConfig.ini, according to your requirements:
a.
To enable the logging for non-shared
CE:
[RilCE]
DebugCommit=1
b.
To enable logging for shared CE:
[RilSharedCE]
DebugCommit=1
3.
Save the CapConfig.ini file.
4.
Enable Capture Logging in Capture
Manager, and set the trace level to Verbose.
To enable support for your imprinter to print the number of characters that your scanner supports:
1.
On the FileNet
Capture workstation to which the scanner in question is connected, configure a
scanner and exit from FileNet Capture when you are
finished.
2.
Locate and open the scan.ini file. The
default location is in the user temp directory.
3.
In the [Installed Scanners] section
of the ini file, look for "Current
Scanner=" and the name of the scanner.
4.
Create a section within the ini file [<name
of the scanner>]
5.
Create an ini
key name "EndorserSize" and set the desired
value for the number of characters to print. For example:
[Kodak i1300]
EndorserSize=30
Important:
The value you enter here must be correct and supported by the scanner.
6.
Save the scan.ini file
7.
Reboot the FileNet
Capture workstation.
FileNet Capture supports duplex (also known as "double-sided" or "front and back") scanning mode. Note that the scanner must also support duplex scanning for this feature to be available.
NOTE
·
The new support is applicable only
to newer scanners in which there are persistency problems with duplex and
simplex modes.
·
If you are not experiencing any
problems with your scanner, then you do not need to make any modifications, as
described in this section.
To enable support for duplex scanning mode:
1.
On the FileNet
Capture workstation to which the scanner is connected, locate and open the scan.ini file. The
default location is in the user temp directory.
2.
Make a note of the value of the Current Scanner= entry
in the scan.ini file.
3.
Add the following entries to the
scan.ini file.
[Current Scanner]
Page UI=1
For example, to enable duplex mode for the Böwe Bell+Howell
3210, the scan.ini file includes these entries:
Current Scanner=Böwe Bell+Howell 3210
[Böwe Bell+Howell 3210]
Page UI=1
4.
Save the scan.ini file and reboot
the FileNet Capture workstation.
CAP-5.2.1-002 is qualified for use with:
·
IDM 4.0.3
·
IS 4.2.0
·
Microsoft SQL Server 2008 SP2
·
Microsoft Windows 7 SP1
·
Microsoft Windows Server 2008 R2 SP1
To commit a multi-TIFF file with a PDF file within the same document, you enable specific Merge and Commit options in the CapConfig.ini file, as described in the following procedure:
1.
Create or edit the CapConfig.ini file in
the same default location as the Local Repository (For example, C:\Documents
and Settings\All Users\Application Data\IBM\Capture\CapConfig.ini).
2.
Enter the following entries under
Merge component and Commit component in the CapConfig.ini.
[merge]
SkipPdfOptions=1
;Option set to 0 will disable the option, while option set to 1 will enable the option
[commit]
SkipPdfOptions=1
;Option set to 0 will disable the option, while option set to 1 will enable the option
If the Merge component detects the [merge] key with SkipPdfOptions flag equal to one, Merge will merge only the TIFF images and leave the PDF images intact. If the Commit component detects the [commit] key with the SkipPdfOptions flag set to one, Commit adds both the TIFF images and the PDF files to Content Engine.
When you enable "SkipPdfOptions" in both the Merge component and the Commit component:
·
Single TIFF images are removed.
·
A committed document will contain a
multi-TIFF file and a PDF file.
TIP
If your environment does not require a change to the Merge and Commit behaviors, then you do not need to create the CapConfig.ini file, and the Merge and Commit components will function the same as in previous releases.
RESTRICTIONS
·
Only TIFF files are merged. If a
document contains more than one PDF file and more than one TIFF image, only the
TIFF images are merged together.
·
The functionality of merging PDF
files is not available if you implement the changes to the Merge and Commit
components.
CAP-5.2.1-001 is qualified for use on Microsoft Windows 7 and Windows 2008 R2 64-bit platforms.
RESTRICTIONS
·
FileNet Capture is a 32-bit application running on a 64-bit
platform in emulation mode.
·
For details about FileNet Capture and independent software vendor support for
Windows 7 and Windows 2008 64-bit platforms, see IBM
FileNet Capture Hardware and Software Requirements.
Installation of this fix pack is not affected by any virus protection software that might be running in the background.
NOTE Capture
uses ODBC to connect to various databases, such as DB2, SQL and Oracle. If you
are using one of these databases, make sure your ODBC connection is working
properly prior to configuring Capture.
Before installing this fix pack, verify that you have the latest copy of the IBM FileNet Capture Documentation. Capture documentation contains additional information that you might need to perform the procedures mentioned in this readme, such as stopping services and applications.
This fix pack has the following minimum requirements:
·
CAP-5.2.1
·
CAPADR-5.2.0-001 (For ADR
installation)
·
IDM-4.0.0a and IDM-4.0.1-008 (For IS
and CS installations)
For more information about IDM requirements, see the Hardware and Software Requirements
Guide that is available at: http://www.ibm.com/support/docview.wss?uid=swg27015454.
If you installed any test modules, review the table in Product fix history. If any test module fixes are not listed in the table, you must reapply the relevant test modules after you install this fix pack.
1.
Download the CAP-5.2.1-004 fix pack,
and extract its contents to a temporary location. To download this fix pack
from the IBM support page, see Accessing IBM FileNet documentation, compatibility matrices, and fix
packs.
2.
Stop Capture and all other
applications that are running.
3.
Back up the existing copy of the
affected files. To determine the affected files, see the resolved defects table
under Product fix history.
4.
If you plan on installing this fix
pack silently, you must first record an installation response file:
a.
Navigate to the folder where you
extracted the contents of this fix pack and run the setup.exe program from a
command prompt:
setup /r /f1"c:\file1.iss"
where c:\file1.iss is the response file that will be used in subsequent silent installations.
NOTE The installation response file records all of your installation preferences and is unique to an installation scenario. The configuration details in the recorded and the replicated system must be identical. For more information about silent installation, see the IBM FileNet Capture Installation and Upgrade Guide.
5.
Start the installation process in
one of the following ways:
To upgrade interactively
Navigate to the directory where you extracted the contents of this fix pack, launch the setup program, and follow the steps in the installation screens.
To upgrade silently
Navigate to the directory where you extracted the contents of this fix pack and run the setup program from a command prompt:
setup /s /f1"c:\file1.iss"
where c:\file1.iss is the response file that you recorded in the previous step.
This fix pack does not have an uninstall option.
The following tables list the product fixes in this fix pack.
·
Defect
# IMCS defect number
|
CAP-5.2.1-004 |
||||
|
APAR Name |
Defect # |
Files Affected |
Area |
Description |
|
PJ39535 |
00973397 |
Fncaptureviewer.ocx |
Viewer |
When saving
an image on the viewer, the image gets rotated. |
|
PJ39652 |
00976115 |
Zonalocr.ocx |
PDF/OCR/Zonal OCR |
Capture
hanging when processing particular images using Zonal OCR. |
|
PJ39655 |
00976352 |
Index.ocx |
Indexing |
Problem
entering numeric value below zero into index field. |
|
PJ39684 |
00977242 |
CapOcr.ocx |
PDF/OCR/Zonal OCR |
Full-Text OCR
component crashes with multipage TIFF files when option "Convert
multipage tiff to single pages" is enabled. |
|
PJ39705 |
00977884 |
CapOcr.ocx |
PDF/OCR/Zonal OCR |
Slow Full
Text OCR in Capture 5.21 after upgrade from Capture 5.2 |
|
PJ39750 |
00978850 |
FNRptViewer.ocx |
Viewer |
Unable to run Capture reports on Capture 5.2.1 FP2 DB2 shared DB |
|
PJ39751 |
00979170 |
Zonalocr.ocx |
PDF/OCR/Zonal OCR |
Slow
performance of ZonalOCR in Capture 5.2.1 vs 4.0 |
|
PJ39772 |
00979358 |
Capturehelperu.dll |
Libraries |
Capture 5.2.1
Shared Statistics using DB2 9.5 report is incorrect |
|
PJ39767 |
00979415 |
CapOcr.ocx |
PDF/OCR/Zonal OCR |
TIFF images
with very large dimensions cannot be processed using Full Text OCR |
|
PJ39789 |
00979943 |
CapOcr.ocx |
PDF/OCR/Zonal OCR |
When trying
to create an "Image + Text" pdf on a
batch with 765+ images, Capture Prof forces a shutdown with an error |
|
PJ39796 |
00980052 |
FnCaptureApp.exe |
Capture Application |
Capture
screen panes layout is intermittently changing. |
|
PJ39868 |
00981829 |
CaptureHelperu.dll |
Libraries |
Error
Exception while attempting to open Statistics |
|
PJ40250 |
01116411 |
FnCaptureApp.exe |
Capture Application |
Capture
viewer corruption |
|
PJ40277 |
01118180 |
CapOcr.ocx |
PDF/OCR/Zonal OCR |
Full Text OCR
is taking a long time to complete on certain images. |
|
PJ40088 |
00987955 |
Capturehelperu.dll |
Libraries |
Capture crashes when logging to a file and with Event log
logging disabled in Capture Manager |
|
PJ40144 |
00989933 |
RilBES34.dll |
Repositories |
FileNet Capture 5.2.1 closes after logging in, to connect to IS
Repository |
|
PJ40182 |
00991135 |
CapOcr.ocx |
PDF/OCR/Zonal OCR |
OCR PDF
Crashed on PDF #95 – Error Code: 80070057 |
|
PJ40218 |
01115129 |
Ptscan.ocx |
Pixel Scan |
Patchcode option to enable does not persist |
|
PJ40220 |
01115187 |
Ptscan.ocx |
Pixel Scan |
Capture
crashing when scanning with HP8200 scanjet using
certain setting collections |
|
PJ40347 |
01121099 |
Cpengine.ocx |
Capture Path |
Capture 5.2.1 install failed on ISS.BIN error if MS office 2010 is installed |
|
PJ40473 |
01125231 |
Index.ocx |
Indexing |
Capture closes when using arrows to move up/down during indexing |
|
PJ40631 |
01133476 |
CapOCR.ocx |
PDF/OCR/Zonal OCR |
FullTextOCR is altering the orignal value when converting to PDF |
|
|
01124290 |
Viewer support files |
Viewer |
Capture Viewer files need to be updated for Outside-In Viewer security
bulletin. IDM customers need to download and install the latest IDM fix pack
(IDM 4.0.2-014 or later). For details about this fix, see "Capture Viewer files updated for
Outside-In Viewer security bulletin" in New in this fix
pack |
|
| ||||
|
CAP-5.2.1-003 |
||||
|
APAR Name |
Defect # |
Files Affected |
Area |
Description |
|
PJ39304 |
960627 |
ZonalOCR.ocx |
PDF/OCR/Zonal OCR |
Capture 5.2.1 FP1 Zonal OCR produces errors on certain TIFF images. |
|
PJ39305 |
963254 |
capturedesktop.exe |
Capture Desktop Application |
Capture Desktop Scan Wizard displays the error, "Scan Wizard Canceled," and the document remains in the original folder. |
|
PJ39023 |
960143 |
RilCE.dll, RilSharedCE.dll |
Repository Server |
When the batch name exceeds 19 characters, the batch name template is truncated and throws an error. |
|
PJ39141 |
966856 |
RilShared.dll |
Repositories |
The Shared Content Engine repository fails to import document class definitions when residing in DB2 on a Linux server. |
|
PJ39229 |
966417 |
ZonalOCR.ocx |
PDF/OCR/Zonal OCR |
Zonal OCR does not mark the batch in error, or does not return an error status code, when it fails during the processing of bad images. NOTE This fix requires entries in the CapConfig.ini file. For details on this implementation, see "Suppressing Zonal OCR errors" in New in this fix pack. |
|
PJ39230 |
966420 |
RilBes34.dll |
Repositories |
When login credentials are not entered in Capture Manager, Capture Professional closes after the user clicks Yes to continue opening Capture Professional. |
|
PJ39269 |
967195 |
Index.ocx |
Indexing |
Using the left arrow key to access the first document that has custom properties, with a CVL list in the CS library, returns a General Protection Fault (GPF). |
|
PJ39317 |
967614 |
RilShared.dll |
Repositories |
Unable to upgrade Capture 5.2.0 to a previously used Capture 5.1 Shared CE Oracle database. |
|
PJ39318 |
967616 |
Index.ocx |
Indexing |
The Index component stops autoindexing when the document requires manual input from user. |
|
PJ39319 |
967617 |
RilOfflineIs.dll |
Merge |
Merge component in an offline-only repository throws the error, "Pages in document do not have the same format." |
|
PJ39320 |
967618 |
RilBes34.dll |
Repositories |
User receives "Object page released too many times" error during scanning. |
|
PJ39322 |
967615 |
ZonalOCR.ocx |
PDF/OCR/Zonal OCR |
When AutoRotate is enabled by default, ZonalOCR produces Error -2147467261 "Attempted to read or write protected memory" in a custom application. NOTE This fix requires entries in the CapConfig.ini file. For details on this implementation, see "Disabling Auto Rotation" in New in this fix pack. |
|
PJ39323 |
967404 |
ptscan.ocx |
Pixel Scan |
Capture terminates abnormally while scanning a color image after scanning a black-and-white image on the Kodak i280 scanner. |
|
PJ39325 |
968312 |
index.ocx |
Indexing |
The Index display preference reverts to the default option when a document is re-indexed on a 64-bit operating system. |
|
PJ39326 |
967619 |
Picn20.zip |
ADR/Forms Processing |
Installing PICN20.dll, that is found in an interim fix, prevents ADR Scripted Export from exporting multi-page TIFF images. NOTE This fix requires manually copying PICN20.dll to C:\WINDOWS\SYSTEM32. For details on this implementation, see "Exporting multi-page TIFF images" in New in this fix pack. |
|
PJ39378 |
969943 |
ptscan.ocx |
Pixel Scan |
Turn on compression settings for TIFF + 256 Grey Scale scanning to compress scanned image size on the Fujitsu fi6130. |
|
PJ39400 |
969779 |
capturedesktop.exe |
Desktop Application |
Document destination folder settings should only be enabled for the first document in a batch. |
|
PJ39437 |
971259 |
kfbee.ocx, capturehelperu.dll |
Kofax
Scan |
The Kofax VRS configuration file gets corrupted intermittently. |
|
|
972777 |
Viewer support files |
Viewer |
Capture Viewer files need to be updated for Outside-In Viewer security bulletin. IDM customers need to download and install the latest IDM fix pack (IDM 4.0.3-001 or later). For details about this fix, see "Capture Viewer files updated for Outside-In Viewer security bulletin" in New in this fix pack. |
|
CAP-5.2.1-002 |
||||
|
APAR Name |
Defect # |
Files Affected |
Area |
Description |
|
PJ38900 |
954841 |
capturedesktop.exe |
Capture Desktop |
In Capture Desktop, the Scan wizard does not correctly display text in the status bar. |
|
PJ38910 |
955324 |
ZonalOCR.ocx |
PDF/OCR/Zonal OCR |
Zonal OCR, configured to return an entire page, saves only the first line. |
|
PJ38937 |
957013 |
capturehelper2.dll |
Helper Library |
Users cannot add VS 2005 custom components in Capture Manager on a Windows 64-bit operating system. |
|
PJ38967 |
944346 |
PIXMDLN.DLL |
Viewer |
Faxed images are truncated in the Capture Viewer after the user saves the Display Orientation. |
|
PJ38968 |
947851 |
Index.ocx |
Indexing |
The String Index field displays data incorrectly on certain video cards. |
|
PJ38969 |
944348 |
PTScan.ocx |
Pixel Scan |
Users cannot configure duplex scan mode when Capture is connected to the Bell & Howell 3610 through a USB port. NOTE This fix requires entries in the scan.ini file. For details on this implementation, see New in this fix pack. |
|
PJ38970 |
947850 |
PTScan.ocx |
Pixel Scan |
Canon 9050c scanner attribute values are changed after FileNet Capture is used with other scanners. |
|
PJ38971 |
944354 |
Index.ocx |
Indexing |
Batches with missing required fields are re-indexed several times during the polling process. |
|
PJ38972 |
946604 |
RilCE.dll, RilSharedCE.dll |
Repository Server |
The folders retrieved by commit from Content Engine are not placed in alphabetical order. |
|
PJ38973 |
946596 |
RilCE.dll, RilSharedCE.dll |
Repository Server |
Customers require more trace information for a failed committal batch to Content Engine. NOTE This fix requires entries in the CapConfig.ini file. For details on this implementation, see New in this fix pack. |
|
PJ38974 |
946597 |
RilCE.dll, RilSharedCE.dll |
Repository Server |
Batch does not commit even after Index has auto-indexed the required fields. NOTE This fix requires entries in the CapConfig.ini file. For details on this implementation, see New in this fix pack. |
|
PJ38975 |
946603 |
Capturedesktop.exe |
Capture Desktop |
The FileNet Capture Desktop Assembly component does not separate the batch into the correct documents according to the Assembly Rules. |
|
PJ38976 |
946599 |
PTScan.ocx |
Pixel Scan |
The Panasonic kv-s2048c-u imprinter only prints 19 characters. NOTE This fix requires entries in the scan.ini file. For details on this implementation, see New in this fix pack. |
|
PJ38977 |
946600 |
merge.ocx |
Merge, Commit |
When committing custom date properties to Content Engine, Capture occasionally posts date and time values that are off by one hour. NOTE This fix requires entries in the CapConfig.ini file. For details on this implementation, see New in this fix pack. |
|
Enhancement |
949929 |
RilCE.dll, RilSharedCE.dll |
Repository Server |
Expose the CE binary properties for use in custom applications. For details on this enhancement, see New in this fix pack. |
|
CAP-5.2.1-001 |
||||
|
APAR Name |
Defect # |
Files Affected |
Area |
Description |
|
PJ38147 |
926747 |
merge.ocx |
Merge, Commit |
FileNet Capture is unable to commit TIFF files together with the PDF document to CE 4.5.1. NOTE This fix requires entries in the CapConfig.ini file. For details on this implementation, see New in this fix pack. |
|
PJ38240 |
934022 |
PTScan.ocx |
Pixel Scan |
Capture application returns an error when trying to scan with Ricoh IS 330 Pixel interface. |
|
n/a |
936919 |
capture.chm |
Documentation |
FileNet Capture online help contains references to the Creating a customized toolbar option that is no longer supported in FileNet Capture 5.2.1. |
For information about contacting customer support:
1.
Navigate to the Information
Management support page (www.ibm.com/software/data/support).
2.
Select the appropriate IBM FileNet product from the "Select a category"
list.
3.
From the Product Support page, click
View all Flashes, and then select How to get support for IBM FileNet products.
This information was developed for products and services offered in the U.S.A.
IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service.
IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not grant you any license to these patents. You can send license inquiries, in writing, to:
IBM Director of Licensing
IBM Corporation
North Castle Drive
Armonk, NY 10504-1785U.S.A.
For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to:
IBM World Trade Asia Corporation
Licensing
2-31 Roppongi 3-chome, Minato-kuTokyo 106-0032, Japan
The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you.
This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice.
Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk.
IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you.
Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact:
IBM Corporation
J46A/G4
555 Bailey Avenue
San Jose, CA 95141-1003U.S.A.
Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee.
The licensed program described in this document and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or any equivalent agreement between us.
Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurements may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment.
Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products.
All statements regarding IBM's future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only.
This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental.
COPYRIGHT LICENSE:
This information contains sample application programs in source language,
which illustrate programming techniques on various operating platforms. You may
copy, modify, and distribute these sample programs in any form without payment
to IBM, for the purposes of developing, using, marketing or distributing
application programs conforming to the application programming interface for
the operating platform for which the sample programs are written. These
examples have not been thoroughly tested under all conditions. IBM, therefore,
cannot guarantee or imply reliability, serviceability, or function of these
programs.
·
IBM, the IBM logo, and ibm.com are
trademarks or registered trademarks of International Business Machines
Corporation in the United States, other countries, or both. If these and other
IBM trademarked terms are marked on their first occurrence in this information
with a trademark symbol (® or ™), these symbols indicate U.S. registered or
common law trademarks owned by IBM at the time this information was published.
Such trademarks may also be registered or common law trademarks in other
countries. A current list of IBM trademarks is available on the Web at
"Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml.
·
Microsoft, Windows, Windows Vista,
and the Windows logo are trademarks of Microsoft Corporation in the United
States, other countries, or both.
·
Other company, product, or service
names might be trademarks or service marks of others.
This product incorporates technology covered by one or more of the following patents: U.S. Patent Numbers: 6,094,505; 5,768,416; 5,625,465; 5,369,508; 5,258,855.