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

MID Server domain separation

Log in to subscribe to topics and get notified when content changes.

MID Server domain separation

MID Servers can be configured in separate domains.

The records that can be read, updated, or created by a MID Server are determined by the credentials configured for that MID Server in the config.xml file. These are the user credentials that a MID Server uses to access the instance and specify which domain's records that MID Server can access.

You can create versions of these specific MID Server policy records that only a MID Server from the same domain can use. This process separation is supported for records in tables that extend MID Server Synchronized Files [ecc_agent_sync_file]:
  • MID Server MIB File [ecc_agent_mib]
  • MID Server JAR File [ecc_agent_jar]
  • MID Server Script File [ecc_agent_script_files]

See Set up domain separation for MID servers for instructions on setting up domain separation through the MID server.

Note: Attachments on MIB or JAR file records might not appear as they did in a non-domain separated environment. This occurs because the Attachments [sys_attachment] table is data separated. When data is separated between domains, a record in a child domain cannot access records in a parent domain.
Feedback