Developing custom server extensions

You can use custom server extensions to discover targets for which TADDM has limited or no specific built-in support or to add functionality to TADDM.

The custom server extensions provide an Application Programming Interface (API) that you can use to create programs that set attributes defined in the Common Data Model (CDM) or extended attributes you have added to the CDM using the Data Management Portal.

These Jython-based extensions run inside the TADDM Discovery Engine which provides the custom server extensions with a framework to harness many of the sensor building blocks within TADDM.

Custom server extensions offer the following features:

  • You can use the TADDM user interface and API to view the discovered attributes.
  • Custom server extension messages are written to the Discovery Manager log and to the appropriate computer system sensor log (or CustomAppServerSensor logs if split sensor logs are enabled).
  • No additional software is required to use the system.
Limitation: You cannot use script-based sensors to create custom server extensions.
Limitation: When you extend the discovery on the Windows operating systems to run commands which return the output with Unicode characters, such characters are not stored.
Fix Pack
3 In TADDM 7.3.0.3, and later, storing the Unicode characters is supported. However, you must first send the output to a file and then read the file. The following example shows commands, which you can use to perform these two operations. In the example, the output of the unicodetest.bat command is sent to the c:\\r.txt file.
os_handle.executeCommand("c:\\unicodetest.bat | out-file c:\\r.txt")
output =  os_handle.executeCommand("cmd.exe /u /c type c:\\r.txt")