ITOM Content Service use case
Summarize
Summary of ITOM Content Service use case
The ITOM Content Service enhances visibility into an organization’s application environment by improving the discovery and management of Application Configuration Items (CIs) within the Common Service Data Model (CSDM). Application CIs are crucial for supporting IT operations across multiple products such as Service Mapping, ITOM AIOps, IT Asset Management (ITAM), IT Service Management (ITSM), and Enterprise Architecture (EA).
Show less
Challenge
Organizations with numerous applications often struggle to maintain accurate and comprehensive visibility of their infrastructure. Traditional discovery methods like Discovery and Service Mapping Patterns rely on dedicated patterns for applications. Without these patterns, applications are only recorded in the Running Process table without product identification or CI creation. This lack of accurate application CIs limits the organization’s ability to:
- Bind CIs to monitoring alerts and incidents
- Schedule automated software upgrades
- Automate scripts for optimization or troubleshooting
- Perform impact and change impact assessments
- Create security workflows
Solution
ITOM Content Service improves discovery by tagging and classifying process fingerprints to identify the publisher, product, and key components of applications without relying on published pattern classifiers. This approach allows continuous content delivery outside of scheduled release cycles. For example, processes like E3DBEngine.exe can be tagged and converted into CIs on subsequent discovery scans even if no pattern is triggered.
Result
By using ITOM Content Service, organizations gain enhanced, continuous visibility into their complete application landscape. This leads to more accurate CI records and supports better monitoring, proactive IT actions, and ongoing optimization of the environment.
This ITOM Content Service use case demonstrates how organizations can achieve enhanced visibility into their environment.
Use case overview
The Application Configuration Items (CIs) class is a key component of an organization’s data platform within the Common Service Data Model (CSDM). Application CIs help log software activities and support critical IT operations.
- Service Mapping: Uses application CIs to create service maps
- ITOM AIOps: Monitors application health and resolves incidents using application CIs
- IT Asset Management (ITAM): Tracks and manages software applications and their associated licenses with application CIs
- IT Service Management (ITSM): Analyzes service impact and calculates blast radius with application CIs
- Enterprise Architecture (EA): Leverages application CIs to generate business outcomes
Challenge
A large organization with numerous applications requires accurate discovery. Managing application CIs is essential, yet the IT team finds it challenging to maintain visibility over its growing infrastructure.
ITOM Visibility offers several methods for discovering products within an organization’s infrastructure, such as Discovery and Service Mapping Patterns. This method provides detailed visibility into a product's information. When a wide range of applications is in use, not all can have a dedicated pattern. If an application does not have a dedicated pattern, discovery populates only the Running Process [cmdb_running_process] table without identifying the product or creating a CI for it.
- Bind CIs with monitoring alerts and open incidents regarding the CIs
- Schedule automated software upgrades
- Automate scripts to optimize or troubleshoot the product
- Perform impact assessments and change impact analysis
- Create security workflows
Solution
ITOM Content Service enhances the discovery process by tagging and classifying process fingerprints. This service provides details about the publisher, product, and the essential component of the CI. Unlike pattern-based discovery, ITOM Content Service identifies applications directly within the organization’s environment without requiring published pattern classifiers. This approach enables the continuous delivery of content without being constrained by a scheduled release cycle.
For example: Discovery identifies the Elipse Software E3 Database Engine process (E3DBEngine.exe) and lists it in the Running Process [cmdb_running_process] table. If the E3DBEngine.exe process classification condition isn’t set to trigger a pattern, it doesn't launch a pattern and a CI isn't created. However, with ITOM Content Service, the E3DBEngine.exe process is tagged and classified, enabling Discovery to turn the process into a CI during the next scan.
Result
Discovery using ITOM Content Service creates a CI record by tagging and classifying the publisher, product, and essential component for all applications in the organization’s environment. This method provides enhanced and continuous visibility into the application landscape, enabling effective monitoring, proactive actions, and ongoing optimization.