HTTP(S) Connection from the Enterprise Manager

To start communication with a server, the Enterprise Manager makes an HTTP(S) connection to the Secure Gateway proxy on the server that hosts the EMA (or RM). The Secure Gateway proxy forwards this connection to the EMA (or RM) on the server.

This connection is necessary so that configuration information (in XML format) and alarm information can be exchanged between the Enterprise Manager application and the EMA.

The HTTP(S) connection occurs on the Server connection port (default 80) that is specified in Enterprise Manager for the managed server Server that is managed by the Enterprise Manager application.. (This port is the connection port of the Secure Gateway proxy on the server.) To view these connection settings for a specific server, select the Server node in the Installations tree and click the Settings tab.

The Avaya Contact Recorder (ACR) server does not have a Secure Gateway proxy component. HTTP connections to the ACR server occur on port 8080. HTTP connections to all other servers occur on port 80, as noted earlier.

For the HTTP(S) connection between the Enterprise Manager and the managed server to succeed, the following must be true:

In the Installations tree, the Settings tab for the Server node that hosts the EMA must list the correct Server name and port number (default 80) on which the Secure Gateway proxy listens for connections.
All networks and firewalls between the Enterprise Manager and the managed server must allow HTTP(S) communications on the specified port (default 80).
The EMA or RM must successfully establish a connection back to Enterprise Manager to complete an authentication process. This connection is discussed in HTTP(S) Connection to the Enterprise Manager.

This HTTP(S) communication between the Enterprise Manager and the managed server can be encrypted with TLS for tighter security.