Sametime 9.0.1 Cumulative Hotfix for Meeting Server and Proxy Server - Sametime WebPlayer support for Firefox 52 and above
A new cumulative hotfix for Sametime 9.0.1 Meeting Server and Sametime 9.0.1 Proxy Server is available.
IBM is releasing this hotfix to support Sametime WebPlayer for users who are upgrading to Mozilla Firefox 52.
Mozilla Firefox 52 is a non-ESR version and no longer supports Mozilla's NPAPI.
For more information, please see this technote.
We strive to bring you the topics that will answer questions that you're currently facing and give you access to the technical experts who can provide that in-depth learning experience.
JaredWallace 310000KF1P Visits (6939)
Occasionally, after installing a new Sametime server, the installer fails to register and federate the server. To remedy the situation, we offer a script named registerProduct.sh (or .bat for those poor souls on Windows). I had a customer try and run the script, to only partial success. The script successfully registered the server, but did not federate it. The error message he got was this:
I dug into our script and Java code, looking for what may have caused the error. After understanding what it was trying to do, I re-examined the logs that were generated. The logs are located in the same directory as where the script was run. At the bottom of the logs was this message:
2016:5:17› 14:28:40› com.
The relevant part is at the beginning of the path - notice it starts with "Manager"
Reviewing the text printed to the screen after running the script, we see a more clear example of the issue:
Parameters passed are: -federateNode, C:\I
Note there are three parameters: [-federatenode] [C:\
This is not what we want - we want two parameters:
[-federateNode] and [C:\
Our code is equipped to handle three parameters, since you have the option of passing in [-silent] as the second parameter. Unfortunately, all we do is check to see if the second parameter is exactly equal to "-silent". If it isn't, we just ignore it and move on. Our sanity checking for the third parameter involves checking to see if it ends with "bin", and whether the path actually exists. That second check is what generates the error message
"AIDSC1689E: JRE path entered does not seem correct."
To resolve the issue, you have three options: (1) escape the space (C:\
You can then re-run the script, as it can be run multiple times with no ill effects.
Dwight Harper 120000A87B Visits (6961)
If you have been thinking about migrating to cloud meetings in order to take advantage of the simplified administration and rich feature set the cloud offers, you will want to see these two new videos presented by Senior Software Engineer, Josh Edwards.
The first video is an introduction and walkthrough of IBM Connections Meetings Cloud.
If you already using IBM Connections Meetings Cloud and you or your users have questions about how to enable screen sharing and audio/video, you will want to check out this video:
Dwight Harper 120000A87B Visits (7431)
When you call IBM Support for help, you might wonder “Just who is this that is helping me resolve this issue?" Over time, you may begin to prefer a particular Software Engineer who has saved the day for you several times.
Does the name Joshua Edwards ring a bell?
As a very technically well-rounded engineer, Joshua continues to provide solutions to difficult issues facing IBM clients.
You might have heard Joshua as a presenter or panelist on several Open Mic or Ask the Expert webcasts. Or you might have viewed one of his videos on our YouTube channel.
On August 3rd, we will be hosting an Open Mic on the topic “Advantages of IBM Cloud Meetings with Feature Walkthrough.” In this webcast, we plan to discuss popular topics like using video and VoIP in meetings, as well as how to use meeting features to make your meetings more productive.
Be sure to pencil in this meeting on your calendar and remember to join Joshua and myself for a very interesting session.
So my entire infrastructure is on RHEL 6.7 (except MCU, which is 6.5 because MCU is picky). I personally hate typing, mainly because I really stink at it. In order to make my life easier, I've created start and stop scripts for all my servers. This is especially crucial for servers like the Video Manager, which require startup in a specific order. I chose to do this instead of creating services that auto start, just because I'm a control freak who likes to manually control everything. It's probably helpful to understand that my SSC, Community and DB2 servers all reside on a single VM (not recommended for production of course).
#1: Without further ado, here's my Community/SSC/DB2 startup script
This script, like all my scripts, resides in the "/root" directory with 700 permissions. This ensures it can only be run by root.
So the first section, titled "Kill any leftover pids, is because often when one of our servers shuts down dirty, it leaves pid files laying around. If you don't kill these off, your server will startup in a bad state, if at all. Obviously, if you have anything other than a Sametime server installed, you should make sure the other programs don't also leave pids in the "/opt" directory, lest you discover new and interesting ways to break them when you run this script.
#2: Stopping is slightly different
First, you need to type "quit" in the terminal window where Domino is running. Then you can run the following script to stop. Note that you have to pass in username and password to stop the server.
Again, straightforward. Note the stopping order is the inverse of starting.
#3: Advanced script for other servers
The other servers are not quite so interesting, here's the Advanced script (I have a cluster, and the WAS proxy resides on this node, so there's an extra line to start the proxy).
Stopping follows the same template as the Community script.
#4: Starting SolidDB to ensure Vmgr startup success
You can use the above scripts as general guides for any server you wish, with the exception of the Video Manager (Vmgr) and the MCU. The MCU is (or should be) started automatically. The Vmgr is a stand alone server (not federated to the SSC lke all the other children) so you have no node agent to start, but you do need to make sure SolidDB is started first - it's critical to successful Vmgr startup.
#5: Shutting down Vmgr
Shutting down the Vmgr is unique as well; after running the script you'll have to enter SolidDB credentials (default is admin:admin)
JaredWallace 310000KF1P Visits (8636)
One of the things that immediately frustrated me when I went to install my MCU was the slightly obscure fact that RHEL 6 requires quite a few dependencies. We don't make this very obvious in our documentation, and if you do happen to notice, the link we give you brings you to this technote, "Lis
Now the technote is accurate in what it lists. My problem is that it's not set up to just copy and paste. Moreover, why on earth do we require manually installing this stuff? Why can't we release an RPM that does this automatically?
If you just want to install the dependencies, and get on with your life, here's a single command you can copy and paste (remember to be root, and that this is for Red Hat 6.X only!):
yum install dialog glibc-devel glibc-devel.i686 glibc-common zlib-devel.i686 zlib-devel libgcc.i686 libgcc libs
Now instead of being content with that on my environment, what I decided to do was make a dummy package, that would handle the dependencies for me, as well as ensure that httpd was NOT installed (since that prevents the MCU install from proceeding). If you have plans to install a large number of MCUs, this may make sense to replicate. I know practically nothing about package management, but there is a nifty tool called FPM (effing package management) that is super simple to use. (For details on FPM, see http
What you need is the latest MCU from Fix Central (htt
Steps (perform these on a Red Hat 6.X box):
1) Install FPM
yum install ruby-devel gcc
gem install fpm
2) Use FPM to build the dummy MCU package. Note that specifying 32 bit versions of dependencies ("-d") requires a different syntax than yum.
fpm -s dir -t rpm -n wallaceMCU -d dialog -d glibc-devel -d 'gli
Explanation of options:
-d : dependency
-s : source for the rpm is a directory
-t : target is an rpm file
-n : name of the resulting file
The end result is an rpm file named "wallaceMCU.rpm". You can install this on your MCU server by copying it over and running "yum install wallaceMCU.rpm". That action will install all dependencies, make sure Apache (httpd) is not installed, and will extract the MCU code itself into "/So
Jared Wallace, IBM Software Engineer, Sametime Extended Support
Dwight Harper 120000A87B Visits (7859)
The Sametime Proxy Server Cumulative hotfix for April 2016 is now available. Here are some highlights of what's included:
For more details about this fix, including a complete Fix List, refer to http
Dwight Harper 120000A87B Visits (8914)
The Sametime 9 Rich Client Cumulative hotfix for March 2016 is now available. Here are some highlights of what's included:
migFix (IBM) 270000N9EW Visits (7743)
I can't tell you how many times some Sametime inst
Wow! The tips helped me help my customer and I've since shared it with other engineers so I'm sure it's helped others. And I'm sure it can help you too!
Scott Puls 110000BY2Y Visits (10173)
At our next Support Open Mic Webcast this Wednesday, June 17, the IBM Sametime team will present on the ways clients set up business card and photos, as well as files and debug information to collect for a PMR. The session will also contain information on the IBM Connections business card plugin and concatenation of fields.
We hope you can join us for this interactive, educational, and lively session.
Scott Puls 110000BY2Y Visits (9669)
This session will cover IBM Domino as an LDAP client in Directory Assistance, emphasizing SSL connections to LDAP server, and will also include a dive into Domino LDAP security configuration, SSL and POODLE vulnerabilities if Sametime uses Domino for its LDAP server.
After a presentation, attendees will have an opportunity to ask our panel of experts questions. Throughout the event, attendees will also be encouraged to comment or ask questions in the IBM Connections Meetings Web chat.
Karen Gallo - IBM 100000FG9T Visits (9912)
We have a new video uploaded on our Coll
This 7-min demo overview by Tony Payne is an excerpt of a Sametime Open Mic session titled "SSL and Sametime: POODLE Training 101" (held in March 2015). It demonstrates using the Sametime System Console -- showing some default settings, key stores, and cell vs. node ideas within the concept of the WebSphere Application Server (WAS). The full playback recording of this entire Open Mic event, along with the presentation used, can be found here.
For additional Sametime support resources, visit the IBM
Community Server 9 HF1 and version 9 Limited Use are affected by vulnerabilities in OpenSSL when TLS is enabled
Karen Gallo - IBM 100000FG9T Visits (9296)
If you have enabled TLS in IBM Sametime 9, be aware of a new security vulnerability and available patches to address the vulnerability. Please note: This security vulnerability does not affect IBM Sametime 9 Community servers if TLS is not enabled (which is the default).
For a download link and install instructions please visit:
For additional Sametime support resources, visit the IBM
Scott Puls 110000BY2Y Visits (11815)
As a reminder, technical support for the following IBM Collaboration Solutions products will end on 30 April 2015:
Version 8.0.x of Sametime and version 8.5.x of Sametime Entry
Lotus Symphony - all versions
Lotus Protector for Mail Encryption - final version
Lotus ActiveInsight - final version
For End of Marketing (EOM) and End of Support (EOS) dates for other IBM software, visit the IBM