Mid Server Services Requirement




Properties must be updated in each instance for New York on going.

property: glide.discovery.source_name   value: ServiceNow

Discovery Schedule


You must VPN in to access the window servers.

Discovery Schedule


The discovery schedule will contain a Location(cmn_location) and Data Center(cmdb_ci_datacenter) location data attributes 



YaleSandbox1 Midserver Configuration

Configuration Parameter

Noted: added mid.log.level  Value=trace

Supported Application

IP Ranges

Capabilities


   Properties

Clusters

Note: IMPORTANT - You can restrict protocols from executing on your schedule by setting up discovery functionality on your schedule.


Statics (NEW)


Agent Logs(NEW)



Agent Files(NEW)


MidServer Services Architecture


The Management, Instrumentation, and Discovery (MID) Server is a Java application that runs as a Windows service or UNIX daemon on a server in your local network. 

The MID Server facilitates communication and the movement of data between a ServiceNow instance and external applications, data sources, and services.


The MID Server enables communication between a Servicenow Instance and the customer network
It is  a Java Application that runs as a Windows Service or a Unix Dameon
It requires only an outbound connection on Port 443


MIdServer Services Requirements


The Management, Instrumentation, and Discovery (MID) Server is a Java application that runs as a Windows service or UNIX daemon on a server in your local network. The MID Server facilitates communication and the movement of data between a ServiceNow instance and external applications, data sources, and services.


Windows server: To discover Windows-based servers, run Service Mapping patterns, or execute Orchestration commands on Windows devices, the MID Server must be installed on a Windows server. The MID Server supports all Windows Server 2008, 2012, and 2016 editions, virtual machines, and 64-bit systems.


Note: .NET Framework version 3.5, 4.0, 4.5, 4.6, or 4.7 is required for Service Mapping support and for Windows pattern-based discovery.

ServiceNow Configs

·         Ensure Discovery is able to write discovered objects to correct tables
·         ServiceNow Administrator web browser must have Flash Player 10.1 or higher


Clusters - Load Balancing and Failover

2 Load balancer Mid-Server for https://yalesandbox.service-now.com and  https://yaledev.service-now.com
2 Failover Mid-Server - another location for https://yalesandbox.service-now.com and  https://yaledev.service-now.com
1 Load balancer Mid-Server for https://yale.service-now.com
1 Failover Mid-Server - another location for https://yale.service-now.com


FireWall Ports

  • Local LAN inbound (from MID server IP to scanned IPs)
  • Any/Any for Windows desktop firewall
  • Access to admin share (e.g. C$)
  •   Allow 22, 80, 135, 161, 443, 445, 8585, 1024-65535
  •  May need additional allowed ports if targets not listening on default ports on scanned devices

MidServer Installation Process


ServiceNow Discovery Journey#MidServerInstallationProcess

Mid-Server Validation process



VALIDATE MID-SERVERS

Navigate to MID Server > Servers.
Open the new MID Server from the list of MID Servers.
Under Related Links click Validate.
The Set Initial Selection Criteria window appears if there are no records in the Supported Applications, IP Ranges, or Capabilities related lists.
On the Set Initial Selection Criteria window, use the switches to enable or disable selection criteria for this MID Server:
Allow ALL capabilities: Allow all capabilities for Orchestration and Event Management use this MID Server.
Note: Service Mapping and Event Management alert aggregation and RCA, which used capabilities in previous releases, rely on the application for MID Server selection starting with the Istanbul release.
Allow ALL applications: Allow all applications that use MID Servers use this MID Server.
Allow ALL IP ranges: Make all IP ranges valid for this MID Server, meaning that it can target any IP address.
Setting initial selection criteria


If you click Cancel, the validation continues but none of the capabilities, applications, or IP ranges are added.
Click OK.
The Validated field on the dashboard is set to Validating, and then set to Yes after the validation completes.

YaleSandbox Mid-Servers


MidServer NameServiceNow InstanceLocationIPhost nameStatusClusterHost Os
yalesand1yalesandbox@service-now.comNorwalk172.18.16.39snow-tst-mid1.yu.yale.eduupYeswindows
yalesand2yalesandbox@service-now.comwest Campus 172.18.16.52snow-tst-mid2.yu.yale.eduupYeswindows
yalesand3yalesandbox@service-now.comwest campus172.18.16.52snow-tst-mid2.yu.yale.eduupyeswindows


New DEV, TEST  and Production MidServers

New Production Mid-ServerslocationHost OScluster
Discovery 1West CampuswindowsYes
Discovery 2West CampuswindowsYes
Discovery 3NorwalkwindowsYes
Discovery 4NorwalkwindowsYes
Integration 1West CampuswindowsYes
Integration 2NorwalkwindowsYes

Out of Scope