Miradore recently released a new version of its ServiceNow integration. The updated integration supports ServiceNow’s latest Eureka version. It also has many improvements in its functionality. To mention the biggest one, data is now imported using ServiceNow’s import sets which offer great possibilities to configure how the data will be mapped in ServiceNow. In this blog post, I will show how easy it’s to install and use the integration.

To start using the integration, ServiceNow update set must be downloaded from Share. This update set should be imported to your ServiceNow instance and it will add Miradore application which contains all the functionalities that the integration requires. In ServiceNow, update sets are imported in Retrieved Update Sets module. After the import, update set must be previewed and committed from update set’s form. So, let’s do those steps and we’ll end up having committed Miradore update set as shown in the following picture.

Miradore-ServiceNow integration 01

The only thing you need to configure in Miradore is the user account which has read access to Miradore web service. Miradore user accounts can be created in Miradore management console > Administration as seen in the following picture. Miradore server must also be accessible from ServiceNow instance. Typically this means that HTTPS connections from internet to Miradore server must be opened.

Miradore-ServiceNow integration 02

Now we can configure a few settings on ServiceNow’s side. We need a ServiceNow user account which is used to run the integration related scheduled jobs. This account must belong to admin role. As shown in the following picture, I have created an account with user id miradore_integration and added it to admin role.

Miradore-ServiceNow integration 03

Now we can open Miradore application’s Settings module and configure the required settings. MiradoreURL is used to configure Miradore server address and instance name. In this case, my Miradore server’s address is mgw.miradore.com and instance name is demo01. Another required setting is MiradoreUser which is Miradore user account used to connect Miradore web service. I will use servicenow.integration@miradore.com account I created earlier.

Miradore-ServiceNow integration 04

Next, I will configure the ServiceNow user account used to run the scheduled jobs. This can be done in Scheduled jobs module. There are two jobs, Miradore full replication and Miradore incremental replication. I will configure both jobs to use the user account I created previously. I will also activate the jobs.

Miradore-ServiceNow integration 05

Now we are ready to run the integration for the first time. Replication jobs can be run manually from Miradore application’s Run full replication and Run incremental replication quick links. I will run full replication and open Replication status module which can be used to follow the status of the replication. Logs module can be used to see more detailed information about the replication and for troubleshooting.

Miradore-ServiceNow integration 06

When integration is run for the first time, all the computer assets from Miradore will be replicated to ServiceNow. Also some supporting items like locations, manufacturers, models and users are replicated. Item specific transformation maps are used to map Miradore items to ServiceNow items and links to those can be found under the Miradore application. For example, transformation map for users is opened in the following picture.

Miradore-ServiceNow integration 07

Now we have configured and run the Miradore integration. Let’s see how the replicated computer item looks in ServiceNow. In the following picture, I have opened one of the computers replicated from Miradore. We can see that all the basic information like name, asset tag, model and user are replicated. Also lots of hardware inventory information like file systems, network adapters and memory modules are replicated.

Miradore-ServiceNow integration 08

From now on, Incremental replication scheduled job will run every five minutes by default. It replicates all changes made in Miradore to ServiceNow which guarantees that you have always up-to-date asset information in both systems. Full replication job will run once in a day by default. In addition to basic asset data, it also replicates hardware inventory information which is not done by the incremental replication.

That’s all for this blog post. Feel free to test Miradore – ServiceNow integration and, as always, if you have any questions, don’t hesitate to contact us.

Mika Purmonen

Mika Purmonen

Senior Software Engineer at Miradore Ltd
Mika Purmonen has been working for Miradore since 2008, currently as a senior software engineer. He has specialized in software integration and is responsible for integration interfaces of Miradore products. Mika has experience in several customer specific integration projects as a technical specialist. Mika holds MSc. from Lappeenranta University of Technology and has also earned multiple Microsoft certificates like MCSA: SQL Server 2012. | LinkedIn
Mika Purmonen