Transmission Acknowledgment configuration parameters
The following table shows the configuration parameters that are required by the transmission
acknowledgment task.
| Parameter | Required | Default | Description |
|---|---|---|---|
| Gateway outgoing directory | Yes | None | The directory where Gateway Server gets the transmission acknowledgment files to be processed. The directory must exist in the file system and be no more than 256 characters long. For example, the directory structure of this path is /opt/ibm/ftm/runtime-processing/outbound/source. |
| Transmission Definition | Yes | None | A valid transmission definition name from an existing configuration. |
| Working Directory | Yes | None | The directory where the transmission acknowledgment files are created before they are moved to the Gateway outgoing directory for processing. If this directory does not exist during configuration, it is created. The directory specification must be valid for the file system and be no more than 256 characters long. For example, the directory structure of this path is /opt/ibm/ftm/services-engine/working |
| Environment Identification Text | No | No environment identification text | An optional string to identify the environment. This parameter is combined with the
system property instance name and placed in the transmission
acknowledgment XML. If this parameter is left
unspecified, only the system property is used in the XML. The environment identification text must be no more
than 256 characters long. For example, |
| Transformation Stylesheet | No | No transformation stylesheet | The XSL transformation stylesheet used to convert the standard transmission acknowledgment XML file into a different format. If an XSL transformation file is not specified, the resulting transmission acknowledgment file contains the default XML format. The entire path to the file must be specified, no more than 256 characters long, and the file must exist in the file system. For example, the directory structure of this path is /opt/ibm/ftm/services-engine/task-config |
| Errors Displayed | No | 500 | The maximum number of errors to present in the transmission acknowledgment file. It keeps the errors that are reported by transmission acknowledgment to a reasonable limit for batches (ICLs) that contain many errors. It must be a valid, positive integer value in the range 1 - 2,147,483,647. |
| Errors Per File Displayed | No | 10 | The maximum number of transmission level errors to present for each transmission record in the transmission acknowledgment file. It keeps the errors that are reported to a reasonable limit when there are many errors. It must be a valid, positive integer value in the range 1 - 2,147,483,647. |
| Errors Per Batch Displayed | No | 10 | The maximum number of batch (ICL) level errors to present for each batch (ICL) record in the transmission acknowledgment files. It keeps the errors that are reported to a reasonable limit when there are many errors. It must be a valid, positive integer value in the range 1 - 2,147,483,647. |
| Errors Per Bundle Displayed | No | 10 | The maximum number of bundle level errors to present for each bundle record in the transmission acknowledgment files. It keeps the errors that are reported to a reasonable limit when there are many errors. It must be a valid, positive integer value in the range 1 - 2,147,483,647. |
| Errors Per Item Displayed | No | 10 | The maximum number of transaction level errors to present for each transaction record in the transmission acknowledgment files. It keeps the errors that are reported to a reasonable limit when there are many errors. It must be a valid, positive integer value in the range 1 - 2,147,483,647. |
| Acknowledgment File Extension | No | .xml | Extension to use for the acknowledgment file. |
| Acknowledgment Route File Extension | No | .rte | Extension to use for the acknowledgment route file. |
| Acknowledgment End-of-File Extension | No | .eof | Extension to use for the trigger file that indicates the data file is ready for processing. |
| Scheduled Transmission Acknowledgment | No | false | Set this parameter to true to send acknowledgments for transmissions on a fixed schedule. If set to true, changes might be required to the default Transaction Server scheduler XML file. When you register the task, make sure that the task is allowed to be scheduled. |
| Scheduled Batch Acknowledgment | No | false | Set this parameter to true to send acknowledgments for batches (ICLs) on a fixed schedule. If set to true, changes might be required to the default Transaction Server scheduler XML file. When you register the task, make sure that the task is allowed to be scheduled. |
| Delay (in seconds) for sending transmission acknowledgment | No | 60 | Delay, in seconds, for sending acknowledgments for transmissions. This delay allows time for the transmissions and their batches (ICLs) to be fully loaded and also to group multiple acknowledgments in a single scheduled run of the task. |
| Report Accepted Batches | false | true | Set this parameter to false to exclude batches (ICLs) from the acknowledgment. Batches (ICLs) that have a condition of accepted and are also in the complete status are excluded. Set this parameter to true to include all batches (ICLs) in the acknowledgment, regardless of their batch (ICL) status. The default is true. |
| Maximum Batches to Report | false | 500 | The maximum number of batches (ICLs) to include in the acknowledgment. When acknowledgments are created for transmissions with numerous batches (ICLs), this limit helps keep the acknowledgment to a manageable number of bytes in size. |