SAP technical CI's in the CMDB

[Ed Laar1]

Hi community members,

I am looking for examples on how a technical SAP backend infrastructure is registered and maintained in the CMDB. Which CI classes are used, which relations are used, is Discovery and/or Service mapping used etc. etc.

Use case here is to have an up 2 date view on all those components that provide the SAP platform in order to be able to determine Incident prio's, change- and vulnerability risks etc. etc. 

Hope you guys can help me with this. Looking forward to your reactions,

Ed

[Maik Skoddow]

Hi @Ed Laar 

Please have a look on that video: https://youtu.be/-wD-E5IBzys?t=1048

Maybe it can answer some of your questions.

Kind regards
Maik

[Ed Laar1]

Thanks Maik as its always good as a reminder to watch such video's again.

What I am interested in is the design in the CMDB of the SAP Platform itself so the involved CI's, databases and so on. SAP Platforms seem to have a common design so I wonder if there are examples of that.

Use case: The Platform runs on multiple IT-Infra elements. Some of them are more essential / crusial than other ones and we want to be able to track this.

Perhaps you have info on this part?

Cheers,

Ed

[Maik Skoddow]

Hi @Ed Laar 

sorry for the late response and unfortunately I cannot help any further.

Kind regards
Maik

[Tam_s Holics]

You can load your SAP landscape data from the SAP Solution Manager LMDB tables using this SAP add-on: https://sta-technologies.com/sap-data-sync-for-servicenow/

We have a customer who implemented this funcationality: they identified the key tables in SAP, wrote a simple ABAP report that combined them together and the SAP add-on product loads the result of the ABAP report periodically to a specified ServiceNow import set table.