The Socket API registry key contains these values:
Type: REG_DWORD
Data: Defaults to 8538. This registry value specifies which port number the Socket API listens on for data sent by applications using the Contiguous protocol. The Milter MTA agent uses this protocol and hence this port. If this port is not used, you can set this value to zero to conserve machine resources.
Type: REG_DWORD
Data: Defaults to 8539. This registry value specifies which port number the Socket API listens on for data sent by applications using the Interlaced protocol. The Network Boundary Agent uses this port and hence this port. If this port is not used, you can set this value to zero to conserve machine resources.
Type: REG_DWORD
Data: Specifies whether to generate External Agent Request diagnostic messages in the folder specified by DiagnosticFolder (see below). If set to:
0 Messages are never generated.
1 Messages are always generated.
2 Messages are only generated on error.
Type: REG_DWORD
Data: Specifies whether to generate External Agent Response diagnostic messages in the folder specified by DiagnosticFolder (see below). If set to:
0 Messages are never generated.
1 Messages are always generated.
2 Messages are only generated on error.
Type: REG_SZ
Data: Specifies the path and folder where External Agent Request and Response diagnostic messages will be saved. The creation of these messages is determined by the CreateEARsp and CreateEAReq registry values.
Note: This folder is not created automatically.
Type: REG_DWORD
Data: Defaults to 800. This registry value specifies the minimum level of free disk space (in MB) on the on the Socket API host machine. If free disk space falls to this level, and while it remains below this level, the Socket API rejects all further messages passed to it.
Note: This registry value refers to free disk space on the drive hosting Windows temporary files.
Type: REG_DWORD
Data: Defaults to 1024. This registry value specifies the level of free disk space (in MB) on the Socket API host machine that triggers a change in how messages are processed.
If free disk space falls below this threshold, the Socket API applies ‘wait throttling’ or ‘fail throttling’, depending on whether messages were captured by a Milter MTA agent or the NBA.
Note: This registry value refers to free disk space on the drive hosting Windows temporary files.
Type: REG_DWORD
Data: Defaults to 1, indicating the Socket API is connecting to a local PE hub. You do not need to change this registry value.
This registry value is only created on machines hosting the External Agent, Socket API and a Remote Policy Engine Connector (that is, a hub).
Type: REG_DWORD
Data: Defaults to 1, indicating the Socket API is connecting to a local policy engine. You do not need to change this registry value.
This registry value is only created on machines hosting a policy engine and the Socket API.
Type: REG_DWORD
Data: Defaults to 60. Specifies the maximum number of items that can be queued by the Socket API while they await processing by a policy engine.
We recommend that you set this value to 12 times the total concurrency for all policy engines (if using a hub) or simply 12 times the concurrency of the local policy engine.
Policy engine concurrency is defined by the Maximum Number of Concurrent Operations setting in each PE’s machine policy. This policy setting sets the maximum number of events that can be processed simultaneously by a policy engine. It prevents a performance slowdown if a policy engine is heavily loaded.
Type: REG_DWORD
Data: Defaults to 2. This determines the level of logging for message processing. For example, you can configure the Socket API to only log errors or important system messages.
Log entries are written to WgnSAgent_<date>.log where <date> is the date and time when the log file was created. The supported logging levels are:
1 Errors only
2 Errors and warnings
3 As 2, plus informational and status messages
Note: Setting LogLevel=3 will cause the log file to grow extremely rapidly. This level of logging is provided for testing purposes only.
Type: REG_DWORD
Data: Defaults to 10. This specifies the maximum number of log files. When the maximum number of log files exists and the maximum size of the latest is reached (see below), the oldest log file is deleted to enable a new one to be created.
Type: REG_DWORD
Data: Defaults to 1,000,000. This specifies the maximum size (in bytes) for each log file. When the current log file reaches its maximum size, the email server agent creates a new log file. Log entries are written to WgnSAgent_<date>.log; see above.
Type: REG_DWORD
Data: Defaults to 300. This registry value specifies the level of memory usage (in MB) on the Socket API host machine that triggers a change in how messages are processed.
If memory usage rises above this threshold, the Socket API applies ‘wait throttling’ or ‘fail throttling’, depending on whether messages were captured by a Milter MTA agent or the NBA.
Type: REG_DWORD
Data: Defaults to 400. This registry value specifies the maximum level of memory (in MB) used by the Socket API. If memory usage rises to this level, and while it remains above this level, the Socket API rejects all further messages passed to it.
Type: REG_DWORD
Data: Defaults to 180. This registry value specifies how long the Socket API waits (in seconds) before rejecting a message. This timeout applies to:
We recommend that you do not shorten this timeout (for example, do not reduce it to less than three minutes) because this may adversely affect performance.
Note: The Socket API checks an email’s progress (in terms of policy processing or the arrival of its constituent parts) every 10 seconds.
Type: REG_DWORD
Data: Defaults to 0. Enables administrators to update the Socket API configuration. Set to 1 to force the Socket API to re-read the registry. When it has accepted the changes, it automatically resets this value to 0.
If a registry value has been updated with invalid data, UpdateConfig is set to 2; the new value is discarded and an entry written to the log.
|
Copyright © 2014 CA.
All rights reserved.
|
|