Re-use MID server for different instance

[Dan Belostotsk1]

Hi,
Our client asks if re-using currently working MID server installation(configured against their sandbox) is possible,
meaning they would like to stop using this MID server for their sandbox and connect it to their(new, still unused ) production instance.

** I'm aware this isn't best practice and each instance should have their own separate MID server, I'm also aware, multiple MID server services can be
installed on the same machine.

My question mainly is if this is possible? What are the configuration steps required to point this MID server to another instance? Any documentation provided
by ServiceNow on this matter?

Thank you.

[lasse3]

Hi Dan,

You can do this, but you would not gain anything from it. You need to delete the configuration files generated, so basically your are resetting the installation to the files that you copied when you first installed the MID server. So just deleting everything and then copying from source would be faster.

Maybe you could elaborate on why the customer wishes to reuse the MID server service?

As you say, you can have multiple MID servers on the same physical Server, so this would be the recommended approach.

Please note that any scripts etc. created on the MID Server via ServiceNow will be included in update sets and automatically moved when the update set is moved.

I hope this helps.

/Lasse

[Dan Belostotsk1]

Hi Lasse,
Thanks for your reply.
The client wants to move their current development state into production but getting new VM for prod MID server is holding them back as this requires involving external
  team. I'm recommending the client to install additional MID server service on existing machine to avoid "migration" problems but wanted to check if its even
possible to switch instances.

If i understand correctly, i can remove configuration files from MID server folder (where MID server deployed) and that would reset from MID side, how about
configuration from instance side?

Thanks.

[lasse3]

Hi Dan,

You would need to first stop the service on the MID server. Then clean-up and remove the configuration files. Then you can then run the setup and connect it to your new instance. Once this is done you need to approve the MID server in your new instance. On the old instance the MID Server will appear as offline, as it will loose the connection to the MID server once you stop the service on the MID server.

You would however not gain anything from the above, so I would recommend that you instead download a new source from your new instance via MID Server -> Downloads. Then unpack the download to a different folder than your current MID Server runs in. You can then setup af new MID Server service on the same server following normal installation instructions. This way you are sure that everything is clean and that you have the correct version matching your new instance.

Optional: Consider running the new MID Server with a Service Account. In this case remember to change the ownership of the new MID Server folder to the Service Account before starting the MID Server. Once you complete the installation open Services on the Server and stop the MID Server Service and change the Run as to the Service Account. Then start the service again. In many cases you then need to reboot the Server in order for the MID Server function properly. Running the MID Server as a service account often makes it easier when you want to integrated to other systems, but again - this is optional.

/Lasse

[Dan Belostotsk1]

Great, thank you Lasse.
I'll review the steps with the client an hopeful get him to deploy additional service on the same server to minimize configuration impact.