Microsoft SCOM Connector
This section of the documentation contains technical specifications about the connector that is implemented to link ASM Core and Microsoft SCOM systems.
Including:
The name of the .NET assembly file
Connection methodology
The resource and link types that can be discovered on the application
The attributes of each resource and link types that can be imported into the ASM Core Configuration Management Database (CMDB)
For compatibility and version support details, refer to the ASM Connector Matrix.
You should familiarize yourself with the information in Installing Connectors before installing any connectors, and read the Integration topics for more information on how to configure them.
Use Case Scenario
Purpose
An organization uses Microsoft SCOM to discover and maintain resources present in its organization networks. SCOM is also used to raise alerts about adverse events that occur on the supervised networks.
Role
The role of this connector is to expose the resources and their relationships in order to allow for population and ongoing consistency checks of the ASM Core CMDB. The connector also possesses an Event Management capability which allows for SCOM alerts to be integrated in shapes of calls/requests.
Connector Description
The table below provides a description of the Microsoft SCOM connector.
Information fields
Name
Connector
Microsoft SCOM <-> ASM Core
Third-party application
Microsoft SCOM
Assembly
Infra.Connector.SCOM.dll
Connector class
Infra.Connector.SCOM.SCOMConnector
Configuration file
Infra.Connector.SCOM.icnf
Connection methodology
SCOM SDK Service (Proprietary API)
Connection Parameters
The table below provides a description of the Microsoft SCOM connection parameters.
Parameters
Description
DB connection
SCOM SDK Service (Proprietary API)
DB Login ID
Database Login ID
DB password
Database password
Customization
This connector permits extensions to the schema through customization of the configuration file. The possible customizations are listed below. However, the customizations are not limited to these:
New resource types
New resource properties
New link types
Resource Types
All exposed resource types inherit from a specific “Entity” type. The list of descendent types represents what is available after a default install. Actual type lists may vary between SCOM instances. All descendent types may have additional type-specific fields.
All exposed resource types share the following properties:
Name
Path
Display Name
FullName
IsManaged
LastModified
HealthState
StateLastModified
IsAvailable
AvailabilityLastModified
InMaintenanceMode
MaintenanceModeLastModified
MonitoringClassIds
LeastDerivedNonAbstractMonitoringClassId
Id
ManagementGroupId
The resource types available for mappings are:
Logical Entity
Alert Notification Subscription Server
Application Component
Database
SQL Database
SQL 2000 DB
SQL 2005 DB
SQL 2008 DB
FTP Site
Unix Application Component
Web Site
Windows Application Component
Microsoft Audit Collection Services Collector
Microsoft Audit Collection Services Forwarder
SQL Component
SQL Agent
SQL 2000 Agent
SQL 2005 Agent
SQL 2008 Agent
SQL Agent Job
SQL 2000 Agent Job
SQL 2005 Agent Job
SQL 2008 Agent Job
SQL DB File
SQL 2005 DB File
SQL 2008 DB File
SQL DB File Group
SQL 2005 DB File Group
SQL 2008 DB File Group
SQL Distributor
SQL 2005 Distributor
SQL 2008 Distributor
SQL Publication
SQL 2005 Publication
SQL 2008 Publication
SQL Publisher
SQL 2005 Publisher
SQL 2008 Publisher
SQL Subscriber
SQL 2005 Subscriber
SQL 2008 Subscriber
SQL Subscription
SQL 2005 Subscription
SQL 2008 Subscription
Client Monitoring Entities
Agentless Exception Monitoring Entities
AEM Computer: DEPRECATED
AEM User
Application
Application Name and Application Version Identifiters
Crash Listener
Error group
Override Values For Error Group/Application
System Error Group
CEIP target
CEIP Data Listener Instance
Computer Role
Unix Computer Role
Windows Computer Role
Health Service Watcher Group
Health Service Watcher Group (Agent)
Health Service Watcher Group (Collection Management Server)
Health Service Watcher Group (Gateway Management Server)
Instance Group
All Business Critical Windows 2000 Clients
All Business Critical Windows Clients
All Business Critical Windows XP Clients
GLO - Active Directory Controllers
GLO - Database Servers
GLO - Managed Objects
GLO - Oracle Servers
GLO - SQL Servers
GLO - VMVC Machines
Windows Client Instances Group
Windows Server Instances Group
Network Device Group
OLE DB Data Source Group
Operations Manager Agent Group
Operations Manager Management Server Group
Site
SQL 2000 DB Engine Group
SQL 2005 DB Engine Group
SQL 2008 DB Engine Group
SQL Instances
SQL Server 2000 Databases
SystemCenter Operations Manager Operational Database Watchers Group
TCP Port Group
Web Application Perspective Group
Windows Cluster
Local Application
Unix Local Application
Unix Local Service
Generic Unix Service
Unix Service
Unix User Application
Windows Local Application
Base Monitored Process Class
Health Service
Agent
Management Server Agent
Management Server
Collection Server
Root Management Server
Data Warehouse Connection Server
Gateway
Site Management Server
Notification Subscription Server
Notification Server
Windows Cluster Service
Windows Local Service
Windows Service
Windows Service
Windows Service (svchost)
Windows User Application
Logical Hardware Component
Unix Logical Hardware Component
Disk Partition
Logical Disk
Network Adapter
Physical Disk
Processor
Windows Logical Hardware Component
Disk Partition
Disk Partition (Client)
Windows Client 2000 Disk Partition
Windows Client Vista Disk Partition
Windows Client XP Disk Partition
Disk Partition (Server)
Windows Server 2000 Disk Partition
Windows Server 2003 Disk Partition
Logical Disk
Logical Disk (Client)
Windows Client 2000 Logical Disk
Windows Client Vista Logical Disk
Windows Vista Client Aggregate Logical Disk
Windows Client XP Logical Disk
Logical Disk (Server)
Windows Server 2000 Logical Disk
Windows Server 2003 Logical Disk
Chassis (Rackable)
Chassis (Standalone)
Chassis (Storage)
Computer Hardware
Virtual Machine
Rack
Unix Supported Agents
SQL Role
SQL Analysis Services
SQL 2005 Analysis Services
SQL 2008 Analysis Services
SQL DB Engine
SQL 2000 DB Engine
SQL 2005 DB Engine
SQL 2008 DB Engine
SQL Integration Services
SQL 2005 Integration Services
SQL 2008 Integration Services
SQL Reporting Services
SQL 2005 Reporting Services
SQL 2008 Reporting Services
Data Set
Standard Data Set
Device
All Network Devices
SNMP Network Device
Computer
Unix Computer
Windows Computer
MOM 2005 Backward Compatibility Windows Computer
MOM 2005 Backward Compatibility Windows Client
MOM 2005 Backward Compatibility Windows Domain Controller
MOM 2005 Backward Compatibility Windows Server
System Center Managed Windows Computer
System Center Managed Computer (Client OS)
System Center Managed Computer (Server OS)
Windows Client
Windows Client 2000 Computer
Windows Client Vista Computer
Windows Vista Client Aggregate Computer
Windows Client XP Computer
Windows Server
Virtual Server
Windows Domain Controller
Windows Server 2000 Computer
Windows Server 2003 Computer
Distributed Application
Connected Management Group
Connector
Operations Manager Management Group
User Created Distributed Application
Blank
Line of Business Web Application
Messaging
Distributed Application Component
Directory Services
Messaging Clients
Messaging Components
Network Services
Physical Network
Storage
Web Application Databases
Web Application Web Sites
Group
Client Monitoring Data Group
Computer Group
All Business Critical Windows Vista Clients
All Windows Computers
Collection Management Server Computer Group
Gateway Management Server Computer Group
Management Server Computer Group
Root Management Server Computer Group
SQL 2000 Computers
SQL 2005 Computers
SQL 2005 Replication Computers
SQL 2008 Computers
SQL 2008 Replication Computers
SQL Computers
System Center Managed Computer Group
Agent Managed Computer Group
Agentless Managed Computer Group
System.Mom.BackwardCompatibility.ScriptDiscoveredComputerGroup
Unix Computer Group
Windows Client 2000 Computer Group
Windows Client Computer Group
Windows Client Vista Computer Group
Windows Client XP Computer Group
Windows Server 2000 Computer Group
Windows Server 2003 Computer Group
Windows Server Computer Group
Network Adapter
Network Adapter (Client)
Windows Client 2000 Network Adapter
Windows Client Vista Network Adapter
Windows Client XP Network Adapter
Network Adapter (Server)
Windows Server 2000 Network Adapter
Windows Server 2003 Network Adapter
Physical Disk
Physical Disk (Client)
Windows Client 2000 Physical Disk
Windows Client Vista Physical Disk
Windows Vista Client Aggregate Physical Disk
Windows Client XP Physical Disk
Physical Disk (Server)
Windows Server 2000 Physical Disk
Windows Server 2003 Physical Disk
Processor
Processor (Client)
Windows Client 2000 Processor
Windows Client Vista Processor
Windows Client XP Processor
Processor (Server)
Windows Server 2000 Processor
Windows Server 2003 Processor
Windows Vista Client Aggregate Physical DIMM
Microsoft System Center Data Warehouse
Operating System
Unix Operating System
Windows Operating System
Windows Client Operating System
Windows Client 2000 Operating System
Windows Client Vista Operating System
Windows Client XP Operating System
Windows Server Operating System
Windows Server 2000 Operating System
Windows Server 2003 Operating System
Perspective
Health Service Watcher
Health Service Watcher (Agent)
Health Service Watcher (Management Server)
Health Service Watcher (Collection Management Server)
Health Service Watcher (Gateway Management Server)
Health Service Watcher (Site Management Server)
OLE DB check Perspective
SQL DB Perspective
SystemCenter Operations Manager Operational Database Watcher
TCP port check Perspective
User Action Manager
Agent Manager
Web Application Perspective
Software Installation
Unix Software Installation
Windows Software Installation
Physical Entity
Hardware Component
Fan
Modem
Physical Disk
Physical NIC
Port
Power Supply
Processor
StorageArrayController
Video Card
Virtual Hardware Component
Hardware Enclosure
Blade
Blade (Network)
Blade (Server)
Chassis
Blade Chassis
Blade Chassis (Network)
Blade Chassis (Server)
Link Types
The table below provides all the SCOM link types that are exposed by the ASM Core Microsoft SCOM Connector.
Description
Resource Type A
Resource Type B
Entity Watched By Perspective
Entity
Perspective
Windows Computer Hosts Windows Computer Role Relationship Type
Windows Computer
Windows Computer Role
Windows Computer Hosts Windows Software Installation Relationship Type
Windows Computer
Windows Software Installation
Windows Computer Hosts Windows Logical Hardware Relationship Type
Windows Computer
Windows Logical Hardware Component
Windows Computer Hosts Windows Operating System Relationship Type
Windows Computer
Windows Operating System
Windows Computer Hosts Windows Local Application Relationship Type
Windows Computer
Windows Local Application
Health Service Watcher Monitors Health Service
Health Service Watcher
Health Service
Management Group contains Management Server
Operations Manager Management Group
Management Server
Group contains Computers
Computer Group
Computer
Management Group contains Operational Database Watchers Group
Operations Manager Management Group
SystemCenter Operations Manager Operational Database Watchers Group
Site Membership
Site
Entity
Health Service should manage Entity
Health Service
Entity
Computer hosts System Center Operations Manager Operational Database Watchers Group
Windows Computer
SystemCenter Operations Manager Operational Database Watcher
Database Watchers Group contains Operational Database Watchers
SystemCenter Operations Manager Operational Database Watchers Group
SystemCenter Operations Manager Operational Database Watcher
Management Group contains Agent
Operations Manager Management Group
Agent
Microsoft.SystemCenter.InstanceGroupContainsEntities
Instance Group
Entity
Microsoft.SystemCenter.ServiceDesigner.Messaging. MessagingServiceContainsPhysicalNetwork
Messaging
Physical Network
Microsoft.SystemCenter.ServiceDesigner.Messaging. MessagingServiceContainsMessagingComponents
Messaging
Messaging Components
Microsoft.SystemCenter.ServiceDesigner. Messaging.StorageReferencesPhysicalNetwork
Storage
Physical Network
Microsoft.SystemCenter.ServiceDesigner.Messaging. MessagingComponentsReferencesNetworkServices
Messaging Components
Network Services
Microsoft.SystemCenter.ServiceDesigner. Messaging.NetworkServicesReferencesPhysicalNetwork
Network Services
Physical Network
Microsoft.SystemCenter.ServiceDesigner.Messaging. MessagingClientsGroupContainsPerspective
Messaging Clients
Perspective
Microsoft.SystemCenter.ServiceDesigner.Messaging. DirectoryServicesReferencesPhysicalNetwork
Directory Services
Physical Network
Microsoft.SystemCenter.ServiceDesigner. WebSiteGroupContainsWebSite
Web Application Web Sites
Web Site
Microsoft.SystemCenter.ServiceDesigner.Messaging. StorageGroupContainsLogicalHardware
Storage
Logical Hardware Component
Microsoft.SystemCenter.ServiceDesigner.Messaging. MessagingServiceContainsStorage
Messaging
Storage
Microsoft.SystemCenter.ServiceDesigner.Messaging. DirectoryServicesGroupContainsComputerRole
Directory Services
Computer Role
Microsoft.SystemCenter.ServiceDesigner.Messaging. MessagingServiceContainsMessagingClients
Messaging
Messaging Clients
Microsoft.SystemCenter.ServiceDesigner.Messaging. MessagingClientReferencesMessagingComponents
Messaging Clients
Messaging Components
Microsoft.SystemCenter.ServiceDesigner.Messaging. MessagingComponentsReferencesPhysicalNetwork
Messaging Components
Physical Network
Microsoft.SystemCenter.ServiceDesigner.Messaging. MessagingServiceContainsDirectoryServices
Messaging
Directory Services
Microsoft.SystemCenter.ServiceDesigner.Messaging. MessagingComponentsReferencesStorage
Messaging Components
Storage
Microsoft.SystemCenter.ServiceDesigner.Messaging. PhysicalNetworkGroupContainsNetworkDevice
Physical Network
All Network Devices
Microsoft.SystemCenter.ServiceDesigner.Messaging. MessagingComponentsGroupContainsMailStore
Messaging Components
Local Application
Microsoft.SystemCenter.ServiceDesigner. DatabaseGroupContainsDatabase
Web Application Databases
Database
Microsoft.SystemCenter.ServiceDesigner. WebSiteReferencesDatabase
Web Application Web Sites
Web Application Databases
Microsoft.SystemCenter.ServiceDesigner. WebApplicationContainsDatabaseGroup
Line of Business Web Application
Web Application Databases
Microsoft.SystemCenter.ServiceDesigner.Messaging. StorageGroupContainsPhysicalHardware
Storage
Physical Entity
Microsoft.SystemCenter.ServiceDesigner. WebApplicationContainsWebSiteGroup
Line of Business Web Application
Web Application Web Sites
Microsoft.SystemCenter.ServiceDesigner.Messaging. MessagingServiceContainsNetworkServices
Messaging
Network Services
Microsoft.SystemCenter.ServiceDesigner.Messaging. NetworkServicesGroupContainsComputerRole
Network Services
Computer Role
Microsoft.SystemCenter.ServiceDesigner.Messaging. DirectoryServicesReferencesNetworkServices
Directory Services
Network Services
Microsoft.SystemCenter.ServiceDesigner.Messaging. MessagingComponentsReferencesDirectoryServices
Messaging Components
Directory Services
Data Warehouse contains data set
Microsoft System Center Data Warehouse
Data Set
Application Hosts Error Group
Application
Error Group
Management Server Hosts CEIP Listener
Management Server
CEIP Data Listener Instance
Management Server Hosts Crash Listener
Management Server
Crash Listener
Client Monitoring Group Contains All Client Monitoring Data
Client Monitoring Data Group
Client Monitoring Entities
Management Server Group contains Management Servers
Operations Manager Management Server Group
Management Server
Agent Group contains Agents
Operations Manager Agent Group
Agent
Computer hosts Web Application Perspective
Windows Computer
Web Application Perspective
Network Device Group Contains Network Devices
Network Device Group
SNMP Network Device
TCP Port Group Contains TCP Port Perspective
TCP Port Group
TCP port check Perspective
OLE DB Data Source Group Contains OLE DB Data Source Perspective
OLE DB Data Source Group
OLE DB check Perspective
Computer hosts OLE DB check Perspective
Windows Computer
OLE DB check Perspective
Computer hosts TCP port check Perspective
Windows Computer
TCP port check Perspective
Disk Partition Contains Logical Disk
Windows Client XP Disk Partition
Windows Client XP Logical Disk
Physical Disk Contains Disk Partition
Windows Client XP Physical Disk
Windows Client XP Disk Partition
Physical Disk Contains Disk Partition
Windows Client 2000 Physical Disk
Windows Client 2000 Disk Partition
Disk Partition Contains Logical Disk
Windows Client 2000 Disk Partition
Windows Client 2000 Logical Disk
Disk Partition Contains Logical Disk
Windows Client Vista Disk Partition
Windows Client Vista Logical Disk
Physical Disk Contains Disk Partition
Windows Client Vista Physical Disk
Windows Client Vista Disk Partition
Microsoft Windows Computer Hosts Microsoft Audit Collection Services Collector
Windows Computer
Microsoft Audit Collection Services Collector
Microsoft Windows Computer Hosts Microsoft Audit Collection Services Forwarder
Windows Computer
Microsoft Audit Collection Services Forwarder
SQL Database Engine Hosts SQL Database
SQL DB Engine
SQL Database
Instance Group Contains All Instances of SQL DBEngine
SQL Instances
SQL DB Engine
Windows Computer Hosts Database Perspective
Windows Computer
SQL DB Perspective
SQL Server 2008 Instance Group Contains Instances
SQL 2008 DB Engine Group
SQL 2008 DB Engine
SQL 2008 Database Engine Hosts Subscriber
SQL 2008 DB Engine
SQL 2008 Subscriber
SQL 2008 Database Engine Hosts SQL 2008 Agent
SQL 2008 DB Engine
SQL 2008 Agent
SQL 2008 Database Hosts Subscription
SQL 2008 DB
SQL 2008 Subscription
SQL 2008 Distributer Contains SQL 2008 Database
SQL 2008 Distributor
SQL 2008 DB
SQL 2008 Database Hosts Publication
SQL 2008 DB
SQL 2008 Publication
SQL 2008 Database Engine Hosts Distributor
SQL 2008 DB Engine
SQL 2008 Distributor
SQL Server 2008 Database Hosts File Group
SQL 2008 DB
SQL 2008 DB File Group
SQL 2008 Agent Hosts Agent Job
SQL 2008 Agent
SQL 2008 Agent Job
SQL 2008 Database File Runs on Logical Disk
SQL 2008 DB File
Logical Disk
SQL 2008 Database Engine Hosts Publisher
SQL 2008 DB Engine
SQL 2008 Publisher
SQL Server 2008 File Group Hosts File
SQL 2008 DB File Group
SQL 2008 DB File
SQL 2005 Database File Runs on Logical Disk
SQL 2005 DB File
Logical Disk
SQL 2005 Database Engine Hosts Distributor
SQL 2005 DB Engine
SQL 2005 Distributor
SQL 2005 Agent Hosts Agent Job
SQL 2005 Agent
SQL 2005 Agent Job
SQL 2005 Database Engine Hosts Subscriber
SQL 2005 DB Engine
SQL 2005 Subscriber
SQL Server 2005 Database Hosts File Group
SQL 2005 DB
SQL 2005 DB File Group
SQL 2005 Database Engine Hosts Publisher
SQL 2005 DB Engine
SQL 2005 Publisher
SQL 2005 Database Hosts Subscription
SQL 2005 DB
SQL 2005 Subscription
SQL 2005 Database Engine Hosts SQL 2005 Agent
SQL 2005 DB Engine
SQL 2005 Agent
SQL 2005 Database Hosts Publication
SQL 2005 DB
SQL 2005 Publication
SQL 2005 Distributer Contains SQL 2005 Database
SQL 2005 Distributor
SQL 2005 DB
SQL Server 2005 Instance Group Contains Instances
SQL 2005 DB Engine Group
SQL 2005 DB Engine
SQL Server 2005 File Group Hosts File
SQL 2005 DB File Group
SQL 2005 DB File
SQL Server 2000 Hosts SQL Agent
SQL 2000 DB Engine
SQL 2000 Agent
SQL 2000 Agent Hosts Agent Job
SQL 2000 Agent
SQL 2000 Agent Job
SQL Server 2000 Database Engine Group Contains Database Engines
SQL 2000 DB Engine Group
SQL 2000 DB Engine
SQL Server 2000 Database Group Contains Databases
SQL Server 2000 Databases
SQL 2000 DB
Disk Partition Contains Logical Disk
Disk Partition
Logical Disk
Unix Computer Hosts Unix Operating System Relationship Type
Unix Computer
Unix Operating System
Physical Disk Contains Disk Partition
Physical Disk
Disk Partition
Computer Hosts Logical Hardware Relationship Type
Unix Computer
Unix Logical Hardware Component
Unix Computer Hosts Unix Local Application Relationship Type
Unix Computer
Unix Local Application
Unix Computer Hosts Unix Computer Role Relationship Type
Unix Computer
Unix Computer Role
Unix Computer Hosts Unix Software Installation Relationship Type
Unix Computer
Unix Software Installation
Disk Partition Contains Logical Disk
Windows Server 2000 Disk Partition
Windows Server 2000 Logical Disk
Physical Disk Contains Disk Partition
Windows Server 2000 Physical Disk
Windows Server 2000 Disk Partition
Physical Disk Contains Disk Partition
Windows Server 2003 Physical Disk
Windows Server 2003 Disk Partition
Disk Partition Contains Logical Disk
Windows Server 2003 Disk Partition
Windows Server 2003 Logical Disk
Event Management
This section provides information about the Event Management capability of the SCOM connector.
Functionality Overview
The purpose of this functionality is to:
Automatically transpose alerts generated by SCOM into ASM Core calls or requests.
Maintain the consistency of the information held in the SCOM alert and in the item created in ASM Core.
Event Management Operation
The operation of this functionality relies on the connector monitoring the SCOM alerts in order to detect any new alerts. When such event occurs, the Integration Platform automatically compares the attributes of the new alert against some user-defined criteria. In case criteria are met, the platform proceeds with the creation of a call/problem or a request depending on the user settings.
From a practical point of view, SCOM alert attributes can be mapped to ASM Core fields. This mapping is used when creating a new call or request. Upon creation, the ASM Core call or request ID is sent back to SCOM and the appropriate alert record is updated to reflect the ID of the item that has been created in.
As the alert is updated, the connector ensures that these modifications are properly transmitted to the related ASM Core item. The current behavior of ASM Core, upon receipt of such updates and notifications, depends on the Event Mapping settings that are configured in ASM Core.
Eventually, physical actions on the network will be taken to fix the issue and the SCOM alert will be marked as Inactive or will disappear from its queue. This fact will also be transmitted to the relevant ASM Core item and the final result (Call Updated, Call Closed and so on) will again depend on the Event Mapping settings in ASM Core.
Specific Use Case
The following use case describes the scenario where an organization sets up integration between ASM Core and Microsoft SCOM. In this scenario, ASM Core is responsible for Service Desk and Change operations and SCOM is responsible for issuing alerts.
Use case scenario
Action
Event Management transaction
SCOM sends an alert to ASM Core
ASM Core logs a call with this information and automatically forwards the call to the Incident Management group. The analyst takes over the call and clicks the Acknowledge Event button.
ASM Core sends an Acknowledgement transaction to SCOM
Event Management and Transactions
The use case scenario in the previous section, and more generally the Event Management operation of the connector, rely on a particular communication protocol between the two systems. This protocol is composed of different transactions that are detailed below.
The transactions and their descriptions are listed below.
Event Management transactions
Description
Receive
An alert is sent from an external system to ASM Core. ASM Core receives this alert.
Acknowledge
ASM Core sends a transaction to an external system with a formal statement acknowledging that their alert has been received.
This is different from a transactional acknowledge/not acknowledge (ack/nack) note sent between systems.
Notify
Occurs when there is a call or request within ASM Core logged due to an alert sent from an external system:
Notification is initiated from ASM Core to the external system after an analyst adds a note to the call or request.
Notification is initiated from an external system and is sent to ASM Core as a NOTIFY event. It is either added as a note or ignored, depending on the settings in the Event Mapping screen.
Update
Occurs when there is a call or request within ASM Core logged due to an alert sent from an external system:
From ASM Core, an Update is created and sent to the external system when an analyst updates a call / request by forwarding Internally, Externally, Deferring, or Saving to the database.
From the external system, an UPDATE message is sent to ASM Core any time an alert related to a call in ASM Core is modified. Either the ASM Core call/request is physically closed, a note added, or it is ignored, depending on the settings in the Event Mapping screen.
Resolve
Occurs when the alert has been resolved in the external system and a Resolve transaction is sent to ASM Core. Either the ASM Core call/request is physically closed, a note is added, or it is ignored, depending on the settings in the Event Mapping screen.
Delete
Occurs when the alert is no longer valid on the external system (for example, the alert sent of the root cause with 60% certainty has been superseded by a more accurate root cause at 90% certainty). It also informs ASM Core through a transaction. Either the ASM Core call/request is physically closed, a note is added, or it is ignored, depending on the settings in the Event Mapping screen.
Business Rules
The table below defines some business rules that specifically apply to the SCOM integration.
Transaction
Rules
Receive
The Receive transaction leads to a new call being logged, a new problem being created or a request being initiated depending on Integration Platform settings.
A reliable unique ID is stored against any specific call created to ensure proper management of the subsequent communications
Any possible data in relation with the time or date of the alert is made available to ASM Core. This allows for possible back-dating of any call or problem logged in ASM Core after it receives a Receive message from SCOM.
There are no business rules for the other transaction types.
Setting up the Event Management Functionality
Check the following items when setting up the Event Management functionality of the SCOM Connector:
Ensure that the Event Management checkbox is selected in the Integration Platform settings window.
Ensure that the SCOM Connector is installed and the check boxes in the Events and Visible columns are selected in the Integration Connectors window.
Ensure that a SCOM source is defined in the Integration Source window.
Ensure that a SCOM Event mapping is defined in the Event screen. This mapping should at least specify the action to be performed (log call/create request) when a notification is carried over, as well as the template to be used for this action.
Starting the Event Management Functionality
If the Event Management checkbox in the Integration Platform administration screen is selected, the Event Management functionality starts running as soon as a proper Event mapping is completed and saved. When starting, the connector immediately connects to SCOM system and logs a call/request for every alert that is present and fulfills the criteria that are implemented in the Event mapping. This can lead to a large number of calls/requests being created when activating the Event Management functionality.
One solution to avoid this behavior is to include in the Event criteria setting an item based on the TimeRaised attribute. For example, you could plan to “go live” with Event management on a precise date and, as a consequence, specify that the value of TimeRaised has to be after this date before any action can be triggered in ASM Core.
SCOM Alert Attributes
The table below lists all the SCOM alert attributes that are exposed by the ASM Core Microsoft SCOM Connector.
Key
Display
Data Type
Is Multi Valued
Id
Id
string
False
Name
Name
string
False
Description
Description
string
False
MonitoringObjectDisplayName
MonitoringObjectDisplayName
string
False
MonitoringObjectName
MonitoringObjectName
string
False
MonitoringObjectPath
MonitoringObjectPath
string
False
MonitoringObjectFullName
MonitoringObjectFullName
string
False
IsMonitorAlert
IsMonitorAlert
bool
False
ProblemId
ProblemId
string
False
MonitoringRuleId
MonitoringRuleId
string
False
ResolutionState
ResolutionState
profile
False
Priority
Priority
profile
False
Severity
Severity
profile
False
Category
Category
profile
False
Owner
Owner
string
False
ResolvedBy
ResolvedBy
string
False
TimeRaised
TimeRaised
dateTime
False
TimeAdded
TimeAdded
dateTime
False
LastModified
LastModified
dateTime
False
LastModifiedBy
LastModifiedBy
string
False
TimeResolved
TimeResolved
string
False
TimeResolutionStateLastModified
TimeResolutionStateLastModified
dateTime
False
CustomField1
CustomField1
string
False
CustomField2
CustomField2
string
False
CustomField3
CustomField3
string
False
CustomField4
CustomField4
string
False
CustomField5
CustomField5
string
False
CustomField6
CustomField6
string
False
CustomField7
CustomField7
string
False
CustomField8
CustomField8
string
False
CustomField9
CustomField9
string
False
CustomField10
CustomField10
string
False
TicketId
TicketId
string
False
Context
Context
string
False
ConnectorId
ConnectorId
string
False
LastModifiedByNonConnector
LastModifiedByNonConnector
dateTime
False
MonitoringObjectInMaintenanceMode
MonitoringObjectInMaintenanceMode
bool
False
MonitoringObjectHealthState
MonitoringObjectHealthState
profile
False
ConnectorStatus
ConnectorStatus
profile
False
RepeatCount
RepeatCount
int
False
NetbiosComputerName
NetbiosComputerName
string
False
NetbiosDomainName
NetbiosDomainName
string
False
PrincipalName
PrincipalName
string
False
SiteName
SiteName
string
False
MaintenanceModeLastModified
MaintenanceModeLastModified
dateTime
False
StateLastModified
StateLastModified
dateTime
False
Parameters
Parameters
string
False
ManagementGroupId
ManagementGroupId
string
False
MonitoredObject
MonitoredObject
entityReference
False
Last updated
Was this helpful?