Troubleshooting services

This topic describes all Ambiance services. All services installed should be running all of the time regardless of the functionality being used.

Use the Service Manager to view the status of any service.

AmbianceServer—Acts as a container service that runs Bus services as parallel tasks. To monitor these services, it opens a port and it has a WebAPI endpoint. Uses port 49999.

AmbianceClient—Communicates to encoder devices through USB, and establishes WebSocket to the Server for communication. Provides two endpoints (Web API and SignalR gateway) to communicate with the user interface and Maintenance Unit devices. Port 40100.

Ambiance API—API gateway to receive messages from the user interface or field gateway services such as DokaClient and HubManagerGateway. Ports: 26265/443.

Encoder Service—Communicates to encoder devices through TCP/IP and establishes a WebSocket to the Ambiance Server for communication. Ports: 28000/ 28001(Encrypted).

Related to Licensed Features

MobileKeyDeliveryService—Listens to the Bus (RabbitMQ) and calls the Legic API to deliver mobile keys.

AuroraSync—Communicates with the Keyscan Aurora database by using the AuroraSDK (Software Development Kit).

Related to the Online Gateway

Ambiance VHE—Communicates with the HubGateway service to receive commands from the Ambiance Server. Opens a socket and acts as a proxy for different devices. Serves as Web API endpoint (Port 6099) to create SignalR proxy gateway (for monitoring). Serves as endpoint (Port 6007) and provides SOAP for IRMS. Opens TCP port (Ports 6006/5020) to receive messages from HubGateway.

Ambiance HubGateway—Opens a WebSocket to receive commands from the Ambiance Web API. Opens a TCP port to receive messages from Gateway devices and the VHE service. Ports: 27000/27700.

Ambiance HubManager—Manages Gateway devices. Serves as Web API endpoint to receive queries from HubManager gateways. The HubManager service also opens a WebSocket to Ambiance Web API to transfer commands to the Hub Manager Gateway. Port 9000.

PMS-Related (Property Management System)

Ambiance PMS Agent—Serves as Web API endpoint and delivers messages from socket service to the Bus.

Ambiance PMS WS—TCP listener and provides SOAP for PMS applications. Port 80 for HTTP and 443 for HTTPS.

Ambiance PMS Agent—Serves as Web API endpoint and delivers messages from socket service to the Bus. Port 9595.

Ambiance PMS IRSPRS Agent—Serves as Web API endpoint and delivers messages from socket service to the Bus. Port 9696.

Ambiance PMS IRSPRS—It has TCP listener to receive messages from PMS applications. Port 8264. Communicates with PMS applications by using RS232 standard.

Ambiance PMS FIAS—TCP listener to receive messages from PMS applications. Port 8265.

Related to Third-Party Software

Rabbit MQ—Principal message broker framework for relaying internal Ambiance Server communication.

Redis—Data store used to improve internal message broker performance.

SQL Server (Ambiance)—Serves as the database engine supporting the Ambiance database.

SQL Server Agent (C)—Windows service supporting SQL Server.

SQL Server CEIP service (C)—Runs the SQL Server Customer Experience Program.