How to convert a "Calculated application service" in to a tag based application service?

[chaithra10]

We have been using "Calculated application services" in our infra from a long time, now we are working on implementing "Service mapping". for cloud based apps - we are using "tag based application service" creation method and we have built tag based app services. But  the same app already exists in "Calculated app " class creating duplicates.

Could you someone guide me on how to address these duplicates effectively? We also need to ensure this doesn't break the existing relationships and any ITSM processes.

[Mathew Hillyard]

@chaithra10 

What are you trying to achieve?

• Calculated Application Services use CI relationships from the "entry point" CI that is linked to the App Service to pull in the service map for that App Service. It presents a hierarchical map of the linked CIs
• Tag-based Service Mapping relates CIs together based on Tags. No hierarchy or individual dependencies will be present unless you run some form of discovery to populate those relationships. Tag-based App Services are more preferred for cloud services where a traditional "app runs on host which depends on database/storage" scenario.

I don't see much value in converting one to the other. Use the source data and your desired outcomes and pick the most suitable solution.

I hope this helps!
Mat

[chaithra10]

We already have existing manual "calculated app services" and wanting to implement automated services maps , one of which is "tag-based" for cloud infra. As we already had existed manual apps and the associated rels, now converting the same into tag-based, is relating new Cis with the key value pairs we have defined, and it retains the old rels, but it is deleting the manula endpoints of old CIs that were related, and so ,when I create an INC or CHG, old CI is not refelcting on the "Impacted services" .

If we retire old App services and build new tag-based, we will loose history of the CI, affected by tasks etc. and outbound integrations will be affected.

[CMDB Whisperer]

You will not lose the history, per se, if you retire the old application service.  Whatever references history audit records you have on the task or on the CI will still be there.  I think what you mean is that the references and audit history will no longer be a contiguous on a single record, which is correct.  If you want to merge the references and relationships to a single service instance, you could in theory "force" the CIs to be identified as duplicates and then run them through the de-duplication engine, which would programmatically merge all references, relationships, and related items to point to a single CI.  However, even if you do this, the audit history will not change for a CI.  There is no way to merge the audit history trail between two CIs.  Since you are asking about "history" this is important to consider.