GUI ScreenIO Client/Server |
Define the applications that you wish to make available to your clients. Note: Only GUI ScreenIO applications are supported.
The items appear in this table in alphabetical order.
Item | Significance |
Application: | Name of the application that will be displayed on the client menu. |
Application: | Text which will be appended to the command when the
application is launched.
If you specify a command tail when you add an application to a user's menu, it will override the default command tail. |
Application: | Complete pathspec of the application's executable as seen
from the server. It can be a network url such as:
or it can contain drive-letter structured links: C:\program files\myapps\program.exe If you use drive letters, you are responsible to be sure that drive is mapped at execution time. You can use the Browse button to find the executable. WARNING: Do not use the browse button if configuring a server remotely. (That is, when you access the server configuration from a menu item on your menu via the client.) Instead Key in the entire path. |
Application: | Unique number greater than zero that is assigned as a key for this application. These are assigned automatically, but you may override the number if you wish. |
Application: | The current directory when the application is launched. This defaults to the directory where the executable is located. If blank, it is indeterminate, but will most likely be the directory where the server executable is located. |
Availability: | Specifies that this application will be available to any user who connects to your server, unless that user is registered and the user's definition does not have the "Include default menu" box checked. |
Availability: | The application is not available. |
Availability: | The application is only available to registered users whose menu specifically includes the application. |
Availability: | Number of times that a user may run this application, potentially useful for subscriptions. |
Availability:
Maximum Idle Time |
Specified the time in minutes that the application may be idle (not sending data to the server) before it will be asked to terminate. 0=Not timeout. The application will be asked to terminate gracefully after being idle for this duration. The programmer of the application needs to make provision for this functionality as documented in the Getting Started section of the GUI ScreenIO documentation. |
Delete | Deletes this registered application from the configuration database. This also deletes it from all user menus. |
When not available: | If the application is marked not available, it will be displayed on the client's menu, but will be grayed out and may not be launched. |
When not available: | If the application is marked not available, it will not appear on the client's menu. |
Remember that the only applications that GUI ScreenIO Client Server layer can make available are those applications written in GUI ScreenIO. Further some Applications may not be suitable for use under the client server.
The server configuration utility CAN be used to allow remote management of the server, but it must be used with care as you can disable your server remotely with the configuration facility.
NOTE:
RM/COBOL and AcuCOBOL are interpreters rather than true compilers. Therefore at runtime, you must set the Registered application to run the compiler's RUNTIME rather than an EXE file. You must pass the name of the application to be run as a parameter to the runtime.
For example, for RM/COBOL you would set up an application named "smail" as shown in the example below (paths shown are for example only):
RM needs the trailing "a='" (Letter A, equal sign, single quote) to outsmart the runtime.
© 2000-2019 Norcom, all rights reserved |