- Welcome to the EasyVista Wiki
- Integrations
- LANDESK Gateway
LANDESK Gateway
SM_IntegrationIntroduction
You can integrate third-party systems with 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 contact the Consulting & Professional Services team, the
Support team, or your service provider and integrator.
Integration summary
This gateway is used to integrate the LANDESK Equipment/Software/Attribute tables in the 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
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 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
|
|
Operating principle
The process is made up of 3 phases:
- Run a preimport task using the smoBackOfficeClient tool to:
- Extract and store information from LANDESK tables in
work tables by using a filter to retrieve only the data corresponding to the catalog entries to be monitored in
.
- Normalize data by grouping LANDESK names together.
- Run various processing to normalize and standardize data.
- Store all data in the final
tables.
- Extract and store information from LANDESK tables in
- Integrate data in the final
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.
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
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.
- Allocation of users to workstations: third-party data is loaded to user-defined fields containing information in
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.
See How to choose the best tool for automating integration.
Best practice
- To ensure optimal performance of the
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
are mapped using the Manufacturer/Model unique ID.
- Rules for software: LANDESK and
are mapped using the Software unique ID.
- Rules for attributes: The LANDESK table is integrated as it is in
, without normalization.
Procedure: How to monitor LANDESK references in catalogs
1. In , 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.
- For software, enter the field outlined in red, Software.
- For equipment, enter the fields outlined in red, Model and Brand Name.
- In the field outlined in blue, LANDESK Reference, indicate the LANDESK names to be monitored via the catalog entry.
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 .
TranscodageExamples
Examples of normalization
Example 1
|
|
Example 2
|
|
Example 3
|
|
Mapping LANDESK tables and catalogs
Equipment
![]() |
![]() |
|||
---|---|---|---|---|
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
![]() |
![]() |
|||
---|---|---|---|---|
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
![]() |
![]() |
|||
---|---|---|---|---|
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
![]() |
![]() |
|||
---|---|---|---|---|
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
![]() |
![]() |
|||
---|---|---|---|---|
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, -, |