Personalize domains for push connector events to use in event creation

  • Release version: Xanadu
  • Updated August 1, 2024
  • 1 minute to read

    • Configure push connectors to personalize domain separation of events so you can use them to create events in different domains other than the user's currently logged-in or MID Server domain.

    Before you begin

    Make sure that you have the following setup:

    • You have read access to the domain information table for the evt_mgmt_integration role (default table: core_company). For more information, see Configure an ACL rule.
    • You enabled the evt_mgmt.connector_enable_custom_domain_separation .system property.
    • You installed the following plug-ins in the ServiceNow AI Platform® instance:
      • Event Management (com.glideapp.itom.snac)
      • Event Management connectors (sn_em_connector)
      • Domain Support - Domain Extensions Installer (com.glide.domain.msp_extensions.installer)

        You can download the plug-ins from the ServiceNow Store.

    Role required: evt_mgmt_admin

    Procedure

    1. Navigate to All > Event Management > Integrations > Push Connectors.
    2. Open a push connector.
    3. On the Push Connector screen, scroll down to the Push Connector Configurations list and select New.
      Note:
      If this list is not displayed, you must create a push connector configuration parameter. For more information, see Create a push connector configuration parameter.
    4. In the Push Connector Configurations screen, determine whether events should be created in the provided domain or the domain provided in the payload of each event.
      Domain creation locationParameter and values
      The provided domain
      • Field name: payloadDomainInfoFieldValue
      • Value: domain-identifier
      The domain provided in the payload of each event
      • Field name: payloadDomainInfoFieldName
      • Value: field-name-in-payload

      Example: If the payload key “company” holds the domain identifier, then “company” is the value.

      “company”
      {
      “source”: “Solarwinds”,
      “host”: “127.0.0.1”,
      “company”: “ServiceNow”
      }
      Note:
      If both the payloadDomainInfoFieldValue and the payloadDomainInfoFieldName parameters are provided, then the payloadDomainInfoFieldName takes precedence.
    5. Select Submit.

    Result

    Events are created in the domain referred to by the domain identifier.
    Note:
    The table that stores domain information records (for example, core_company) must be domain separated. For more information, see Domain-separate a custom table.