Configuring an entry services profile

This section describes how to configure a sample entry services profile within Transaction Server. These steps are to be used as a guide and may vary depending on what is needed for a specific entry allocation process.

Scenario

The main purpose of this scenario is to extract only ICL Cash Letters and the message queue work that is loaded through the Gateway Server. The work is aggregated using the debit amount totals with a threshold of 10 million dollars. Once 10 million dollars worth of batches (ICLs) arrive in the system, those batches (ICLs) are to be contained in a single entry.
Note: The $10-million debit threshold is used as a guide. The actual dollar value in the file will be more than $10 million, depending on the amount of the batch (ICL) that caused the threshold to be exceeded.
Follow these steps:
  1. Download the EntryServicesProfile.xml file from the artifacts pod for your offering. For example, share/artifacts. For more information, see Getting the files from the artifacts container for your FTM offering and the related artifacts container contents section
  2. Make a copy of the EntryServicesProfile.xml file and rename the file. For this example, MySampleProfile.xml is used.
  3. Open MySampleProfile.xml.
  4. Add the parameters to use for allocating the entries: 
    <parameters>
   <parameterSet name="sample parameters">
      <parameter name="entryNumberApplication">APP1</parameter>
   </parameterSet>
</parameters>
  5. Alter the profile definition to identify the sources of the entries to be allocated (ICL Cash Letters and the message queue) and enable aggregation by defining a rule to set the threshold for the debit amount to 10-million dollars: 
    <profile type="ENTRY"
  name="My sample profile"
  parameterSet="sample parameters">

   <!-- sources for ICL Cash Letters and the message queue -->
   <sources>
      <type>3</type>
      <type>2</type>
   </sources>

   <!-- Only want to send those batches that are LOADED in the system -->
   <conditions>
      <column>LOADED</column>
   </conditions>

   <!-- enable aggregation (providing our aggregation rule) -->
   <aggregationRules type="rule based">
      <rule name="10 Million debit threshold">
         <debitAmount min="1000000000" max="1000000000" />
      </rule>
   </aggregationRules>
</profile>
  6. Save the MySampleProfile.xml file.
    Once all of the changes are made, the MySampleProfile.xml file should look something like this: 
    <?xml version="1.0" encoding="UTF-8"?>
<extraction>
   <parameters>
      <parameterSet name="sample parameters">
         <parameter name="entryNumberApplication">APP1</parameter>
      </parameterSet>
   </parameters>
   <profile type="ENTRY"
     name="My sample profile"
     parameterSet="sample parameters">

      <!-- sources for ICL Cash Letters and the message queue -->
      <sources>
         <type>3</type>
         <type>2</type>
      </sources>

      <!-- Only want to send those batches that are LOADED in the system -->
      <conditions>
         <column>LOADED</column>
      </conditions>

      <!-- enable aggregation (providing our aggregation rule) -->
      <aggregationRules type="rule based">
         <rule name="10 Million debit threshold">
            <debitAmount min="1000000000" max="1000000000" />
         </rule>
      </aggregationRules>
   </profile>
</extraction>
  7. Deploy the MySampleProfile.xml file by using the Red Hat® OpenShift® Container Platform ConfigMap process, Customizing the configuration files in a ConfigMap. The XML file is then located in the Red Hat OpenShift Container Platform directory configDropins folder: /opt/ibm/wlp/usr/servers/defaultServer/configDropins/overrides/MySampleProfile.xml
    • As specified in Customizing the configuration files in a ConfigMap, the pod must be deleted for the new file to be activated. Specify this directory when configuring the task.
  8. Configure the entry marking and entry allocation tasks in Services Framework. For more information about configuring the tasks, see Services Framework task registration and configuration.