Modelling of application interfaces

[HMJ]

Based on the CSDM 3.0 how and where would you model interfaces (data exchanges) between applcations and there attributes. We currently have them available at businessapllication level in an EA tool and would like to find the proper level within ServiceNow and hopefully base this on experiences others already made in this context. Thanks for any experiences shared 

[Daniel Carvalho]

Hi

At the CSDM 3.0 Foundation training it is said that this use case is yet to be documented by CSDM Team.

We are to wait or keep current discussions, such as this:

https://community.servicenow.com/community?id=community_question&sys_id=f52d7f4cdb9e9c50fa192183ca961953&view_source=searchResult

Cordial

Daniel

[HMJ]

Hi Daniel,

seen your entry already and looking forward to a response from the SNOW team, but I assume someone has already tackled the issue and could share their experiences.

[Daniel Carvalho]

Yes, I also think the more people share their practices, the best!

Cordial

[Ed Laar1]

Hi Hans-Martin.

I should consider an interface as a real entity or piece of functionality with it's own characteristics, version, specs and so on.

Also an interface connects 2 (or perhaps more) entities (source and target) together, can fail, needs to be changed and so on.

From these standpoints I should say: Create a CI class for Interfaces (I think it's not already there) and define minimum attributes for it. An attribute called category will be usefull to have the possibility to devide different interface types.

Create CI's for all the interfaces there are and add them to the CMDB of the Application Service it belongs to using relations.

In this way a) the registration is doen, b) operational processes can run and c) versioning and updates are easy to trigger.

Hope this helps,

Ed