- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-01-2024 01:16 PM
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
Solved! Go to Solution.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-02-2024 06:09 PM
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
Downstream | Upstream |
Consumes - Siebel Production, Siebel Development |
Relationships on ERP
Downstream | Upstream |
Consumes - ERP Production, ERP Development |
Relationships on Siebel Production
Downstream Relationship | Upstream Relationship |
Runs on - Server1, Server2 | Consumed by - Siebel |
Sends data to - ERP Production |
Relationships on ERP Production
Downstream Relationship | Upstream Relationship |
Runs on - Server1, Server2 | Consumed by - ERP |
Receives data from - Siebel Production |
Thanks,
Narsing
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-02-2024 03:22 PM
@vijaygehc I’d suggest looking at @vNick’s article on New Data Model in CMDB for APIs.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-02-2024 06:09 PM
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
Downstream | Upstream |
Consumes - Siebel Production, Siebel Development |
Relationships on ERP
Downstream | Upstream |
Consumes - ERP Production, ERP Development |
Relationships on Siebel Production
Downstream Relationship | Upstream Relationship |
Runs on - Server1, Server2 | Consumed by - Siebel |
Sends data to - ERP Production |
Relationships on ERP Production
Downstream Relationship | Upstream Relationship |
Runs on - Server1, Server2 | Consumed by - ERP |
Receives data from - Siebel Production |
Thanks,
Narsing