Integrating BigFix

Purpose
TADDM uses Anchors and Gateways to discover machines/applications/network that are behind firewall. The use of Anchors/Gateways can be avoided by using IBM Netcool monitoring tools (ITM) currently. Alternatively, TADDM integration with BigFix architecture can be utilized to avoid using anchors and gateways. BigFix architecture consists of BigFix server (BES Server) and multiple BigFix endpoints (BES clients) where the BES clients are the secure machines which are accessible through BES server. BigFix infrastructure can be reused/utilized for running the TADDM script packages on the BES clients via BES server automatically.
Reference
Documentation for TADDM
Solution Architecture
TADDM-BigFix integration is based on enhancing and automating the current behaviour of Asynchronous Script Discovery (ASD) which requires manual intervention from TADDM administrator. This integration utilizes the connectivity that BigFix infrastructure provides to the firewalled zone machines for running the discovery through the TADDM script packages.
TADDM Bigfix Integration
BigFix enhanced TADDM discovery solution focuses on end-to-end functional execution of discovery for Windows, Linux, AIX and Solaris OS and associated sensors (for multiple endpoints) and with SSL communication supported between TADDM and BigFix via BigFix REST APIs. Discovery can be initiated at TADDM Discovery server and the discovery results should be retrieved automatically and visible on the TADDM GUI.
Configurable Properties
Following are the configurable properties which can be configured in collation.properties
Examples of scripts execution
The following shows examples of the scripts execution during this integration:
Error Codes and Description
The following table lists the Error or Message IDs and their description that can come when user invokes the BigFix script- runBigFixDisocvery.sh(or .bat):

Parent topic: Integrating TADDM with other Tivoli products