The Management, Instrumentation, and Discovery (MID) Server is a
Java application that runs as a
Windows service or
UNIX daemon on a server in an enterprise network.
Service Now interacts with external system and applications running on an enterprise network through this MID-Server.
Mid Server can be used for various reasons like
- Discover new/modified CIs in the enterprise network or in an amazon vpc.
LDAP informationfrom an enterprise network
Import Set and Mid Servertogether to
load data from an external systemto Snow
The MID Server opens a persistent connection to the instance through the
Asynchronous Message Bus (AMB) Client and listens on the
/mid/server/<mid_sys_id> AMB channel. When an output record is inserted into the Queue
[ecc_queue] table, an AMB message is sent to the MID Server’s channel. The MID Server receives this message and immediately polls the ecc_queue table for work.
The MID Server polls the ECC queue on the regular interval defined in the
mid.poll.time configuration parameter, regardless of AMB message activity. The default polling interval is set to 40 seconds, but can be reconfigured. This polling of the ECC queue at a regular interval is done in case the AMB connection is dropped.
Mid Server can interact with various systems/application throughout the enterprise network using protocols like snmp, wmi, ssh, powershell, aws, jdbc etc.
We will use guided
ITOM setup to install mid server. ITOM guided setup helps to setup MID server in a step by step manner. We can setup mid server manually also.
Search with ITOM In the left navigation pane
Click on continue in the next screen
In the next screen we can see various Guided setups like Mid server setup, Discovery etc.For now select Mid Server On the right side we can see the task we need to configure to setup
- Create a MID user
- Download and Install MID
- Validate MID
- Add SNMP credentials (optional)
- Auto-Assign MID server IP Ranges(optional)
1.Create a MID user:
In the first step we need to create a user that we are going to use to communicate from MID server to the ServiceNow Instance. Click on Create Mid User from the above task list
In the next screen we need to add user name, password for the new user which we are going to use as
Once use gets created we can view the user under User application in Servicenow.
Important: In this user creation process, in the backend snow assigns a
mid_server_role to this user so that it can communicate between servicenow and the midserver.
We can see that if we scroll down to roles under this user
Now let’s mark this step complete
2.Download and Install MID server:
In this step we are going to install and start the mid server. In our example we are going to setup the mid server in a
First we need get the MID server binary from ServiceNow instance
Click on Configure button and the download page for MID server binary will be displayed as shown below.
Next right click on Linux 64 bit(as we are installing in EC2 linux instance)
And copy the link address as shown in the diagram above. Now let’s login to the EC2 instance as root user Create a folder under temp as mid_server where we are going to download the agent
Now we will use the wget command to download the binary link which we copied from the above step Once the download finishes we need unzip the package
Now we will see a folder below after unzipping
let’s go inside the folder and see the content
Now let’s configure this agent using the
Once done save this file and start the server Our agent sever is installed correctly now. let’s go back to service now instance and mark this step as complete
As a next step we need to validate the MID server that we installed and started. In this step SNOW validates the mid server so that only authorized MID server can get access to snow. This is done of security reasons Now let’s see our MID server listed, search in the left navigation pane
Click on MID server and in the right pane we can see the list of MID servers
When we first see the mid server it will appear as below
We have to click on the mid server and click on validate on the screen below
Once validated, we will see both status and validate as
We now mark this steps also complete
Step 4 and Step5 is optional
This is required if we have multiple MID server and multiple subnets in our environment.MID server will query the SNMP router and check the host ips from the router table. It will then try to discover those IPs under that router automatically.
We are going to skip this for now. As we are going to assign the IP of the host that the MID server needs to scan manually. This completes our MID server configuration steps.
Now as we have completed MID server setup and installation .As a next step we have to setup the discovery part of it.
There are 4 phases in which discovery happens
- PortScanning: This is the first step where SNOW instance will send a
Shazzamprobe to the list of IP /Ip Ranges defined in the discovery schedule. For example, if probe see an active response from port 135 it understands that this node is type of windows. Then discovery will launch the windows classification probe.
Now as Discovery knows that this a windows instance, it sends a
WMIprobe to gather OS related information like OS versions.
- Identification: In this phase sends more probe to uniquely Identify this device. Discovery then uses the CI identification rule to check with CMDB for a matching CI. For example a Windows server CI example WIN00012 is already discovered in previous discovery schedules.It will check with cmdb for matching CI and update the CI instead of creating a duplicate CI
- Exploration In this phase, Dicovery try to gather detail information about this device.For example cpu,memory usage,the process running etc.
Now let’s configure the discovery process Go to the ITOM guided setup and click on discovery
Step 0: In this step we have activate the discovery plugin first Go to** https://developer.servicenow.com**
And then activate the discovery plugin
Once the activation is successful we will get a confirmation in mail
Step1: So as first step we need set the discovery targets.
In this step we are going to define what the things we want to discover and exclude are.
For software filter let us add a specific filter for java Write Java in the text box and click on the New key button under s/w filter
So we added a filter for Java discovery We can now mark this step as complete and move to next step
Step2: Add credentials
In this step we are going to specify the credential that the mid server will use to connect to the discovery node.
In our example we will create another EC2 instance as a node that we want to discovery In our ec2 console we can see this environments as below
Now to configure credentials click on configure
This will open up the credential page
Click on new to create a new credentials
In our case we will have given the
Private Key and
IP in the credential form.
Note: the Node doesn’t require to have a public IP, because MID server is in the same network so it will be able to communicate.
Click on New
In the next page, select the type of credential, in our case it will SSH Private key credentials
In the next page we configure the details of the new credential form
Once done we can test it by click test credential and the IP of the machine to test
A pop appears asking for IP of the node which we want to use to test this credentials
After entering the details we click ok. If successful we will get the below confirmation
So we are done validating the credentials we can mark this step as complete.
Step3. Setting up the discovery schedules
In this step we are going to setup the discovery schedule. This process can be automate with
Auto-Assign MID Server IP task (a part of the MID server guide steps) or we can create schedule manually. In this example we are going to create it manually.
Head over to Discovery schedule.
Create a new discover schedules Now in the discovery form page we need to update the IP range, the job run time etc.
Also we scroll down below we can see the list of IP it is going to scan. We can add a new range or a single IP also
Here we have given a single IP of the node which we want to scan To create a new range, click on new and range form will get displayed as shown below
We can also exclude the Ips which we don’t want to scan Now we are set, we can now click on Discover Now to start the discovery process This will star the discovery process, we can see the discover status progress in Discovery Status section
The description field indicates that the discovery has been started by user manually We can click on the discovery job number to see the detail discovery process
We can also see the timeline discovery showing all the
4 phases of discovery we mentioned earlier
Once the discovery is completed we can check the status under Discovery Schedule page
If we click on this completed task we can see • Discovery Log: Logs generated while discovering • Devices: list of devices discovered in this process Here we can also see whether the CI go discovered is an create or update of a CI • ECC Queues: The Queue messages used during the discovery process
Let’s see the CI which this discovery just created/modified Our CI name is ip-172-31-29-25 We go to device type and click on the CMDB CI
This will open up the CI view window
Scroll down below to see the list of discover software,nework adapter, file system etc
We can see the Discovery of all the Cis happenings in the Dashboard
- Understanding Request, RITM, Task in ServiceNow
- Steps to create a case in ServiceNow (CSM)
- Performance Analytics in 10 mins
- Event Management in 10 minutes - part1
- Event Management in 10 minutes - part2
- Custom Lookup List
- Script includes in 5 minutes
- Interactive Filter in 5 minutes
- UI Policy in 6 Minutes
- Client Side Script Versus Server Side Script in 3 minutes
- Performance Analytics
- ServiceNow Scripts
- Script include
- Useful scripts
- Basic Glide Scripts
- Client Script
- Advance Glide Script
- Glide System Script
- Import Set
- Work Flow
- Core Application
- UI Policy
- UI Action
- Client Script
- CAB Workbech
- Data Policy
- Connect Support
- Event Management
- SSO Integration
- LDAP Integration
- SCCM Integration
- AWS Intergration
- Slack Integration
- CTI Integration
- Jira Integration
- Ebonding ServiceNow
- SOAP Integration
- IBM Netcool Integration
- VIP Mobile App Integration
- Rest Integration
- Service Portal
- Performance analytics(PA) Interactive Filter
- Various Configurations in Performance analytics(PA)
- Service Portal
- Performance Analytics(PA) Widgets
- Performance Analytics(PA) Indicator
- Performance Analytics(PA) Buckets
- Performance Analytics(PA) Automated Breakdown
- Client Script
- Rest Integration
- Understanding the Request, RITM, Task
- Service Catalogs
- Events in ServiceNow
- Advance glide script in ServiceNow
- CAB Workbench