For each system using ACE Chat, there must be at least one ACE Chat Engine installed exclusively for the system. ACE Chat Engine is exposed to the Internet and acts as a protective layer between the chatting customers on the Internet and the ACE Server. See Configuration Instructions ACE Chat for details.
In the Chat engines window you configure parameters for the chat engines installed for the system. The chat engines are shared by all organisation areas in your ACE solution.
See Chat configuration made in ACE Admin for requirements on access rights.
- Chat engine
- The identifying name of the chat engine. When an ACE Chat Engine connects to the ACE Server, this name must be presented by the chat engine in order for it to be allowed to connect.
- Description
- A short text describing the engine. This description is not used by ACE, but is there for your information.
- Max chats
- The maximum number of ongoing chats allowed. A value of 0 means that no chats can be started.
- Read linger *
- The time in seconds before a HTTP read request from the chat client is replied to by ACE Chat Engine. See Configuration Instructions ACE Chat for details.
- Delay (max) *
- The maximum time in seconds the engine will wait for a new HTTP read request from Web SDK, for an ongoing chat, before the session is regarded dead. The value must be at least 3 * Read linger. See Configuration Instructions ACE Chat for details.
- Inactivity — Timeout *
- Time in seconds a party in an ongoing chat is allowed to be inactive (i.e. not posting a chat entry) before automatically terminating the chat. A value of 0 means the inactivity function is disabled.
- Inactivity — Detector *
- Which side of the chat — (chat) Client, Agent, or Both — that is responsible for detecting inactivity.
- Allow missing origin *
- Tick this box if you need to allow chat from clients that do not send the
originheader. Some web browsers omit this when sending a request to the same domain as the web page. The header might also be configured to be omitted in Internet Explorer. - Allowed origins *
- A list of origins from where it is allowed to initiate a chat session, e.g. https://www.telia.se.
From ACE 13 and onwards, the configuration has been moved to ACE Admin. For backwards compatibility reasons, these configurations will however not be used by ACE Chat Engine until the local configurations on the server computer hosting ACE Chat Engine have been removed. Nor will ACE Web SDK use the configuration from ACE Admin until the old configuration is changed.
The configurations marked with a "*" above will also not be used by old versions of ACE Chat Engine and ACE Web SDK, i.e. version 12 and older.
Company name in URL
The URL-adapted company name is shown in this window since the configuration of allowed origins made in this window is also required in the company's web pages using ACE Web SDK to start a chat. The URL-adapted company name must be included in the URL loading ACE Web SDK. See Configuration Instructions ACE Web SDK for details.
If the configuration of company name for URL:s is missing, the configuration of allowed origins in this window will not be used by ACE Web SDK and this will be indicated in the window. Configuration of company name for URL:s is made in the System parameters for interfaces window .
Two chat engines in the same ACE system
Here are two scenarios where more than one chat engine is used by the same ACE system.
Internal and external chat
Agents cannot use ACE Agent or ACE Interact to chat directly with each other. However, if you want to use chat internally, you could use ACE Chat. Anyone who wants to initiate a chat session with a colleague uses a designated page on the Intranet to request internal chat. Thus, agents are able to receive chat requests in ACE Agent or ACE Interact from their co-workers in the same way as for external customers.
In this scenario, the company thus offers chat on the company's public web pages as well as on internal web pages. The internal chat should not be possible to access from the public web pages and vice versa. In order to solve this problem, two instances of ACE could be installed and configured in ACE Admin. One connected to the Internet and one only connected to the company's internal network. The configuration of allowed origins would differ and public chat entrances would be connected to the public chat engine together with internal entrances connected to the internal chat engine. Even if both ACE Chat Engines would be connected to the Internet, it would be impossible to start a chat on one of the internal chat entrances from public web pages provided that the configuration of allowed origins prevents this.
Redundancy
To achieve redundancy in the system, two instances of ACE Chat Engine could be installed on different server computers. The configured name of the chat engines would be the same (i.e. only one chat engine would be configured in ACE Admin). By doing so, the same configuration would be reflected to both instances of ACE Chat Engine. To make the redundant solution complete, a proxy or load balancer would have to be added to direct chat sessions to either of the two instances in a random or round-robin manner (but all messages for the same session must be directed to the same instance).