# Alemba Discovery powered by Lansweeper {% hint style="danger" %} This is currently Draft documentation and may change before being published. {% endhint %} 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
PurposeAn organization uses Centennial Discovery version 2007/FrontRange 2009 to discover and maintain resources present in its organization networks.
PurposeAn organization uses Lansweeper to discover and maintain resources present in its organization networks.
RoleThe 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 FieldsDescription
ConnectorAlemba Discovery
Third-party applicationLansweeper
AssemblyAlemba.Connector.Custom.Connector.dll
Connector classAlemba.Connector.Custom.Connector
Configuration fileConfiguration is stored in the ASM Database (Connector Builder)
Connection methodologyREST 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 {% stepper %} {% step %} ### Install ASM Connector See [Step 1](/asm-hermes/integrate/managing-integration/connectors-to-asm-core/cmdb-connectors/alembadiscovery-connector/step-1-installation-and-configuration-of-alemba-discovery-in-asm.md) for full instructions. {% endstep %} {% step %} ### 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](/asm-hermes/integrate/managing-integration/connectors-to-asm-core/cmdb-connectors/alembadiscovery-connector/step-2-installation-and-configuration-of-alemba-discovery-in-alh.md) for full instructions. {% endstep %} {% step %} ### 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](/asm-hermes/integrate/managing-integration/connectors-to-asm-core/cmdb-connectors/alembadiscovery-connector/step-2-installation-and-configuration-of-alemba-discovery-in-alh.md) for full instructions. {% endstep %} {% step %} ### 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](/asm-hermes/integrate/managing-integration/connectors-to-asm-core/cmdb-connectors/alembadiscovery-connector/step-2-installation-and-configuration-of-alemba-discovery-in-alh.md) for full instructions. {% endstep %} {% step %} ### 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](/asm-hermes/integrate/managing-integration/connectors-to-asm-core/cmdb-connectors/alembadiscovery-connector/step-2-installation-and-configuration-of-alemba-discovery-in-alh.md) for full instructions. {% endstep %} {% endstepper %} --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.alemba.com/asm-hermes/integrate/managing-integration/connectors-to-asm-core/cmdb-connectors/alembadiscovery-connector.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.