IBM®
Skip to main content
    Country/region [select]      Terms of use
 
 
    
     Home      Products      Services & industry solutions      Support & downloads      My IBM     
developerworks > My developerWorks >  Dashboard > Tivoli Application Dependency Discovery Manager > ... > Sensor Community > Sensor Taxonomy
developerWorks
Log In   View a printable version of the current page.
Sensor Taxonomy
Browse space Browse Space    
Added by obriend, last edited by mallo on Feb 13, 2009  (view change)
Labels: 
(None)

 Application Dependency Discovery Manager

Home > Sensors > Sensors Taxonomy

Sensor Taxonomy

To learn more about the TADDM Sensors and Reports Community and how you can contribute, click here. This is a Community page, and anyone can contribute. Sign in in to the wiki and begin contributing to the TADDM Sensors and Reports Community.

This page includes a taxonomy of IBM® Tivoli® Application Discovery Manager (TADDM) sensors.  Sensors are typically used to discover applications, relationships, and configuration details directly from TADDM's discovery processing.  If you are looking for integrating TADDM with an existing data store, please check out the Discovery Library Adaptor information on the integrations scenario wiki page here

Sensors come in three flavors:

  1. Sensors
    • Agent-less discovery of applications
  2. Deep Sensors
    • TADDM's traditional deep-dive discovery
  3. Packaged Application Sensors
    • Deep-dive discovery of commercial business applications such as SAP, Oracle Financials, PeopleSoft, JD Edwards, Siebel, etc

Community

 Sensor flavor #1 will be the focus of the TADDM community, the other sensor types remain with the TADDM development team to pursue

Sensors

  • Sensors are a tool for discovery
  • A Sensor should be targeted towards discovering a single application such as e.g. BEA Tuxedo
  • Patterns for matching and thus correctly identifying an application can use the following choices in any combination (AND/OR)
    • CMD line, argument, environmental variables, ports or Windows Service name (Windows only)
    • The above attributes are returned by default by TADDM for all running processes on all servers TADDM discovery is run on
  • Comparison expressions
    • In order to determine if attribute values match a known application, the user provides one or more string, numerical or regular expressions in the UI which these values are compared against.


What is discovered?

  • Up to ~10 attributes about this application should be captured (number will vary) and returned to TADDM
    • Attributes must at a minimum include ProductVersion and ProductName
    • Use the sensor examples to understand how to include new attributes in a sensor
  • Configuration files, when available should be returned by the Sensor


Visualization

  • A single application module should be represented by a single icon
  • Icons should be specific to the application module and supplied by the author
  • Attributes returned are displayed in the details panel as a configuration file
  • By default in TADDM, an application discovered by a Sensor will be shown on a topology map, once it is added to a business application
  • Application dependencies will be shown on a map when an "ESTABLISHED TCP Session" is observed between this new application and another application during a discovery run

Optional extras

  • A Sensor author can create Sensors for multiple application modules and create an Application Template to group them together

    About IBM      Privacy      Contact