- Post History
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
on 10-18-2024 03:07 AM
✨ Step-by-Step Guide to Host One MID Server for Multiple Instances
Step 1: Download the MID Server ZIP Archive
- Navigate to Downloads: Log in to your ServiceNow instance and go to MID Server → Downloads.
- Download the ZIP Archive: Check the option for Download MID Server as ZIP archive and download the file.
Step 2: Extract the ZIP File
- Locate the ZIP File: Find the downloaded ZIP file on your machine.
- Extract the Contents: Right-click the ZIP file and select Extract All. Choose a destination folder to store the MID Server files.
Step 3: Rename the MID Server (Optional)
If you plan to host the MID Server for multiple instances, renaming it can help you keep track of each environment.
- Open the Extracted Folder: Navigate to the folder where you extracted the MID Server files.
- Rename the Agent Folder: Change the folder name from agent to something more descriptive, like agent_DEV.
Step 4: Configure MID Server Settings
- Access Configuration Files: Go to the newly renamed agent_DEV folder, then into the conf folder.
- Edit wrapper-override.conf:
- Open the wrapper-override.conf file in a text editor.
- Update the following lines:
# REQUIRED: Name token of the service
wrapper.name=snc_mid
# REQUIRED: Display name of the service
wrapper.displayname=ServiceNow MID Server
- Change to:
wrapper.name=snc_mid_DEV
wrapper.displayname=ServiceNow Dev MID Server
- Edit config.xml:
- Open the config.xml file in the same conf folder.
- Update the instance URL:
<parameter name="url" value="https://YOUR_INSTANCE.service-now.com/"/>
- Replace YOUR_INSTANCE with your actual ServiceNow instance URL.
- Add credentials for the MID Server user:
<parameter name="mid.instance.username" value="YOUR_INSTANCE_USER_NAME_HERE"/>
<parameter secure="true" name="mid.instance.password" value="YOUR_INSTANCE_PASSWORD_HERE"/>
- Replace with the username and password of a user with the MID Server role.
- Update the MID Server Name:
<parameter name="name" value="YOUR_MIDSERVER_NAME_GOES_HERE"/>
- Replace with a name for the MID Server as it will appear in ServiceNow.
Step 5: Start the MID Server
- Run the MID Server: In the agent folder, right-click the start.bat file and select Run as administrator to start the MID Server.
Step 6: Configure Certificate Check Policies
To ensure secure communication, you need to create a Certificate Check Policy.
- Navigate to MID Security Policies: Go to MID Server → MID Security Policy.
- Create a New Record:
- Name: Enter the IP address of your MID Server (e.g., 10.51.2.174).
- Active: Set to True.
- Domain: Set to Global.
- Policy Type: Select Overridden Host.
- Submit the Policy.
Step 7: Validate the MID Server
- Check the Status: In ServiceNow, go to MID Server → Servers.
- Validate: Find your newly configured MID Server and click Validate. This step ensures it’s connected correctly to your ServiceNow instance.
That's it, Now if you want to install for another instance then repeat all the steps again.
Regards,
Harsh Deep Singh
- 2,647 Views
- Mark as Read
- Mark as New
- Bookmark
- Permalink
- Report Inappropriate Content
Hi @Harsh_Deep ,
Thanks for the article.
One question is where should we add the other instance URL, for the same mid server.
In the Config file, I have already added the DEV Instance URL, now I want TEST Instance URL, where should be I adding it ? As, the URL value is already taken with DEV instance URL.
Regards,
Najmuddin.
- Mark as Read
- Mark as New
- Bookmark
- Permalink
- Report Inappropriate Content
Hello @Najmuddin Mohd
Where you have renamed the Agent Folder there create a new folder with the new name and copy all the matter of the agent folder and paste inside of new created folder.
For example-
In D drive you have mid_server folder.
Inside it you have agentdev folder which is mentioned here Step 3: Rename the MID Server (Optional)
Now create another agentdev2 folder inside mid_server folder and copy all the things of the agentdev folder now change the url and configuration of the agentdev2 folder.
Thanks and mark this helpful.