The configuration files that Silk Meter servers and clients rely on are listed below.
This file is located in the SilkMeter\bin directory.
Thus is the configuration file for Silk Meter Proxy Service. To activate changes, first stop Silk Meter Proxy Service, make your changes, and then restart Silk Meter Proxy Service again. Silk Meter Proxy Service handles all incoming requests, forwards requests that are synchronized with and are performed in the Silk Meter Core process, and then provides response data to clients. This file also monitors the health of the Core process and, when required, restarts the Core process.
Structure of the config.xml:
<SMPSettings>
<Server>
<BindTo></BindTo>
<Port>0</Port>
<MultihomedMode>true</MultihomedMode>
<Threads>100</Threads>
<VerboseLevel>0</VerboseLevel>
<VerboseFile>smSystemDebug.log</VerboseFile>
</Server>
<Log>
<WebPort>19462</WebPort>
<Refresh>20</Refresh>
<Extended>false</Extended>
<ClientName>false</ClientName>
<DebugFile></DebugFile>
<DebugMsgListLen>100000</DebugMsgListLen>
<ClosedConnListLen>1000</ClosedConnListLen>
</Log>
<Settings>
<Timeout>15000</Timeout>
<HandleLimit>0</HandleLimit>
<VMLimit>419430400</VMLimit>
<KeepAlive>
<Time>100000</Time>
<Interval>0</Interval>
</KeepAlive>
</Settings>
</SMPSettings>
Server:
BindTo: Enables the binding of Silk Meter server listening to a specific IP address. When this parameter is not specified, Silk Meter listens on all available IP addresses.
Port: Enables changing of the listening port. When this parameter is set to 0, Silk Meter listens on the default port 5461.
MultihomedMode: Set this property to true if the license server has different network adapters enabled and connected.
Threads: Configures how many different threads are used for incoming requests. Default is 100.
VerboseLevel: Specifies the debug level for logging. If set to 0, nothing is logged.
VerboseFile: The name of the debug file. Default is "smSystemDebug.log".
Log:
WebPort: Configures the listening port of the Status Web interface. When this parameter is set to 0, no Web interface is available. Default is 19462.
Refresh: Specifies the refresh interval of the Status Web interface. When this parameter is set to 0, the page does not automatically refresh.
Extended: When set to true, additional extended logging information is collected.
ClientName: When set to true, the client names instead of client IP addresses are logged: Default is false.
ClosedConnListLen: Size of the history for closed connections. Default is 1000.
Settings:
Timeout: Specifies the amount of time that a request may reside in the pending state, in milliseconds. When the specified value is exceeded, all connections are closed and the Silk Meter Core is re-initialized. Default is 15000.
HandleLimit: Specifies the number of threads that the license server process may open. When the specified value is exceeded, all connections are closed and the Silk Meter Core is re-initialized. Default is 0, which means that the handles are not being checked.
VMLimit: Specifies the virtual memory that the license server process may consume in bytes. When the specified value is exceeded, all connections are closed and the Silk Meter Core is re-initialized. Default is 419430400 bytes.
KeepAlive:
Time: Specifies the TCP keep-alive time of all connections in milliseconds. Each time the keep-alive timer expires, the connection is probed to determine if the client is still accessible. If it is not accessible (i.e., the connection has been broken), the connection is closed and all associated licenses are released. Default is 100000.
Interval: Do not change this setting.
This file is located in the cfg directory.
Usually only the setting that determines if Silk Meter is configured for server or standalone mode is set in this file. Either the line run_standalone=true or run_standalone=false is included.
This setting is updated each time a user changes the mode using either Silk Meter Policy Administrator, command line tool (smCmdTool.exe), or Client Admin Tool.
This file is located in the cfg directory.
This file only has one line, which provides the ORB connection setting for Silk Meter Manager. This file is only used when Silk Meter is not configured for standalone mode. This setting must be set the same as is specified in the other two *.ref files.
line: IIOP://hostname:port/ls_segue
hostname: Name of the machine where Silk Meter server runs (or localhost)
port: Port number on which Silk Meter server listens for requests. This must be the same port number as is used in the server’s config.xml file.
This file is located in the cfg directory.
This file only has one line, which provides the ORB connection setting for Silk Meter Licensing service (This service runs in the same process as Silk Meter Manager). This file is only used when Silk Meter is not configured for standalone mode. The setting must be the same as is specified in the other two *.ref files.
line: IIOP://hostname:port/CosLicensingService
hostname: Name of the machine where Silk Meter server runs (or localhost)
port: Port number on which Silk Meter server listens for requests. This must be the same as is specified in the config.xml file on the server.
This file is located in the cfg directory.
This file only has one line, which provides the ORB connection setting for Silk Meter Property service (This service runs in the same process as Silk Meter Manager). This file is only used when Silk Meter is not configured for standalone mode. The setting must be the same as is specified in the other two *.ref files.
line: IIOP://hostname:port/CosPropertyService
hostname: Name of the machine where Silk Meter server is runs (or localhost)
port: Port number on which Silk Meter server listens for requests. This must be the same as is specified in the config.xml file on the server.