Service Configuration Items Association - How are records removed?

carlasteen
Tera Contributor

How are associations removed from the Service Configuration Items Association table?   Does the map have to fully remove the items?  Or what happens when the map' operational status is changed?

 

We are using the unauthorized change process and only want to alert for items that are part of a valid, active service map.

1 ACCEPTED SOLUTION

Mathew Hillyard
Mega Sage

Hi @carlasteen,

The Service Configuration Item Association table stores relationships between a CI and one of the Application Service tables (including Dynamic CI Group). It is populated automatically using various methods, but basically using one of two solutions:

  1. CI relationships that ultimately go up to an Application Service
  2. CIs whose data means they form part of a CMDB Group referenced by a Dynamic CI Group

 

If anything changes with either of these methods (so a CI relationship is removed, or a CI's data changes, or the conditions in a CMDB Group change) then Service Configuration Item Association is automatically updated - any new relationships are added, and any that should no longer exist are removed.

 

The actual heavy lifting is done by script includes in the backend. It depends on the population method and whether you are using Service Mapping (or not) as two which scripts do the work.

 

These mechanisms do not consider status as far as I am aware. If you retire a CI then you need CMDB Data Manager Policies set up to remove CIs from service maps (should your organisation permit it). As far as the service map goes, again, this should be a process (potentially with a CMDB Data Manager policy, but more likely a formal process that requires approval) and is part of the retirement of the infrastructure or service above the Application Service.

 

I don't see any configuration within the Unauthorized Change application that allows you to exclude inactive CIs or even inactive Application Services, but I am not that familiar with it. As far as I can see you may need to extend the "UnauthorizedChangeRequest" Script Include to add in your functionality.

 

I hope this helps!

Mat

View solution in original post

2 REPLIES 2

Mathew Hillyard
Mega Sage

Hi @carlasteen,

The Service Configuration Item Association table stores relationships between a CI and one of the Application Service tables (including Dynamic CI Group). It is populated automatically using various methods, but basically using one of two solutions:

  1. CI relationships that ultimately go up to an Application Service
  2. CIs whose data means they form part of a CMDB Group referenced by a Dynamic CI Group

 

If anything changes with either of these methods (so a CI relationship is removed, or a CI's data changes, or the conditions in a CMDB Group change) then Service Configuration Item Association is automatically updated - any new relationships are added, and any that should no longer exist are removed.

 

The actual heavy lifting is done by script includes in the backend. It depends on the population method and whether you are using Service Mapping (or not) as two which scripts do the work.

 

These mechanisms do not consider status as far as I am aware. If you retire a CI then you need CMDB Data Manager Policies set up to remove CIs from service maps (should your organisation permit it). As far as the service map goes, again, this should be a process (potentially with a CMDB Data Manager policy, but more likely a formal process that requires approval) and is part of the retirement of the infrastructure or service above the Application Service.

 

I don't see any configuration within the Unauthorized Change application that allows you to exclude inactive CIs or even inactive Application Services, but I am not that familiar with it. As far as I can see you may need to extend the "UnauthorizedChangeRequest" Script Include to add in your functionality.

 

I hope this helps!

Mat

thank you this is very helpful