|
PxPlus Simple Client-Server Interface |
|
This is a stripped down client-server interface that allows WindX workstations to connect to a host system. It provides more functionality than NTHost by using a single port and advanced security but less functionality than the Application Server. Due to the use of the ONESHOT functionality, a single port can be shared by multiple processes.
The simplified host/client server interface consists of the three programs explained below: *plus/cs/host, *plus/cs/client and *plus/cs/spawn.
This TCP port monitoring program runs on the server. Normally, this program will be launched from the Command line. Generally, this is initiated during system start-up.
Command Line:
pxplus.exe *plus\cs\host -arg portid[;options] [program]
Where:
|
|
portid |
This argument contains the Port ID to monitor. If the portid is not supplied, port 4093 is used. | ||||||
|
Additional options (separated by semi-colons) can be specified in the portid argument. If a secure server is required, you will need to include the SECURE=xxxxx option following the port id (separated by a semi-colon). Note:
|
|
Any server option that is valid for a TCP connection (see [TCP] Transmission Control Protocol) can be specified. Example: SECURE=/home/user/cert.pem;PRIVKEY=/home/user/privkey.pem;NOSSLV2;NOSSLV3;NOTLSV1 Additional options such as defining the ciphers and SSL protocols may be specified by setting the system environment variable PXP_CS_OPT. Any settings in the variable will be used when issuing the [TCP] OPEN command. Note:
| |
|
RECON=nn |
When provided, this option allows automatic client reconnection to the host in case of a disconnect. See Reconnect. The value in nn defines the number of seconds that the host will wait for a reconnect before forcibly terminating the session. (The auto-reconnection feature was added in PxPlus V11.) |
|
When a user connects and the USERKEYS option is present, PxPlus will get the key supplied from the *plus/cs/client ARG(1) value and compare it to the values in the Userkeys file for that User ID. A common key can also be provided under a * User ID in the Userkeys file. If the key matches, the connection will be allowed; otherwise, the user will be denied connection. On the host, the Userkeys file will be specified in the first ARG: pxplus.exe *plus/cs/host -arg 4093;userkeys=pathname Suppose that a Userkeys file called connectkeys is located at the following pathname: c:/pvx plus technologies/pxplusconnect/connectkeys connectkeys is a simple text file that might look something like this: User1=akey Where: User1 and User2 are the User ID values (returned from the WHO function) for two specific workstations. The command used to launch the host would be: pxplus.exe *plus/cs/host -arg '4093;userkeys='c:\pvx plus technologies\pxplusconnect/connectkeys' (The single quotes are necessary if the pathname contains spaces.) (The USERKEYS option was added in PxPlus 2019.) |
program
This optional argument, if supplied, defines the program to be run on the server whenever a user connects. If specified, the "program" parameter submitted with client (workstation) setup will be ignored and placed into %LPG_USER$.
If the server program (the one supplied on the *plus/cs/host Command line) wants to run the program requested by the client, it should issue a RUN "*plus/cs/host;FORCED_RUN". Otherwise, it may take whatever action it desires to complete the connection.
(Logic to allow forced programs to spawn sessions was added in PxPlus 2016.)
Example:
On Windows - To launch this program to monitor port 12345:
pxplus.exe *plus\cs\host -arg 12345
On UNIX/Linux - To launch this program to monitor port 4093, provide a 5 minute reconnect and run MySys:
./pxplus/pxplus "*plus/cs/host" -arg "4093;recon=300" MySys >/dev/null </dev/null
This client program will be run on each workstation to connect to the server. This program is normally run from the Command line.
Command Line:
pxplus.exe *plus\cs\client -arg server[;portid[;options]] [program]
Where:
|
server |
This argument defines the server TCP address. The server name can be either a recognized TCP host name or a TCP/IP address consisting of a "dotted quad" (e.g. 201.129.10.23). | |||||||
|
|
portid |
This argument defines the port number. If no port number is specified, port 4093 is assumed. | ||||||
|
|
options |
Additional options (separated by semi-colons) can be specified. (Support for additional options was added in PxPlus 2017.) If connecting to a secure server (one that has a SECURE=xxxxx option), you will need to include the keyword "SECURE" following the port id (separated by a semi-colon). Important Note:
|
|
Any client option that is valid for a TCP connection (see [TCP] Transmission Control Protocol) can be specified. Example: SECURE;CERTIFICATES=TRUST The system environment variable PXP_CS_OPT_CLIENT can be set on the workstation (client) to define additional options. Any settings in the variable will be used when issuing the [TCP] OPEN command. (Client-Server host security using the system environment variable PXP_CS_OPT_CLIENT was added in PxPlus 2016.) | |
|
PUBKEY=xxxxxxx |
Defines how to validate the server's public key. |
|
USERKEY=xxxxxxxxxxxx |
USERKEY value that will be checked against the Userkeys file that was specified by the host connection. This file will contain entries for each User ID and a key value that the workstation must supply on their *plus/cs/client connection. On the workstation, the USERKEY value will be specified in the first ARG: pxplus.exe *plus/cs/client -arg servername;4093;userkey=xxxxxxxxxxxx Referring back to the above Example where the host specified the connectkeys file, if the workstation belongs to User1, the command might look like this: pxplus.exe *plus/cs/client -arg servername;4093;userkey=akey Or if a common key is used for all users, the command might look like this: pxplus.exe *plus/cs/client -arg servername;4093;userkey=commonkey (The USERKEY option was added in PxPlus 2019.) |
program
This optional argument contains the program to run on the server, along with any associated Command line parameters and/or arguments. If this argument is not supplied, the client will be launched to standard Command mode.
Example:
pxplus.exe *plus\cs\client -arg MySrvr;12345 "*winstar -dr=c:\demo -arg main panel.en"
This example would connect to the *plus/cs/host program running on a server called MySrvr on port 12345. The host program would run program *winstar in the directory c:\demo with the ARG(1) = "main" and ARG(2) = "panel.en".
This utility program can be used to spawn additional sessions when running the PVX Plus Host/Client Server interface. The *TOOLS/HOSTTEST utility is used to test the *plus/cs/spawn interface.
Calling Sequence:
CALL "*plus/cs/spawn", cmd_line$, fid_id$, hideflag, INI_file$
Where:
|
|
cmd_line$ |
Program name and associated arguments to be launched in a separate session. |
|
|
fid_id$ |
FID to use in the launched task. Generally, this will be FID(0). By default, the launched task assumes the FID(0) value of the originating task. |
|
|
hideflag |
This parameter can be used to control whether the main window will be hidden on the launched task. If set to a non-zero value, the main window of the launched task will be hidden (minimized). Generally, you want to set this flag if you are launching a NOMADS application where the panel is a freestanding dialogue box. |
|
|
INI_file$ |
INI file to use on the WindX workstation when spawning the process. If omitted, the default INI file will be used. If an * (asterisk) is specified as the name of the INI_file$, the sub-routine will use the INI file for the current session. |
If desired, you can enable a session reconnect capability. This will allow workstations to reconnect to the server in case the connection is severed or dropped. To reconnect, the client session (WindX - CS/Client) must remain active. When the disconnection occurs, the workstation will attempt to reconnect automatically to the server. If the reconnect can be successfully completed with 10 seconds, the session will continue uninterrupted. If the reconnect takes longer than 10 seconds, the user will be informed that a reconnect is being attempted and given the opportunity to abandon the session.
To enable the reconnect capability, append ";recon=nnn" to the server *plus/cs/host first argument (the port number), where nnn is the number of seconds to allow the user to reconnect. See RECON= above.
During the reconnect time period, all session resources will remain intact, and the session will be released only if the reconnect timeout period is exceeded and the workstation has not reconnected. If the client can reconnect to the host but the host cannot find the task, the timeout is executed immediately.
To shut down all *plus/cs/host processes, you can either run ./pxplus/pxplus "*plus/cs/host;shutdown" or create the following file:
*plus/cs/shutdown
To shut down a specific server, create the following file where #### is the port number:
*plus/cs/shutdown.####
You can also shut down the *plus/cs/host process(es) by calling this program with the following format:
CALL "*plus/cs/host;shutdown",port#
Where:
You can specify the port# to shut down a specific server. If no port# is specified, the default is to shut down the *plus/cs/host process on port 4093. If 0 (zero) is specified as the port#, all host processes on all ports will shut down.
If you shut down the *plus/cs/host process(es) either by using a shutdown file or by calling "*plus/cs/host;shutdown",0, the process(es) will shut down once the next client connects and disconnects from them.
If you shut down a *plus/cs/host process by calling "*plus/cs/host;shutdown",port#, then it will shut down immediately.
The shutdown file will be deleted when the server is started again, making it possible to see who created the shutdown file to determine who terminated the host process.
If you run a *plus/cs/host process on Windows (not as a service), a button displays in the system tray to indicate it is running in the background. Hover the mouse pointer over this button to display a tooltip that includes the port number of the server. Right clicking on this button displays a different tooltip with an option to shut down the server, as well as see the port number and the number of PxPlus user slots currently occupied. If the host process is running in secure (HTTPS) mode, the tooltip shows ";secure" after the port number (e.g. Shutdown Simple CS Host (4093;secure / 4 users)). As an alternative, you can shut down the server by selecting the Terminate button in the minimized PxPlus window of the host process.
(The ability to shutdown specific host processes was added in PxPlus 2017.)
(The "secure" text in the tooltip was added in PxPlus 2023.)
The host sets the following global variables before running your application:
|
|
%PXPLUS_HOST$ |
IP address and port number of the host system |
|
|
%PXPLUS_NID$ |
Network ID (computer name) of the workstation (NID from local workstation) |
|
|
%PXPLUS_WHO$ |
User ID from the workstation (WHO from local workstation) |
The Simple Client Server can be installed and run as a Windows Service using either of the following two methods:
|
Location |
Method | ||||
|
From the PxPlus IDE Main Launcher |
Expand the Installation and Setup category and select Install Windows Services to launch the Install Windows Services interface. From the Type of Service drop box, select Simple Client Server. After entering the service settings in the grid, select the Install button. | ||||
|
From the Command line |
Enter the following: RUN "*plus/cs/service" PxPlus includes this special installation and monitoring program call that will confirm that you want to install the service and request the Starting Directory and Port Number to use:
To alter any of the settings or to remove the service from the system, simply run the program again. It will detect that the service is already installed and ask if you wish to delete it or modify its settings. | ||||
When installed, the system will default to Manual start. To have the service start automatically when the system is booted, you will need to go to your Windows Control Panel and change the start-up setting to Automatic.