Converting my existing Sametime Entry server to a full Sametime Community server was a snap. We've used IM and presence awareness for the last 6 months and we've got the licensing for Sametime Standard and nearly there for the SUT Lite licenses. Ideally in the end I'll have a full ST deployment w/SUT Lite all running under our Power Systems server. That's one box. Then a clustered solution to another one.
Converting the Sametime Community Server from using Domino to LDAP in order to use the Sametime System Console (and the rest of the features which I will put on Linux partitions underneath IBM i) wasn't too bad. There were a couple of hiccups and the server was down for a good few hours because the IBM call center logged my call as a severity 2 instead of a severity 1. Whoops. Once I got some support we ironed out the issues.
Installing the Sametime System Console on IBM i (and all the Websphere stuff that goes with it) went really smooth. My only gripe is that the Sametime 8.5.2 wiki lists Websphere Application Server Network Deployment as a "requirement" so I assumed I needed to download it separately, install it, patch it and then install the SSC. However, the SSC installer automatically installs and configures WAS ND. A few hours wasted but I was able to brush up on my QSHELL, so not all was lost.
The only issue now is registering my Community Server with the SSC. I get the following error and I can only find one reference to it online:
Deployment record updated successfully.
preReqType:LDAP
Attaching pre-requisite -LDAP
Failed to attach prereq -LDAP
Make sure the dependent pre-requisite is registered with the Sametime System Console.
It's funny because the SSC binds with the LDAP server just fine...I can see the users, etc. Time for a new PMR unless someone else has any ideas.
Look at technote 1503682 "Failure to manually register a Community Server with the Sametime System Console" at http://www.ibm.com/support/docview.wss?uid=swg21503682.
ReplyDeleteI'll try to improve the indexing for that technote so it'll rank higer in search results.
--Jeanmarie, IBM Support
Jeanmarie, the host names do match in the SSC and the Stconfig.nsf LDAP document. I should've listed that technote as the only one I could find, however it didn't solve the problem.
ReplyDeleteIn the end, I reinstalled the whole thing. Works fine a 2nd time with no issue. I must have missed some error in the installation log the first time around.
ReplyDelete