Thank you for your feedback.
Form temporarily unavailable. Please try again or contact docfeedback@servicenow.com to submit your comments.
Versions
  • London
  • Kingston
  • Jakarta
  • Istanbul
  • Helsinki
  • Geneva
  • Store
Close

Event collection via MID Server using a pull operation

Event collection via MID Server using a pull operation

Configure connector instances to use connector definitions (script instructions) that enable the MID Server to connect to external servers to obtain event information.

Use one connector instance for each type of event server that sends events via a MID Server. You can configure connector instances to use the default connector definitions for supported event sources. Alternatively, you can create a custom definition that enables the MID Server to run a script for event collection.

Collect events from external servers using a pull operation

The schedule for the pull interval is set in the Schedule field of the connector instance. Users of the external servers must have read permission. However, if the connector instance is also configured to be bi-directional, the external server users must also have write permission. After configuring the connector instance, use the Test connector to verify the connection with the external source. Thereafter, set the connector instance to Active and events start to be received from the external server according to the pull interval schedule.

Connector instances

Configure connector instances to use script instructions that enable the MID Server to connect to external servers to obtain event information. Each connector instance is specific to an event source vendor.