- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-04-2020 12:04 PM
We use Mulesoft to provide integrations between various systems. We need a way to track these integrations in the CMDB and the systems that they link so that if/when they, or the systems they connect, encounter issues we leverage the CI relationship maps and / or the Service Mapping maps to identify which Mulesoft integrations need to be reviewed as a part of troubleshooting (also for linking to incidents, changes, and problems).
Is there an OOB way to track these in the CMDB, or is this something where we will need to create a new CMDB class to track the integrations and their relationships to the various applications / application services they link?
Solved! Go to Solution.
- Labels:
-
Service Mapping

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-04-2020 06:46 PM

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-04-2020 06:46 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-01-2021 01:00 PM
Hi Rahul,
Is the cmdb_ci_interface class part of Out Of The Box ServiceNOW? I can't find it in our deployment (although we've not yet moved to CSDM.... maybe it is in there?)
Or is this something you would recommend creating.
Many thanks,
Matt

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-01-2021 07:42 PM
I am unable to recall but i also do not see in Paris version. You can inherit and create a custom interface class or you can also treat application interfaces as application CI also.
Regards
RP
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-24-2021 09:06 AM
I know this is a little dated at this point, but just wanted to weigh in for posterity's sake. In our instance, we extended a new class and called it "integrations". We made it generic enough to handle as many integration types as possible.
For certain use cases, we may extend the integrations table. For example, we extended the integrations table for uiPath to allow them to have their own fields, business rules, and make reporting easier.