Configure the SCOM connector instance

Configure the Microsoft System Center Operations Manager (SCOM) connector instance to receive alerts and Operational Intelligence raw data from the SCOM server.

Before you begin

Role required: evt_mgmt_admin
Connector validation performed on versions:
  • 2007 – version 6.1.7221.0
  • 2012 - version 7.1.10226.0
  • 2016 - version 7.2.117190
Before starting the procedure to configure the connector, ensure:
  • The MID Server is running with a user that has local admin permissions to enable the MID Server to run PowerShell and the user has read access to the SCOM API.
  • The MID Server resides in the same domain as the SCOM server.
  • The MID Server uses the same time zone as the SCOM server.
  • The MID Server is running on Windows.
  • The MID Server has .NET framework version 3.5.
  • If you want to activate Metric Collection, ensure that the MID Server that retrieves metrics is configured with the Operational Intelligence extension and that the extension is in Started mode. See Configure the Operational Intelligence extension.
If Bi-directional is selected, ensure that:
  • PowerShell version 3.0 is installed on Windows.
  • That the MID Server is running with a user that has local admin permissions to enable the MID Server to run PowerShell.
If Metric Collection is selected and the Database login with Windows authentication option is also selected, ensure that:
  • As Windows authentication is used by the connector to access the SCOM database (OperationsManagerDW), the MID Server service should be running with a user having read access to the SCOM database. Ensure that the correct credentials are used:
    1. In the local services, right-click the MID Server service and select Properties.
    2. In the Log On tab, ensure that This account is selected with the details of the user in the Windows domain having read access to the SCOM database.
    Note: If the OperationsManagerDW database has been renamed, also change the database name in the SCOMConnector.groovy MID Server Script as well as in the MetricCollector script include.
  • If you upgraded from a release earlier than Istanbul and a SCOM connector was defined:
    1. Define the Log On user on the MID Server service. Ensure that This account is selected with the details of the user in the Windows domain having read access to the SCOM database.

About this task

To receive SCOM alerts, you can obtain the redistributable SCOM files from your SCOM application. Add the files to the MID Server, and then configure a SCOM connector instance to collect the alerts and Operational Intelligence raw data.

The collection of Operational Intelligence is performed using JavaScript running JDBC in place of PowerShell.

