IBM FileNet P8, Version 5.2.1            

How replication workers process actions

Replication workers process actions as a batched database transaction or as single database transactions. The lower the number of database transactions that are required to complete the batch, the higher the throughput. Optimal throughput is achieved when the replication worker can process all the actions that are required for the entire batch with a single database transaction.

The following primary actions are associated with the inbound replication workers:

If an entire batch consists of insert and export actions, Content Platform Engine processes the batch as a single insert transaction to the database. Update and delete actions are processed as single database transactions. A batch of action requests that consists of update and delete actions generally requires many more transactions and more time to complete.

For example, an inbound batch has the following action codes: Insert document1, Insert document2, Insert document3, Update document2, Update document2, Insert document4, Insert document5, Insert document6, Insert document7. Assuming that no errors are encountered, the batch requires six transactions:
The following primary actions are associated with the outbound replication workers: The outbound journal selection on FileNet® P8 assigns one journal for the same document in each batch. Multiple actions for the same document are in different batches. Within the same batch, different operations are sent in separate remote procedure calls (RPCs) to FileNet Image Services.
For example, assume that document1 was replicated. The following journals are in the replication queue: Initiate document2, Initiate document3, Update document2, Update document2, Update document1, Initiate document4, Initiate document5, Initiate document6, Initiate document7. Assuming that the batch size is 50, this batch requires three RPCs.


Last updated: October 2015
p8pca040.htm

© Copyright IBM Corporation 2015.