How to model integrations/interfaces within CMDB?

[jamesmcwhinney]

Could anyone provide any guidance in to the best practice for modeling integrations/interfaces between applications within the CMDB?

For example:

• web service call from application A to application B
• Flat file export from application C via nightly job and uploaded to application D

Will this be 100% achieved via Service Mapping?

What about scheduled jobs which would not be active at the time the top down discovery takes place?

Is there any good means of modeling these interfaces manually? (Ideally in such a way as to align with CSDM)

Thanks in advance!

[CasperJT]

We had a discussion about it in this thread: https://community.servicenow.com/community?id=community_question&sys_id=befd1153dbd3b7001cd8a345ca96...

In our company we have create a separate class called 'Integration Scenario'. This is used to represent the integration (linked with documentation for the integration). The integration scenario has a "sends data to::receives data from" relationship with the sender and receiver application service in question.

In addition the integration scenario is linked with the application(s) or application service(s) it requires to actually fulfil the integration (SAP PO, FTP server).

You could then have a Technical Service Offering called 'integration' which manages the integration.

[jamesmcwhinney]

Thanks! are these "Integration Scenarios" created and linked manually? or do you have discovery patterns that create & update them?

[jamesmcwhinney]

Also, why would the integration scenario be between application services rather than between applications?

[CasperJT]

We do not have discovery, so we are not using patterns. Currently they are being maintained manually, but we are working on a way to load the data from our integration platform in to ServiceNow. We have added a correlation ID for our integration platform, meaning it can use this to recognise endpoints, so we will be able to automate, just not using discovery.

For now the data we have now we are 'placing' the Integration Scenario between two Application Services, but there are cases, where it may make more sense to do it at an application level (for example if the integration is targeting a specific database).