Procedure

  1. On the SCOM server, download the following files to a local computer.
    Version and locationSCOM path and library names
    SCOM 2012R2 or SCOM 2012 %ProgramFiles%\Microsoft System Center 2012 R2 or 2012\Operations Manager\Server\SDK Binaries
    • Microsoft.EnterpriseManagement.Core.dll
    • Microsoft.EnterpriseManagement.OperationsManager.dll
    • Microsoft.EnterpriseManagement.Runtime.dll
    SCOM 2007 %ProgramFiles%\System Center Operations Manager 2007\SDK Binaries
    • Microsoft.EnterpriseManagement.OperationsManager.Common.dll
    • Microsoft.EnterpriseManagement.OperationsManager.dll
    Note: Do not append 2007 to the Microsoft.EnterpriseManagement.OperationsManager.Common.dll file.
    SCOM 2016 %ProgramFiles%\Microsoft System Center 2016\Operations Manager\Server\SDK Binaries
    • Microsoft.EnterpriseManagement.Core.dll
    • Microsoft.EnterpriseManagement.OperationsManager.dll
    • Microsoft.EnterpriseManagement.Runtime.dll
    Note: The MID Server must be installed with .NET 4.6 or higher.
    Note: A connection cannot be made to SCOM 2012 and SCOM 2007 from the same MID Server. To work with both SCOM 2012 and SCOM 2007 in your instance, before uploading the following files to your instance, append .2012 to the end of the filename Microsoft.EnterpriseManagement.OperationsManager.dll that is found in the 2012 path and append .2007 to the end of the filename Microsoft.EnterpriseManagement.OperationsManager.dll that is found in the 2007 path. Using these modified filenames enables the relevant MID Server to load the applicable dll when both SCOM versions are deployed. Do not append 2007 to the Microsoft.EnterpriseManagement.OperationsManager.Common.dll file (for SCOM 2007).
  2. Navigate to MID Server > JAR Files.
  3. Click New and add a separate record for the SCOM version for each of the DLL files that you downloaded from the SCOM server.
    1. In the Name field, specify the SCOM version and an identifier to make the name unique, for example 2012 1. If you are using SCOM 2016, specify 2012 as the version.
    2. Click the paper clip icon in the form header and then attach one of the appropriate DLL files that you downloaded.
    3. Click Submit.
  4. Repeat step 3, creating a separate record for each of the remaining DLL files. Ensure that you have a unique identifier after the SCOM version for each file that you attach, for example 2012 2.
  5. Navigate to Event Management > Event Connectors (Pull) > Connector Instances.
  6. Click New and create a connector instance with the following details:
    Field Value
    Name Unique name for the SCOM connector instance.
    Description Description for the use of the SCOM event collection instance.
    Active Select this option only after running a successful test.
    Connector definition The vendor and protocol used to gather events from the external event source. Select the SCOM connector definition.
    Host IP Specify the SCOM IP address.
    Credential Select Windows credentials.
    Event collection last run time The last event collection run time value is automatically updated.
    Last event collection status The last event collection run time status is automatically updated.
    Event collection schedule (seconds) The frequency in seconds that the system checks for new events from SCOM Operations.
    Bi-directional Select to invoke the bi-directional option. This option enables the bi-directional exchange of values to-and-from the external event source. There is default implementation for SCOM. The Last bi-directional status option displays only when this option is selected.
    Last bi-directional status The value of this field is automatically populated.
    Last error message The last error message field is automatically updated. This message is the last error message received by the connector. If the test connector fails, an error message is displayed in this field.
    Metrics collection Select to enable the collection of Operational Intelligence.
    Metrics collection last run time The last run time of the metrics collection scheduled job.

    This option displays only when the Metrics collection option is selected.

    Last metrics collection status Status of the Operational Intelligence collection activity. The value of this field is automatically populated.

    This option displays only when the Metrics collection option is selected.

    Metrics collection schedule (seconds) The time, in seconds, to repeat the Operational Intelligence collection scheduled job.

    This option displays only when the Metrics collection option is selected.

    Metrics database host The IP address or the host name of the metrics database host.

    This option displays only when the Metrics collection option is selected.

    Connect using a named instance When selected, the connection is made using the specified named instance. Otherwise, the connection is made using the specified port.

    This option displays only when the Metrics collection option is selected.

    Metrics database port The port used by the metrics database. The connection is made using JDBC. Default port number 1,433.

    This option displays only when the Metrics collection option is selected. However, if Connect using a named instance is selected, this option no longer displays.

    Metrics database named instance The metrics database instance name.

    This option displays only when the Metrics collection option is selected.

    Database login with Windows authentication Perform database login with the credentials of the log-on user that is defined on the MID Server service.

    This option displays only when the Metrics collection option is selected.

    Metrics database credential Credentials for the metric database. Use JDBC credentials for the local database user.

    This option displays only when the Metrics collection option is selected. However, if Database login with Windows authentication is selected, this option no longer displays.

    MID Servers (MID Server for Connectors section) Specify the MID Server that must run the SCOM connector instance.

    You can configure several MID Servers. If the first is down, the next MID Server is used. If that MID Server is not available, the next is selected, and so on.

    MID Servers are sorted according to the order that their details were entered into the MID Server for Connectors section. If no MID Server is specified, an available MID Server that has a matching IP range is used.
  7. Right-click the form header and select Save.
  8. In the Connector Instance Values section, you can edit the values of the mandatory SCOM parameters.
    1. metric_chunk_size Default value 50000.
    2. scom_date_format Default format M/d/yyyy/ h:mm:ss a
    3. scom_initial_sync_in_days Default value 7.
    4. scom_version It is mandatory to specify the SCOM version, select from 2016, 2012, or 2007.
  9. Right-click the form header and select Save.
  10. Restart the MID Server service to copy the files.
  11. Click Test connector to verify the connection between the MID Server and the connector.
  12. If the test fails, correct the problem by following the instructions issued by the error and then run another test.
    Tip: Use a network tool, such as ping, to verify that the SCOM server is running and the IP address matches the value in the Host IP field.
  13. After a successful test, select the Active check box and then click Update.
    Note:

    The default binding rules that contain SCOM as the external source, that applies to IT alerts and Operational Intelligence raw data, are the following SCOM Management Packs:

    • All OS Management Packs
    • MS SQL Server
    • IIS

Example

If bi-directional is configured, the bi-directional exchange of values to-and-from the external event source is enabled.

These scenarios describe the default bi-directional functionality for SCOM connectors:

  • When an alert is resolved in SCOM, it is auto-closed in ServiceNow. However, it is updated irrespective of the bi-directional feature because during each collection cycle, all alert changes are updated.
  • When an alert is manually closed in ServiceNow, it is auto-closed in SCOM. If the alert state is changed to Reopen, SCOM is also updated.
  • When an incident is created and associated to an alert in ServiceNow, SCOM receives the incident number as a ticket ID. However, the state of the incident is not available on SCOM. Therefore when the incident is resolved in ServiceNow, SCOM is not updated as the incident number remains the same. When the alert is associated with a new incident, the new incident number is updated in SCOM.