[Music] please subscribe to my channel and click on the bell icon to get the regular updates of my channel and do not forget to like comment and share hello everyone welcome back to sas with servicenow this session is part of servicenow discovery training in this training you will learn about mid servers in servicenow which is the second topic of this training in this section we will learn what is mid server mid server application ecc queue how discovery works with probes sensors eccu and mid server we will learn about eccq process flow and we will also learn about how to install and set up a mid server for discovery application so starting with what is a mid server mid server is a java application that runs as a windows service or unix demon on a server in your local network the mid server enables communication and the movement of data between a servicenow instance and external applications data sources and services let's understand with an example there is a company sas now which has cloud service now this sas now instance wants to connect with network of sas now company maybe for ldap integration or any other type of integration maybe to integrate with internal application that means internet application of sas now company but servicenow instance cannot communicate with internal applications of sas now company the reason is because access is limited to internal network only for this sas now company so in that case mid server comes into the picture in order to establish this communication sas now needs to install a mid server in their internal network and once mid server is installed servicenow can communicate with internal network of sas now company via mid server this is basically needed when you want to make an outbound call from servicenow to your internal network you still might have some question that how installing an application in internal network gave access to servicenow so let's understand that as well now mid server is installed in the internal network which means it already has a connection in the network and there can be a handshake between mid server and internal devices and applications of sas now company but the question is how servicenow will be able to communicate with this mid server so in order to establish this connection you need to perform some configuration on this mid server where you need to put some details of your instance with the username and the password so that mid server will have access to your servicenow instance and once that configuration is done mid server will be able to communicate with servicenow instance and they can do handshake as well successfully this overall means that servicenow has access to the internal network of this sas now organization and now you can use the same setup for discovery as well the next topic is mid server application service now has out of the box application to manage and configure mid servers directly in servicenow instance this application also helps you to download mid server java application in your internal server let's see what all modules you can see in this mid server application in my personal developer instance this is my personal developer instance in order to go to mid server you can type mid server and you can access this application mid server which has various modules under this application the first module under this application is installation instruction and if you will click on this button this module it will take you to the servicenow product documentation where it is talking about how you can install the mid server so i will close this the next module we have is downloads which will show you that how you can download the what file you have to download for your mid server overall you have two options one is for linux servers another one is for windows so you might have linux servers in your organization or you might have windows servers in your organization servicenow mid server can be installed in both the machines it is also giving you the option of 32 bit and 64 bit for both linux and windows machines if you want to directly download the zip file so if you will check this box it will show you the option to download the zip file as well which you can extract it and then you can install that particular mid server as well but this zip file is only available for windows machine and if you will click this button this will basically automatically download the file of that mid server so that you can install in both type of machines the next module is dashboard which shows the data related to mid server like if you will install the mid server you can see the status over here that how many mid servers have been installed what exactly their status and some other information as well and you can see more information over here like average percentage of cpu used for the mid server average percentage of max memory used for the mid server that is what you can see in this dashboard the next one is servers in which you will see the list of rackets for all mid server installed for your instance but all the mid servers which you have installed on different servers of your organization they will be visible over here but only for this particular instance wherever you have provided the configuration of this instance those mid server rackets you will see in this particular list and you will see a lot of details other details as well about the mid server next is server issues now in this module you see what kind of issues you have in your mid server so time to time it keep on checking that what kind of issues we have and if system will find any issue it will populate it now as of now there was a mid server installed but i have deleted that that's the reason it is showing this one issue but i can delete this as well but overall you will see the list of issues if you have for any of your mid server and once you will see the list of issues you can troubleshoot it as well you can fix it and then you can resolve these issues manually next is upgrade history in which you can see all the upgrades done for your mid servers when you upgrade your service now instance so like in this particular instance we have paris version like you can see now this one was for previous uh mid server which we installed but i have deleted i have uninstalled that mid server for now because i want to install a fresh a new mid server for this demo so here you can see it will show you the history of all the upgrades happened for those different mid servers you have in your instance so those details can be seen over here then we have clusters so you can configure mid server clusters for your different mid servers like load balancers which will distribute the traffic of the transaction and another one is failover which will make one mid server as primary and other bit servers as secondary as well and if i give you a quick example let's say you are using mid server for any particular functionality and one of the mid server goes down maybe it stopped working because of some issues on the mid server and now you want you if you want to continue with that functionality and if you will make that failover then what system will do system will automatically route the selection of mid server to the secondary one so that that functionality continue to work so your functionality of any functionality it can be discovery or all other functionalities all even the integration which are using which server in that case that functionality will not break and it will continue to work because of the secondary mid server then you see properties in which you can configure different properties for different functionalities of your mid server and you can just change the values over here and you can also create new mid server properties it is different from the actual properties we have in servicenow instance then we have script includes now this is specifically for bit server script includes so you can see the list of script includes which you can use for different type of scripting you want to do or to achieve some kind of functionalities to achieve some kind of maybe features you want to implement wiremit server in that case you can create different script includes as well these are all out of the box but you can create your own script include mid server script include as well similar to properties it is also different it is in a different table so these all these script includes are different from the normal or generic script includes you have in your service now instance the next module is script files which stores different type of files you can run on mid server or wiremix server like powershell files you have some uh scripting files shell scripting files as well like you can see over here dot fh files those are all linux files shell scripting files so you can store them and you can run them as per the functionality you need via mid servers then we have ip ranges now in this particular module you will see what kind of ip ranges you want to include or what kind of ip ranges you want to exclude for i mid servers so you can configure that what for example you have multiple mid servers and you want to include or exclude specific ip address uh mid servers then you can mention over here as of now we have selected all that means all the ip ranges whatever mid servers i will be putting in my instance i'll be installing it will consider all of them then we have applications now here you can mention different applications so for example mid server is used for different applications in service now like cloud management like discovery and some other applications as well like event management as well so in that case if you want to specify that this these mid servers should be used for these these applications that you can define over here and if you want to just just configure it for all the mid server all the applications in that case you can just select all next one is mid selector override which is for cloud override configuration with the help of scripting next is capabilities in which you can define what capabilities different mid servers should have to perform different activities like you can see we have capabilities for powershell ffh wmi even for discovery if i talk about discovery in discovery you have to discover maybe windows servers you have to discover linux servers and in for linux you should definitely need ffh for for windows you should definitely need this wmi so these are all different capabilities you want to have for your mid servers and there are some other modules as well which you can configure as per your requirement from your customer and clients in your organization mid server installation mid server should be installed in your organization's server machine which will have access to communicate with internal devices and ip addresses now what servicenow applications use mid server so mid server is used by ldap orchestration event management discovery application service mapping and integration integration with different third-party applications maybe internet applications next is ecc queue so what is accq ecc is external communication channel eccq is a connection point between an instance and the mid server eccq is a table of rackets which stores information sent from servicenow instance to another system and from another system to servicenow instance eccq racket is a message sent from servicenow or incoming message from third party system this is one of the ecc methods racket which shows some other details as well like q which shows if the message is output or input method then state as well which shows the status of the message whether it got processed whether it got triggered it is ready there are different states which we will learn later now how mid server uses ecc eccq in service now let's say we have image server a service now instance and ecc queue on the same instance now mid server always communicates with servicenow instance with worker job and checks for new output messages so that mid server can perform the action as per the message provided by servicenow now this ecc queue stores input and output messages input messages are processed in the instance to perform action in the instance only and output messages are processed by mid server to perform some action maybe to perform some action for third party applications as part of the integration the next topic is how discovery works with probes sensors eccq and mid server let's understand this with an example let's assume we have one server and one database in the network of any organization like we talked about sas now company we have servicenow instance and we have mid server now this mid server is installed and configured in the internal network of this sas now company in servicenow instance you have probes for different types of devices and applications like windows linux and you also have sensors now service now has a lot of out of the box probes and sensors created in the instance however you can also create your own probes and sensors to discover specific information of your systems and process them now mid server always query the probes to run on target machine to collect the information now this mid server is subscribed to asynchronous message bus and that is called as amb which is always available to send and receive messages in servicenow instance and also notify to mid server if there is any pending job to be processed in ecc queue if a job exists in accq for that mid then mid server says to the instance that hey i'm going to work on this work mid server process the request as per the probe and then reports back to the ecc queue with the results and now this information which was collected is basically processed by sensors the next topic is eccq process flow we will see how eccq process the work and change the state as per different activities so let's start with a new message is created in accq then system checks if the message is input or output message and if the message is output then state becomes ready which is basically ready to send the job to mid server now when mid server receives the job then state becomes processing so that mid server can process that particular work once job is completed by image server then state becomes processed in eccq this is how output accq message is processed in service now then in servicenow instance mid server creates a new message in eccu as input method with the results collected by probes and state becomes ready then sensor picks the message to process which change the state to processing once message is processed in the servicenow instance then state of that ecc queue becomes processed and this is how input eccq method is processed in service now in servicenow instance you can access eccq by typing ecc in application navigator and you will get this application ecc and if you will click this module queue you will see all ecc queue rackets here you can see we have output and input so let me just group it so that you can see both types of cues we have so we have input messages we have output if i open one of the input let's say we open this one and you can also see it is basically using the one of the mid server we have so you can see it has a lot of information like it has payload what kind of payload it is getting this is basically input so maybe it is getting getting the response basically from third-party system and i think it is basically getting the data for discovery so that's the reason it says here input that means it has processed as well you can see the state and we have different states like ready processed error and processing and if i close this one and if i open output one that means i am sending something that means service now instance is sending something to mid server so you can see we have this one as an output and if i open this racket so this is the output message so maybe i'm just sending some instruction to another system so mid server will pick it and then process it accordingly and this is the output message i hope you like this video thank you and have a great day