 |
The Kerridge ToolSet DivisionUsing the Kerridge Service Administrator |
|
The Kerridge ToolSet DivisionUsing the Kerridge Service Administrator |
Before users can connect to KCML running on an NT server at least one listening service needs to be configured. The KCML listening service listens for KClient connections on the specified port. Once a connection is made the service then starts up a KCML process. The process will first prompt the user for a valid NT login/password before loading the application.
Once a service has been installed it is automatically installed the next time the system is booted.
Machine
Displays "Local Machine" if managing local services, otherwise the name of a
remote machine is displayed. Remote machines can be selected by clicking on the
browse button.
Kerridge Service
This area displays the details of any currently configured services. See below for a
description of each column.
Install
Installs the currently selected service. This will register the service so that it
is automatically started when the system boots up.
Uninstall
This will unregister the service so that it will not automatically start when the system
starts.
Start/Stop
This is used to stop and restart services. Stopping a listening service does not effect
currently running processes. However, stopping a "Running" process such as
a global library may effect any users who are accessing the library.
Add, Remove, Edit
Used to add, modify and remove services.
Events
Used to call up the NT event manager. This can be used to troubleshoot services that
fail to start.
Bkstat
Used to display the $PSTAT information for currently running processes.
| Name | This is the name give to the service. This name is only used by the Service Administrator to describe each service. |
| Status | This column displays the current status of the service. Not Installed Appears for a service that is not currently running and is not configured to start up automatically when the system starts. Not
running Running Listening |
| Port | This column displays the port number used by listening services. Normally a port number of 23 is used which is the standard for TCP/IP telnet connections. |
| Service Provider | Normally KCML for listening services and global libraries. Other KCML services include "LicServer" for the WKCML licence server, "ODBC" for the KISAM ODBC server and "KPrint" for the Kerridge print manager. |
| Command Line | Displays the default command line for the service. Normally this would contain the start-up program name. Global libraries must have a -G flag before the program name. |
At least one regular listening service is required to allow Client PC's to execute a KCML on the server. To install a new listening service click on the "Add ..." button and the following dialog is displayed.
Name
Specifies the name of the service. The name has no effect on the service itself it
is used only as an administrators description.
Service Provider
Specifies the type of service. A regular KCML listening service only ever uses the
KCML service provider. Other services include:
| LicServer | LicServer is used by the WKCML product to restrict users access to the KCML software. When installing onto a Windows 95 PC, the licence server program is executed as a normal program and appears in the system tray on the PC. On NT the dongle must be connected to the PC running this service, the WKCML software must also reside on the same machine. When configuring this service there is no need to specify a command line. The connection type shuld also be set to "Direct" |
| ODBC | This service is only available if the KISAM ODBC Server for Windows NT has been installed. |
| KPrint | This service is only available if the Kerridge Print Manager software has been installed. |
Command Line
Specifies the full path name of the program to be started when a connection is made.
Other standard KCML command line options may also be specified before the program
name. If no program name is specified then clients connecting to the service will be
taken straight into the KCML editor.
Connection
For a regular listening service this should always be set to "Listen".
Ideally the port number should be set to 23 which is the default port number used by
telnet connections from client PC's. A port number other than 23 must be specified
by the client when making a connection. When using KClient the port number can be
specified after the hostname by separating the two with a comma.
The above example would install a KCML listening service on the standard telnet port (port 23), which would start the program "C:/MainApp/PROGS/Startup".
Once the service has been added to the list, the install option is used to physically start the service. Once the service has been installed it is then registered so that it will automatically get started the next time the system is booted.
A global library service is added in the same way as the regular listening service. The difference being that the command line option -G must be specified to signify that the program is to be loaded as a global library. Global libraries are not started as a listening service hence a connection type of "Direct" must be set.
Note that the global program must contain a DEFFN @PART statement to specify the actual name of the library.
Once the service has been added to the list, the install option is used to physically start the service. Once the service has been installed it is then registered so that it will automatically get started the next time the system is booted.
The following example would install a KCML global library.
Multiple listening services can be started on the NT server by using different port numbers. Multiple listening services are only required if you need to provide access to different applications. Generally port number above 1000 are available for general use, however you should check your services set-up before allocating new numbers. The services configuration on NT 4 can generally be found in the file \WINNT4\system32\drivers\etc\services file, however this may very between systems.
Services can be temporarily stopped and restarted if necessary. This is particularly useful for global libraries as changes made to library programs will not come into effect until the library is restarted. However, you should make sure that all users that are likely to attach to the global library are logged out before the service is stopped. Failure to do this may cause problems for users that are attached to the global at the time it was stopped.
Regular listening services can be stopped to prevent users from logging in to the application. Stopping a regular listening service will not effect any current KCML processes.
The Kerridge Server Administrator can also be used to maintain services on a remote server. Currently remote server administration can only be performed from an another NT 4 Server/Workstation, the administrator must also had "Administrator" rights on the remote server.
To remotely mange KCML servers, run the Kerridge Server Administrator. Click on the "Browse" button next to where the "Machine" name is displayed (the machine name would normally display "Local Machine", for this machine.). Next enter the name of the remote server, you should now see a list of KCML services for that machine.
If a service fails to start the reason can be found by running the NT Event viewer. This can be called directly by clicking on the "Events" button within the Kerridge Server Administrator.