Step 1: Installation and Configuration of Alemba Discovery in ASM

Installing and configuring the Alemba Discovery Connector in Alemba Service Manager (ASM)

Installation

This is currently Draft documentation and may change before being published.

Prerequisites

Please review the Installing Connectors guidance:

Installing Connectors

Install Connector Builder Source

To install the predefined Connector Builder Queries and Fieldsets run the following script via the ASM Server Console → Run Custom SQL Script:

Alemba.Custom.Connector.Lansweeper_NR.Install.scp

Step by Step

1. Log in to ASM Server Console.

2. Navigate to Run Custom SQL Script.

3. Execute: Alemba.Custom.Connector.Lansweeper_NR.Install.scp

4. This loads Connector Builder with predefined queries and fieldsets.

5. In ASM Core → Integration → Connector Builder, verify the new entry for: LansweeperSoftwareAssets.

6. Edit this entry in the Connector Builder and verify the following resources and link settings:

   1. LAN-ASSETS

   2. LAN-SOFTWARE

   3. SW-ASSETLINK

LAN-ASSETS entry in Connector Builder will by defult map all Asset Types from Lansweeper. Should you only want to import a subset of Asset Types or limit the import for testing then you can apply an Asset Type Filter to this Entry. Duplicate Entries will be required for each Filtered Asset Type you wish to import.

Create Integration Platform Source

Using this newly added LansweeperSoftwareAssets Connector definition create a new ASM Integration Source. Please review this documentation for further details:

Defining Sources

Integration Source Details

Field	Description
Name	Provide new name for the source
URL	Provide the node-red base url: https://[ServerName].alembacloud.com:1880/
Login ID	Provide a Login ID. This will also be configured in AIH(Azure vault) to validate incoming requests from ASM
Password	Provide a password. This will also be configured in AIH Flows (Azure vault) to validate incoming requests from ASM
Test URL	ls-all-assets?$page=0&$limit=100

Test the Connector Source before proceeding to ensure the connection is successful

Configure Integration Platform Resources and Links

As per standard connector configuration you can then map the Lansweeper fields to the ASM fields using Resource Mapping:

Resource Mapping

In addition you can then map the CMDB Links for Software to Assets by defining the Link Type Mappings:

Defining Link Type Mapping

Scheduling

Imports can be scheduled using ASM’s integration scheduler (daily, weekly, or on-demand). The Connector Builder handles paging (default page size is 100 records per call). Subsequent imports update existing records incrementally. Please review the Managing Scheduled Integration Scans for more information

Managing Scheduled Integration Scans