Connecting the System Center Products for Better Integration
Many who use the System Center products 2012 still using tools like in 2007 and 2008, i.e. autonomously.
Thus, the Service Manager receives events manually when some type of alert is generated in Operations Manager. The reports and inventory data (CI) need to be consulted in Configuration Manager.
Using the Service Manager connectors we can integrate all the products as shown in the diagram below:
As can be seen in the diagram, is the Service Manager who plays the role of integration between the various System Center products. The Orchestrator also acts, but through Runbooks that can interact with the design of activities, but already mentioned in another post http://www.marcelosincic.com.br/blog/post/Orchestrator-Integration-Packs-para-System-Center-2012.aspx
Creating Connectors in Operations Manager
The connectors need to be created on both sides, initially by Operations Manager in Administration-> Internal Connectors, as can be seen below, where the various connectors are already created, and only one is created in the wizard and the other automatically created depending on the number of Management Packs:
The first step is to define the name of the connector and the SCOM computer groups will be integrated:
In the next step we define what are the Management Packs that will be integrated with the Service Manager, and at the time of creation of the connector you can choose all and care after the connector already created and tested, as will be shown in the next topic:
The last step when you create the connector is set filter criteria. This item is more important than the two above (Computer Groups and Management Packs), because it allows you to set granular form which alerts will generate incidents in Service Manager. For example, only errors are important in incidents, as well as the priority, and the State of alert in SCOM 2007.
It is also important to note that the incidents in Service Manager can be opened by the States resulting from the Healthy Operations Manager Monitors, which expands the number of events that will be generated:
Edition of the connector in Service Manager
Created the Operations Manager console connector it is possible to see the same replicated connector in Service Manager in Administration-> Connectors.
If you need to change how the incidents are registered and automatically open it is necessary to amend the Service Manager console connector, as shown in the screen below:
In the configuration screen template define the criteria of incidents that will be synchronized, noting that if it is not properly configured the connector in Service Manager when closing an incident it will terminate in Operations Manager and vice versa.
In the example below, I selected all computers by the group, but could be made a filter by Management Pack, level of severity, priority, or even a custom field:
Creating item (CI) Connector in Service Manager
Note that importing Management Packs has to do with the configuration items and not with the previously defined alerts.
In this case, which will be imported are items, computers and data collected by Operations Manager agents, to form the library configuration data together with System Center Configuration Manager.
Therefore, create the configuration items connector is not as important as creating the connector for the alerts, especially in environments where System Center Configuration Manager also was implemented and synchronize.
Anyway, I recommend that the CI connector so that machines monitored by Operations Manager and not containing Configuration Manager Agent are included in the Service Manager database to open a call. In addition, the connector will allow you to see applications such as IIS Web sites and other Windows services by Service Manager.
To create and administer this, simply set the Connector Management Packs that will send data and the schedule for this task:
More details of each of the connectors can be seen on TechNet at http://technet.microsoft.com/en-us/library/hh524326.aspx