Transmission Acknowledgment File Name Pattern

The transmission acknowledgment task creates the following file set in the Gateway outgoing directory:
.dat
Contains the acknowledgment XML that was transformed using XSL.
.rte
Routing information Gateway uses to send the file to its destination.
.eof
Empty file written last to signal that the other files are delivered and ready for processing.

To name these files, transmission acknowledgment uses a file name pattern from the transmission definition configuration. Based on the incoming transmission type loaded, the name pattern uses a substitution algorithm to produce a unique file name for each transmission acknowledgment. Distinct file extensions are added to the name to generate the complete acknowledgment file set.

The file name pattern for transmission acknowledgment uses a substitution pattern to ensure the file names sent to the Gateway outgoing directory are unique. The following is an example of a file name pattern used by the transmission acknowledgment task. For more information, see File Name Patterns and Custom File Formatters. 
MYBANK.%DTyyyyMMdd%.%DThhmm%.<ext>

You can further modify the file name by extending the TransmissionAckTask class and overwriting the modifyAcknowledgmentFileName(String filename) method.

The following is an example of a file created on May 29, 2009 at 1:41:23:497 PM: 
MYBANK.20090529.134123497.dat
MYBANK.20090529.134123497.rte
MYBANK.20090529.134123497.eof

A formatter is a Java™ class that generates a custom routing file string. To create a custom routing file, the user must implement a unique formatter class and define the class and routing file schema name. Define the class and routing file schema name on the edit transmission definition screen. For more information about defining the class and routing file schema name, see Transmission Definitions Management. Transmission acknowledgment uses the %PID%, %PT%, %FIM%, and %DT% patterns.

Here is a sample file naming pattern: 
MYBANK.%PT%.R%PID%.D%DTyyyyMMdd%.T%DThhmm%
This pattern creates a file name that includes the transmission type indicator, receiving point routing ID, and the date and time. For an acknowledgment having transmission type T, a receiving point routing value of 5555-1234 and occurring on May 29th, 2009 at 1:41 PM, the file name created is: 
MYBANK.T.R5555-1234.D20090529.T1341
The file naming pattern does not include the file extension, so transmission acknowledgment adds file extensions to each file it creates. By default, it delivers the following files to Gateway Server.
  • MYBANK.T.R5555-1234.D20090529.T1341.dat
  • MYBANK.T.R5555-1234.D20090529.T1341.rte
  • MYBANK.T.R5555-1234.D20090529.T1341.eof

The DAT file contains the acknowledgment XML, which may have been transformed using XSL. The RTE file contains routing information that Gateway uses to send the file to its destination. An empty EOF file is always written last to signal that the other files are delivered and ready for processing.

When a second batch (ICL) is processed 4 minutes later with a transmission type of R and a receiving point routing of 5555-4321, the following files are copied to the Gateway outgoing directory.

  • MYBANK.R.R5555-4321.D20090529.T1345.dat
  • MYBANK.R.R5555-4321.D20090529.T1345.rte
  • MYBANK.R.R5555-4321.D20090529.T1345.eof