---
sourceDocument: Yokohama IT Operations Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/it-operations-management
Release :
- yokohama
ft:locale :
- en-US
ft:publication_title :
- Yokohama IT Operations Management
ft:clusterId :
- itom
bundleId :
- itom
workflow :
- Technology
---
# Personalize domains for pull connector events to use in event creation
# Personalize domains for pull connector events to use in event creation {#ariaid-title1}
* Release version: Yokohama
*
* Updated January 30, 2025
*
*  2 minutes to read
Configure pull connectors to personalize domain separation of events so you can use them to create events in 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](https://www.servicenow.com/docs/access?context=t_CreateAnACLRule&version=yokohama&pubname=yokohama-platform-security&ft:locale=en-US).
* You enabled the evt_mgmt.connector_enable_custom_domain_separation system property .
* You installed the following plug-ins on your ServiceNow instance:
* Event Management com.glideapp.itom.snac plug-in
* Event Management connectors sn_em_connector plug-in
* Domain Support - Domain Extensions Installer com.glide.domain.msp_extensions.installer plug-in
{#personalize-domain-separation-pull-connectors__ul_d3q_5mh_11c}
You can download the plug-ins from the [ServiceNow Store](https://store.servicenow.com/sn_appstore_store.do).
{#personalize-domain-separation-pull-connectors__ul_rmd_y4v_mxb}
Role required: evt_mgmt_admin
## Procedure
1. Navigate to AllEvent ManagementIntegrationsConnector Instances.
2. On the Connector Instances list, deactivate the connector instance of the connector for which you want to configure domain separation by selecting it and clearing the Active check box.
3. Select Update.
4. Navigate to AllEvent ManagementIntegrationsConnector Definitions.
5. From the Connector Definitions list, select your connector definition.
6. Determine whether all events should be created in a provided domain or determined by a domain provided in the payload of each event.
1. In the Connector Parameters table, double-click Insert a new row
2. Choose the event creation domain definition location.
* To have all events be created in the provided domain, enter payloadDomainInfoFieldValue in the Name column.
* To have events be created in the domain provided in the payload of the event, enter payloadDomainInfoFieldName in the Name column.
{#personalize-domain-separation-pull-connectors__ul_p2j_hgk_zyb}
Note:
If both the payloadDomainInfoFieldValue and the payloadDomainInfoFieldName are provided, the domain provided in the payload of the event takes precedence.
3. Select Update.
{#personalize-domain-separation-pull-connectors__substeps_br1_cfk_zyb}
7. Navigate to AllEvent ManagementIntegrationsConnector Instances.
8. On the Connector Instances page, select your connector instance from the list.
9. In the Connector Instance Values list, provide a value in the Value field of the parameters.
| Parameter | Value |
| payloadDomainInfoFieldValue | The value that will be used to match the domain record. For example, ServiceNow. |
| payloadDomainInfoFieldName | The key in the payload that has the domain identifier. For example, if the payload key company holds the domain identifier, then the value in the Value column would provide the company information. For example: company : { : "source": "Solarwinds", : "host": "127.0.0.1", : "company": "ServiceNow" : } Note: Dot-walking isn't supported. |
|-|-|
{#personalize-domain-separation-pull-connectors__choicetable_bfv_4yr_3zb}
10. Select Save.
11. Select Test Connector to verify the connection between the MID Server and the connector.
* If the test is successful, a confirmation message appears.
* If the test fails, a message provides instructions to correct the problem.
{#personalize-domain-separation-pull-connectors__choices_ph5_wjb_d1c}
On a successful test, an onscreen message appears. If the test fails, follow the onscreen message instructions to correct the problem and then run another test.
Note:
Use a network tool such as ping to verify whether the credentials are correct and network connection from the MID Server to the connector server.
12. After the connector is verified, select the Return to Connector Instance link.
13. Activate the connector instance by selecting Active and Update.
14. **Optional:** Configure the domain for events by providing domain metadata through the connector parameters.
For example, to use the User \[sys_user\] table for a single connector instance in the Connector Definitions form, create parameters with the following names, and add their values in the Connector Instance form.
* connectorDomainInfoTableName - sys_user
Note:
The table must be domain separated.
* connectorDomainInfoColumnName - user_name
* connectorDomainIdColumnName - sys_domain
* connectorDomainPathColumnName - sys_domain_path
{#personalize-domain-separation-pull-connectors__ul_dyq_x5b_d1c}For more information, see [Connector domain metadata](https://servicenow-prod.fluidtopics.net/Qs2PfJVVK_uXIWfzu3ImOw "Override push connector default domain metadata values installed with Event Management with the values in the event HTTP request, including the URL, headers, request body (payload), and connector parameters. Override pull connector domain metadata values with connector parameters only.").{#personalize-domain-separation-pull-connectors__simpletable_trw_vsv_1zb__entry__3}
| | | |
|-|-|-|
| | | |
| | | |
| | | |
| | | |
[ ]
{#personalize-domain-separation-pull-connectors__simpletable_trw_vsv_1zb}
## Result
The Event Management connector is set up for domain separation.
*[\>]: and then