What is the recommended approach and practice to map dependencies between application services?

Richard29
Tera Contributor

What is the recommended approach and practice to map dependencies between application services?

I understand you map application services to CI's using the Service Configuration Item Association table [svc_ci_assoc] .

Should dependencies between application services be created in the CI Relationship [cmdb_rel_ci] table directly? I notice also there is the ability to at least from the child application service to indicate the parent application service as a tab on the application service form.  I notice the list of options for parent application service doesn't display the full list of application services to link things that way.  I'm assuming it does not appear in the list if the parent app service is already a mapped application service. 

Would be great in addition to an explanation in some cases to provide a quick video demo of the practice of doing some of these things. 

Willem
Tera Sage

Hi Richard,

Application Service to Application Service use the "Depends on / Sends data to":

find_real_file.png

Reference:https://docs.servicenow.com/bundle/rome-servicenow-platform/page/product/csdm-implementation/concept...

Richard29
Tera Contributor

Thanks this is helpful for the type of relationship classification, but how about the best/recommended way to create this relationship?

Should I go direct to CI Relationships and add a record directly or is there a different recommended way for this?

Hi Richard,

Not sure what you mean. On the Application Service form (CSDM-> Manage Technical Services -> Application Service) I have the option to Set Relationships:

find_real_file.png

Is this what you are looking for?

Richard29
Tera Contributor

I've noticed i can't use that tab to pick associated application services. 

The stop appearing in the available list of application services after the following occurs:

1. If i create a new application service and link it to no CI's at all -- it is visible on this list to other application services of parent application services. 

2. If the parent application service I link to CI's e.g. using the manual method of linking the application to CI's.  It stops being visible on this list. 

From this I infer a service can only be a parent application service if that application service has no associated CI's bound to it. 

Is this intentional?

The only way I can see to map application services dependencies is if I go directly to CI Relationships and add a record there.