Changing preferences for the TMTM Configuration Agent

The TMTM Configuration Agent uses a set of default preferences that permit it to run immediately. The default behavior is to:

  • Write configuration files to MQS_HOME/ExtensionConfig (where MQS_HOME is a variable set in your environment).
  • Use automatic deployment via an HTTP connection to the TMTM Application Service

You can change the TMTM Configuration Agent preferences using the agentpref tool provided as part of the agent distribution. See also Defining policies.

The following table lists the TMTM Configuration Agent preferences. To list these preferences, use the following command: agentpref --list-preferences

Preference

Value

Default

ASHost

For auto deployment. The host where the TMTM Application Service runs.

The TMTM Application Service normally resides on the same host as the TMTM Topic Service so the TMTM Configuration Agent uses the TMTM Topic Service setting.

When you configure the agent to connect to the TMTM Topic Service using agentpref, the TMTM Configuration Agent begins automatic deployments.

ASPort

For auto deployment. The port where the TMTM Application Service runs.

The default TMTM Application Service port is 15007. Ensure that no firewalls between the agent and TMTM Application Service host are blocking this port.

ASSecure

For auto deployment. Connects to the TMTM Application Service using a secure (HTTPS) connection. See Post core component installation and configuration.

False.

BatchInterval

How often BTM extensions publish updates.

30 seconds.

ChangeConfigDirectoryTo

Instructs the TMTM Configuration Agent to change the directory to which it writes configurations. If configurations exist, they are moved to this location. If the agent is not running, they are moved when it starts. The agent removes this preference when the change is processed.

Not applicable.

ConfigInterval

Configures the interval, in seconds, used by monitoring extensions to check for configuration changes.

60 seconds.

DeploymentInterval

Configures the interval, in seconds, used to check the deployment source for changes.

60 seconds.

DeploySourceDirectory

For manual deployments. The directory from which the TMTM Configuration Agent reads deployments.

If this preference is not set, the TMTM Configuration Agent automatically reads deployments from the TMTM Application Service.

If this preference is set, the agent processes manual deployments, and preferences for auto deployment are ignored.

Remove this preference to revert to automatic deployments.

MSPassword

For auto deployment. The password used to connect to the media repository of the TMTM Application Service.

A default password is used.

MSRetries

Number of retry attempts made when accessing media.

3

MSRetryInterval

Interval between retry attempts.

1 second.

MSUser

For auto deployment. The username used to connect to the media repository of the TMTM Application Service.

A default username is used.

NativeEncoding

Override the default native encoding of a BTM extension.

If not set, the environment's default native encoding is used (as set by the system). If set, the BTM extensions use the CCSID defined by the NativeEncoding property.

DisableAgentDistribution

Disables any further agent distribution. Any distributions already scheduled complete.

False.

ChangeDistributionDirectoryTo

Instructs the TMTM Configuration Agent to change the directory to which it writes agent and extension distributions. If distributions exist, they are moved to this location. If the agent is not running, they are moved when it starts. The agent removes this preference when the change is processed.

Not applicable

ASSecure

For auto deployment and agent and extension distributions, indicates that the agent connects to the TMTM Application Service using a secure (HTTPS) connection.

True.

EXAMPLE: Change the deployment interval from the default to 30 seconds.

 Use this command: agentpref --set "BTMConfig Ext" DeploymentInterval 30
 

where:
BTMConfig Ext is the name of the extension. Any space characters in the extension name might need to be enclosed in quotation marks or escaped depending on the shell being used to issue the command.

Was this page helpful? Yes No Submitting... Thank you

Comments