A Couple of TADDM OPAL Gems

A couple of useful TADDM OPAL contributions for those interested in learning how to get more from your application discovery and mapping investment.

—

Best Practices for using TADDM Sensors

Discovery is performed using sensors which are currently built and deployed as part of the TADDM product. The sensor asks, figuratively, the host and the applications how they are configured and who they are talking to.

This paper does not include detail on the complete list of sensors. Over time this list will be enhanced as we attempt to document all Tivoli Application Dependency Discovery Manager (TADDM) supported sensors, as well as the new ones that are added with every release. The following sensors are addressed:

Apache, DB2 database, IIS, Oracle database, Oracle Application Server, SAP - CCMS and SLD, SQL server database, Weblogic, pplication Server, Websphere Application Server, Windows OS

Tivoli Application Dependency Discovery Manger’s Flexible Approach to Discovery Whitepaper

Tivoli Application Dependency Discovery Manager’s (TADDM) flexible approach to discovery and automatic mapping of dependencies from layer 2 through 7 enables its users with the visibility and necessary agility requisite to improve service availability at their firms. TADDM’s unique approach of combining agent-less and credential-free discovery in configurable discovery profiles facilitates its user’s control over where they discover, what they discover and how deep they go. TADDM allows users continue to leverage their best practices for the business, but now armed with the powerful data analysis TADDM provides in order to make the best informed decisions for their firm.

License

This work is published under a Creative Commons Attribution-NonCommercial-ShareAlike 2.5 License.