Random thoughts from an unusual company

Sametime 8.5.2 - Install Cheat Sheet and Forget-Me-Nots

Gabriella Davis  7 June 2011 11:21:47
If you're building a Sametime 8.5.2 environment you may be confused where to start and where to stop.  Don't try and wing it without reading any documentation, you won't lose geek points for at least skimming this entry.  There is a lot of good information in the Sametime Wiki, although don't try going there and choosing "Installation" - that's a blank page.  Go into the Sametime Administration documentation for 8.5.2 here .  Even if you try to follow the documentation many people don't religiously read every page and there are some things you may miss in your hurry to get started.  

Here then is a - very top level summary - list of tasks for building a ST 8.5.2 environment.  It's obviously not comprehensive but hopefully gives you a bit of a checklist to work against.  I'm assuming you want EVERYTHING - IM, Meetings, browse client, audio / video through the clients and through the web.
  • Do yourself a favour if you can and disable IPV6 before starting
  • Install DB2
  • Create System Console database
    • you do this by using the CreateDB script found in the databasescripts folder in the SSC install files)
    • remember to sign in to the server using the db2 admin credentials you just created to create the database, then sign out and back with your admin credentials to carry on
  • Install the Sametime System Console (SSC)
  • Log into the SSC and setup your LDAP server under guided activities
    • Now is the time to sort out your LDAP credentials and import the SSL key if you are using SSL (636) instead of LDAP (389)
    • If you can't connect to your LDAP server use a tool such as Softerra's LDAPBrowser to verify the details you are attempting to use
    • Make sure the hostname of the LDAP server is resolvable from the SSC server as well as from your client where you are configuring
    • Under "Environment" in the SSC choose "Users" and try searching your directory for names to confirm your LDAP configuration is returning what you expect
  • Install Domino as a base for your Community Server and create an admin ID that can manage stconfig.nsf
  • Create a deployment plan for the Community Server and use the admin id that you just created when asked for an "administration id"
    • HTTP needs to be running on the Domino server during deployment plan creation because the SSC will attempt to log into Domino using the credentials you just gave it
  • Install the Community Server (shut down Domino first) using the deployment plan drawn from the SSC

Once the Community Server Is Installed You Can Continue.  You Need To Have A Community Server In Place In The SSC Before You Can Install Other Components There.
  • Create the Meeting server database
    • you do this by using the CreateMeetingDB script found in the databasescripts folder in the Meeting Server install files)
    • remember to sign in to the server using the db2 admin credentials to create the database, then sign out and back with your admin credentials to carry on
  • Create the Meeting Server deployment plan
  • Install the Meeting Server
    • Create a cluster for the Meeting Server if you want one
    • Create a proxy for the meeting server (under "Websphere Proxy Servers) so it's accessible on ports 80 / 443
    • Test logging in to the Meeting server via a browser on http://[hostname]/stmeetings
  • Create the Media server deployment plan
  • Install the Media Server
  • Create the Proxy server deployment plan
    • don't forget the proxy server must have a different hostname than the Meeting Server and that hostname must be resolvable. If you're going to open your servers to the public network all hostnames must also be in public DNS
  • Install the Proxy Server
    • Add the ip address of the proxy server to the Community Server's list of trusted ips (you will probably want to restart the Community Server to force it to take effect quickly or you can wait an hour)
  • Try opening the Proxy server on http://[hostname]:9081/stwebclient/index.jsp , I've also seen it on 9082 and 9084.  
    • If in doubt go into the Proxy Server under Websphere Application Servers and choose "Ports" to see which port it has installed on
  • In the Meeting Server configuration enter the URL and port for the Proxy server under meetingroomcenter.stProxyAddress
For NAT Traversal
  • find the TURN_Server folder in the Media Server install files and copy the contents to any location
  • Modify the run.bat or run.sh files found in that folder so that the line beginning java.exe will have a path in front of it pointing to the IBM jvm.
    • The IBM jvm is available in a Notes install or a WAS install.  On a standard WAS install it will be found at
  • Modify the stavconfig.xml file found in the directory path under the cell profile the Media Server is installed into and set NATTraversalEnabled to "True"  
  • Edit the Media Manager configuration and enter the hostname of the TURN server on either UDP or TCP.  I have been using TCP as a more reliable method through firewalls but YMMV.
  • Make sure all the ports are open as per the documentation.  

For Web Audio / Video
  • Under the Media Server installers find the file sametimewebav.zip and extract its contents into the proxy server directory folder eg
  • Or put all the files on a webserver and add the URL to the files in the proxy server configuration within the SSC
If in doubt at any point that something isn't working. Restart EVERYTHING.  Websphere does like a good restart.

During the install on Windows you will notice that ST installs services for each server.  If you install everything in one cell on the same box you will have services for the SSC deployment manager, the SSC node agent, the SSC itself and then the Meeting Server, Media Manager and Proxy Server.  The last 3 services will not work and will start and then stop again.  
  • I remove the services the installer puts in using wasservice -remove (WASService is found in the bin directory under Appserver)
  • I then add the services I want including node agents for each server using WASService -add -serverName -profilePath and -logRoot

I'm sure I've forgotten something since this was all from memory but I'll edit / update it if I come across more.

Good luck!


1Marie Scott  07/06/2011 12:37:28  Sametime 8.5.2 - Install Cheat Sheet and Forget-Me-Nots

And the Sametime Admin Guide that Gab, myself and Tom Duff have been working on for the last several months (due out in September) will also be a good source of reference! :)

