Back to all use cases

Architecture AdvisoryCross-Industry

A MID Server design that survives a failover without duplicating data

Integration Team

A typical ServiceNow integration engagement for a team whose JDBC loads sometimes arrive twice: MID Server placement, cluster type, dedicated servers for JDBC sources and a network path check from the MID Server host.

ServiceNow consulting

Overview

This is a typical engagement for a team that loads data from an on-premises database into a ServiceNow instance through a MID Server cluster. After a MID Server restart, some loads arrive twice and nobody is sure which integrations share which server. AceMQ engineers, with a partner subject-matter expert where needed, review the design and write the plan.

Challenge

ServiceNow documents that a cluster is either Failover or Load Balance, that a failover MID Server restarts from the start of the ECC queue task even if some JDBC data was already returned, which can create duplicate data, and that dedicated, non-clustered MID Servers avoid it for LDAP, export set and JDBC data sources. Clusters do not support the Command and SystemCommand topics. The MID Server needs outbound TCP 443 to the instance and no inbound connections, and a web proxy or a blocked OCSP DigiCert server can stop it.

Environment

A ServiceNow instance, two MID Server hosts in one failover cluster, JDBC and LDAP data sources, a REST integration and an on-premises proxy and firewall between the MID Server hosts and the instance.

Approach

AceMQ engineers map each data source and integration to its MID Server or cluster, read the cluster type and the ECC queue history around past failovers, and test the network path from each MID Server host to the instance. They propose which integrations stay clustered and which get a dedicated MID Server, and what the ECC queue and cluster event monitoring should alert on.

Solution

  1. Map of data sources and integrations to MID Servers and clusters
  2. Cluster type decision per group: Failover or Load Balance, and why
  3. Dedicated MID Servers for JDBC, LDAP and export set sources
  4. Network path test: outbound 443, proxy settings, install.service-now.com and OCSP access
  5. Monitoring on the mid_server.cluster.down event and ECC queue depth
  6. Rehearsal of a failover in a sub-production instance, with the expected duplicate behavior recorded

Outcome

The engagement delivers a written design with the MID Server and cluster layout, the dedicated server decisions, the network findings, the monitoring and a failover rehearsal plan. The customer's team implements it, or AceMQ can implement it alongside them.

Technologies

ServiceNowMID ServerJDBC

Have a ServiceNow Challenge Like This?

AceMQ's senior ServiceNow engineers have handled this exact type of engagement before. Whether you need architectural guidance, hands-on remediation, or an ongoing managed partnership, we're ready to help.