Dynamic CI Group relationship to Application Services when used as a form of Service Mapping

[DonnaOlsen]

When using Dynamic CI Groups as a form of Service Mapping would you recommend the Runs On Relationship between Dynamic CI group and App Service?

For example:

Technical Service: Application Support

    references

Service Offering: ABC Application

    contains

Dynamic CI Group: query capturing all ABC App Servers

    runs: runs on.  Updated: Depends On:Used By

App Service: ABC Application PROD (app service)

    consumes

Business App: ABC Application 

Edit:

I missed the Tech Service Offering also will have a contains:contained by relationship above with the App Service.

Adding visuals to help display what I am trying to outline and inquire about.  I am not running both SM and Dynamic CI group as a form of SM. This example is to show the relationships and differences.

[User342536 · Accepted solution]

Hi @DonnaOlsen ,

Please use Parent Service on configuration Dynamic CI Group, to set application service as parent of this DynCIGrp.

This DynCIGrp will be showed as an endpoint of AS, and will be impact the map.

Please mark correct if it helped!!!
Kindest Regards,

Rodrigo Donnangelo

[User342536 · Accepted solution]

Hi @DonnaOlsen ,

Please use Parent Service on configuration Dynamic CI Group, to set application service as parent of this DynCIGrp.

This DynCIGrp will be showed as an endpoint of AS, and will be impact the map.

Please mark correct if it helped!!!
Kindest Regards,

Rodrigo Donnangelo

[DonnaOlsen]

Thank you this was very helpful. I did not think to use DynCIGrps from the App Service Wizard.

By doing this it provides a Depends On: Used By relationship.

[Mathew Hillyard · Accepted solution]

I think the question @DonnaOlsen is asking is relating an Application Service as a child of a Dynamic CI Group.

This is not contained within the CSDM standard and is not a recommended method for linking objects together, because a Dynamic CI Group is not related to its CIs via CI Relationships, but instead from the queries returned by its referenced CMDB Group.

Therefore it would make no sense to have a child object with the Dynamic CI Group as a parent, because you would have no visibility of the Dynamic CI Group's CIs in the dependency view or the relations formatter; furthermore, in the CSDM standard, only a Service Offering or another Application Service should be the parent of an Application Service. A Dynamic CI Group is a group of related CIs - it does not "run on" anything.

@DonnaOlsen In your example above, you should have as the child of a Service Offering either a Dynamic CI Group (if for example Discovery is not running on the instance, or you have no way of relating the CIs in an application service together), or an Application Service. The flavour of the Service Offering's parent will determine the CI Relationship type (Technical Service Offering = Contains::contained by, Business Service Offering = Depends on::Used by).

[DonnaOlsen]

Thank you, I had the Dynamic CI Group a "child" of the Technical Service Offering with a contains:contained by relationship. I did not think to also use it as a child of the Application Service.  

I needed to change my mindset even though I was trying to mimic a "runs on" relationship as I was thinking of ServiceMapping, I needed to be mindful of the relationship that the Dynamic CI Group provides rather than turn it into something else.