Messages Sent to the Duplicate Detect Engine

The Duplicate Detect engine is a J2EE application running inside the WebSphere® Application Server. Data is sent to and from the engine using JMS RFH messages in XML format. The following shows the format of the XML message:

<?xml version="1.0" encoding="UTF-8"?>
<duplicateCheck xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
                xsi:noNamespaceSchemaLocation="DupDetect.xsd">
  <totals>
    <totalItems>500</totalItems>
  </totals>
  <status code="rerun"></status>
  <records>
    <record>
      <fields>
        <field name="ACCOUNT">1234567890</field>
        <field name="ROUTING_TRANSIT">0987654321</field>
        <field name="AMOUNT">145709</field>
        <field name="AUX_ONUS">1111-2222</field>
        <field name="SOURCE">X937</field>
        <field name="PROCESS_CONTROL"></field>
        <field name="FIELD_4"></field>
        <field name="EXT_PROC_CODE"> </field>
        <field name="PAYMENT_ID">987654321</field>
      </fields>
    </record>
    ...
    ...
    <record>
      <fields>
        <field name="ACCOUNT">1234567891</field>
        <field name="ROUTING_TRANSIT">0987654322</field>
        <field name="AMOUNT">500000</field>
        <field name="AUX_ONUS">3333-444</field>
        <field name="SOURCE">X937</field>
        <field name="PROCESS_CONTROL"></field>
        <field name="FIELD_4"></field>
        <field name="EXT_PROC_CODE"> </field>
        <field name="PAYMENT_ID">987654322</field>
      </fields>
    </record>
  </records>
</duplicateCheck>

Each record element contains a fields element, which contains all the field elements making up an item. Each field contains a name attribute. The name should match the corresponding column name in the details table within the namespace. This is the only way the Duplicate Detect engine knows which fields to insert into which database columns. One record element should exist for every item to be duplicate checked.

The totals and totalItems elements are used to split one unit of work into multiple messages. If there are thousands of items in a unit of work, the user does not want to create one XML message, which is hundreds of thousands bytes long. Split the items up among several messages, using the same unit of work name for each message and putting the total number of items across all messages into the totalItems element. The Duplicate Detect engine sends back one response for each message received and when the entire unit of work is finished it sets a complete flag in the user area of the RFH2 header.

The status code="rerun" element is used to inform the engine this particular unit of work is being reprocessed. The engine dispositions each item in the unit of work being rerun the same as it was dispositioned the first time the unit of work was processed. In addition to setting the status code equal to rerun, ensure the unit of work name is identical to the original unit of work being rerun.