Mitch A Carlyle 7.Oct.08 03:53 PM a Web browser Sametime Entry 8.0.1 Windows
We have the following configuration:
Community Servers: 3 MUXs, 2 Clustered Community servers
Meeting Servers: 2 External, 5 Internal
All using an LDAP directory, all are part of the same Community (e.g. all servers know about all the other servers via server docs in the NAB).
We have always configured our Home Sametime Server field on the meeting servers to point to the cluster name of the Community servers. We've done this because we thought by offloading the community services connection to our dedicated chat environment, we would save some load on the meeting servers. We've been recently steered into severing this connection as it might not be giving us any gains.
Anyone have any insight? If we were to choose to break the connection, what would be the best practice way of doing so....simply leaving the Home Sametime Server field blank on the meeting server's LDAP configuration documents? If we were to do that, would our users be able to have separate connections to our chat and meeting environments (e.g. ST Connect would talk to the community environment at the same time the user attends a meeting)......or would there be a conflict because users would be creating a Community services connection with multiple servers in the same community?
If we shouldn't leave the option blank, should we create custom java methods to default the community services connection onto the meeting server?