Input and output settings
Because maps executed with a Command Server can only override those input and output settings that have corresponding execution commands, some input and output settings are not configurable in the Integration Flow Designer.
Note: If you use cluster support for the Launcher, the system definition file
(.msd) is a key factor in the behavior of file triggers. To
prevent trigger files from being processed more than once, set the
OnSuccess card setting to Delete, or
configure a keep directory. See the Launcher documentation for details about
the keep directory and the OnSuccess setting.
Input settings
The following table lists input settings.
| Input Setting | Available in Command Server Settings? | Available in Launcher Settings? |
|---|---|---|
| FetchAs | No | Yes |
| WorkArea | Yes | Yes |
| Backup | No | Yes |
| SourceEvent | No | Adapter-dependent |
| ErrorDirectory | No | Yes |
| KeepDirectory | No | Yes |
| Source | ||
| Command | No | Yes |
| OnSuccess | No | Adapter-dependent |
| OnFailure | Yes | Yes |
| Retry | Yes | Yes |
| Scope | No | Yes |
| Warnings | No | Yes |
| FetchUnit | No | Yes |
Note: See the Map Designer documentation for information on how to
configure these settings.
Output settings
The following table lists output Launcher and Command Server settings.
| Output Setting | Available in Command Server Settings? | Available in Launcher Settings? |
|---|---|---|
| Backup | Yes | |
| Target | ||
| Command | Yes | Yes |
| OnSuccess | Adapter-dependent | |
| OnFailure | Yes | Yes |
| Retry | Yes | Adapter-dependent |
| Warnings | Yes | |
| Scope | Yes |