How to create an empty Application Service with 'Operational' status ?

[Ishan4]

I want to create an Application Service but with no-entry point, when I do it from Application Service Dashboard it makes a non-operational Application Service. I am providing a Dynatrace id which later will scan and add CI but not at the moment of creation.

[Natascia Heil · Accepted solution]

Create the application service in the class cmdb_ci_service_auto. That is the parent class of mapped application service (cmdb_ci_service_discovered) and does not check on the operational state.

[Florian Spisla]

What I started to do is, populate it with a generic Application (cmdb_ci_appl) with the name of "Dummy Application". So at a later point I can always check, which Applications Services need to be specified into more detail, but INC and CHG can still be opened for the Application Service.

[Ishan4]

Hi @flospi ,

Thanks for reply, sorry I just it now. That is sounds some really experimental trick to try. Would like to try.

[TaylorJ]

Two ways you can do this..

1st approach: if you have applications stored in cmdb_ci_appl (class=Application) then migrate the data to [cmdb_ci_service] with the (class=application service) and (service classification=application service).  This will create a FLAT Application Service that can be used for in ITSM.

2nd approach: migrate to cmdb_ci_service_auto and use the same class and service classification as listed above. The file will be flat and should not allow service mapping but provide visibility to the ITSM tool set.

I really wish SN would come up with an entry point for these issues instead of having us do so much manipulation.