Medium environment guidelines

For environments containing from 5K to 75K targets, you can use server installation types 2 or 3 in Server environment guidelines. In terms of performance, installation type 2 is suitable. However, with installation type 3 you can also use the admin functions of the installed WebSphere Application Server.

Also, consider the following extra requirements.
  • Processors: 1 Quad core or 2 dual core processors, 2.40 GHz.
  • Memory: 8 GB RAM.
  • Storage: RAID 5 - 6 HDD. DB2, Oracle, or MS SQL 64 bit or 32 bit.
  • Heartbeat configuration -
    Table 1. Heartbeat configuration properties: suggested values for a medium environment
    Property in trc.properties Value
    heartbeat.timeout 1440
    Note: If there are specific groups of computers where more regular updates are needed, a smaller heartbeat timeout setting can be applied as a group attribute for those specific groups of targets. For details of setting this attribute at group level, see the chapter that explains how to create a target group in the IBM® BigFix® Remote Control Administrator's Guide.
    heartbeat.retry 10
    Note: In an environment that contains target numbers nearer to 75 K, set this value to 20 to help with performance.
    heartbeat.delay 20
    Note: In an environment that contains target numbers nearer to 75 K, set this value to 40 to help with performance.
    heartbeat.on.wake 0
    heartbeat.on.user.change 1
    heartbeat.on.change 0
    heartbeat.on.stop 0
Note: In this type of environment, ensure that the target deployment is done in stages. A staged deployment can avoid overload in the server when the targets try to register with the server. Give the RegistrationDelay target property a value that distributes the target computer registration evenly through the staged deployment. Distribute the target registration to avoid too many computers trying to register at the one time.