Collect Config Files Recursively
TADDM allows for collection of config files during computer system discovery. This is configured under "Computer Systems" in the Discovery Management Console.
Configuration files are collected on a computer system type basis. Open the template that matches the type you wish to target for collection. Ensure that the template is enabled.
Click on the Config Files tab to input the configuration files to capture. Click Add to define the file capture.
Now we want to configure TADDM to recursively collect configuration files according to a name with wildcard. For example, we want TADDM to collect all *.config files under /app or any sub-directory under /app.
APAR IV79730 was created to fix the recursive collection issue with versions of TADDM prior to 7.3.0.3. It is recommended to request and e-fix from IBM support with this APAR so that the default collection method can be used. If this APAR cannot be applied you can workaround the issue by chaining together multiple definitions. The downside is that you will only be able to go so deep. In the example below, we are defining searches down to 3 directory levels deep.
With the APAR applied it is much simpler to configure for recursive file capture.
After discovery, the config files are captured at all levels.
