MID Servers and Worker NodesSummary<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } The MID Server is fundamentally an integration for doing other integrations through, and generally uses SOAP/REST transactions to pass data to the instance. If for performance reasons an instance has been configured with application nodes split between Worker Nodes and UI Nodes, and a worker URL provided, then all MID Servers should be reconfigured to use the worker URL, just like the other inbound integrations to the instance. Release<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Any, where Worker Nodes have been implemented. Instructions<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } MID Servers will have originally been configured to connect to the main instance URL, and that is set in the 'url' parameter of the MID Server config.xml file in its install folder. Unless they are reconfigured to use the worker URL, they will now be using what has become the UI-specific URL. MID Server 'url' Parameter value: Generic Nodes onlyHas Worker Nodes Normal URL onlyurl = <instancename> url = <instancename> Has additional Worker URL N/A url = <instancename>worker The url parameter cannot be changed from the MID Server form in the instance (PRB1248643 - closed in 2025 unfixed). Customers need to log into each MID Server host to reconfigure them. Confirm the worker node URL is now activeNavigate to MID Server -> Servers, to open a list of MID ServersPersonalize columns, to add Host name and Home directory columns.For each MID Server: Log into the host that the MID Server is installed on, and navigate to the Home directory.Open config.xml in a text editor. If on Windows, use a an editor that understands UNIX line feeds e.g. Wordpad, not NotepadFind the line with the 'url' parameter <!-- Tells the MID server where to contact its associated ServiceNow instance. Edit this value to provide the URL of your organization's ServiceNow instance. --> <parameter name="url" value="https://<instancename>.service-now.com/"/> Edit the value from your <instancename> to add 'worker' on the end. <parameter name="url" value="https://<instancename>worker.service-now.com/"/> Save the fileRestart the MID Server, either: Click the 'Restart MID' related link on the MID Server's form in the instance.or Restart the MID Server Service directly, either running stop.bat and start.bat from a command line, or from the Services Control Panel. Related Links<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Every ServiceNow Instance has several application nodes, which share the work of the instance between them. These are multi-threaded, and threads share physical cpu and memory resources so can impact, or be impacted by, other threads. User transactions, such as loading forms in a browser, can be slow if the app node is busy on other things. For performance reasons, an instance may have been set up with what we call "Worker Nodes", as a way of offloading certain jobs, integrations and background tasks to a pool of dedicated nodes, so that those jobs won't affect the remaining nodes, which we then call "UI Nodes". Our Load Balancers will direct requests to the original instance URL to the non-worker "UI Nodes", as before. An additional worker URL may be created so that it is possible to direct inbound integrations to worker nodes instead. That URL will usually be the instance name appended with 'worker'. e.g. http://<instancename>worker.service-now.com (<instancename>soap has been used in the past). As part of a worker node implementation where inbound integrations are involved, where there is a large volume of SOAP/REST transactions compared to User transaction volume, inbound integrations will be changed to use the worker URL. Changes will also be made to the Scheduler Worker configuration on the app nodes. UI Nodes will normally be set to run only specified background jobs, and the worker nodes will be set to run Any. Scheduled Jobs, such as Discovery Sensors or Event Management jobs, will now run in worker nodes, and no longer run in UI nodes. If a worker node setup is approved and all inbound integrations are not directed to the worker URL, a P1 instance outage may occur. Where some existing nodes are reconfigured to become worker nodes, rather than add new ones, the UI node pool will reduce, and make the situation worse until the integrations are reconfigured for the new worker URL to move them away from that UI node pool.