LANDESK Gateway

Last modified on 2022/11/30 17:51

IntegrationIntroduction

You can integrate third-party systems with Service Manager in many ways. The method you select will depend on business requirements, architectural and security constraints as well as the characteristics specific to each third-party application or service.

This document describes an integration process that has already been implemented in a customer context. 

To find out more about this integration (e.g. scripts to be used), please do not hesitate to contact your EasyVista contact, or your service provider and integrator.

Integration summary

This gateway is used to integrate the LANDESK Equipment/Software/Attribute tables in the Service Manager equipment/software catalogs.

  • The gateway is automatically managed through the creation and update of catalog entries that indicate the LANDESK data to be extracted and normalized, if required. 
  • LANDESK tables and Service Manager are mapped using two unique IDs:
    • Brand name/Model for equipment
    • Software for software

In this way, all LANDESK gateway processes are used to synchronize Service Manager catalogs with third-party inventory tools using only the desired references based on the corporate strategy adopted. The catalogs must then be updated daily to integrate new LANDESK references.

Supported Versions

Landesk Management Solutions 9.0 Landesk Management and Security Suite 9.5 Landesk Management and Security Suite 9.6 Landesk Management and Security Suite 2016
Check icon.png Check icon.png Check icon.png Check icon.png

Operating principle

          Landesk Gateway Process.png

The process is made up of 3 phases:

  • Enter the equipment/software catalog entries for LANDESK references to be monitored in Service Manager.
  • Run a preimport task using the smoBackOfficeClient tool to:
    • Extract and store information from LANDESK tables in Service Manager work tables by using a filter to retrieve only the data corresponding to the catalog entries to be monitored in Service Manager.
    • Normalize data by grouping LANDESK names together.
    • Run various processing to normalize and standardize data.
    • Store all data in the final Service Manager tables.
  • Integrate data in the final Service Manager tables using Equipment/Software/Attribute integration models.

Example

  • LANDESK software table:

    The third-party inventory tool detects three versions of FastStone, resulting in three records in the LANDESK table: FastStone 5.1, FastStone 5.5, FastStone 6.1.

  • Service Manager software catalog: different options are possible:
    • You can create a single catalog entry that groups together the three LANDESK names, FastStone.
    • You can create one catalog entry for each major version, FastStone 5, FastStone 6.
    • You can create one catalog entry for each version, FastStone 5.1, FastStone 5.5, FastStone 6.1.

Notes

  • The following data is not automatically processed by the LANDESK gateway:
    • Allocation of users to workstations: third-party data is loaded to user-defined fields containing information in Service Manager Equipment forms.
    • Allocation of sites and departments to workstations: not loaded by the LANDESK gateway.
    • Management of software licenses: not performed by the LANDESK gateway.
    • Management of the status of Equipment/Software forms: not performed by the LANDESK gateway.
  • Service Manager Equipment/Software/Attribute integration models are shipped with the LANDESK gateway. Only those that are enabled at integration are taken into account.
  • For SaaS customers, LANDESK tables are read using a VPN connection to ensure restricted and encrypted access to data.
  • Depending on the type of third-party database, LANDESK data may be case-sensitive.

    Open url.png  See How to choose the best tool for automating integration.

Best Practice

  • To ensure optimal performance of the Service Manager platform, you should integrate only data that is new or modified since the previous processing.

LANDESK gateway rules

  • The LANDESK Reference field of each equipment/software catalog entry is used to indicate the LANDESK data to be extracted and filtered, and if required, to group LANDESK names together. It must comply with certain rules:
    • LANDESK references must be separated using the sequence of characters /+-+/
    • The joker % can replace any string of characters
  • Rules for equipment: LANDESK and Service Manager are mapped using the Manufacturer/Model unique ID.
  • Rules for software: LANDESK and Service Manager are mapped using the Software unique ID.
  • Rules for attributes: The LANDESK table is integrated as it is in Service Manager, without normalization.

Procedure: How to monitor LANDESK references in catalogs

