SCOM connector instance form

Release version: Xanadu

Updated August 1, 2024

3 minutes to read

Summarize

Summarized using AI

Summary of SCOM connector instance form

The SCOM connector instance form in ServiceNow is used to configure connectors that gather events or metrics from Microsoft System Center Operations Manager (SCOM). This form provides fields to define connection details, authentication, scheduling, and operational status for both regular SCOM event connectors and SCOM metrics connectors.

Show full answer Show less

Key Fields for SCOM Connector Instances

Name and Description: Assign a unique name and describe the purpose of the connector instance.
Active: Activate the connector instance after creation.
Connector Definition: Choose between SCOM for event collection or SCOM Metrics to monitor metrics, with relevant fields changing accordingly.
Assignment Group: Designate a support or administrative group responsible for the connector.
Host IP: Specify the SCOM server IP address (not required for metrics connectors).
Credential: Select Windows credentials for authentication; ensure MID Servers specified in credentials align with those on the connector form.
Event Collection Schedule: Set how often, in seconds, the system polls SCOM for new events (not applicable to metrics connectors).
Bi-directional Option: Enable bi-directional data exchange with SCOM; status fields appear only if enabled.
Last Run Times and Status Fields: Automatically updated fields display the last event or metrics collection run time and status, providing operational visibility.
Last Error Message: Displays the most recent error encountered by the connector, aiding troubleshooting.
MID Servers: Specify one or more valid MID Servers to handle communication; these must match those on the Windows Credentials page. The connector requires MID Servers with port 1433 access to the SCOM server.

Additional Fields for SCOM Metrics Connectors

Metrics Collection: Always selected and read-only, indicating the connector gathers metrics.
Metrics Collection Schedule: Defines how often metrics collection job runs, in seconds.
Metrics Database Host and Port: Specify the IP/hostname and port (default 1433) for the metrics database connection.
Named Instance Connection: Optionally connect using a named instance instead of a port.
Authentication: Choose between Windows authentication using the MID Server service user or JDBC credentials for database access, configured accordingly.
Metrics Database Credential: Provide credentials for the metrics database if Windows authentication is not used.

Practical Considerations for ServiceNow Customers

Ensure that MID Servers specified on the connector instance form and Windows credentials match to enable successful communication with SCOM servers.
Use the appropriate connector definition depending on whether you want to collect events (SCOM) or metrics (SCOM Metrics), as fields and capabilities differ.
Configure the event or metrics collection schedule to balance timeliness of data with system performance.
Monitor status and error fields regularly to ensure the connector runs smoothly and troubleshoot issues promptly.

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.