Thursday, October 5, 2006

Upgraded to Sametime 7.5 on iSeries (SnTT)

Last Friday night I upgraded our internal Sametime server to 7.5. As part of that process, I had to upgrade the the 6.5.4FP1 Domino server to Domino 7.0.1 and then upgrade ST 6.5.1FP1 to 7.5. This worked like a champ and we haven't had any issues with the server this week. It was a very smooth upgrade.

One thing that we have been waiting on to be "fixed" was the poor screen sharing capabilities of ST 7.0 and earlier. It's one reason I didn't worry about taking the server to 7.0. After testing the screen sharing of ST 7.5 on my test server, I was very pleased with what I saw. So, this was a good reason for us to upgrade. We may be able to get rid of a WebEx account. Speaking of screen sharing, we did have one ST server crash this week while holding a test meeting. I've worked with Lotus a bit on that and it may be related to the Meeting Room preference to optimize screen sharing for performance. This basically drops the color depth to 8 bit and looks pretty bad. The NSD showed a crash due to some type of conversion. I'm thinking it may be the 8 bit conversion, but neither Lotus or I could reproduce this.

Another "gotcha" that we ran into is with the DWA integration with chat. There were actually 2 gotchas. First of all, if you are upgrading the Sametime server and you have chosen to have your DWA server set to load STLinks from the DWA server, you will need to delete the domino/html/sametime/stlinks directory on the DWA server and copy over the stlinks directory from the IM server. Then restart the DWA server's HTTP task and it works! Since I could see the java console error in IE about a StartIM{} function call, I figured it was something with the stlinks jar file. I think this may be the case if you have a 7.0 or earlier stlinks folder on your DWA server.

The second gotcha is also with DWA and I haven't actually "confirmed" it. We are almost complete with an MS XP migration from Windows 2000 in our company. Since going to ST 7.5, I have actually seen that a Win2K user without the Sun JVM worked for a day with the MS VM but then their DWA chat failed and I had to load the Sun JVM. That's really odd that it would work and then fail. It appears that only Sun JVM is supported, though.

Now Playing: "Taking Notes Podcast #34" by Bruce & Julian


No comments: