Extract each batch (ICL)

This example shows extracting each batch (ICL) individually by its sort pattern and source.

This example shows how to configure your extraction profile to extract each batch (ICL) individually, based on its source and sort pattern. It extracts only those batches (ICLs) that come into the Transaction Server through the Gateway message queue and are assigned any one of the valid sort patterns.

<?xml version="1.0" encoding="UTF-8"?>
<extraction>
   <parameters>
      <parameterSet name="basic example">
         <parameter name="processedPath">c:/ITSExtraction/processed</parameter>
         <parameter name="errorPath">c:/ITSExtraction/error</parameter>
         <parameter name="intermediatePath">c:/ITSExtraction/processing</parameter>
         <parameter name="autoNotify">true</parameter>
      </parameterSet>
   </parameters>

   <profile type="CPCS" name="cpcs (single presentment)"
    parameterSet="basic example">

      <!-- Only extract batches (ICLs) that were loaded        -->
      <!-- by the Gateway through the Gateway message queue    -->
      <!-- sources:                                            -->
      <!-- 3 = Gateway message queue                           -->
      <sources>
         <type>3</type>
      </sources>

      <!-- Valid list of sort patterns for extraction -->
      <sortPatterns>
         <pattern>108</pattern>
         <pattern>205</pattern>
         <pattern>250</pattern>
      </sortPatterns>

      <!-- Only want those batches (ICLs) to be extracted when they -->
      <!-- are successfully loaded.                                 -->
      <conditions>
         <column>LOADED</column>
      </conditions>

      <!-- Extract batches (ICLs) individually (never grouped) if     -->
      <!-- 1)  Loaded in Transaction Server as the Gateway message queue work. -->
      <!-- 2)  Has sort pattern equal to 108, 205, or 250.          -->
      <aggregationRules type="single presentment"/>
   </profile>
</extraction>