Configuring the CMSDISAgent

The CMSDISAgent runs periodically as a topology builder agent and updates the registration of TADDM configuration items (CIs) in the Context Menu Service and Data Integration Service database, registering any new or modified CIs and deregistering any deleted CIs.

If enabled, the CMDDISAgent begins running after you complete the initial registration of TADDM CIs using the run_cms_dis_registration script. You can modify the agent configuration to change how the agent runs.

To enable or disable the CMSDISAgent, edit the $COLLATION_HOME/etc/collation.properties file and set the following property:
```
com.ibm.cdb.DisCmsIntegration.enabled=value
```
where value is either true or false. If the value is set to true, the agent runs periodically after the initial registration is completed. (This property does not affect the operation of the run_cms_dis_registration script, which can be run at any time.)
To customize which CIs are registered in the database, modify the following files in the $COLLATION_HOME/etc/cmsdis directory:

classtype-changehistory.list

Lists the model object types of CIs for which TADDM has launch-in-context support for the change history report.

classtype-detailPanel.list

Lists the model object types of CIs for which TADDM has launch-in-context support for the details panel.

You can remove any model object types that are not needed for other products to launch TADDM in context. Do not add any types to these files; TADDM might not support launching in context for additional types.
After modifying the class type list files, disable the agent and then run the run_cms_dis_registration script again, specifying the re-register-all option.