SCOM connector instance form

  • Release version: Zurich
  • Updated July 31, 2025
  • 3 minutes to read
    • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of SCOM connector instance form

    The SCOM connector instance form in ServiceNow is used to configure instances that connect to Microsoft System Center Operations Manager (SCOM) to collect events or metrics. It allows you to define connection parameters, credentials, scheduling, and other settings required to integrate SCOM data into your ServiceNow environment effectively.

    Show full answer Show less

    Key Configuration Fields for SCOM Event Connector

    • Name and Description: Provide a unique name and a description for the connector instance to identify its purpose.
    • Active: Activate the connector instance after creation to enable data collection.
    • Connector Definition: Choose between SCOM for event collection or SCOM Metrics for metrics monitoring.
    • Assignment Group: Assign the connector to a support or admin group responsible for managing it.
    • Host IP: Enter the SCOM server’s IP address or hostname (not required for metrics connectors).
    • Credential: Select Windows credentials for connecting to the SCOM API. Ensure MID Servers specified in credentials align with those on the connector form.
    • Event Collection Schedule: Define how often (in seconds) the system polls SCOM for new events (not applicable for metrics connectors).
    • Bi-directional Option: Enable this for two-way alert exchange between ServiceNow and SCOM, with status tracking fields available when selected.
    • MID Servers: Specify one or more valid MID Servers to facilitate communication with SCOM. The connector requires port 1433 open from MID Server to SCOM server. MID Servers must correspond with those defined in credentials.
    • Status Fields: Various automatic fields show last run times, statuses, and error messages to help monitor connector health and activity.

    Key Configuration Fields for SCOM Metrics Connector

    • Metrics Collection: Enabled by default and read-only to confirm the connector is collecting metrics.
    • Metrics Collection Schedule: Define the frequency (in seconds) for the metrics collection job.
    • Metrics Database Host and Port: Specify the IP/hostname and port (default 1433) of the metrics database. Optionally use a named instance instead of a port.
    • Database Authentication: Choose between Windows authentication (using MID Server service user credentials) or JDBC credentials for database login.
    • Metrics Database Credential: Provide credentials for database access if not using Windows authentication.
    • Status Fields: Read-only fields display the last collection run time and status to monitor metrics collection health.

    Practical Considerations for ServiceNow Customers

    • Ensure credentials and MID Server configurations are aligned to avoid connectivity issues.
    • Use the bi-directional option if you need alert synchronization between ServiceNow and SCOM.
    • Configure schedules thoughtfully to balance timely data collection with system performance.
    • Monitor the status and error message fields regularly to detect and troubleshoot connection problems.
    • Choose the correct connector definition (SCOM vs. SCOM Metrics) based on whether you want event or metrics data.

    The SCOM connector instance form displays the fields you must fill in when creating a SCOM connector instance.

    Table 1. Connector instance page
    Field Description
    Name Unique name for the SCOM connector instance.
    Description Description for the use of the SCOM event collection instance.
    Active Select to activate the connector instance.

    Appears only when selecting a connector instance that has already been created.
    Connector definition The vendor and protocol used to gather events from the external event source.

    For a regular SCOM connector, select SCOM.

    For a connector instance that you want to monitor metrics, select SCOM Metrics. When selecting this option, the fields in the Connector instance - metrics fields table appear.
    Assignment group Select the group to whom the connector instance is assigned.

    For example, this may be a group of administrators or a support group.
    Host IP Specify the SCOM server IP address or hostname.

    This field does not appear when SCOM metrics is selected as the Connector definition.
    Credential Select Windows credentials.
    This is the credential used to connect to the SCOM API — you can use the MID service account or a Windows credential from the credential store. Optionally set Bi-directional to enable bi-directional alert exchange.
    Note:
    When configuring Windows credentials, if the credential applies to specific MID servers, ensure that the MID Servers you specify on the credential record match the MID Servers specified in the MID Servers for Connectors section on the Connector Instance form.

    This field does not appear when SCOM metrics is selected as the Connector definition.
    Event collection last run time The last event collection run time value updates automatically.

    This field does not appear when SCOM metrics is selected as the Connector definition.
    Last event collection status The last event collection run time status updates automatically.

    This field does not appear when SCOM metrics is selected as the Connector definition.
    Event collection schedule (seconds) The frequency in seconds that the system checks for new events from SCOM Operations.

    This field does not appear when SCOM metrics is selected as the Connector definition.
    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.

    This field does not appear when SCOM metrics is selected as the Connector definition.
    Last bi-directional status The value of this field populates automatically.

    This field does not appear when SCOM metrics is selected as the Connector definition.
    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.

    This field does not appear when SCOM metrics is selected as the Connector definition.
    MID Servers (MID Server for Connectors section) Specify one or more MID Servers that are up and valid.

    MID Servers sort according to the order that their details were entered into the MID Server for Connectors section. The port requirement from the MID Server to the SCOM server is 1433. If the specified MID Server is in a cluster, it may not be selected and another available MID Server is selected in its place. Ensure that the specified MID Servers match the MID Servers specified on the Windows Credentials page, as the connector uses Windows credentials to access MID Servers.

    If no MID Server is specified, an available MID Server that has a matching IP range is used.
    Table 2. Connector instance - metrics fields (displayed when Connector definition = SCOM Metrics)
    Field Description
    Metrics collection Selected by default. Read-only.
    Metrics collection last run time The last run time of the Metrics Collection scheduled job.

    This field is read-only.
    Last metrics collection status Status of the Metric Intelligence collection activity. The value of this field populates automatically.

    This field is read-only.
    Metrics collection schedule (seconds) The time, in seconds, to repeat the Metric Intelligence Collection scheduled job.
    Metrics database host The IP address or the host name of the metrics database host.
    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.
    Metrics database port The port used by the metrics database. The connection is made using JDBC. Default port number is 1433.

    If Connect using a named instance is selected, this option does not appear.
    Metrics database named instance The metrics database instance name.
    Database login with Windows authentication Perform database login with the credentials of the logged-in user defined on the MID Server service.
    Metrics database credential Credentials for the metric database. Use JDBC credentials for the local database user.

    If Database login with Windows authentication is selected, this option does not appear.