Deferred processing configuration required

Since DB-to-JMS runs as a deferred process, the deferred process DB_TO_JMS must be registered by adding an entry in the DPProcess table. This can be done by either an SQL statement or by a Data Manager file. Examples of each are shown below.

Figure 1. Using an SQL statement to setup the DB-to-JMS deferred process

-- Register the DB-to-JMS deferred process:
  INSERT INTO DPPROCESS
    (PROCESSNAME, INTERFACENAME, METHODNAME, TICKETTYPE, SUBJECT)
  VALUES
    ('DB_TO_JMS',
    'curam.util.internal.deferredprocessing.intf.DBtoJMSbpo',
    'continueTransfer', 'INF',
    'Transfers messages from database to JMS queues.');

Figure 2. Using the data manager to setup the DB-to-JMS deferred process

<!--  Register the DB-to-JMS deferred process: -->
  <table name="DPPROCESS">
    <column name="PROCESSNAME" type="text" />
    <column name="INTERFACENAME" type="text" />
    <column name="METHODNAME" type="text" />
    <column name="TICKETTYPE" type="text" />
    <column name="SUBJECT" type="text" />
    <row>
      <attribute name="PROCESSNAME">
        <value>DB_TO_JMS</value>
      </attribute>
      <attribute name="INTERFACENAME">
        <value>
        curam.util.internal.deferredprocessing.intf.DBtoJMSbpo
        </value>
      </attribute>
      <attribute name="METHODNAME">
        <value>continueTransfer</value>
      </attribute>
      <attribute name="TICKETTYPE">
        <value>INF</value>
      </attribute>
      <attribute name="SUBJECT">
        <value>Transfers messages from database to JMS queues.
        </value>
      </attribute>
    </row>
  </table>