Database - all data is stored in a common database. Azure SQL Database or MS SQL Server is used as the database system.
Alvao WebApp (WA, WebApp) - is a web-based interface through which requesters and solvers can interact with the system. The WebApp is implemented on the MS IIS/ASP.NET platform. Users can use any web client to access the WebApp, e.g. Microsoft Edge, Internet Explorer, Mozilla Firefox, Opera, etc. Similarly, users can use any email client to receive information messages. It is also used for system administration.
Alvao Service - a server component that provides automatic loading of tickets and follow-up email communication to the ALVAO Service Desk system. Messages are loaded using IMAP or EWS (Exchange WebService) protocol. The system uses any SMTP Server to automatically send email messages to both requesters and solvers. It also includes a utility for retrieving users from Active Directory.
REST API Service - REST API interface used by ALVAO for Outlook, ALVAO for Teams, and other applications. It can be also used by custom applications, see ALVAO Service Desk Enterprise API.
Database - all recorded data is stored in a database. If multiple users use the system, they all work with a common shared database. MS SQL Server and its Express edition
can be used as the database system.
Asset Management Console ( AM Console) - is
the basic application for working with the system. The user connects to the Asset Management WebService
or directly to the database via the AM Console. It
is a Win32 application.
Alvao WebApp (WebApp, WA) - The system includes an intranet interface
that allows you to view and change data in the database using a web browser.
Accessing the database via the intranet (or the Internet) does not allow all
operations to be performed like the AM Console. Its
main purpose is to provide ICT staff with access to the database when solving
technical problems away from their workplace.
Asset Management Collector (AM Collector, Collector) - Win32 application
that performs remote hardware and software scans of computers on a network.
Data is scanned based on a request issued by an IT staff member to the
AM Console. The ticket is stored in the database. AM
Collector handles the issued tickets and writes the scan results back to
the database, where they are accessible to the user in AM Console.
AM Collector can be run as an interactive application or as a system service,
e.g. on a server. Data can be scanned in 4 ways, see points (5) to (8).
Asset Management WebService (AM WebService) - used for communication with
autonomous agents and also for remote connection to the Asset Management Console.
The agents are queried via the web service to perform a scan and after
performing the scan, they send it to the server via the web service.
Scan by Autonomous Agent - An Agent is installed on the station that
autonomously performs the scan and sends it to the server. The
communication is done via HTTP/HTTPS protocol and the station can be anywhere on
the Internet.
Scan without Agent - AM Collector can scan data from Windows
11/10/8.1/8/2000/XP/Vista computers without having Agent installed on them.
Scan is done via DCOM, WMI and Remote Registry.
Scan with Agent over TCP/IP (retired) - On stations with Windows 95/98/Me and NT/2000/XP/Vista/7 operating systems, scan can be performed using Agent. On Windows NT/2000/XP/Vista/ and 7 the Agent is implemented as a system service. On Windows 95/98/Me, it is a hidden application that runs at Windows startup. AM Collector communicates with the Agent using TCP/IP protocol.
Scan with Agent through a shared folder (retired) - The Agent can also
communicate with AM Collector through a shared folder on the server. This option is retained for compatibility with older versions of the system. When using Agent, we recommend choosing to communicate via TCP/IP.
