![]() |
Clustering IBM Sametime servers adds some additional requirements to the AE Services TCSPI Conference Service configuration due to the interaction between the IBM® Sametime® servers. There are two installation types for the AE Services TCSPI either the Media Manager or the Community Server. Although there are only two deployment types there are many different ways to cluster these servers and it is outside the scope of this document to specify how every deployment should be configured. The figures in the following sections represent the two configurations tested by Avaya for an IBM® Sametime® Media Manager cluster and an IBM® Sametime® Community Server cluster. These are presented to give a more thorough understanding of how the AE Services TCSPI and Presence Components interact in a cluster and these same techniques can be applied to your specific configuration.
The key to configuring the AE Services TCSPI Conference Service in a cluster is that the Conference Service must be available on the IBM® Sametime® server where the connect client lands during login. In a cluster like that depicted in IBM® Sametime® Community Server Horizontal Cluster figure, a connect client has the potential to land on Community Server 1 or Community Server 2 during the login process. This means that the AE Services TCSPI must be installed on Community Server 1 and Community Server 2. In addition, both of these TCSPIs must have a valid AE Services connection where the extension of the user resides. Depending on how your Community Server cluster is configured you may have a HomeServer attribute to force a user to login to a specific Community Server. In this case you may not require a valid connection to all AE Services servers for the community. However, in general when you deploy a cluster document in a Sametime Community you will no longer use the HomeServer attribute.
With the release of IBM® Sametime® 8.5.1, a new component called the IBM® Sametime® Media Manager was introduced and changes how the cluster is configured. The IBM® Sametime® Media Manager Vertical Cluster figure depicts a clustered environment which includes a vertically clustered Media Manager. It is important to note that the Media Manager still requires a Community Server to operate but once the Media Manager is installed the AE Services TCSPI must be installed in the Conference Manager component of the Media Manager and not the Community Server. As shown in IBM® Sametime® Media Manager Vertical Cluster figure, there are actually two Conference Manager instances running in the cluster and you can see that each Community Server will maintain a single connection with the Media Manager. In this instance the AE Services TCSPI must be installed on both instances of the Conference Manager since a Sametime Connect user could potentially be routed to either Conference Manager. This is true regardless of a Vertical or Horizontal Media Manager cluster, and again both of the TCSPIs must have a valid AE Services connection where the extension of the user resides.
In a cluster where more than one AE Services connection is required per Sametime Server, you will need to add an additional LDAP attribute. This LDAP attribute is used by the AE Services TCSPI to properly route the dial request.