SPO Section
The SPO section contains the parameters that supply the global default for the OpenROAD Server Pooler. These parameters are described as follows.
Note: Any changes to these parameters require the SPO to be stopped and restarted.
Maximum Dispatchers
Specifies the maximum number of dispatchers that can be started in the SPO
Default: 48
Maximum Total Slaves
Specifies the maximum number of slaves that can be started in the SPO
Default: 48
Note: A dispatcher can be configured to control more than one slave. If this is done, the dispatcher will attempt to reserve the maximum number of slaves when it is created. This could exhaust the value specified in this resource even if not all slaves have been started. Ensure that the value for this parameter is set to the maximum number of slaves that can be started by all dispatchers.
Purge Interval
Specifies the interval that ASOs will be checked to see if they need to be released. An ASO will be released if the client reference count reaches zero and this interval has expired.
Default: 1 minute
Shutdown Grace Period
Specifies the period that the SPO will wait before continuing with a shutdown request. This period should give any active ASO request time to complete before continuing with the shutdown. After this value expires, all ASOs will be forced to shut down regardless of the status of any active request.
Default: 15 seconds
Run Authorized Apps Only
Specifies whether dispatchers are restricted to run only authorized image files. An image file is considered to be authorized by registering it with the Server Manager. (ASOLib does not need to be used in the application.) This is intended to prevent unauthorized image files from being launched as ASO slaves by the SPO. If this parameter is set to YES, the SPO will create a dispatcher only if the ImageFile parameter of the Initiate has been predefined through the Server Manager.
Default: NO
Restricted ASO Log Path
Specifies whether the full path defined in the -L parameter of the signature should be used. If this parameter is set to YES, the file name is extracted from the -L parameter and the file is created in the default location for Ingres LOG (II_LOG, II_FILES, or %II_SYSTEM%\ingres\files).
Default: NO
Use Application Signature Names (ASNs)
The signature of an OpenROAD Server application uniquely identifies an ASO configuration for the purposes of pooling shared ASO instances. The full signature is actually a concatenation of the ImgFile and CmdFlags parameters that were passed to the Initiate method. For each unique signature that the SPO encounters, a separate dispatcher instance is created to manage the pool of (one or more) shared slaves assigned to that signature. All clients that call Initiate with the same signature are assigned to the same dispatcher and share the same pool of slaves.
The configuration of a dispatcher (such as the number of slaves, timeout period, transaction limit, and so on) is controlled by the registry at two levels. First there are global defaults. Then there are per-signature overrides that apply to specific dispatchers. Therefore, all signatures that share the same image name also share the same dispatcher configuration options.
So the image name is already used as a registry key to control dispatcher configuration options. The application signature name concept just abstracts that one step further, and takes full advantage of a level of indirection through the registry. When a client passes an application signature as the ImgFile parameter on the Initiate method, that application signature is interpreted as a unique key with which all the information needed to configure a dispatcher and configure the ASOs can be obtained from the registry. Moreover, that registry key provides a place to put new ASO configuration options, such as environment variables. This allows different ASO instances under a single SPO to have different environment settings.
To prevent any risk of changing behavior for existing installations, the application signature name feature will remain dormant unless the Server Manager adds a new registry value under the Server Config key. If the “UseSignatureGUIDs” registry exists and is a nonzero REG_DWORD, then the new behavior will be activated.
After the feature is activated, if the ImgFile string passed on an Initiate call begins with a curly brace “{”, then that string is interpreted as an ASN and not a real image name. This ASN string is then used as a subkey of Dispatcher Config to obtain the “real” ImgFile and “real” CmdFlags strings. (Any CmdFlags passed on the Initiate by the client are ignored in this case.) Furthermore, if the ASN key has an “Environment” subkey, then all the environment variables specified there will be set before the Initiate call is passed to OpenROAD runtime. The Server Manager can be used to set up this section.
This change is transparent to the SPO. The SPO treats an ASN ImgFile string just like any other ImgFile string. All the transformation happens inside the ASO, and applies the same way for private and shared ASOs.