2Carl Tyler  07/06/2011 13:41:30  Sametime 8.5.2 - Install Cheat Sheet and Forget-Me-Nots

Excellent post!

I'd add one thing to the list. Make sure that all servers are pingable, and that firewalls are not stopping ICMP, otherwise the install can fail at various points., setting up LDAP, setting up Proxy etc.

3Thomas Duff  07/06/2011 14:13:47  Sametime 8.5.2 - Install Cheat Sheet and Forget-Me-Nots

Great info, Gab... it should be pinned up on the cubicle wall of each ST admin.

4Michael Kobrowski  07/06/2011 15:14:31  Sametime 8.5.2 - Install Cheat Sheet and Forget-Me-Nots

Yup, printing it and pinning it to my cubicle wall in a minute.

5Michael Kobrowski  07/06/2011 15:15:08  Sametime 8.5.2 - Install Cheat Sheet and Forget-Me-Nots

And most likely purchasing that book in September too. Can it come out earlier please? :)

6Tim Paque  07/06/2011 17:25:42  Sametime 8.5.2 - Install Cheat Sheet and Forget-Me-Nots

Printed... and on wall. :-) good list!

7Mike Smith  13/06/2011 14:25:21  Sametime 8.5.2 - Install Cheat Sheet and Forget-Me-Nots

Gabriella also talks about Sametime 8.5.2 on the 'This Week in Lotus' podcast 055 - { Link }

8Saad Alrasheed  16/06/2011 11:06:59  Sametime 8.5.2 - Install Cheat Sheet and Forget-Me-Nots

Great information,

I just have one question can install Sametime 8.5.2 on one machine for a pilot system? and if yes, is the installation procedure the same as mentioned here?

9Alexey Zimarev  20/07/2011 16:01:16  Sametime 8.5.2 - Install Cheat Sheet and Forget-Me-Nots

Great, however not clear what to do with this modified run.bat for the TURN server.

Would be nice to hear upgrade experiences. I started last week with 8.5.1 to 8.5.2 upgrade and have opened three tickets already. I need to install a fresh proxy server - can't do this. Meeting server lost all static resources. Media stopped working. The only thing I have now is the old good Domino/Community server, none of new fancy features work after the upgrade :(

10Christin Linke  04/08/2011 09:59:32  Sametime 8.5.2 - Install Cheat Sheet and Forget-Me-Nots

Great post and the kind of list I have been waiting for!

Already pinned on my wall... as I will need it desperately to for the unavoidable migration from to 8.5.2. (Behold the NAT! :)

Thank you, Gab.

11Alex Novak  05/08/2011 12:42:40  Sametime 8.5.2 - Install Cheat Sheet and Forget-Me-Nots

Here are my meeting experiences; after upgrading an 8.5.x environment all ST Services run well - except the new WebAV feature.

I got at customer and inside me test environment 408 error messages, if i try to start AV within meeting.

It seems there is a problem, if you installed the old environment with the Cell deployment (each ST service in its own cell). Installation inside the SSC Cell - WebAV works fine.

We also have open PMR concerning this AV problem.

At the moment my upgrade path looks like this (if you want to use WebAV).

1.) Unregister all ST Services from SSC

2.) Update DB2 Software & DB2 Tables (SSC & Meeting)

3.) Update SSC

4.) Update Community Server and register into SSC

5.) Install new instances for Media & Proxy into SSC Cell

6.) Map existing Meeting DB into SSC and install new Meeting Server (you should keep all old Meeting configuration & rooms)