1. In Service Manager, create or modify the equipment/software catalog entries you want to monitor.

  • Enter the unique ID of the catalog entry:
    • For equipment, enter the fields outlined in red, Model and Brand Name.
        Equipment Catalog - Landesk Example.png
       
    • For software, enter the field outlined in red, Software.
        Software Catalog - Landesk Example.png
  • In the field outlined in blue, LANDESK Reference, indicate the LANDESK names to be monitored via the catalog entry. Open url.png See normalization examples.
    • Separate each reference using the sequence of characters /+-+/
    • Use the joker % to replace any string of characters

2. In the menu, select Integration > Integration Models. Enable and schedule the Equipment/Software/Attribute integration models for the data you want to integrate in Service Manager.

TranscodageExamples

Examples of normalization

Example 1

Caneco references in the {third-party} table

Caneco BT 4.1 (EN)

Caneco BT 4.1.4 (FR)

Caneco BT 4.1.6 (FR)

Caneco BT 4.2 (FR)

Caneco BT 4.3 (EN)

Caneco BT 4.3 (FR)

Caneco BT 5.1 (EN)

Caneco BT 5.1 (FR)

Caneco BT 5.5 (EN)

Caneco BT 5.5 (FR)

How to monitor Caneco software in Service Manager
To monitor... In the catalog, create... In the Software field, enter... In the {third-party} Reference field, enter... Grouping performed
For all versions and languages A single entry Caneco BT Caneco BT Caneco BT
By major version One entry for each major version Caneco BT 4 Caneco BT 4%

All versions 4* =

4.1 (EN), 4.1.4 (FR), 4.1.6 (FR), 4.2 (FR), 4.3 (EN), 4.3 (FR)

Caneco BT 5 Caneco BT 5%

All versions 5* =

5.1 (EN), 5.1 (FR), 5.5 (EN), 5.5 (FR)

By language One entry for each language Caneco BT (EN) Caneco BT%(EN)

All EN versions =

4.1 (EN), 4.3 (EN), 5.1 (EN), 5.5 (EN)

Caneco BT (FR) Caneco BT%(FR)

All FR versions =

4.1.4 (FR), 4.1.6 (FR), 4.2 (FR), 4.3 (FR), 5.1 (FR), 5.5 (FR)

Example 2

Caneco references in the {third-party} table

Caneco Design 2013

Caneco Design 4.4

Caneco HT 1.2

Caneco HT 2.0

Caneco HT 2.5

Caneco HT 2013

Caneco Implantation 2.3

Caneco Implantation 2010

Caneco Implantation

Caneco Implantation 2011

Caneco Implantation 2013

Caneco Implantation V2.4.0

Caneco Implantation V2.5.1

Caneco Implantation V2.5.2 Beta

Caneco EP 3.2

Caneco EP 3.3

Caneco EP 2013

How to monitor Caneco software in Service Manager
To monitor... In the catalog, create... In the Software field, enter... In the {third-party} Reference field, enter... Grouping performed
For all versions and languages A single entry Caneco Caneco%Design%/+-+/Caneco%Implantation%/+-+/Caneco%HT%/+-+/Caneco%EP% All Caneco Design, Caneco Implantation, Caneco HT, Caneco EP products
By product One entry for each product Caneco Design Caneco%Design% All Caneco Design products, regardless of year or version
Caneco Implantation Caneco%Implantation% All Caneco Implantation products, regardless of year or version
Caneco HT Caneco%HT% All Caneco HT products, regardless of year or version
Caneco EP Caneco%EP% All Caneco EP products, regardless of year or version
By year One entry for each year Caneco 2010 Caneco%2010

Year 2010 =

Caneco Implantation 2010

Caneco 2011 Caneco%2011

Year 2011 =

Caneco Implantation 2011

Caneco 2013 Caneco%2013

Year 2013 =

Caneco Design 2013, Caneco HT 2013, Caneco Implantation 2013, Caneco EP 2013

Warning: In this case, {third-party} references by version will be ignored in Service Manager: Caneco Design 4.4, V2.4.1 - Caneco HT 1.2, 2.0, 2.5 - Caneco Implantation 2.3, V2.4.0, V2.5.1, V2.5.2 Beta - CanecoEP 3.2, 3.3

Example 3

Caneco references in the {third-party} table

Caneco Design

Caneco Design Module

CanecoDesign

Caneco Des

Caneco EP

Caneco HT

Caneco Module Design

Design Caneco

