Sametime 8.5.x has really helped in consolidating management of Sametime and WebSphere configurations into a single location. However, it is with this configuration that some additional issues crop up. Several Sametime components utilize the a technology called RTC4Web. This is used extensively in the Sametime Proxy, Advanced and Meetings server components. When more than one of these components is installed in the same cell, messages may be misrouted to the incorrect location.
Virtualhosts can help to route traffic to a specific location. By default, everything is assigned to default_host. To segregate the traffic, you will need to create a new virtual host. The hostnames which you provide should always include the load balanced hostname for the service and the ports through which the service is accessed. Administrators may optionally add the backend servers and the respective ports to make it easier to troubleshoot the infrastructure in case problems arise.
Another trick with virtual hosts if that they can be used for security. If you for example, do not want users to access the Sametime proxy service directly on the backend server, administrators count theoretically restrict access to only the load balanced hostname. On the other hand, you may also remove port 80 from the virtual hosts configuration and in doing so force everyone to access the service through a secure connection on port 443.
For information on setting up the WebSphere virtual hosts, take a look at the following IBM Technote:
IBM WebSphere Proxy redirects to Sametime Proxy unexpectedly
Learn MoreSametime 8.5 marks a major turning point in the product platform from IBM Lotus Domino to the IBM Websphere and DB2 infrastructure. As you plan out your environment, there are a couple key points to consider:
I would like to announce a series of Wiki articles which outline what you can do to improve Sametime name lookup performance. I have given some presentations on this in the past but the wiki article below gives the most comprehensive set of documents on our optimization strategy. I would encourage every administrator to take a look at these documents.
Special thanks to David Tull and Jeanmarie White for their contributions in publishing these articles.
Sametime Wiki: Optimizing_Sametimes_Name_Lookup_solution
Learn MoreI would like to thank all of you who attended today’s IBM Webcast on Sametime Resolve, Notes Instant Messaging and Directory Performance Considerations. I sincerely hope that everyone who attended took away some new nugget of information. Please feel free to post comments about the presentation here. I do welcome your feedback. Alternatively, you may also provide feedback to me via email at andy_yiu@us.ibm.com.
The slides are now available for download and the recorded presentation should be posted shortly. I will update this post when I receive the links to the recorded presentation.
PDF of Presentation: IBM Webcast – Sametime Resolve Performance Considerations
Learn MoreThe certificates which were used to sign the Sametime Applets (Meeting Room client, Sametime Java Connect, Directory Applet, Sametime Links), will expire on May 18th this year. IBM has been working to resign these applets as quickly as possible. All of the applets from Sametime 7.0 to 8.0.2 have been resigned with the updated certificate. If you do not update the applet files on the server, users will see a Java security prompt asking them to approve the execution of the applet. However, users will still be able to use the applet.
Here’s the best news though. You do not need to open a support ticket with IBM to download the updated applets. They are available on IBM Fix Central for immediate download! For installation instruction and download information, see IBM Technote 1390778.
The Domino Applets will also expire on May 18th. Information on downloading the Domino Applets is available in IBM Technote 1381298.
Learn More
Recent Comments