File Naming Pattern Considerations
Outbound acknowledgment places the following files in the Gateway outgoing
directory:
- Acknowledgment XML
- Routing
- End of file
For more information about file naming patterns and using the transmission definitions screens, see Transaction Server User's Guide.
Here is a sample file naming pattern:
MYBANK.%PT%.R%PID%.D%DTyyyyMMdd%.T%DThhmmssSSS%The
pattern creates a file name that includes the transmission type indicator,
receiving point routing ID, and the date and time down to the milliseconds.
For a notification having transmission type T, a receiving point routing
value of 5555-1234 and occurring on May 29th, 2009 at 1:41:23:497
PM, the file name created is:
MYBANK.T.R5555-1234.D20090529.T134123497The file naming pattern does not include the file extension, so outbound
acknowledgment adds
file extensions to each file it creates. It delivers the following
files to Gateway Server.
- MYBANK.T.R5555-1234.D20090529.T1341.xml
- MYBANK.T.R5555-1234.D20090529.T1341.rte
- MYBANK.T.R5555-1234.D20090529.T1341.eof
The XML file contains the outbound acknowledgment in XML format. The RTE file contains the routing information that instructs the Gateway about how to deliver the file to its receiving point. The EOF file is empty and always written last. It is used to signal the other files have been delivered and are ready for processing.
When a second batch (ICL) is processed four 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.xml
- MYBANK.R.R5555-4321.D20090529.T1345.rte
- MYBANK.R.R5555-4321.D20090529.T1345.eof