7.) Implement SSO between SSC Cell & Domino

8.) Make additional configuration for WebAV

opt. install TURN & Bandwith Manger

The good thing about 8.5.2 - you could now easy install ST Advanced AND all works fine in one cell (and for demo environment all on ONE BOX)

Information you should now.

- Remote control NOT working for webbrowsers on WAS Meeting server (like in classic meeting)

- WebAV is only visible if you have ST Proxy (with ST Community Server) configured and connected (not very proud about this for companies without domino & chat feature running)

I will continue to get more experience with 8.5.2 and will tell more @AdminCamp 2011 in Gelsenkirchen

12Richard Lugtu  06/09/2011 02:19:39  Sametime 8.5.2 - Install Cheat Sheet and Forget-Me-Nots


I'm new with Lotus Sametime, can Sametime 8.5.2 works with only installing a Domino server and Sametime Community Server. Only needs IM in lotus. Please help.

13Gabriella Davis  13/09/2011 13:26:52  Sametime 8.5.2 - Install Cheat Sheet and Forget-Me-Nots

@Richard. Yes if all you want is IM and IM within the Notes client then all you need is Domino and not any WAS components

14Marcie K. Vantrease  30/09/2011 17:20:56  Sametime 8.5.2 - Install Cheat Sheet and Forget-Me-Nots


I have a couple of questions. We are a medium sized company with 5000 notes / sametime users with the potential to increase our numbers (20000+ employees). We had a Business Partner install our ST 8.5.1 installation. We are now getting ready for an upgrade to 8.5.2. In the meantime, we are trying to duplicate our Production environment in a test area. Current production install has 3 servers. One has DB2/WAS/SSC installed. 2nd server has Community, Proxy & Mobile installed. 3rd server has Meeting & Media Manager installed. First question, is this a viable setup or should we consider moving to 2 servers. 2nd Question. If we stay with the 3 server setup, would there be a better deployment scenario that we should move to. As Domino Admins, we have searched many websites for a best case scenario but, most are referring to everything on 1 box. We always enjoy your guidance at Lotusphere and thought you would be the best person to ask for advice.

Thank you and have a good day.

Marcie K. Vantrease

SavaSeniorCare - Houston, TX

15Gabriella Davis  04/10/2011 17:52:04  Sametime 8.5.2 - Install Cheat Sheet and Forget-Me-Nots

Hi Marcie

Because of the changes in WAS deployment in Sametime 8.5.2 from 8.5.1 and the new ST server components I have been rebuilding existing 8.5.1 customers onto 8.5.2. For example in 8.5.1, all servers had to be installed in their own cells if they were on the same computer which made administration more overhead, this isn't true with 8.5.2.

There are several other reasons why you should consider a rebuild rather than an upgrade but it depends on your existing network and WAS infrastructure. We should probably take this offline and I'll be happy to answer further questions. Email me on gabriella at turtlepartnership.com.


16Marcie K. Vantrease  19/10/2011 19:00:14  Sametime 8.5.2 - Install Cheat Sheet and Forget-Me-Nots

Hi Gabriella,

I know that you are extremely busy but, I responded to you in an email sent on 10/14/2011.

We are pursuing the idea of a New Deployment instead of an upgrade but, want to make sure that all the chat groups and meetings get transitioned over so, we are digging through those issues.

Thanks so much. Have a great day.


17Scott Beattie  26/10/2011 05:38:32  Sametime 8.5.2 - Install Cheat Sheet and Forget-Me-Nots

Another great tip is to work out what database you're going to need to create prior to starting. That way once you login as db2admin to build the DB's you can create them all at once.

This will save you having to log out an log back in as db2admin to create them later.

18Sarwar Javaid  26/11/2012 09:42:32  Sametime 8.5.2 - Install Cheat Sheet and Forget-Me-Nots

Chat logging: While using Sametime Proxy Server 8.5.2 - IFR1 (how to enable web chat logging)

19wesley  11/10/2013 15:53:37  Sametime 8.5.2 - Install Cheat Sheet and Forget-Me-Nots

hi can u please tell me if it possible to setup the whole commnity on one server , and if so what do we have to change during the setup, thanks

20AShah  23/10/2013 12:52:08  Sametime 8.5.2 - Install Cheat Sheet and Forget-Me-Nots

Hello Guys, Can anyone share link for supported web browsers for IBM Sametime proxy 8.5.2 IFR1.

As per my investigation at this point ... only firefox is supported. All other browsers ie and chrome are behaving abnormally.

Thank you.