Details of the run external command clause

Specify the following fields in the Run External Command clause to provide Secure Exchange Gateway with details about the executable program or script:

• External Command: The full path and file name of the executable program or script.

  You must set the correct permissions on the executable file. Files must be accessible and executable by the user gw-services or by the group cs-adm. Example user: chown gw-services /my/app/location/myapp chmod u+x /my/app/location/myapp Example group: chown :cs-adm /my/app/location/myapp chmod g+x /my/app/location/myapp

• Command line parameters: The command-line parameters for the executable program or script.

  For the executable program or script to run on content, you must enter the %FILENAME% token. Secure Exchange Gateway uses the %FILENAME% token to relay the file name which the executable program or script must run. Enter the %LOGNAME% token to ensure the executable program or script generates a log file . You can use both the %FILENAME% and %LOGNAME% tokens at the same time. You can also use Property tokens in the command line parameters field. See External program tokens for a list of available tokens. If you specify the %LOGNAME% token as a command line parameter, you can use the %LOGTEXT% token in the Description field on the Response Codes table. See Responses for more information on configuring a response code.

• Timeout (in seconds): The permitted amount of time, in seconds, for Secure Exchange Gateway to run the executable program or script on a single message or item. If this limit is exceeded, Secure Exchange Gateway stops running the executable program or script and triggers either the Message Processing Fails content rule (if you have it applied to a policy route) or the global Message Processing Failure rule.