Integer; number of seconds. The default is 60.
The frequency with which the MPX Cache Agent compares its cache size to the configured cache limit (MaxCacheSize). When the total cache size exceeds the configured limit, least-recently-used files are removed from the cache until the cache size is under the configured limit.
Minimum value is zero, which disables the feature.
Path. The default is "/MPXCacheAgent/Cache".
The root folder of the MPX Cache Agent's local cache. Cached files are stored in compressed, encrypted format within subfolders of this path.
As files are requested from the Root MPX Cache Agent either by “downstream” MPX Cache Agents or by clients, they are compressed, encrypted, and stored in a folder tree rooted at the specified directory. The local cache makes secondary file access faster, and it removes I/O contention with files in the server configuration’s vault.
The Root MPX Cache Agent uses the StarTeam Server configuration’s cache.
Specifies the type of information that will be cached by the MPX Cache Agent. If this group is not specified, the MPX Cache Agent caches file contents only.
A valid object type such as Change, File, Folder, Requirement, Task, Topic or the name of a Custom Component created for this installation. The special entry $CustomComponent$ can also be used.
Caching File objects means that artifact properties are cached, which is independent from caching file content.
The $CustomComponent$ setting is used to cache all custom components, including new ones added while the server is running. This can be used instead of adding separate entries for each custom component created, which would require restarting the MPX Cache Agent.
Comma-separated list of IP addresses. By default, the MPX Cache Agent uses a list of its machine's IP addresses.
Returned by the MPX Cache Agent in "poll" responses, this list also appears as the "Inbound Addresses" value on the MPX Cache Agent's status page.
In cases where some addresses should be hidden from clients (for example, they are not routable) or the MPX Cache Agent has additional addresses that should be presented to clients (for example, an additional address assigned by a firewall's NAT), this option can be used to control exactly what list is presented to clients.
Integer; number of connections. The default is 10. The range is from 1 to MaxConnections.
The initial number of request handler threads launched when the MPX Cache Agent starts. Additional request handler threads are launched, up to MaxConnections, as needed when all current threads are dedicated to active connections.
Comma-separated list of IP addresses. By default, the MPX Cache Agent binds to the "system" address (IPADDR_ANY), which allows it to receive connections from all available physical (for example, NIC) and logical (for example, VPN) IP addresses.
This list allows you to control the exact set of IP addresses with which the MPX Cache Agent will listen for inbound connections. This list must contain only IP addresses that are valid for the current host and/or the loopback address (127.0.0.1) that allows connections only from the local host.
Unless the InboundAddresses value is specified, the addresses provided in this option are used in poll requests and displayed in the "Inbound Addresses" value on the MPX Cache Agent's status page.
Integer; number of bytes. The default is 1000000000. The range is 0 to approximately 8 exabytes.
The maximum size of the MPX Cache Agent's cache in bytes. If this value is zero, the cache size will not be constrained. Otherwise, files are periodically deleted on a least-recently-used basis to maintain the specified size.
The actual total size of the cache may rise above this value momentarily while new files are received.
Integer; number of bytes. The default is 100MB. The range is 0 to 263-1.
For a Root MPX Cache Agent, this parameter constrains the maximum number of files returned in a catch-up request. For a Remote MPX Cache Agent, this parameter constraints the maximum number of files requested in a catch-up request. In both cases, the value is the total size in bytes of the files in the catch-up operation. If this value is 0, the catch-up request is unconstrained. In a given catch-up operation, the smaller of the requester's and the requestee's MaxCatchupSize is used to constrain the operation.
Integer; number of connections. The default is 100. The range is 1 to 1000.
The maximum number of simultaneous connections that the MPX Cache Agent will accept. This value controls the maximum number of request handler threads used by the MPX Cache Agent. If all request handler threads have been started and are in use when a new connection is received, it is queued until a request handler becomes available.
A larger value than the default could be used in highly concurrent environments, at a cost of more memory and potentially more demand on the MPX Cache Agent. A smaller number is generally unnecessary. The maximum is limited by OS/process issues.
Required group. A group for specifying Message Broker parameters. Minimally, a MPX Cache Agent's MessageBroker group should contain the <Name> tag and a value for the server_names parameter.
The <Name> property in the <MessageBroker> section indicates what type of messaging will be used with this configuration:
A Remote MPX Cache Agent uses a Message Broker connection to receive file content messages from the content source(s) that it is monitoring. It also uses the Message Broker connection if is a “public” MPX Cache Agent that will respond to poll messages. (See SharePolicy.)
Defines the publish/subscribe messaging service to be used by the MPX Cache Agent in the format tcp:host:port.
The default is the value “_node” which is equivalent to “localhost”. To use the default, the Message Broker must be on the same computer as the MPX Cache Agent.
host must be the name or IP address of the Message Broker computer, and port must be the port number with which the Message Broker is receiving connections (61616 by default). Example: tcp:MBServer1:5101.
Integer. Number of seconds. The default is 10.
Specifies the interval between attempts to reconnect to the Message Broker.
Integer. Number of seconds. The default is 5.
Controls how long in seconds the Event Transmitter, MPX Cache Agent, or StarTeam client waits to connect to the Message Broker before giving up. The default is good for most environments. Minimum value is zero, which disables the feature.
The maximum amount of memory in bytes that will be used for memory caching. When enabled, most-recently-used cached objects are buffered in memory. A value of 0 disables memory caching. If this value is not specified, the default value is 100MB. This value appears as Memory Cache Max Size (bytes) on the MPX Cache Agent’s status page.
The maximum size of an object that will be cached in memory. When memory caching is enabled, only new and recently accessed objects at or below this size in bytes will be memory cached. If this value is not specified, the default value is 10KB. This value appears as Memory Cache Max Object Size (bytes) on the MPX Cache Agent’s status page.
Integer; port number. The default is 5201. The range is 1 to 65535.
The port number with which the MPX Cache Agent receives requests. The port number cannot be in use by any other process on the same host.
Integer; number of seconds. The default is 30.
Specifies the time which a MPX Cache Agent will wait to read the next request from a client before passively closing the corresponding connection. When the connection is closed, the request handler thread is freed-up to service other connections.
Minimum value is zero, which disables the feature.
Public or Private. The default is Public.
Indicates whether or not this MPX Cache Agent advertises the server GUIDs for which it is caching data. A cache-aware MPX client can broadcast a "poll" request to look for MPX Cache Agents that are caching data for a specific StarTeam Server GUID. Public MPX Cache Agents will respond to such requests when they are caching the requested server's content, but private MPX Cache Agents will not.