Adobe Module Design

Design Adobe Creative

How to monitor Caneco software in Service Manager
To monitor... In the catalog, create... In the Software field, enter... In the {third-party} Reference field, enter... Grouping performed
All names A single entry Caneco Design Caneco%Des%/+-+/Design Caneco All Caneco Design products
Warning
%Design%

All Caneco Design products

But also: Adobe Module Design - Design Adobe Creative

Caneco Design

All Caneco Design products

But not: Caneco Design Module - CanecoDesign - Caneco Module Design - Design Caneco

Caneco Design%

All Caneco Design products

But not: CanecoDesign - Caneco Module Design - Design Caneco

Mapping LANDESK tables and catalogs

Equipment

LANDESK Service Manager
Equipment table EZV_ASSET table Views: Column
CompSystem.DeviceName ID ID
CompSystem.SerialNum SerialNumber SerialNumber
Computer.HWLastScanDate LastScanDate LastScanDate
CompSystem.type Category LanCatalog
CompSystem.Manufacturer Manufacturer Manufacturer
CompSystem.Model Model Model
CompSystem.LoginName LoginName LoginName
Computer.PrimaryOwner PrimaryOwner PrimaryOwner
Computer.ComputerLocation ComputerLocation ComputerLocation

Software

LANDESK Service Manager
Software table EZV_SOFTWARE table Views: Column
Computer.DeviceName ID ID
AppSoftware.Title SuiteName SuiteName
AppSoftware.Version Version Version
AppSoftware.Version LongVersion LongVersion
AppSoftware.Vendor Publisher Publisher

Software suites

LANDESK Service Manager
Software Suite table EZV_SOFTWARE_SUITE table Views: Column
Computer.DeviceName ID ID
AppSoftwareSuites.Title SuiteName SuiteName
AppSoftwareSuites.Version Version Version
AppSoftwareSuites.Version LongVersion LongVersion
AppSoftwareSuites.Vendor Publisher Publisher

Antiviruses

LANDESK Service Manager
Antiviruses table EZV_ANTIVIRUS table Views: Column
Computer.DeviceName ID ID
AntiVirus.ProductName SuiteName SuiteName
AntiVirus.ProductVersion Version Version
AntiVirus.DefVersion LongVersion LongVersion
AntiVirus.PubDate PubDate PubDate

Attribute tables

LANDESK Service Manager
Attribute tables EZV_CHARACTERISTIC table Views: Column   /   Name
Computer_System_DATA_RCM.Name00 ID ID   /  
Bus.BusType Characteristic Characteristic   /   Motherboard Bus Type
LogicalDrives.COUNT(*) Characteristic Characteristic   /   Disk Qty
LogicalDrives.StorageTotal Characteristic Characteristic   /   Disk Size
LogicalDrives.StorageAvail*100/StorageTotal Characteristic Characteristic   /   Disk Available
Processor.Type Characteristic Characteristic   /   CPU Type
Processor.ProcCount*CoresPerPkg Characteristic Characteristic   /   CPU Qty
Processor.MhzSpeed Characteristic Characteristic   /   CPU Frequency
Computer.LoginName Characteristic Characteristic   /   Login
Memory.BytesTotal Characteristic Characteristic   /   Memory Total (Gb)
Memory.BytesAvail Characteristic Characteristic   /   Memory Available
Memory.NumSlots Characteristic Characteristic   /   Memory Slots
Memory.MaxMem Characteristic Characteristic   /   Memory Max
Printer.Port Characteristic Characteristic   /   Printer X: Port
Printer.Driver Characteristic Characteristic   /   Printer X: Driver
Printer.Name Characteristic Characteristic   /   Printer X: Name
CompSystem.SerialNum Characteristic Characteristic   /   Serial Number
CompSystem.type Characteristic Characteristic   /   Hardware Type
CompSystem.Manufacturer Characteristic Characteristic   /   Hardware Manufacturer
CompSystem.Model Characteristic Characteristic   /   Hardware Model
CompSystem.PrimaryOwner Characteristic Characteristic   /   User
CompSystem.ComputerLocation Characteristic Characteristic   /   Location
  Unit Unit   /   Go,Mhz, -,
Tags:
Powered by XWiki © EasyVista 2022