Installing LMDX with Domain Separation

Last updated on 09 January, 2024

The LogicMonitor Data Exchange (LMDX) application integrates Dexda with your ServiceNow instances. This article describes how to install and set up LMDX for domain separated ServiceNow instances.

Note: The setup process for non-domain separated ServiceNow instances is different. For information on how to set these up, see Installing LMDX.

Requirements

Ensure you have the following before getting started with the configuration:

  • A ServiceNow user account with the admin role. This is required to install and configure the LMDX application.
  • An Dexda API endpoint and token provided by your Dexda administrator. For more information, see API Tokens.

1. Installing the LMDX Application

Start by requesting the LMDX application from the ServiceNow App Store. Once your request has been approved, you can install LMDX from the app store.

2. Creating a Service Account

A ServiceNow user record needs to be created to allow Dexda to access the instance, for example an integration service account. The account must have the x_lomo_dx.api_user role that comes with the application installation. 

This account must be in the Global domain to be able to access all the necessary records. For more information on how to create a user within a specific domain, see the ServiceNow documentation.

Provide the username and password of this service account, as well as the instance name to your Dexda administrator to be added to your Dexda configuration.

Note: You can enable the Web Service Access Only setting for the account. This will ensure that the service account can only interact with the instance via web services, and cannot be used to log into the SN instance from the user interface. For more information, see the ServiceNow documentation.

3. Enabling Domain Support

Do the following to enable domain support for LMDX:

  1. Navigate to Configuration > LMDX properties, and under Domain Separation select “Yes” (set system property x_lomo_dx.domainEnabled to “true”).
  2. Under Domain Separation > Endpoints, add all the Dexda URLs required. For each URL, create a new record and add the Endpoint URL and API Key provided by your Dexda administrator.
  3. Create an Enabled domain record defining which ServiceNow domain should synchronize using LMDX. This record links the ServiceNow domain to an LMDX endpoint. In the Dexda domain field, enter the value provided by your Dexda administrator (this will be the Tenant ID in Dexda).
  4. The Config table displays a mandatory Domain field indicating which Enabled domain record is associated with a Config record.

4. Completing the Default Configuration

After installing the LMDX app, follow the steps described in the following to complete the activation of the default configuration in ServiceNow.

  1. Associate the Config record with an Enabled domain record.
  2. Move the Business Rule that is associated with the Default configuration (for example LMDXDefaultInc sync) from the Global domain to your instance’s primary domain.
  3. Select the Active checkbox.
  4. Select one or more fields as Trigger fields, see Configuration Records.
  5. For LMDXDefaultInc only:
    1. Navigate to the LMDXDefaultInc import (x_lomo_dx_incident_import) Import Set Table and add a string field labeled “Domain” (the field will be named u_domain).
    2. Navigate to the LMDXDefaultInc Import Transform Map and add a new Field Map for the Domain field you just created, mapping it to the target field Domain (sys_domain).
  6. (Optional) Set a Condition to filter the records that are processed.
  7. (Optional) Select one or more Trigger fields as an Important update field, see Configuration Records.
  8. Save the Config record.

After completing the LMDXDefaultInc specific steps and saving the Config record, the configuration is activated and LMDX is ready to start processing data between Dexda and your ServiceNow instance.

5. Creating Scheduled Jobs for Enabled Domains

LMDX uses a scheduled job to process records in the background without affecting user sessions. For domain separated instances, you must create an individual scheduled job per Enabled Domain in LMDX. 

You can copy the original scheduled job named LMDX – Process outbound payloads, and add the name of the SN domain as a string parameter in the script.

In This Article