Interoperability Connectors for Microsoft System Center

Kevin MuldoonSenior Program ManagerMicrosoft CorporationMGT307

Agenda

Challenges Addressed / Key CapabilitiesWhy Interop ArchitectureOperations Manager 2007 R2 Connectors

Product FeaturesUniversal Connector Demo

Service Manager ConnectorsRoadmap

System Center Interoperability

Challenges Addressed

• Utilize multiple tools to manage IT environments• Management cannot see health

of IT investment in one place• Administrators need to be

experts in multiple technologies to handle issues from different sources• Help desk tickets manually

transcribed to incident management systems

• Interoperate with enterprise management & incident management systems• Forward alerts from SCOM 2007 R2

to enterprise management & incident management systems to create events and incidents• Inter-twining of tools/processes

to produce an effective, efficient solution

Key Capabilities

Windows Server 2003

Microsoft System Center Operations

Manager 2007

Windows Server 2003

HP Openview

Windows Server 2003

IBM Tivoli

TEC Connector for HP OpenView

TEC Connector for IBM Tivoli

IIS Web Server is unavailableApplication Pool is unavailable

Apache server is not runningNetwork Adapter state

Connector for HP OpenView

Connector for IBM TEC

CfgMgr

Why Interop for System Center?Interoperate with other Enterprise Management and Ticketing systems

Integrate alerting data and asset information into their Enterprise Operations workflow

Ability to receive inbound alert, asset, and health data

OpsMgr

SvcMgr

System Center Interop

Interoperate with other Enterprise Management and Ticketing systems

Interoperate with other CMDB’s and Ticketing systems

Interoperate with other CMDB’s and Ticketing systems

Manager of Managers Integration

Provide alerting data from Operations Manager into the top level Enterprise Management System

Enables creation of tickets on 3rd party systems upon incident detectionSync of alert information between both systems

Provide ticketing data from Service Manager into the Enterprise level ticketing system

System Center Interop Architecture

Common across System Center Cross Platform & Interop

Microsoft is active on the OpenPegasus steering committee

Our commitment to using open source technology

WS-Man (OpenPegasus)

OpsMgrProviders

ConnectorProviders

OpsMgr SvcMgr

WS-Man WS-Man

OSResources

TEC, OVORemedy, Universal

CIMOM (OpenPegasus)

Systems Center Interop Architecture Flow Operations Manager

OpsMgr EMS

Connector Service

OpsMgr SDK

Public APIs, i.e., GetMonitoringAlerts

Systems Center Interop Architecture Flow Operations Manager

OpsMgr EMS

Connector Service

OpsMgr SDK

WinRM Open Pegasus

Public APIs, i.e., GetMonitoringAlerts

Systems Center Interop Architecture Flow Operations Manager

OpsMgr EMS

Connector Service

OpsMgr SDK

WinRM Open Pegasus

winrm invoke CreateEvt http://schemas.microsoft.com/wbem/wscim/1/cim-schema/2/SCX_Connector@{<alert/event details>} –r: https://<remote system>:1270 -u:<User> -p:<Password>

Public APIs, i.e., GetMonitoringAlerts

Systems Center Interop Architecture Flow Operations Manager

OpsMgr EMS

Connector Service

OpsMgr SDK

WinRM Open Pegasus

Interop Provider

Public APIs, i.e., GetMonitoringAlerts EMS APIs

winrm invoke CreateEvt http://schemas.microsoft.com/wbem/wscim/1/cim-schema/2/SCX_Connector@{<alert/event details>} –r: https://<remote system>:1270 -u:<User> -p:<Password>

System Center Operations Manager 2007 R2 Connectors

Operations Manager 2007 R2 Connector

EMS Version EMS OS Platform

IBM Tivoli Enterprise Console (TEC) - Tivoli Framework 4.1 & 4.1.1- TEC 3.9

- Windows 2003- Solaris 10- AIX 5.3

HP OpenView Operations for Windows - OVO/W 7.5- OVO/W 8.x

- Windows 2003

HP OpenView Operations for Unix - OVO/U 7.2- OVO/U 8.x

- HPUX 11i v3 Itanium & PA-RISC- HPUX 11i v2 Itanium & PA-RISC- Solaris 10

BMC Remedy ARS - ARS 6.3- ARS 7.1

- Windows 2003 *(supports remote connection to unix/linux platforms)

Universal Not Applicable - Windows 2003 - Windows 2008- Solaris 10- AIX 5.3- HPUX 11i v3 Itanium & PA-RISC- HPUX 11i v2 Itanium & PA-RISC- RHEL 5- SLES 10

Operations Manager 2007 R2Universal ConnectorWhat is it?Enables Operations Manager 2007 R2 to share alert data with any remote systemEnables customers to develop custom integration logic on the remote system to process the received alert dataProvides bi-directional synchronization once the alert has been forwarded to the remote system

