Moving to Application Services

[David A2]

We are starting to undertake the effort to move our Bus App environments (Dev, Test, Prod) from the table they currently live on to something that better aligns with the future CSDM. In the presentation from K19 and the documentation found here it says to populate those on the Application Services table (cmdb_ci_service_discovered). What we're seeing however is that table has a new UI and different functionality than the standard table we're using now which will make adoption difficult. 

What were planning is for now to move those environments onto the cmdb_ci_service table with a Service Classification of Application Service. It looks like there is a button we could use later to truly convert them, Would that be a step in the right direction? Or will we be creating more work for ourselves down the road?

[scott_lemm · Accepted solution]

Hello David,

You have 3 choices and you already outlined the first choice.

• Second Choice: create another "view" for the Application Service table that accounts for the operational attributes you seek as opposed to the Service Mapping attributes that are part of their new UI. 
• Third Choice: create a new filtered navigation item that looks at the service table (cmdb_ci_service) where the Class = Application Service. This will give you the Application Service CI's only but the view will be from the cmdb_ci_service table instead of the Application service table. Since Application Service extends from the Service table you will be viewing/maintaining the same records but with the value of an operational view you seek.

The ITOM team is planning a fix to the view of Application Service in the Orlando time frame. Until then, either of the above would be acceptable but the 3rd option is less work over the long run. 

Hope this helps,

Scott

[dick1]

hi @scott.lemm although this is an older threat, Where doing at the moment the same 
where trying to allign more close to the csdm so usinge the Application service is key.
we made in the past the mistake to map our legacy to business application so this is to be corrected

looking at the class structure for applicatio_service_auto there are several sub classes.
can you give some ideas on how to use the sub classes or is it better to avoid this?

We don't use itom for disovery at the moment but might do this in the future

I see option like

 

What is the indended use of all these sub classes?