The CreatorCon Call for Content is officially open! Get started here.

MID Server for multiple sub production instances

Go to solution
hadyndickson
Mega Expert

‎03-13-2017 06:55 PM

What is the best practises / pitfalls / workarounds for deploying mid servers and using them with multiple instances?

 

Currently I have 3 sub prod instances (dev,test,stag) and 1 production isntance.

I have 2 Mid Servers (Dev, Prod) Prod is linked to production instance an reporting UP status. Dev is linked to dev instance and reporting UP.

From the test instance I cannot seem to communicate with the dev MID server. It reports being DOWN.

Interestingly there is a "url" configuration parameter specified in the mid server record on the test instance which points to the dev instance and cannot be changed.

Can a mid server ONLY be bound to 1 instance?

0 Helpfuls
  • 11,895 Views
1 ACCEPTED SOLUTION

Go to solution
Hadyn
Tera Expert
In response to doug_schulze

‎03-14-2017 03:31 PM

Thanks Doug, I found this in the docs too: Install multiple MID Servers on a single system



For anyone reading this, I ended up Installing multiple separate MID server service instances on the one windows host, all working out of different folders on c:\.



Each MID server service instance can only be configured to talk to one servicenow instance.



Be sure to match your MID server version / patch level to your target instance.



I use the same user record in servicenow across all instances to authenticate. (After clone things will continue to work, although I guess you could have multiple user records across all instances for each mid server instance)



If you are tempted to copy/paste the agent folder per install, be sure to remove the <parameter name="mid_sys_id" value="123456789123456789123456789"/> from config.xml in each new install. A new mid server (ecc_agent) record is created on the target instance during initial installation. Interestingly if you remove the record from the target instance it will be recreated with the same sys_id eventually. This makes sense if you clone from prod and don't have that mid server record already. I guess it's possible to point each mid server service instance to the same mid server record sys_id in the target instance via the mid_sys_id value in the config.xml as above. Then You would only have one mid server record in servicenow but it would communicate to the correct MID server service instance per unique servicenow instance (haven't tried this).



Also check out .\agent\conf\wrapper-override.conf for the default service names.



I ran installer.bat as administrator each time. Also I had to restart between installs else I got a null pointer exception during install.


View solution in original post

10 REPLIES 10

Go to solution
Runjay Patel
Giga Sage

‎12-15-2020 01:04 AM

Check out this video, it will clear all your doubts and help you to understand mid server in details. It will help you resolve below queries:

Link: https://youtu.be/RMXhYJxPMPU

  1. Mid Server Installation step by steps
  2. Mid Server Troubleshooting for all version.
  3. I am unable to install mid server.
  4. Unable to configure MID server.
  5. Service Mapping Mid Servers.
  6. How to log in to the Mid server using the Credential.
  7. MID Server for multiple sub production instances.
  8. Why do we use MID server? Purpose of using MID Server?
  9. How to define a specific mid server for the discoverIpAddress () function?
  10. Other issues.
0 Helpfuls