15 March 2016 blogs Klaas Hulder 3 min read
Before we can answer that question we first need to know what is meant by the terms ‘SCOM Distributed Application’ and ‘IT Service’.
Distributed Applications are an important feature within SCOM, and according to TechNet, they are defined as follows: ‘A Distributed Application in Operations Manager is an application that is comprised of multiple objects. These objects may be defined by different management packs and may be managed on the same agent or on different agents. The purpose of the distributed application is to provide an overall health for an application that is comprised of different objects.’
Such a clear definition is always nice, because it allows you to easily explain to others what is meant with a term like ‘SCOM Distributed Applications’.
With the term ‘IT service’, we are not that lucky. There are a lot of people trying to describe what they mean by an ‘IT Service’, but, unfortunately, I was not able to find a clear definition for this term. From ITIL we know ‘The IT service is provided by an IT service provider. An IT service is made up of a combination of information technology, people and processes.’ However, if you look further to the service types, they distinguish external facing, internal facing and supporting services.
ITIL refers to ‘supporting services’ as ‘as something that is needed, but despite it would help, could not generate direct revenues.’
For example, the Dynamic Host Configuration Protocol (DCHP) is designed to provide every user of the network with an IP address, so this could be seen as a supporting IT Service.
In the title you also see the word ‘model’. An important question when it comes to modeling is always: where and what are we going to use that model for? In our case, the model is used to administer dependencies between an IT Service and multiple objects on multiple computer systems. In a SCOM Distributed Application it is already possible to relate objects to an application.
That is one of the reasons why we chose to use the ‘SCOM Distributed Application’ as a base for our Live Maps Service Model.
With the dependency information between IT Services and IT Configuration Items, Live Maps can help support several ITIL processes. Like in the case of an ‘Incident’ or ‘Problem’, it is very easy to determine the affected IT Services; and in case of a ‘Change’ it is not hard to determine the business impact.
Because Live Maps can integrate with multiple ITSM solutions like ServiceNow, System Center Service Manager and in the near future BMC Remedy. it is also not hard to integrate this knowledge in your current IT management processes.
If you are interested in finding out more about Live Maps, you can schedule an online demo with our team of experts or try it yourself in your own environment.
Lead Developer- Savision
Klaas is Savision’s first employee. He has been working for Savision since it was founded by Dennis Rietvink and Douwe van de Voort in late 2006. At the moment he is leading the development team responsible for the development of Live Maps. He has over 17 years of software development experience working for banks, utility and telecom companies at EDS.
Klaas studied Information and Communication Technology in the Netherlands.