IBM Support

How do I establish a dynamic policy?

Technote (troubleshooting)


Problem(Abstract)

Dynamic policies are advanced TEM configuration settings that give you a high level of flexibility and control over the behavior of TEM. These options allow you to customize the default behavior of the TEM Server, TEM Relays, and TEM Clients. However, these settings should be used with caution, as misuse can lead to non-optimal behavior or prevent TEM from functioning properly.

Resolving the problem

To establish a dynamic policy:

  1. Open the TEM Console and go to Computers tab
  2. Select the computer(s) that you would like to apply the TEM Configuration Settings to
  3. Right Click on the computer(s) and choose the Edit Computer Settings option
  4. Click on More Options
  5. Check the Custom Setting box. For "Name" and "Value", enter in values from the configuration table at the bottom of the TEM Configuration Settings page. For even more customization, relevance language can be used to determine the "Value".
  6. Click OK to send out the configuration setting, which will take effect immediately (you can view a computer's settings by selecting a computer and clicking on the Settings tab in the Computer Status dialog)

EXAMPLE

If network bandwidth is a concern, such as with dial-up connections, the TEM Client can "throttle" the download speed by limiting the amount of bytes it downloads per second. Although the presence of TEM Relays is useful in helping with bandwidth concerns, if there is a significant amount of download requests going to TEM Relays that are too far away, then servers can still be overwhelmed with downloads, no matter how much it is throttled. It would be useful to lock computers that are not utilizing TEM Relays optimally so that inefficient downloading can be prevented. In this case, a solution would be to utilize the _BESClient_Download_LimitBytesPerSecond and the __LockState settings. The first setting determines the throttling while the second setting determines whether or not to lock a target computer. Locking a computer will allow for an administrator to analyze why certain TEM Clients are choosing TEM Relays that are potentially too far away without having to worry about any downloading happening automatically if it can be done more effectively.

Note that as with all TEM Client settings, actions are automatically given an "effective date" of the datetime when they are issued. Newer settings will override the previous settings on a TEM Client. If you create a dynamic settings policy and then change the setting at any time, the new setting on will override the previous setting on the targeted computers and the older dynamic policy will be overridden. Similarly, newer dynamic policies will override the setting that was previously set with an older effective date.

Here are sample relevance phrases:

Bandwidth Throttling Version: If the TEM Relay is over 2 hops away, enable throttling at 1Kb.

{if (((exists setting "BandwidthOverride" of client) and (exists value of setting "BandwidthOverride" of client) and (value of setting "BandwidthOverride" of client = "1")) OR (exists relay service) OR (exists main gather service)) then "0" else if (exists selected server and upper bound of distance of selected server > 2) then "1000" else "0"}

Locking Version: If the TEM Relay is over 4 hops away, enable locking. This will prevent an overload in the bandwidth.

{if (((exists setting "LockOverride" of client) and (exists value of setting "LockOverride" of client) and (value of setting "LockOverride" of client = "1")) OR (exists relay service) OR (exists main gather service)) then "false" else if (exists selected server and upper bound of distance of selected server > 4) then "true" else "false"}

There are override settings specified for each of these polices. If you need to override the locking/bandwidth policy, do not do it by editing the policies above. Instead, just create a new setting on the client and call it 'BandwidthOverride' or 'LockOverride' as appropriate and set the value to '1'.

Historical Number

367

Document information

More support for: IBM BigFix family

Software version: All Versions

Operating system(s): Platform Independent

Reference #: 1506053

Modified date: 03 January 2012


Translate this page: