Minor changes are by default collapsed in the page history.
No changes
The page does not exist yet.
Failed to load changes
Version by on
Leave Collaboration
Are you sure you want to leave the realtime collaboration and continue editing alone? The changes you save while editing alone will lead to merge conflicts with the changes auto-saved by the realtime editing session.
Information
This documentation supports the 20.02 version of BMC CMDB.To view an earlier version, select the version from the Product version menu.
Troubleshooting the Dynamic Service Modeling plug-in
The Dynamic Service Modeling (DSM) plug-in is the background engine that wakes up periodically and queries to see if there are any new CI or modified CIs that meet the criteria in the saved queries for a specified CI. If a CI is found, a relationship is created to relate it to the specified CI. The DSM plug-in uses its own sandbox dataset to make changes and then runs a Reconciliation Engine job to BMC.ASSET.
By using the DSM plug-in, you can dynamically relate physical CIs to a technical service. For example, the Web Farm Technical service could have a query that finds any web server with web_aus_ in the front part of the name.
Troubleshooting tips
<AtriumCore>/logs/dsm.log, <AtriumCore>/Logs/AtriumpluginSvr.log, and AtriumCoreSvr.log file log errors if any.
To set the log level:
In a browser tab, log in to the Remedy AR System using the following URL: http://<midTierServer>:<portNumber>/arsys/
Open the Remedy Action Request System Administration Console.
Click System > General > Plugin Server Configuration.
On the Plugin Server Configuration tab change the logging level from INFO to DEBUG. documentation.
