Command Execution Tool

The Command Execution Tool is only available on Windows systems.

The Command Execution Tool allows you to start applications which run interactively in the logon session of the user from within follow-up processing. The tool comprises the Command Execution Server and the Command Execution Client.

The Command Execution Server (CES) must be started in the logon session of the user for whom openFT is to start an application interactively. The Command Execution Client (CEC) is called during follow-up processing.

Format

Server: ft_cexsv.exe [<ID 1..16>]

Client: ft_cexcl.exe [–sv=<ID 1..16>] <command 1..2000>

Description

ID

is an optional identifier for the CES with a maximum length of 16 characters. It serves to distinguish concurrent instances of CES. The identifier is defined when CES is started and is read by the client with the parameter -sv.

command

designates the commands to be executed.

Notes

• A CES can be started automatically, for instance by making an entry in the Startup group. After the CES is started, a small icon (globe) appears in the task bar.

• The CES listens for commands that the Command Execution Client (CEC) sends to it for execution. The CES and CEC together ensure that only those CECs and CESs communicate with each other that belong to the same user context. This prevents User A from executing processing in an interactive logon session of User B with the rights of the latter.

• The CES terminates automatically when the user logs off or when the computer is shut down. It can be terminated manually by right-clicking on the CES icon and choosing Exit from the context menu that appears.

• The CEC is simply called during follow-up processing. The command string to be executed is passed as an argument when the application is started. If the optional parameter –sv is to be specified when the CEC is started in order to address a particular CES, –sv must be the first parameter passed when CEC is started.

Examples

1. User A receives files from a partner via openFT and these are to be edited using the WordPad (write.exe) word processing program after the files have been transferred successfully. In order to achieve this, User A can, for instance, set up an FTAC protocol in which follow-up processing is defined which starts the Command Execution Client and passes the command to be executed to CES.

   • Starting the CES:

     ft_cexsv.exe

   • Follow-up processing command for starting the CEC:

     ft_cexcl.exe write.exe %FILENAME

2. User A has opened two sessions with a terminal server. Files received over the admission profile profile1 are to be opened with write.exe in the first terminal session. Files received over the admission profile profile2 are to be opened with Microsoft's Excel.exe in the second terminal session.

   • Starting the CES in the first terminal session:

     ft_cexsv.exe Session1

   • Starting the CES in the second terminal session:

     ft_cexsv.exe Session2

   • Follow-up processing command for starting the CEC for admission profile profile1:

     ft_cexcl.exe –sv= Session1 write.exe %FILENAME

   • Follow-up processing command for starting the CEC for admission profile profile2:

     ft_cexcl.exe –sv= Session2 Excel.exe %FILENAME