Execute Application on Client from within a Telnet Session

Bridge the Gap between GUI processing and a character oriented protocol.

An incredibly powerful utility that facilitates client side processing of server side files when using the Georgia SoftWorks Telnet Client. The Georgia SoftWorks Telnet Server provides the capability to execute commands on the client computer while in the telnet session. This is accomplished through a new utility:

gs_exec client_side_command_line

 This capability is fully developed when coupled with the Georgia SoftWorks File Transfer Utilities (gs_put and gs_get) .

Execution of commands on the client can be used to accomplish:

1.      Edit Sever files[1] using a local GUI editor like MS Word.

2.      Run programs on the client that prompts the user for data and transfers the results back to the server.

3.      Automate file transfer from the sever to the client, run program that uses transferred file for input and then transfer the output data of the program back to the server.

4.      Useful in situations where you want to do part of the processing on the server and part on the client.

5.      Initiate program on client and transfer results to server when complete.

6.      Periodic initiation of client side program processing transferred data and/or transferring data when complete.

7.      View graphic images on the client using a program such as Corel Draw or Microsoft Photo Editor when the image resides on the server.

8.      Run file or system level commands on the client synchronously with the server side script.

9.      AND MUCH MUCH MORE!

Command: gs_exec

Description: Command line utility that executes commands on the client from within a telnet session.

Syntax: gs_exec <client_side_command_line>

Arguments:  There is 1 required argument.

a.       <client_side_command_line> The command to execute on the client computer.

This command is any valid command on the client computer. It can contain command arguments just as if entered on the client.

                              NOTE: Path information as argument data must be from the Clients perspective.

If the program selected to run is a GUI program then a new Windows is opened. If the program selected is not a GUI program and has character output then the output data it is displayed in the Telnet Window for 2000 ms (two Seconds) or the time specified by the /scmddelay gs_clnt.exe command line option .

Typically a script or batch file is created that will transfer the server file to the client; run the client side command using the gs_exec command, and then transfer the file back to the server when completed.

Example - Utilities: Execute program on Client – Local Edit using GUI Editor

A company brochure that resides in a file that contains graphic images and rich text exists on Server that the user would like to edit using the client copy of Microsoft Word.

The file can be transferred using the gs_put utility, then MS Word is invoked using the gs_exec utility, and when the editing is complete, the file is transferred back to the server using the gs_get utility.  The following commands reflect the sequence of commands that detail the steps.

gs_put d:\xfer\cbroch.doc c:\received\cbroch.doc

gs_exec winword c:\received\cbroch.doc

gs_get c:\received\cbroch.doc d:\xfer\cbroch.doc

These commands can be included in a batch file such that the “Local Edit” capability is more “generic” and easily invoked.

Create a batch file (lets call it ledit.bat)

gs_put d:\xfer\%1 c:\received\%1

gs_exec winword c:\received\%1

gs_get c:\received\%1 d:\xfer\%1

Assumptions:

File on server is always in d:\xfer\    folder

File to be edited on client is always in  c:\received folder.

When connected via telnet to the server; when in the d:\xfer folder the user can simply type:

ledit cbroch.doc

to transfer the file to the client and run MS Word. When completed in MS Word the file is automatically transferred back o the server.

Example - Utilities: Execute program on Client –View Image on Client

A car dealership headquarters has images of motor vehicles in the database. A local dealer can easily display the images (pictures) to prospective buyers via telnet.

The file can be transferred using the gs_put utility, then the default image view can be invoked allowing the image to be viewed without required knowledge of the graphics display program. On the Windows OS  the file type[2] extension will invoke a default executable. In the following two lines, the first line transfers the file to the client and the second line will invoke the default image display program, which will display the image.

gs_put d:\auto_database\corvette_1993.jpeg c:\viewcar\corvette_1993.jpeg

gs_exec c:\viewcar\corvette_1993.jpeg

Again these commands can be included in a batch file such that the “View Image” capability is more “generic” and easily invoked.

Create a batch file (lets call it vimage.bat)

gs_put d:\auto_database\%1 c:\viewcar\%1

gs_exec c:\viewcar\%1

Assumptions:

Image files on server is always in d:\auto_database\ folder

Image file to be viewed on client is always in  c:\viewcar folder.

A default image viewer exists for .jpeg extensions

When connected via telnet to the server and positioned in  the d:\auto_database folder the user can simply type:

vimage corvette_1993.jpeg

to transfer the file to the client and display the image.

Example - Utilities: Execute program on Client –Quick Directory Listing

The User needs to transfer a file from the client to the server but does not remember the exact filename. To quickly obtain a directory listing they can simply run:

gs_exec dir

This will display the directory contents without having to open a new window on the client. The contents of the directory (folder) are quickly displayed in the Telnet Window for 2000 ms (two seconds) or the time specified by the /scmddelay gs_clnt.exe command line option