If you have not seen it yet, Microsoft has now released a number of connectors for Ops Mgr 2007 R2. The System Center Operations Manager 2007 R2 Connectors provide System Center Operations Manager 2007 R2 alert forwarding to remote systems, such as an Enterprise Management System (EMS) or service desk system.Â One of the connectors that Microsoft has released is the universal connector,Â aÂ connector that can be installed and configured for potentially any remote system that is hosted on a Windows system or on a supported UNIX system. More info and download here.
Each deployed OperationsÂ ManagerÂ 2007Â R2 Connector has the following components:
Interop Provider â€“ This service is installed on a Windows or UNIX server in a supported remote system environment and is automatically started at install. The Interop Provider receives alerts from the Connector Service in the OperationsÂ ManagerÂ 2007Â R2 environment and forwards them to the supported remote system through APIs of that system. The Interop Provider also sends updates on those events back to the Connector Service. Connector Service â€“ This service is installed on a server in the OperationsÂ ManagerÂ 2007Â R2 environment and is automatically started after configuration is completed. The Connector Service gathers alerts from the OperationsÂ ManagerÂ 2007Â R2 RMS and sends them to the Interop Provider that is installed on a remote system server. The Connector Service also receives updates from that Interop Provider for remote system events that were created from Operations Manager alerts. Connector Configuration UI â€“ This configuration dialog box is installed on a server on which an OperationsÂ ManagerÂ 2007Â R2 console is installed, and it becomes an integrated component in that console. Use the Connector Configuration dialog box to configure communications for OperationsÂ ManagerÂ 2007Â R2 servers with remote system servers. Tabs on the Connector Configuration dialog box also provide for mapping Operations Manager alert properties to properties of the remote systemâ€™s events and for configuring the High Availability feature.
The installation was pretty simple, the manual explain the different steps in a good way. You install the “Interop Provider”Â and theÂ connector service.Â The connector configuration UI needs to be installed on a machine with the Ops Mgr R2 console as there is a integration between the two. It is not possible to upgrade any pre-RTM version of the connector, so if you have been running a pre-RTM version make sure you uninstall it before you tries to install the RTM version. When the installation is complete you will see a new connector in the console
On the Ops Mgr Universal Connector you can configure where your EMS server is, how ofter to synchronize, where your Ops Mgr server is and of course which alert fields to synchronize. You will also see a new connector under Internal Connectors. This is where you can configure which alerts that will be forwarded to the EMS server. With default settings all alerts are forwarded.
When a new alert is generated a XML file will be generated on the EMS server side. In this example I generate an alert for a event in the event viewer.
As you can see below, the alert has ID 8f474850-7308-41f8-ba40-0fb27b72084e, and there are XML files generated for the alert. The filesnameÂ is <AlertID>.Â <sequence number>.XML. The sequence number starting at 1, is added so that if an alert is forwarded and not processed in a timely manner of if an alert is updated multiple times in a short time period, the files are not overwritten. Overwritting the files could result in lose updates. It is important that the EMS system process the file with the lower numbers first so that the sequence of activities is not lost. Note that if you get two alerts at the same time they will be named <AlertID001>.1.XML and <AlertID002>.2.XML, the .X. number is common for the management group, and not a sequence number of each alert ID.
The next step is that the remote system needs to acknowledge (event type = 2) the alert back to Ops Mgr. This is done with a new XML file. Dont forget to delete the first XML file, so you dont process it again.
If you then want to update (event type = 1)Â the alert you generate a new XML file, in the following example the resolution state is set to 100. You can use the same XML code to update the resolution state to 255, in other words close an alert.
There are a couple of different event types you can use with the universal connector
- <EventType>0</EventType>Â = NewÂ Ops MgrÂ alert being forwarded
- <EventType>1</EventType> = Update to an Ops Mgr alert being forwarded to the remote system or update to the event/ticket on a remote system being forwarded to Ops Mgr
- <EventType>2</EventType> = Remote system acknowledgement of a new alert
- <EventType>3</EventType> = Remote system acknowledgement of an alert update
Summary: You can use the Universal connector to forward alert in XML or EVT format to remote systems. Remote systems can then generate files that the connector picks up and process in Operations Manager, for example update resolution state of an alert. You can run the connector against both Microsoft and non-Microsoft systems.