Server Configuration Keywords
The PL/B Application Server program information file (PLBSERVE.INI) file contains information that allows the user to tailor the runtime.
The .ini file name processing occurs as follows:
The runtime qualifies and uses an INI file when the file contains any section header. A section header is an INI file record that starts with '[' and is terminated with a ']'.
The runtime looks for and uses an INI filename found in three possible directories. The runtime always processes the INI files in the same order giving the user the ability to override globally defined parameters. The file name searching is as follows:
First, the runtime looks for an INI filename in the current working directory. This allows someone doing very specific and local program execution using keyword controls that override default keyword controls specified in (b) or (c) below.
Second, the runtime looks for an INI filename in the current user Windows directory. If the INI filename is found, it becomes the local keyword controls for the runtime. This allows someone to define workstation INI file controls. The local INI file controls can override (c) below.
Third, the runtime looks for an INI filename in the directory where PLBSERVE.EXE is found. If the INI filename is found, it becomes the global (default) keyword controls for the runtime.
If the runtime is started without using the '-i' option, the runtime looks for the default INI file named 'PLBSERVE.INI' in the three possible areas. Any PLBSERVE.INI files found in the three directories are then used to locate requested INI file keywords in the order as described in (B).
If the runtime is started with the '-i' option being specified and the INI file name does not have a path specified, the runtime looks for the INI file name in the three possible directories defined in (B) above. The runtime only processes the user named INI file from the three directories defined in (b.) above. This means the 'PLBSERVE.INI' is NOT used in this case.
If the runtime is started with the '-i' option being specified and the INI file name does have a path specified, the runtime looks for and uses the single specified INI file if found. This case disables the runtime from processing multiple INI files as described in (B) above.
Keywords with an associated value are placed in sections. The sections are indicated by surrounding the section name with square brackets. The [version] and [environment] sections are required and at a minimum should contain the following keywords and values:
[version]
Plbserve=10.7
[environment]
PLB_PATH=regular pathing information
PLBCS_PORTNUM=3933
PLBCS_LOGNAME=PLBSERVE.log
PLBCS_HOSTNAME=aaa.bbb.ccc.ddd
PLBCS_LOCALIP=aaa.bbb.ccc.ddd
Within the [environment] section, the user may specify additional runtime keywords as documented in the PLBWIN Runtime Keywords topic of the PL/B Runtime Reference. Additional keywords of interest to PL/B Application Server users are the following:
|
Keyword |
Specifies the ... |
|
PLB_<keyword> |
A PL/B runtime keyword. See the Sunbelt PL/B Runtime Reference for a full list of keywords. |
|
optional authorization number. | |
|
animation file caching method. | |
|
icon file caching method. | |
|
picture file caching method. | |
|
sound file caching method. | |
|
optional event checking time period. | |
|
optional default current working directory. | |
|
optional error locking timeout value. | |
|
optional CE client behavior modification. | |
|
required host name or IP address. | |
|
required host name or IP address in ipv6 format. | |
|
IP filter for client connections. | |
|
optional client access control information. | |
|
optional local IP address. | |
|
optional local IP address in ipv6 format. | |
|
optional maximum log file size. | |
|
optional server log file name. | |
|
optional key used to encrypt log on identifications to and from all PLBCLIENT workstations. | |
|
optional key used to define the maximum log file record length. | |
|
optional key used to enable variable length log records. | |
|
optional keyword that limits the client virtual memory size. | |
|
optional keyword that limits the number of simultaneous PLBCLIENT users. | |
|
optional maximum buffer size used when the server task communicates with the client | |
|
optional checkpoint monitoring function. | |
|
optional prevention of sending default object names to the client in a FORMLOAD. | |
|
required IP port number to use. | |
|
optional key used to encrypt messages to and from all PLBCLIENT workstations. | |
|
optional maximum time allowed to detect a child recovery action | |
|
optional maximum time allowed where no messages are received from the server. | |
|
optional block size used when the server is sending a large amount of data to a client. | |
|
optionally restricts the socket recovery when a socket error occurs. | |
|
optional number of seconds to wait during a server shutdown before clients are forced off. | |
|
assignment of virtual memory. | |
|
optional main window of the client is to be hidden. |
Admin Access Keywords
|
Keyword |
Specifies the ... |
|
optional data items kept by the administrative task. | |
|
optional data items kept by the administrative task. | |
|
optional administrative task host name. | |
|
optional administrative task host name or address in ipv6 format.. | |
|
optional administrative task IP filtering file name. | |
|
optional administrative task logon key file name. | |
|
ability of an ADMLOGON instruction to connect to the administrative server task using the 'local' I/P address. | |
|
optional administrative task logging of a child task. | |
|
optional administrative task logging level of a child task. | |
|
optional administrative task logon encryption key that is used as the default LOGON key in a PL/B ADMLOGON instruction. | |
|
Enable or disable administrative emails | |
|
Defines the administrative email outgoing mail server | |
|
Configures the administrative email receipients | |
|
Defines the administrative email sender | |
|
Triggers an email when the maximum users has been reached. | |
|
Sends an email when the Application Server has been started. | |
|
Sends an email when the Application Server has been stopped. | |
|
Defines the subject of the administrative emails. | |
|
Defines the blind carbon copy recipients of the administrative email. | |
|
Defines the carbon copy recipients of the administrative email. | |
|
Configure the user login for the email server. | |
|
Configures the user password for the email server | |
|
Defines the port for the email server. | |
|
Enables SSL for the email server. | |
|
Enables TLS for the email server. | |
|
Defines a timeout value when communicating with the email server. | |
|
Provides debug tracing via email. | |
|
Provides debug tracing via email. | |
|
Provides delivery confirmation of the administrative emails. | |
|
Reports receipt of the administrative emails. | |
|
Defines the administrative email return address. | |
|
Defines the administrative email Reply To address | |
|
ability to log in to the administrative services of the server via the PLBCS_PORTNUM port. | |
|
optional administrative task port number. | |
|
optional administrative task public encryption key. | |
|
optional optional display in the Windows taskbar icon area. | |
|
optional descriptive server name string. | |
|
optional administrative task control value. |
To allow simultaneous support of normal Windows and CE Windows PLBCLIENTs, the PLBSERVE.INI may have specialized sections named to support CE and non-CE clients. The PLBSERVE.INI sections can be named as follows:
[environment]
This section contains the basic startup keywords required to specify the TCP/IP communication parameters to access the PL/B program server. This section also includes the required runtime keywords required (PLB_TERM, PLB_PATH, etc) to execute a program for a normal Windows PLBCLIENT.
[env_wincepk]
This section contains specific keywords required (PLB_TERM, PLB_PATH, etc) to execute a program for a Windows CE Pocket PC PLBCLIENT executable. This allows a user to setup specialized programs, screen definition files, and pathing to support Windows CE PL/B applications. Also, notice that this section DOES NOT include the TCP/IP communications keywords. In addition to normal runtime program supported keywords, the following PLBSERVE keywords can be included in this section:
PLBCS_CHECKTIME
PLBCS_WINHIDE
PLBCS_MSGBUFFSIZE
PLBCS_LOGNAME
[env_console]
This section contains specific keywords required (PLB_TERM, PLB_PATH, etc) to execute a program for a Windows PLBCLICON executable. This allows a user to setup specialized programs, screen definition files, and pathing to support Windows console applications. In addition to normal runtime program supported keywords, the following PLBSERVE keywords can be included in this section:
PLBCS_CHECKTIME
PLBCS_WINHIDE
PLBCS_MSGBUFFSIZE
PLBCS_LOGNAME
[env_child]
This section contains user-defined keywords that are searched if not found in the user specific INI file.
[mapdrives]
This section contains the mapped drive assignments. The PLBSERVE runtime uses the mapped drive settings to redirect either network drives or local DOS drives.
Format:
{drv}:=[~]{redir}[,{username},{password}]
Where:
Notes:
1. When the {redir} string starts with the '\' character, it identifies a network UNC path name. In this case, the {drv} is redirected as a network drive. If the {drv} already exists, the mapped drive redirection does not occur and no changes are made.
2. When the {redir} string is a DOS drive path string, the mapped drive redirection is executed as a local DOS drive device. If the {drv} already exists, the mapped drive redirection does not occur and no changes are made. The local DOS drive substitution is not supported for the Windows 95, 98, and ME OS versions. The mapped drives are ignored for these Windows versions.
3. The mapped drives redirection support can declare drive specifications when an NT service is started. This is the original intended use for mapped drives.
4. By default, the runtime removes the {drv} mapped drive when the runtime process is terminated. If the '~' character is specified as the leading character before the {redir} string, the runtime does not remove the {drv} when the runtime process is terminated.
5. The {username} and {password} exist as raw text strings. Care should be taken to protect the ini file from unauthorized access since the user name and password are stored in plane text. Limited access to an Application Server or Data Manager should be considered when the {username} and {password} parameters are used.
6. When the application server starts and terminates, the mapped drives are logged.
Example:
[mapdrives]
f:=c:\temp
g:=\\server\sharename\directory
h:=~c:\sunbelt
i:=~\\server\sharename\directory
j:=\\server\sharename\directory;myname;mypassword
See Also: PL/B Client Configuration Keywords
![]() |