Data collected by the MDMSupport PD collector tool

The MDMSupport PD collector tool provides facilities for an advanced user to customize the way PD data is collected.

The following customization types are supported:
Customizing the collection of metadata
A list of metadata tables and the queries to fetch table data are stored in the <MDMSUPPORT_HOME>/config/metadata.properties file. By default, the metadata.properties file comes with a set of key-value pairs that contain the metadata table names as keys and SQL statements as values. If required, you can modify the WHERE clause of the SQL queries to fetch a subset of table data.

In order to control the actual set of tables from where data is collected for the metadata feature, a property with the name metadata.include is included in the mdmsupport.config file. The out-of-the box value of this property is ALL, which instructs the MDMSupport PD collector tool to execute all of the SQL statements that are defined in metadata.properties. If no value is specified for the metadadata.include property, it defaults to NONE, and no data is fetched. You can also provide a comma separated list of table names picked from the list of keys specified in the metadata.properties file as the value for the metadata.include property, which will instruct the MDMSupport PD collector tool to execute only those SQL statements whose keys are mentioned in the comma separated list.

Customizing collection of moredata
The term moredata, in the context of the MDMSupport PD collector tool, refers to data that is not described and specified in the metadata.properties file. If you wish to extend the set of InfoSphere® MDM configuration data collected by the MDMSupport PD collector tool, you can use the moredata facility by adding key-value pairs to the <MDMSUPPORT_HOME>/config/moredata.properties file following the same pattern as used in the metadata.properties file.

To control the actual set of tables from where data is collected for the moredata feature, a property with the name moredata.include is included in the mdmsupport.config file. The out-of-the box value of this property is ALL, which instructs the MDMSupport PD collector tool to execute all of the SQL statements that are defined in moredata.properties. If no value is specified for the moredata.include property, it defaults to NONE, and no additional data is fetched. You can also provide a comma separated list of table names picked from the list of keys specified in moredata.properties file as the value for the moredata.include property, which will instruct the MDMSupport PD collector tool to execute only those SQL statements whose keys are mentioned in the comma separated list.

Customizing collection of morefiles
Collecting additional files other than the out-of-box files collected by PDCollector is often required. Edit the morefiles.properties configuration file to add the paths of additional files that need to be collected. The paths should be relative to MDM_HOME.

This functionality can be controlled by the morefiles.include property in mdmsupport.config file. The default is NO to indicate that no additional files will be collected. You can enable this functionality by changing the morefiles.include property to value to YES. The collected files can be found in the mdm/core/moreFiles/ directory.

Customizing collection of morecommands
This functionality is useful when additional commands need to be executed and the output needs to be verified. Enter the additional commands in the morecommands.properties configuration file.

This functionality can be controlled by the morecommands.include property in the mdmsupport.config file. The defaults NO to indicate that no additional commands will be executed. You can enable this functionality by providing changing the morecommands.include property value to YES. The results will be captured in ystem/moreCommandResults/moreCommandResults.txt in a generated ZIP file.

Customizing collection of eventmanager data
Similar to metadata.properties, a file by name eventmanager.properties contains the SQL statements to fetch data from Event manager tables. The property eventmanager.include in the mdmsupport.config file can be used to configure the set of tables from which event manager data is fetched. This property can take the values ALL or NONE or a set of comma separated SQL keys picked from eventmanager.properties.
Customizing system commands
The directory <MDMSUPPORT_HOME>/syscmd contains command files that specify the operating system commands that should be executed for various scenarios.
There are five files under the syscmd directory:
  • aix.txt – used for the AIX® operating system.
  • solaris.txt – used for the Solaris operating system.
  • hp-ux.txt – used for the HP-UX operating system.
  • linux.txt – used for the Red Hat Linux® operating system.
  • suse-linux.txt – used for the SUSE Linux operating system.
Choose the one matching with your operating system, if you want to modify any of the commands listed in these files.
Important: If you want to modify any of these, back up the command files before modifying them, because any errors in the system commands may render the MDMSupport PD collector tool unusable.