What does ServiceNow consulting from AceMQ cover?
Integration work on the ServiceNow platform: IntegrationHub spokes and flows, MID Server design and clustering, REST and import set data loads, and CMDB data flows through import sets, IntegrationHub ETL and Service Graph Connectors. It does not cover general ITSM implementation or process design. Every engagement starts with a written review and ends with a runbook your team keeps. It is a new AceMQ service line, delivered by AceMQ engineers with partner subject-matter experts.
Do you implement ITSM, HR or customer service workflows on ServiceNow?
No. We work on how data moves between ServiceNow and other systems, and on the middleware and network paths around it. If you need modules, workflows and process design, use a ServiceNow implementation partner and bring us in for the integration layer.
What ports does a ServiceNow MID Server need open?
ServiceNow's documentation says the MID Server communicates securely on port 443 to the instance and requires no inbound connections. A web proxy can still block that connection, the host must reach install.service-now.com for automatic upgrades, and firewalls or proxies that block the DigiCert OCSP servers can stop the MID Server from working (servicenow.com/docs, read 20 November 2026). We check the path from the MID Server host, not only the firewall rule.
How should we cluster MID Servers?
A cluster is either Failover or Load Balance. ServiceNow documents that when a MID Server in a cluster fails, the failover MID Server restarts from the start of the ECC queue task, so JDBC data already returned can arrive again, and recommends dedicated, non-clustered MID Servers for LDAP, export set and JDBC data sources. Clustering also does not support the Command and SystemCommand topics (read 20 November 2026). We decide which integrations share a cluster and which get their own MID Server.
Why do our imports create duplicate CIs?
Import sets and standard transform maps do not apply the Identification and Reconciliation Engine (IRE) by themselves. ServiceNow documents two routes: call the CMDBTransformUtil API from the onBefore transform script and set ignore to true so Import Sets does not insert the record again, or use IntegrationHub ETL, which applies IRE automatically (read 20 November 2026). We check which route each of your data sources takes and whether its identification rules fit the data.
When do we use IntegrationHub, REST or import sets?
As a rule of thumb from ServiceNow's documentation: spokes bundle actions for use in Flow Designer, Data Stream actions handle REST, SOAP or JDBC responses larger than 10 MB or paginated, the Import Set API stages records without a data source record, and IntegrationHub ETL is the path for CMDB data with IRE applied. We map each of your integrations to one and write down why.
Can we work with AceMQ on ServiceNow without a long contract?
Yes. AceMQ works on ServiceNow in two ways: ad hoc engagements for a defined piece of work, such as a health check, an upgrade or an incident, or an annual contract that covers 24/7 support and proactive reviews. Many teams start ad hoc and move to an annual contract once the first engagement is done.
How much does AceMQ ServiceNow support or consulting cost?
Every AceMQ proposal is tailored to your requirements: your ServiceNow environment, the SLA you need, the hours of cover and the scope of work. Most contracts run $24,000–72,000 a year, depending on the SLA, the scope and how ServiceNow is deployed, with aggressive discounts when several technologies share one contract. Request a quote and AceMQ replies within 1 hour.