Remote Command Settings
You can use the Remote Command in order to run commands by using SSH on remote UNIX systems. Remote Command is only supported for SSH to UNIX operating systems. For SSH, you must use SFTP Connection objects.
SSH connections always open via the port that is configured for the SFTP Connection object.
When Jobs with multiple Remote Command commands run, a single logged in session is created for all commands per connection used.
For security reasons, Remote Command commands are disabled by default, but they are always listed in the RA FTP Agent Jobs' Commands list.
When remote commands are: | And a Job with a Remote Command is executed, the command will: |
---|---|
Disabled |
Fail |
Enabled |
Run normally |
For information on enabling remote commands for an RA FTP Agent, see topic RA FTP Agent Administration.
To run a remote command:
- Select a connection under Remote Connection.
- Enter a command in the Remote Command field.
- Optionally enter an expected return code number to determine success in the Return code must be for success field.
- If you do not want the Job to abort if this command fails, uncheck the Abort job on command failure box.
- Optionally add a description of the command under Description.
-
The Description field acts as comment in the command sequence, and is not written to the Job report. To write a message to the Job report use an Echo command .
The only two selectable connections in the drop-down list are the ones selected in the From and To fields at the top of the FTP Job definition page, above the command sequence.
This field allows Automation Engine variables in the format &<name>#.