1. Management Partner Training 2004 MOM 2005 - MOM Connector Framework Vlad Joanovic Program Manager vladj@microsoft.com Vlad Joanovic Program Manager vladj@microsoft.com

2. Agenda Introduce MCF Current releases User Experience Architecture API Partners MOM Management Server API Summary

3. MOM Connector Framework Interoperability  Existing management system  Trouble-ticketing system Expose MOM and MP intelligence  Forwarding MOM alerts  Collecting alerts from other systems  Tracking which alerts have been forwarded  Synchronizing alerts  Exposing discovery data

4. Current Releases MOM Connector SP1 feature pack  MOM connector framework (MCF) web service  MOM to MOM product connector Product Connectors  MOM to Tivoli TEC  MOM to HP OVO  MOM to HP NNM Updated MOM SDK2 release  MOM to generic product connector  Samples and documentation

5. Connecting MOM Alerts Bi-Directionally To Other Management Framework Other Management Framework e.g. Tivoli, HPOV MOM 2005 Management Group Product Connector built on MCF Product Connector

6. When To Use MCF? Building integration with MOM that needs to be bi-directional? Often if no bi-directional integration is needed use the MOM Management Server Class Library If bi-directional integration is needed  Look for existing product connectors available  Start with the samples provided in the SDK

7. MCF Architecture MOM SP1 MOM 2005 MCF v1MCF v2 MOM to Tivoli TEC MOM to MOMMOM to Generic Tivoli TEC MOM SP1/2005 Xml file Product Connectors

8. Mom.Connector Namespace Used to expose Alerts and Discovery data programmatically Subscription based on Setup/Registration Allows MOM Alerts to be synchronized bi- directionally with another system Two types of product connectors  Move MOM alerts out and keep them in sync  Insert alerts into MOM and keep them in sync

9. MOM.Connector – MCF MethodsDescription Setup/Cleanup Used for product connector install and uninstall Setup returns a RegistrationId used in all other methods Product connector can specify the MOM Resolution State they are interested in Alerts are marked and put into this resolution state though existing MOM processes Initialize/Uninitialize Initialize or UnInitialize the “type” of product connector (NewAlerts, UpdatedAlerts, and DiscoveryData)

10. MOM.Connector – MCF MethodsDescription GetData Depending on type of connector either new alerts or updates are returned MCF performs all the business logic and caching so the Product Connector doesn’t have to AckData After product connector takes new alert or updated alert and successfully sends to other system it needs to be Acknowledged in MOM UpdateAlerts To update an alert in MOM when it changes; All the writeable alert fields can be specified here InsertAlerts To insert an alert from another system *RuleID is needed for knowledge and alert suppression to work

11. MOM.Connector – MCF ObjectsDescription DiscoveryData All computer attributes and other MOM service discovery data is exposed through GetData as collected by MOM management packs and used in attribute views, state view, and topology views Alert/AlertUpdate/ AlertInsert Alerts and updated alerts are exposed through GetData

12. User changes A1 – RS = 203 MCF In Action Timeline Product Connector User Alerts created A1, A2 Connector.Setup Connector.Initialize (dataflags) Connector.GetData System Product Connector: Registered for ResolutionState = 203, NewAlerts and Updates Product Connector Product Connector Product Connector Connector.GetData User changes A1 – adds owner No alerts returned A1 returned as a new alert A3 returned as a new alert A1 returned as an update Connector.AckData(A1) Connector.AckData(A1, A2) System A3 created Alert Rule - 203

13. MCF In Action

14. Life Of A Product Connector When alerts originate in MOM Setup (with a resolution state)  Initialize (with change flags)  GetData  AckData  GetData  AckData  UpdateAlert  Uninitialize Cleanup Alert cache is completely based on the Alerts that are specified Only alerts in the PCs cache can be updated Call GetData per some interval Call Update alert as needed

15. Life Of A Product Connector When alerts originate somewhere else Setup (without a resolution state)  Initialize (with change flags)  InsertAlert  UpdateAlert  GetData  AckData  Uninitialize Cleanup Alert cache is completely based on the Alerts inserted Call GetData per some interval Call Update alert as needed

16. What Is The Cost Of A PC? Depends on requirements  One way  Bi-directional flow  Alerts originate in MOM  Alerts originate in another system Can the sample be leveraged? Do APIs exist on the other system?  To insert, to update, to monitor for changes easily and distinguish from ALL items in the system Developer experience Complexity of business logic or retry logic

17. MCF Security Product connector needs to run as a user in the “MOM System” security group on MOM Management Server MCF web service can be setup using https  https:// \mcf\connectorservicev2.asmx

