IBM Support

Are there any limits to the number of components used in a baseline?

Technote (troubleshooting)


Problem(Abstract)

The TEM Client treats each Baseline as a unit that must be periodically checked to see if the Baseline is needed. It is not recommended to add all the Fixlets into a single Baseline.

Resolving the problem

The TEM Client treats each Baseline as a unit that must be periodically checked to see if the Baseline is needed. If the Baseline is very large, the Client will spend a lot of time checking the Baselines and less time evaluating other Fixlets, new policy actions, or other properties that might be relevant..

For this reason it is not recommended to add all the Fixlets into a single Baseline. In some circumstances it can cause the Client to spend most of its time evaluating the Baseline and be less responsive when evaluating other properties and actions. For instance, if you send out a standard Fixlet action in TEM, you expect the action to run on all the computers in your environment and report its status in a few minutes; however, if you had a very large Baseline it can take the Client a much longer period of time to evaluate the Baseline and can cause the Client to appear to be less responsive overall.

The best practice for Baseline size would be to keep the number of Fixlets in a Baseline to 50 Fixlets in a version 6.x deployment, or 250 in a version 7.x deployment with efficient mime enabled. This will prevent the Baselines from getting too big, but still allow you to logically group Fixlets into Baselines.

If you currently have large Baselines, it is recommended that you break them into smaller pieces by deleting the larger Baseline and creating other smaller ones.

Note: In a 7.x Deployment with Efficient Mime enabled the number of Fixlets in a Baseline can be safely raised to 250. Efficient Mime is enabled and disabled through the TEM Administration tool under the Advanced Tab (usePre70ClientCompatibleMIME)

Note: The default size for the TEM server and TEM relay cache for patches is 1 Gb. When patching using large baselines, it is suggested to increase the disk cache on the server and relays to accommodate the patches being deployed. So the relay and the server cache should probably be at least as large as the majority of the patches expected to be active. However, in general the cache should be much larger then currently active baselines. A cache of 5-10 Gbs if the server has the disk space is not an uncommon suggestion.

Historical Number

382

Document information

More support for: IBM BigFix family

Software version: Version Independent

Operating system(s): Platform Independent

Reference #: 1506032

Modified date: 16 July 2014


Translate this page: