Deployment types of Avaya Aura Admin Portal

Last Updated : Jan 24, 2025 |

This section describes the deployment type of Avaya Aura® Admin Portal.

For information about the supported footprints, see Supported footprints of Avaya Aura® Admin Portal.

Note:

To deploy or set up the Avaya Aura® Admin Portal contact Avaya Customer Experience Services (ACES).

Deployment of Application Server and Database Server on the same server

Application Server and Database Server are co-hosted on a single server.

Deployment of Application Server and Database Server on different servers

Application Server and Database Server are hosted on different server.

Cold Standby redundancy support

  • Two Application Servers, one will be an active node and other will be Cold Standby. You can stop services on the Active node and start services on the Standby node to fail over.

    You must use the following order to stop the services:

    1. sf_FaultManager

    2. sf_CMConnector

    3. sf_CMMultiplexer

    4. sf_HistoryMux

    You must use the following order to start the services:

    1. sf_HistoryMux

    2. sf_CMMultiplexer

    3. sf_CMConnector

    4. sf_FaultManager

  • Two Microsoft SQL Database Servers, one in a Primary data center and other in a Secondary data center (VMware). Both Microsoft SQL Database Servers use merge replication.

    Note:

    Admin Portal also supports the existing Microsoft SQL Database cluster that is shared by other applications in your premises.