Stuart Hickson 4.Nov.14 05:57 PM Lotus Notes Sametime Standard 9.0 Windows
I recently built a new V9 Sametime Complete server with SSC, Meetings, ST Proxy and Advanced servers. The v9 Community server cluster already existed so I registered the Community servers and the Community Cluster with the SSC using the provided .BAT files. The two Community servers were setup via STCONFIG.NSF to access two Domino based LDAP servers; primary and DR.
When running registerSTServerNode.bat I had a failure – error message was that both the LDAP directories were not present in the SSC. This was true as I had only created one for the primary LDAP in the SSC. So I created a second one for the DR LDAP server (which is a clustered Domino server so it has a replica of the directory) and the servers registered fine.
Issue is now that we cannot login to any of the WAS based Sametime servers because there are duplicate entries for all users as both the LDAP sources are the same directory! I cannot find reference to this potential issue anywhere in the Sametime Doco; in fact when I created a PMR IBM sent me a link to information on federated repositories in the WAS 6.1 Knowledge Centre (nevermind that ST v9 runs on WAS 8.5.5)
I first attempted to fix this by deleting the DR LDAP server from the SSC. The error message is AIDSC0022E: Delete failed because of dependent products. These products are the two Chat servers. So, I deleted the DR LDAP server from STCONFIG.NSF, unregistered the Cluster and Community servers and reregistered them. This changed the LDAP server associated with the Community Server Deployment Plans tot he Primary but I still couldn't delete the DR LDAP server; same error message. Clearly it is still in DB2 somewhere.
IBM have not been so helpful in recommending a fix except that I could delete the relevant entries from DB2. Instead I'm going to try unregistering the Community servers again and running updateStaleEntry.bat on the WAS server in \IBM\WebSphere\STSCServerCell\console\ to remove the Deployment Plans and entries from DB2. Then I’ll need to reregister the Community servers and the cluster. I'll add a post after I've done this describing the outcome.
Lastly, has anybody added a failover LDAP server in the WAS Console: Global Security / Federated Repositories / Failover server used when primary is not available: and does it work correctly with Sametime?