Large environment guidelines

For environments containing from 75K to 225K targets, you can use server installation type 3 in Server environment guidelines.

Also, consider the following extra requirements.

To host WebSphere Application Server
  • Processors: 2 Quad core processors. 2.40 GHz with supported OS.
  • Memory: 16 GB RAM.
  • Storage: RAID 5 - 6 HDD.
  • Heartbeat configuration -
    Table 1. Heartbeat configuration properties: suggested values for a large 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 BigFix® Remote Control Administrator's Guide.
    heartbeat.retry 60
    Note: In an environment that contains target numbers nearer to 75 K, set to a higher value to help with performance.
    heartbeat.delay 60
    Note: In an environment that contains target numbers nearer to 75 K, set to a higher value to help with performance.
    heartbeat.on.wake 0
    heartbeat.on.user.change 1
    heartbeat.on.change 0
    heartbeat.on.stop 0
  • Optional: 2 network cards, one for target communications and one for database communications that could aid in performance tuning.
To host the database, DB2®, Oracle, or MS SQL supported.
  • Processors: 4 Quad core processors, 2.40 GHz.
  • Memory: As recommended by the database supplier.
  • Storage: RAID 5 - 6 HDD 146 GB
Note: The database administrator must tune the database for appropriate performance.
The following guidelines must also be considered when you use large reports, as some performance degradation can be experienced.
  • Ensure that the All targets report is not the default home page report.
  • Ensure staged deployment of the targets to avoid overload in the server when they try to register.
    Note: 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.
Note: If you configure LDAP and LDAP synchronization is enabled, set a reasonable frequency for the synchronization. If your LDAP configuration is set up to import many users and groups, set the frequency to 24 hours. For more information about configuring LDAP, see Configure LDAP.