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 is used to create and configure SCOM connector instances in ServiceNow. These connectors enable event and metric data collection from System Center Operations Manager (SCOM) into the ServiceNow platform, allowing for effective monitoring and integration of external event sources.

    Show full answer Show less

    Connector Instance Configuration

    When creating a SCOM connector instance, you must specify key fields including:

    • Name: A unique identifier for the connector instance.
    • Description: Purpose of the connector instance.
    • Active: Option to activate an existing connector instance.
    • Connector definition: Select either SCOM for event collection or SCOM Metrics to monitor metrics. Selecting SCOM Metrics reveals additional metric-specific fields.
    • Assignment group: The team responsible for the connector instance.
    • Host IP: The IP address of the SCOM server (not required for SCOM Metrics).
    • Credential: Windows credentials used for authentication; must align with MID Servers specified on both the credential record and connector form.
    • MID Servers: One or more valid MID Servers to facilitate communication with SCOM. Port 1433 is required for connectivity. MID Servers in a cluster may be replaced if unavailable. If unspecified, an available MID Server within the IP range is selected automatically.

    Additional fields such as event collection schedule, last run time/status, bi-directional synchronization, and error messages are available for event-based connectors but not for metric-based connectors.

    Metrics Connector Specific Fields

    When SCOM Metrics is selected, the form displays fields to configure metric data collection:

    • Metrics collection: Enabled by default, read-only.
    • Metrics collection schedule: Frequency in seconds to run the metric collection job.
    • Metrics database host and port: Connection details for the metrics database, using JDBC. You can choose to connect via a named instance or port.
    • Database login authentication: Option to use Windows authentication or JDBC credentials for database access.
    • Metrics database credential: Credentials used if not using Windows authentication.
    • Last metrics collection status and last run time: Automatically updated status fields, read-only.

    Practical Considerations

    • Ensure that Windows credentials and MID Servers are properly aligned to avoid authentication or connectivity issues.
    • Use the bi-directional option if you require two-way data exchange with SCOM, noting that this is only available for event connectors.
    • Configure the event or metric collection schedule to balance timely data gathering with system performance.
    • Monitor automatic status and error message fields to troubleshoot connector health and data collection issues.

    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 IP address.

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