This topic provides some requirements and guidelines for configuring AE Services. For more information about configuring AE Services, see White paper on Avaya Application Enablement Services High Availability (HA) Configurations, located on the Avaya Support Web site http://www.avaya.com/support.
Only one instance of the AE Services server software can reside on an AE Services server machine (requirement).
More than one AE Services server can connect to the same Communication Manager server.
If your applications do not use an AEP connection, there is no limit to the number of connections to Communication Manager servers. For example, if you are using the DMCC service for Device and Media control only that is, first-party call control, and you are using Communication Manager licenses for DMCC endpoints , you would not use the transport link. If you want to use WebLM's DMCC-DMC licenses, you need a transport link.
If your applications use an AEP connection, AE Services can support up to 16 connections to Communication Manager servers. For more information, see Configurations that use AEP connections.
AE Services recommends that you use the Processor Ethernet interface for all configurations.
Applications must run on a separate client application machine (several applications can run on one machine if the machine has the resources to run these applications).
It is recommended that Communication Manager be configured for H.323 registration using the Time-to-Service feature. For High Availability Failover and ESS, it is required that Communication Manager be configured for H.323 registration using the Time-to-Service feature in order to do silent recovery of DMCC registrations. For AE Services 6.1 and later, DMCC device control depends on the Call Information Link and the AEP connection to determine if the Communication Manager server supports the H.323 Time to Service registration feature for AE Services.
An application that uses the Device, Media and Call Control (DMCC) service should keep trying to reestablish the DMCC session when it loses its socket communication link to the DMCC service. Because the runtime state is preserved, once the session is reestablished, all of the Device IDs, device or call monitors, and device registrations will still be intact.
An application that uses the CVLAN, DLG or TSAPI service should reestablish its sessions when it loses the socket connection to the service on the AE Services server. Because no runtime state is preserved for these services, the application should also reestablish any monitors/associations.
The AE Services server can support a mixed environment that includes TSAPI, DMCC, Web Services, CVLAN, and DLG based applications.
The AE Services 7.0.x and later WebLM license will be preserved during a VMware offer type upgrade when Solution Deployment Manager 7.1 and later is used to perform the AE Services OVA upgrade.
