- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-02-2018 03:11 AM
I have to integrate Service-Now with Landesk and need to populate cmdb via integration.
Please guide me through step by step procedure to accomplish this.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-03-2018 06:08 AM
Hi Bipin,
I might say walking you step by step on an Ivanti Landesk integration might be a bit much, but I'll give you the general gist of what I've done prior.
The last Landesk integration I did, there was a SQL table that stored all of the Landesk results and we would query from that. I don't know if thats normal for Landesk or just to that client.
1. Get a service account setup that has SQL access to the Landesk Data.
2. Setup Midserver and have process on server run as the Service Account (So when Midserver reaches out to hit SQL, it has auth). Note that I setup a separate midserver instance, on same server as original midserver, for this purpose.
3. Setup Data Source in ServiceNow, Type = JDBC, Format = SQLServer, Use Integrated Authentication.
4. In Data Source, use SQL Statement to build a query to computer data. I dont know if this is standard or specific to client, but a simplified version of our SQL statement looked like
SELECT
Computer.*,
CompSystem.*,
Operating_System.*
FROM Computer
LEFT OUTER JOIN CompSystem ON Computer.Computer_Idn = CompSystem.Computer_Idn
LEFT OUTER JOIN Operating_System ON Computer.Computer_Idn = Operating_System.Computer_Idn
5. Create a Transform Map that maps your Landesk data to the CMDB. You'll need find your best unique identifier to coalesce on, maybe serial_number.
6. Test it out. Adjust.
Step X and beyond ideas: Build process around what to do if device stops reporting into Landesk after X days. Find ways to populate asset table and create a CI stub to update form purchasing so you can have finance data involved. Use catalog forms and sourcing to tie back original request, source purchasing, PO, arrive on docks, stockroom and then have Landesk data populate the specs and tie in full circle asset management. Use Cabrilo on mobile to introduce barcode scanning. Come to forums and help describe process to others starting.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-03-2018 12:00 AM
Hey bipin,
might be helpful to you.
As per my knowledge, you can use Discovery to popuate CMDB from Landdesk.
For organizations that want to leverage the discovery technologies they already have deployed (SMS, Tally NetCensus, LanDesk, and so on), the ServiceNowplatform supports integrations to those technologies via web services. Scanned data can be mapped directly into the CMDB.
For further information and best practices for designing, constructing, and maintaining the CMDB, see white papers CMDB Design & Configuration and CMDB Design.
Use Discovery
The Discovery product automatically populates the CMDB. Discovery runs probes and sensors to collect information on hardware on the network, software running on that hardware, and the relationships between all the items found. This information is sent back to the ServiceNow instance, and is used to populate the CMDB.Discovery
overview
Import information from another source
Information can be imported to the CMDB using import sets. Import sets find files of information (in formats such as XML, Excel, or CSV), import them, and transform them onto the required table. This process can be scheduled or performed on demand.To import relationships between CIs, use import sets to populate the table [cmdb_rel_ci] with information on the parent, the child, and the nature of the relationship. The [cmdb_rel_ci] table displays a list of all CI relationships and is useful when importing CI data.
Import set overview
Integrate with an existing external CMDB
If the data required for the CMDB is already being collected by another CMDB, it is possible to collect the information from that CMDB in an automated process.CMDB import integration overview
Manually create a CI
Create a single CI for a specific class.
- Identify the table for which you want to create a CI.
- In the navigation filter of the application navigator, enter the table label (such as 'Linux'), or the table name in the format of <table name>.list (such as 'cmdb_ci_linux_server.list').
- In the list view of the table click Newand fill out the form fields for the table.
- Click Submit
Please Refer:
Thanks,
Rajashekhar Mushke
Rising star : 2022 - 2024
Community Leader -2018
Connect me on LinkedIn : Rajashekhar Mushke

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-03-2018 01:46 AM
Hi Bipin,
Landesk?
What it supports. REST, SOAP, etc
Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-03-2018 06:21 AM
I think it supports both.
It is a software distribution tool and I have to integrate it with servicenow.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-03-2018 06:08 AM
Hi Bipin,
I might say walking you step by step on an Ivanti Landesk integration might be a bit much, but I'll give you the general gist of what I've done prior.
The last Landesk integration I did, there was a SQL table that stored all of the Landesk results and we would query from that. I don't know if thats normal for Landesk or just to that client.
1. Get a service account setup that has SQL access to the Landesk Data.
2. Setup Midserver and have process on server run as the Service Account (So when Midserver reaches out to hit SQL, it has auth). Note that I setup a separate midserver instance, on same server as original midserver, for this purpose.
3. Setup Data Source in ServiceNow, Type = JDBC, Format = SQLServer, Use Integrated Authentication.
4. In Data Source, use SQL Statement to build a query to computer data. I dont know if this is standard or specific to client, but a simplified version of our SQL statement looked like
SELECT
Computer.*,
CompSystem.*,
Operating_System.*
FROM Computer
LEFT OUTER JOIN CompSystem ON Computer.Computer_Idn = CompSystem.Computer_Idn
LEFT OUTER JOIN Operating_System ON Computer.Computer_Idn = Operating_System.Computer_Idn
5. Create a Transform Map that maps your Landesk data to the CMDB. You'll need find your best unique identifier to coalesce on, maybe serial_number.
6. Test it out. Adjust.
Step X and beyond ideas: Build process around what to do if device stops reporting into Landesk after X days. Find ways to populate asset table and create a CI stub to update form purchasing so you can have finance data involved. Use catalog forms and sourcing to tie back original request, source purchasing, PO, arrive on docks, stockroom and then have Landesk data populate the specs and tie in full circle asset management. Use Cabrilo on mobile to introduce barcode scanning. Come to forums and help describe process to others starting.