18. Performance Activity is measured/benchmarked per Management Group  Inserts  Updates MOM Connector Framework performance counter  Alert Insert Rate  Alert Update Rate

19. Versioning MOM SP1 – v1 MOM 2005 – v2  New alert properties  Better error handling  Optimistic concurrency  Discovery Data

20. Discovery Data Exposes class attributes collected through MOM service discovery data Used by the MMPC to enable the following on the Destination Management group  State view  Topology view  Computer group membership  Attribute views

21. Developing A Product Connector

22. MCF Partners Aprisma Dirigo eXc Software Maranti Networks Metilinx Skywire Software Smarts

23. MOM 2005 API Replaces the current WMI administration provider (root\mom) Programmatic Access to MOM data in the Operational database  Exposes operational data collected by MOM through management packs  Allows programmatic control of common MOM configuration settings  Available on the MOM Management Server within a management group  Security matches user experience when using Operator console or Management console Includes the following managed code namespaces  Microsoft.EnterpriseManagement.Mom  Microsoft.EnterpriseManagement.Mom.Connector  Microsoft.EnterpriseManagement.Mom.RuleRuntime

24. MOM 2005 SDK Scenarios Operational data scenarios  Reading all Events and performance data associated to a computer  Resolve an alert, updating an owner, adding a comment to the alert history, view the vendor, or company knowledge Configuration scenarios  Configure computers to be managed by mom by creating include/exclude computer discovery rules  Insert alerts against all computer types  Create computer groups, update sub-groups and specify include/exclude rules  Create and target overrides against computers and computer groups and obtain the resulting set of policy  Create, view, edit and delete console scopes  Put a computer in maintenance mode with a reason for a specified amount of time

25. MCL Architecture MOM Mgmt Server API DAS MOM DB Client (e.g., MOM 2005 Web console) Client (e.g., Operator Console task) Web services

26. Practical MCL Uses Tasks that run on the Operators Console (use web services) Managed code responses that run on the MOM Management Server  Available through tasks  Available through server rule responses (disabled by default)  Available to agent responses that target MOM Management Servers

27. MOM 2005 SDK Sample Obtaining all “New” alerts associated to “Domain\Computer” and assign to “Admin” and set the resolution state to “acknowledged” Using Microsoft.EnterpriseManagement.Mom; Administration momAdmin = Administration.GetAdministrationObject(); AlertQuery alertQuery = momAdmin.GetAlertQueryObject(); AlertsCollection alerts = alertQuery.GetAlertsByResolutionStateIdAndComputer(0, “Computer”, “Domain”); Foreach (Alert alert in alerts) { alert.OwnerName = “Admin”; alert.ResolutionState = 85; alert.Update(); }

28. EnterpriseManagement.MOM Main ObjectsDescription Administration This is the root administration class that all MCL clients must get an instance of. Everything from this object is scoped based on the domain\user of the current user credential Alert Read/Write access to the Alerts created through MOM management packs PerformanceData Read access to the performance data collected through MOM management packs Events Read access to the event data collected through MOM management packs Computer Exposes the computers managed by mom and allows inserting alerts; Events and performance data can be inserted for non- windows servers. Also exposes computer state Attribute Exposes attributes associated to the computer as collected through MOM management packs Overrides Exposes rule overrides and allows targets to be configured ComputerGroup Exposes computer groups and hierarchy including sub-groups; Also exposes state ConsoleScope Exposes configuring console scopes ComputerDiscovery Exposes configuring computer discovery rules associated to a management server Knowledge Exposes knowledge associated to an Alert GlobalQuery Main query object used to query for a particular type including Alert, PerformanceData, Event, and computer

29. Security All existing security rules and principles apply to the programmatic scenarios  MOM Users  Access to Alerts and Events  MOM Authors  Access to Rules, Overrides, and ComputerGroups  MOM Admins  Access to Computer and management tasks and scopes Use both object and method level security

30. Summary Connect and integrate MOM into the Enterprise  Process and data flow integration Customize MOM 2005 through the programmatic access to the operational data and configuration MCF documentss are in MSDN and will be released with samples and resources on  http://www.microsoft.com/mom/downloads/sdk/default. asp http://www.microsoft.com/mom/downloads/sdk/default. asp  http://beta.microsoft.com

31. Resources MOM Product Info http://www.microsoft.com/mom/ Management Packs http://www.microsoft.com/mom/downloads/managementpacks/ MOM Connector Framework (MCF) http://www.microsoft.com/mom/evaluation/mcf/ SDK http://www.microsoft.com/mom/downloads/sdk/ Community http://www.microsoft.com/mom/community/ MOM Partner http://www.microsoft.com/management/mma

32. Questions?

33. © 2003-2004 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.