FileNet Image Services: Capability to breakup Fast Batch objects before Integral SDS write.

FileNet Image Services 4.1.2 FP4 introduces SDS Fast Batch Breakup. This enhancement allows documents that are committed via Fast Batch to Integral SDS to be broken up into accessible cache objects prior to writing to the SDS repository. This allows Fast Batch documents to be available from cache if the SDS device is disabled for any reason. The documents would remain locked in cache and write requests would be generated until the repository becomes available. This feature is activated by the presence of a trigger file, /fnsw/local/trigger/SDS_fbc_breakup. FileNet Image Services must be recycled after creation of the trigger file.

Without this enhancement, documents are not retrievable before they are written to the SDS repository because Fast Batch cache objects are in a BLOB format that may not be retrieved, and documents are not catalogued in the MKF DOCS table and the DOCTABA table in the index database. With this enhancement, the Fast Batch BLOB object in cache is broken up into a retrievable format and catalogued to the MKF DOCS table and the DOCTABA table in the index database prior to writing to the SDS repository. This means that if the SDS device is down or disabled, incoming Fast Batch documents are retrievable since they are broken up in cache and catalogued in the MKF DOCS table and the DOCTABA table in the index database.

Another feature is the ability to configure more than one fbc_commit process. Multiple fbc_commit processes can share the processing on cache-only servers or for commits to SDS-only families. It is controlled by a trigger file, /fnsw/local/trigger/fbc_commit_number. The file would contain the desired number of processes, max of 256. IS must be recycled after creation of this file.