Reference implementation support for distribution copy

The reference implementation defines business rules that determine which transactions are copied into sidepoints during ingestion. The transactions that satisfy these rules are copied into a sidepoint and become sidepoint transactions. Use these rules as an example when defining distribution copy rules for a specific deployment.

The reference implementation provides the following Business Rules nodes and tasks for distribution copy.

Business Rules SidepointAssignmentNode

This node contains the rules used to assign transactions to sidepoints. It is an eSort type node that is used in each of the following workflows:
  • For Corporate Payment Services: CpsWorkflow
  • For Check: ChkFwdWorkflow
The node calls the following tasks:
  • SidepointAssignMsgTypeTask
  • SidepointAssignDepProdTask
  • SidepointAssignPresProdTask
Each of these tasks performs a table look up and assigns, at most, one sidepoint to the transaction being ingested.

Business Rules SidepointAssignMsgTypeTask

This task assigns the sidepoint based on the message type assigned to the outbound transaction. It performs a table look up on the SidepointAssignMsgTypeTable using ibmNprMessageTypeNameOut as the key.

Business Rules SidepointAssignDepProdTask

This task assigns the sidepoint based on the product code, depositor ID, and if the depositor is subscribed to the service in the inbound service code field for the transaction. It performs a table look up on the SidepointAssignDepProdTable using ibmValProductId, ibmVal, and ibmValDepositorId as the keys.

Business Rules SidepointAssignPresProdTask

This task assigns the sidepoint based on the endpoint assigned to the transaction, and if that endpoint is subscribed to the service in the outbound service code field for the transaction. It performs a table look up on the SidepointAssignPresProdTable using ibmNprEndpoint as the key.

Transaction Server event

Normally, the reference implementation uses an event to send a message to Settlement whenever an outbound transmission is sent. Settlement processes the outbound transmission as a unit-of-work.

For distribution copy, the reference implementation is configured to not send a message to Settlement when the outbound transmission is a sidepoint transmission. Settlement should not process sidepoint transmissions because they contain copies of transactions instead of the original transactions. For example, when Settlement has already processed an outbound transmission that contains original transactions, processing the copied transactions associated with its sidepoint transmission would result in Settlement double counting the transactions.