The CreatorCon Call for Content is officially open! Get started here.

CSDM framework for Integrations (Operations Perspective)

vijaygehc
Tera Contributor

Hi All,

How can we represent Integration objects within CSDM framework from Operations view point?

For Example: My Integration/Interface (we call it L1)  is Order_Siebel_ERP  (Tells about business object  "order" flowing from Siebel to ERP through a middleware system.  This logical object is hosted on middleware orchestrating a flow from Siebel to ERP.  

Is there any documentation from service now that helps us to align these attributes to CSDM model from Operational perspective?

 

Thanks

Vijay

 

 

 

1 ACCEPTED SOLUTION

Narsing1
Mega Sage

You may think of doing like this.  But its just a thought and completely depends on org. requirements on how they would like to see.  Some will do via Business Service and Business Service Offering / Technical Service and Technical Service Offering.  You may choose these options as well, but the basic structure will be the same.

 

Business Applications

  • Siebel
  • ERP

Application Services 

  • Siebel ==> Siebel Production, Siebel Development, Siebel [Any other environment]
  • ERP ==> ERP Production, ERP Development & ERP [Any other environment]

Relationships on Siebel

DownstreamUpstream
Consumes - Siebel Production, Siebel Development 

 

Relationships on ERP

DownstreamUpstream
Consumes - ERP Production, ERP Development 

 

Relationships on Siebel Production

Downstream RelationshipUpstream Relationship
Runs on - Server1, Server2Consumed by - Siebel
 Sends data to - ERP Production

 

Relationships on ERP Production

Downstream RelationshipUpstream Relationship
Runs on - Server1, Server2Consumed by - ERP
Receives data from - Siebel Production 

 

Thanks,

Narsing

View solution in original post

2 REPLIES 2

SteveMacWWT
Kilo Sage

@vijaygehc I’d suggest looking at @vNick’s article on New Data Model in CMDB for APIs.

Narsing1
Mega Sage

You may think of doing like this.  But its just a thought and completely depends on org. requirements on how they would like to see.  Some will do via Business Service and Business Service Offering / Technical Service and Technical Service Offering.  You may choose these options as well, but the basic structure will be the same.

 

Business Applications

  • Siebel
  • ERP

Application Services 

  • Siebel ==> Siebel Production, Siebel Development, Siebel [Any other environment]
  • ERP ==> ERP Production, ERP Development & ERP [Any other environment]

Relationships on Siebel

DownstreamUpstream
Consumes - Siebel Production, Siebel Development 

 

Relationships on ERP

DownstreamUpstream
Consumes - ERP Production, ERP Development 

 

Relationships on Siebel Production

Downstream RelationshipUpstream Relationship
Runs on - Server1, Server2Consumed by - Siebel
 Sends data to - ERP Production

 

Relationships on ERP Production

Downstream RelationshipUpstream Relationship
Runs on - Server1, Server2Consumed by - ERP
Receives data from - Siebel Production 

 

Thanks,

Narsing