Outbound Acknowledgment configuration parameters
The following table shows the configuration parameters that are required by the outbound
acknowledgment
task.
| Parameter | Required | Default | Description |
|---|---|---|---|
| Activate task | No | No | Identifies if the configuration is active. When it is active, the task is available to send acknowledgment messages. |
| Process end of day | No | No | Run the task when Services Framework is notified to run end of day. Set this value to no because the task does not support running end of day. |
| Process cleanup | No | No | Set this value to no because the task does not need to process cleanup. |
| Gateway outgoing directory | Yes | None | The directory where Gateway Server gets the outbound acknowledgment files to be processed. The directory must exist in the file system and be no more than 256 characters long. |
| Transmission Definition | Yes | None | A valid transmission definition name from an existing Partner Profiles
configuration. The value must be defined before the outbound
acknowledgment task is configured. Note: This
task does not support the FTM workflow transmission format. Do not use a transmission definition that has this
transmission format.
|
| Working Directory | Yes | None | The directory where the outbound 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 that is installed and no more than 256 characters long. |
| Environment Identification Text | No | No environment identification text | An optional string to identify the environment. This parameter is combined with the
Instance Name system property and placed in the XML of the outbound
acknowledgment.
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,
|
| Notification file extension | No | .xml | Extension to use when the notification file is created. |
| Notification route file extension | No | .rte | Extension to use when the notification route file is created. |
| Notification end-of–file extension | No | .eof | Extension to use when the notification end of file is created. |