1. Silent Installations and PI SDK Redistribution


KST Initialization File Syntax

The pisdk.msi may be distributed with a modified command line that allows populating the KST with a predefined set of PI Servers during installation. This command line option requires an initialization file, typically referred to as KST.ini. A KST.ini file may be generated by export from the Tools menu of the PISDK Utility. Additionally, the syntax for defining PI Servers in the KST initialization file is described below.

The KST initialization file must contain at least two sections:

[NUM_SERVERS]
NUM = ##

which defines the number of server entries defined in the KST .ini file.

[PI_SERVER]
# = ServerName

where "#" is a number which defines the server name for entry number "#" in the KST .ini file. These numbers do not define the sorted order of the KST (that is ordered alphabetically), but are merely a set of sequential numbers for the list in the KST .ini file. The following optional sections and arguments can be defined for any of the servers that are to be created during the installation:

[PI_PATH]
# = ServerPath.osi.com ; defaults to ServerName
[PI_PORT]
# = 5450 ; defaults to 5450 for PI3; 545 for PI2
[PI_USER]
# = piadmin ; defaults to pidemo
[PI_DEFAULT_SERVER]
# = TRUE ; should only be one server which is default
[PI_SERVER_ID]
# = xxxxxxxxxx ; not needed
[PI_TYPE]
# = 3 ; defaults to PI3 (2, 3, PI2, or PI3 allowed)

An example of the syntax usage for the KST .ini file can also be found in the silent.ini file for additional reference.

Enabling Operational Intelligence