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]

Hello @Ed Laar 

Can you please comment over my new notes bellow?

• Create a CI class for Interfaces (I think it's not already there) and define minimum attributes for it. 

At first, as mentioned on other posts

https://community.servicenow.com/community?id=community_question&sys_id=81e1cbf61b255050ada243f6fe4b... 

and:

https://community.servicenow.com/community?id=community_question&sys_id=f52d7f4cdb9e9c50fa192183ca96...

I was proposing this new class being an extension of Application Services (Data Integration Services as naming example for this new class).

But given the concept that Application Services relies on a "instantiated syntax", it feels odd to use it, specially to link to object (Business Application) that is on a "higher" level of information concept (non-instantiated).

Extending Business Application or using this table directly for the interfaces CI also do not seems correct. 

So the conclusion I arrive to is to create a new class extending cmdb_ci (keeping some sort of equivalency to Batch Jobs that extend direct to base cmdb_ci).

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

This piece still leaves me on unrest mode. 

Connecting that new Data Integration CI to application services means managing this on "application instance"-level. That means hard work x3 or x4 (depending on DEV/TEST/PROD/etc. being used).

If the intention of that new CI is, for example, to make explicit difference between a Change in non-Prod Integration CI and Prod Integration CI, then I see no other way.

If the main intent is more on documentation and concept of architectural data flows, then the new CI would only me related to Business Applications not to application services.

Cordial

[MikeWilsonNYC]

Would love to hear some guidance from the ServiceNow CSDM team on this.