Managing Integration
ASM Core provides a common Integration Platform to set up various types of integration with external applications and technologies with a view to automate the transfer of information.
There are numerous third party applications and technologies to discover and maintain information about many of these external resources. ASM Core provides a common Integration Platform to set up various types of integration with external applications and technologies with a view to automate the transfer of information(for the resolution of calls or the completion of tasks, for example), the management of alerts across different systems, and the population of the ASM Core CMDB with externally discovered resources.
Terms and Concepts
Before you read about configuring the Integration Platform on your ASM System, it is important that you become familiar with the following terms and concepts.
Integration Platform
Connector
A connector provides an interface between ASM Core and an external application. Each application that needs to be integrated with ASM Core requires a connector. Connectors are .NET Assemblies that are designed to expose data through code in a format that is not application-specific. Therefore, connectors can be customized to enable integration with any external application. IMPORTANT NOTE: Alemba is currently reviewing and updating the whole of the connector section, including all subsections. Expect this section to be updated by end of June, 2025.
Source
A source is configured for each external system with which you want ASM Core to communicate. It represents an “instance” of the external application within ASM Core. For integration with the Federated CMDB, a source is the system to which ASM Core can connect to import objects discovered by a network discovery tool into ASM Core or import users from a directory server. For Event Management, a source is the system from which events are received (for example, a network monitoring tool monitoring the IT infrastructure). For Inbound and Outbound Actions, a source is the system to or from which Actions are sent. It can be, for example, a procurement system, a Service Desk system or another ASM System.
Federated CMDB
Primary or External Resources
These are the principal objects that a connector is responsible for discovering in a source. A Primary Resource can possess child objects (Secondary Resources) that represent the components of that Resource. An External Resource can include a person record discovered on a directory server source.
Definitive Resource Record
For each Primary Resource discovered, the ASM Core database stores a cached replica of that object known as a Definitive Resource Record. Neither Secondary Resources nor their properties are cached.
Cached Resource Search
This is a type of external resources search that returns only those external resources that have been imported into ASM Core and are not excluded.
Scan
Sources can be scanned either as a one-off or regularly in order to discover resources on the external system and the links between these resources.
Event Management
Event
An event is an alert or notification generated on an external source which may lead to a call or request being logged in ASM Core.
Incoming and Outgoing Transactions
Integration Capabilities
The Federated CMDB
This capability enables you to communicate with external applications (network discovery tools or LDAP-compliant directory servers) in order to discover resources on these applications. Once detected, those resources can be imported into ASM Core as CMDB records or linked to existing CMDB records.
Event Management
This capability enables ASM Core to handle incoming alerts received from network monitoring tools and track the progress of these alerts through calls or requests.
Incoming and Outgoing Actions
This capability enables ASM Core to handle actions received from external applications such as other Service Desk systems or initiate items such as calls and tasks in other applications.
Terms
Action
An Action is either initiated by ASM Core or the Source with which it is integrated, and results in various actions in ASM Core or the Source. The lifecycle of an Action consists of Messages.
Outbound Action
This is an action initiated by ASM Core which triggers a response on the Source (for example, when a call or external supplier task is forwarded externally).
Inbound Action
This is an action initiated by the Source which triggers a response in ASM Core (for example, when the source triggers a call or request in ASM Core).
Messages
Creator
The name given to the system which sends the initial CREATE message (the message which generates the Inbound or Outbound Action).
Receiver
The name given to the system which receives the initial CREATE message (the message which generates the Inbound or Outbound Action).
CREATE
This type of Message can be sent by a Creator to initiate an Action. For Outbound Actions, this message is sent when a call or External Supplier task is forwarded to the external supplier linked to the Outbound Action, or when an Outbound Action task is activated in a request. For Inbound Actions, this message logs a call or request in ASM Core.
RECEIVE
An Incoming Transaction in which the Event generated on the Source is sent to ASM Core. ASM Core may then log a call or request depending on how the event is mapped.
ACKNOWLEDGE
An Outgoing Transaction in which ASM Core acknowledges the Event received from the Source.
NOTIFY
This type of Message can be sent by both the Creator and the Receiver. For Outbound Actions, this message is triggered when a note is added to a call or task that initiated the Outbound Action. For Inbound Actions, the message can lead to ASM Core adding a note to a call or request, or taking no action.
UPDATE
An Incoming or Outgoing Transaction in which a call or request is updated in ASM Core by an analyst who takes action on the call or request. The Outgoing Transaction can be configured to update the call or request, add a note to the call or request, or take no action on the call or request.
CANCEL
The Creator sends this message to stop further processing of the Action by the Receiver.
RESOLVE
An Incoming Transaction to inform ASM Core that the Event has been resolved on the Source. This transaction can be configured to close the call or request, add a note to the call or request, or take no action on the call or request.
DELETE
An Incoming Transaction to inform ASM Core that the Event is no longer valid. This transaction can be configured to close the call or request, add a note to the call or request, or take no action on the call or request.
COMPLETE
This message is sent by the Receiver when an Action is successfully performed.
NOT COMPLETE
This message is sent by the Receiver when the Action failed.
CLEAR
An Outgoing Transaction to inform the Source that the call or request has been closed in ASM Core.
Service Desk Actions
This capability enables ASM Core to handle the actions received from and sent to external applications such as other Service Desk systems, to create and update calls in ASM and the external application.
Single Sign-On
Single Sign-On (SSO) is an authentication method that allows users to access multiple applications with a single set of login credentials. This means that after a user logs in once, they do not need to repeatedly enter their username and password for subsequent applications.
Additional mechanisms like Windows Integrated Security also provide SSO for on-premise environments, where the operating system and browser share security tokens to authenticate users automatically. However, many modern deployments, especially in cloud-based environments, rely on SSO to centralize authentication, enhance security, and reduce password management issues.
Webhooks
Webhooks in the ASM HERMES context are user-defined HTTP callbacks that allow external services to receive real-time notifications when specified events occur in the Alemba system. When such events are triggered—such as changes to calls, CMDB items, knowledge, or other supported entity types—the system sends a POST request with a payload containing event data to the configured URL(s).
Additionally, webhook payloads can be configured to include attachments, inline images, and even historical data (like the last note added) depending on the use case and configuration settings available in the integration platform.
Linking
CSV Linking enables ASM Core to integrate and link resources defined in a CSV file into its Configuration Management Database (CMDB).
The Connector Builder
The Connector Builder in ASM HERMES is a feature that allows you to create custom connectors to integrate external applications with ASM. This custom development enables you to build a connector that fits your specific requirements:
It lets you define the API
Understand its operations
Map relevant data into ASM’s CMDB.
Currently, it supports building custom CMDB connectors, which means you can have your connector import external resources as Federated CMDB records or link them to existing CMDB records.
Predefined Connectors
Some examples of predefined connectors are:
Microsoft Active Directory Connector
Novell eDirectory Connector
Sun Java System Connector
vFire to vFire Connector
ASM to ASM Connector
Service Now Connector
vCloud Director Connector
vCenter Orchestrator Connector
CSV Connector
Database Resources Connector
MS SQL Table Resources Connector
MS SQL Table Events Connector
MS SQL Table Lookup Connector
MS SQL Table Outbound Action Connector
SingleSignOn Connector Atlassian
JIRA Connector
Alemba External Process Connector
Alemba Stored Procedure Connector
Alemba Email Event Connector
vRealize Orchestrator Connector
SolarWinds Connector
SCCM/SMS Connector
Snow Inventory Rest Connector
Linking CSV Connector
Azure DevOps Connector
The Role of Connectors
Communication with supported external applications is performed through a series of connectors (one per external application) supplied with ASM Core and which must be installed on the ASM Core server.
Administrator and Analysts Requirements
Once a connector is installed, the system administrator must:
Set up the appropriate security rights for analysts to manage external resources, events and Inbound and Outbound Actions.
No license is required for integration with other supported products in the ASM family and LDAP-compliant directory servers.
However, for integration with any other supported external application (including custom connectors), your organization must be licensed for each individual connector with which you want to set up integration.
Last updated
Was this helpful?