Guidance on queries related to ITOM Module

manojattri1
Tera Contributor

2 hours ago

Hello All,

Requesting to kindly share your knowledge on the following queries regards to ITOM :

 

Query one :

Scenario based: Instance A is connected to a MID Server, and the MID Server sends scan data to Instance A every week.

Is it possible to temporarily switch from Instance A to Instance B for a few hours (for example, once a month), so that the MID Server sends data to Instance B during that time, and then switch back to Instance A afterward?”


Query Two:
How is the data from scanned devices stored after the MID Server completes a scan?

Is the data stored as a file (like a dump or any specific format) that can be extracted or downloaded from the instance?

Also, is there a way to schedule automatic data extraction and transfer it to another instance?”

 

0 Helpfuls
  • 120 Views
1 REPLY 1

SK Chand Basha
Tera Sage

2m ago - last edited 21 seconds ago

Hi @manojattri1 

Query 1:

To switch mid server from instance A to instance B

 

  1. Login to mid server
  2. Stop the mid server service
  3. Go to installed directory like (c:/Servicenow)
  4. you will find config xml file. 
    (C:\ServiceNow\MIDServer\agent\config.xml )​
  5. Click on it and edit ( change url here of Instance B)
  6. Change the User name and Password which was created in Instance B
  7. save the file
  8. start the mid server

Best Practice: Instead of repeatedly switching from one MID Server to another, it is recommended to dedicate specific MID Servers for each instance. Alternatively, consider frequently cloning the data from Instance B to Instance A to maintain consistency.

Query2:

 

1.The MID Server collects data using probes, or patterns.

2.The collected information is sent back to the instance through the ECC Queue table which is store in XML Format as an input record.(ecc_queue.LIST)

3.The instance processes the returned payload using sensors or patterns.

we don't have option to extract data from one instance to another of Payloads, Only option clone the target CI's Data 

0 Helpfuls