Accept data from updates on the remote system in a standard format

Utilize XML for Windows based remote systems and Unix property files for unix/linux based remote systems for data exchange

Includes a Configuration UI for selecting what alert data should be forwarded

WS-Man used for secure communication

Systems Center Interop Architecture Flow Universal Connector

OpsMgr EMS

Connector Service

OpsMgr SDK

WinRM Open Pegasus

Public APIs, i.e., GetMonitoringAlerts Custom Integration Logic

winrm invoke CreateEvt http://schemas.microsoft.com/wbem/wscim/1/cim-schema/2/SCX_Connector@{<alert/event details>} –r: https://<remote system>:1270 -u:<User> -p:<Password>

Integration

Adapter

Interop Provider

Operations Manager 2007 R2 Universal ConnectorProcessing Flow

New alert forwarded to remote system in either XML or Unix Property file format

Provider on remote system creates a file (xml or property file) in a specified directory (%ProviderInstallDirectory%\UnvEvents\FromOpsMgr)

Customer’s integration picks up file from specified directory and inserts data into customer’s application

Customer’s integration creates a file in a specified directory with specific data to update Operations Manager alert, i.e.. TicketID, owner, custom fields (%ProviderInstallDirectory%\UnvEvents\%ManagementGroup%)

Universal Provider picks up Customer’s integration file and sends it back to Operations Manager to update alert

Operations Manager 2007 R2 Universal Connector

demo

Operations Manager 2007 R2 Interop ConnectorsTechNet Forums

Interop – Generalhttp://social.technet.microsoft.com/forums/en-US/interopgeneral/threads/

Interop – Tivoli Enterprise Console Connectorhttp://social.technet.microsoft.com/Forums/en-US/interoptivoli/threads/

Interop – HP OpenView Operations Connectorhttp://social.technet.microsoft.com/Forums/en-US/interophpoperationsmanager/threads/

Interop – BMC Remedy ARS Connectorhttp://social.technet.microsoft.com/Forums/en-US/interopremedy/threads/

Interop – Universal Connectorhttp://social.technet.microsoft.com/Forums/en-US/interopuniversalconnector/threads/

Service Manager ConnectorsConnectors Scenarios

Universal “Inbound” Incident Creation

Create incidents in SCSM from eventing sources Create incidents in SCSM from trouble ticketing sourcesBi-directional synchronization of incident updates in SCSM and the event/trouble ticket in the remote system

HP Service Manager

BMC Remedy & Atrium CMDB

Forward incidents from SCSM to remote service desk to create a new incidentCreate incidents in SCSM from incidents forwarded from remote service deskBi-directional synchronization of incident updates between SCSM and the remote service desk

Service Manager ConnectorsUniversal Inbound Use Cases

Forward events/alerts from monitoring sources (such as HP OM for Windows) into SCSM to create incidents

Forward trouble tickets/incidents from other help desk sources into SCSM to create incidents

Bi-directional synchronization of the event/incident updates throughout the life of the event/incident

Ability to extend the incident class with the necessary data from the remote system

Ability to route newly created incidents to the appropriate support group/person based on data in the incident

System Center Interop RoadmapSystem Center Operations Manager Connectors Scenarios

HP Service ManagerForward alerts to create incidents in remote incident management system

Bi-directional synchronization of alerts and incidents between SCOM and the remote incident management system

IBM OMNIBus/Netcool

Forward alerts to create events in remote EMS

Bi-directional synchronization of alerts and events between SCOM and the remote EMS

Universal “Inbound” Forward events from remote EMS to create alerts in SCOM

Bi-directional synchronization of alerts and events between SCOM and the remote EMS

System Center Interoperability

Microsoft

PartnersCAEMCIBMInfrontiWaveQuestOpalisSeamless

SCOM

SCSM

SCCM

IBM TEC

HP OVO / OM

CA Uni-

center

BMC Remed

y

HP Service Manag

er

IBM Netcoo

l

BMC Remed

y

HP Service Manag

erMS

Visual Studio

TFS

MS Dynami

cs

Uni-versal

IBM Netcoo

l

Uni-versalInboun

d

EMC Smarts

BMC Patrol

HP CMDB

BMC Atrium CMDB

BMC Event Mgr

HP Service Center

CA ServiceDesk

CA CMDB

CA Spectru

m

HP Service Desk

Alarm-Point

MS Project

question & answer

www.microsoft.com/teched

Sessions On-Demand & Community

http://microsoft.com/technet

Resources for IT Professionals

http://microsoft.com/msdn

Resources for Developers

www.microsoft.com/learning

Microsoft Certification & Training Resources

Resources

Complete an evaluation on CommNet and enter to win an Xbox 360 Elite!

© 2009 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS,

IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.