Alemba Discovery powered by Lansweeper

This section of the documentation contains technical specifications about the connector that is implemented to link ASM and Lansweeper Pro/Lansweeper Enterprise Systens.

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

Alemba Discovery is a Federated CMDB connector that seamlessly integrates the Cloud (or Hybrid Mode) Lansweeper asset and software inventory into your Cloud or On Premise instance of Alemba Service Manager (ASM).

Built using the ASM Integration Platform and the Alemba Integration Hub (AIH), it exposes REST API endpoints that query Lansweeper via GraphQL and transform the results into a format compatible with ASM’s Connector Builder.

Through the Connector Builder and Integration Hub, this data is federated and linked into the ASM CMDB—enabling the import of assets, software, and their relationships, with support for scheduled updates.

It describes the details of the third-party application that is Lansweeper, including:

• The version for which the connector has been developed

• The name of the .NET assembly file

• Connection methodology

• The resource and link types that can be discovered on the application

• The attributes of each resource and link types that can be imported into the ASM Configuration Management Database (CMDB)

• If not specified, Lansweeper Pro or Enterpise Cloud Subscription, should be assumed as adequate.

You should familiarize yourself with the information in Installing Connectors before installing any connectors, and read the Integration topics for more information on how to configure them.

Use Case Scenario

Purpose	An organization uses Lansweeper to discover and maintain resources present in its organization networks.
Role	The role of this connector is to expose the resources and their relationships in order to allow for population and ongoing consistency checks of the ASM Core CMDB.

Connector description

The table below provides a description of the Alemba Discovery powered by Lansweeper Connector.

Information Fields	Description
Connector	Alemba Discovery
Third-party application	Lansweeper
Assembly	Alemba.Connector.Custom.Connector.dll
Connector class	Alemba.Connector.Custom.Connector
Configuration file	Configuration is stored in the ASM Database (Connector Builder)
Connection methodology	REST API via Alemba Integration Hub

Prerequisites

The following components must be in place:

• Alemba Integration Hub (Node-RED installation (version 1.0 or higher))

• Lansweeper API access: valid Integration ID, Site ID, API token

• ASM Core access for Connector Builder configuration

• Cloud: Azure Vault / Environment variables for storing tokens & credentials

• On-premise: PowerShell token retrieval script: C:\AlembaPS\azure\Get-Token.ps1

Installation Steps

1

Install ASM Connector

See Step 1 for full instructions.

2

Import flows into Alemba Integration Hub

Import 3 flows into Alemba Integration Hub

1. LS_ASSET_IMPORT.json

2. LS_SW_IMPORT.json

3. LS_SW_ASSET_LINK.json

See Step 2 for full instructions.

3

Amend Cloud/OnPrem Nodes

Edit the "Set CLOUD/OnPrem" node in each of the 3 flows to set:

1. Cloud/On Prem parameter and URL.

2. Site ID from Lansweeper

3. Base URL of the Alemba Integration Hub

See Step 2 for full instructions.

4

Create Azure Secrets and Environment Variables

Copy Get-Token.ps1 to C:\AlembaPS\azure folder in the Alemba Integration Hub server.

Create the below environment variables for On Prem system and assign the values:

• ASM Integration source UserName:

ASM_NR_LS_BASIC_UID

• ASM Integration source Password:

ASM_NR_LS_BASIC_PWD

• Lansweeper API Token :

ASM_NR_LS_TOKEN

See Step 2 for full instructions.

5

Create Azure Vault Secrets

• ASM Integration source UserName:

asm-ls-basic-uid

• ASM Integration source Password:

asm-ls-basic-pwd

• Lansweeper API Token :

ls-graphql-token

See Step 2 for full instructions.