Sametime 8.5.x and Virtualhosts

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 More

What you need to know about Sametime 8.5

Sametime 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:

  • Sametime Classic – Most of the promotional materials and discussions which have occurred over the past two years have shown screenshots of the new Sametime 8.5 meetings experience built on IBM WebSphere technology.  If you are not ready to make the jump, the older version of the Sametime Meeting server is still available.  This version is now referred to as Sametime Classic and contains both the Sametime Community and Meeting server.  The Sametime Classic Meeting server has not undergone any major enhancements, however does contain bug fixes.  Companies running Sametime Classic on AIX, Linux and Solaris will see major improvements in the stability of the Meeting Room client when application sharing.
  • What type of directory should you use? – If you want to utilize many of the new features in Sametime 8.5, you will need to use an LDAP directory.  If you’re still using a Domino Directory, you will need to enable LDAP on a server not used for Sametime and connect the Sametime 8.5 infrastructure to it.  Sametime 8.5 is heavily based on WebSphere technology which connects to LDAP, but not native Domino.  The Sametime 8.5 environment will support most LDAP v3 complaint servers, however if anyone out there is running Microsoft Active Directory 2008 Lightweight Directory Services (AD LDS) you’re out of luck with this release. 
  • IBM Domino Server version - The Sametime 8.5 Classic and Community server can be installed on Domino 8.0.x and 8.5 only.  There is no support for Domino 8.5.1 at this time but IBM is working on supporting this in the next releases
  • What type of Load Balancing device to use? – Historically, the Sametime Mux, IP Sprayer or a round-robin DNS could be use to distribute traffic to a Sametime server.  These options are still available for a Sametime Classic or community only server, however not all of these solutions are valid for the newer components such as meetings, proxy and media manager.  These other components need to use either a load balancer or a WebSphere proxy.  A Sametime MUX can not be used with these new components.  Sametime 8.5 does include the WebSphere Edge components as part of the eAssembly package which is a great easy to setup load balancer once you get the hang of it.  It can be installed on a single machine and serve multiple host addresses.  The WebSphere proxy is a component on the WebSphere Application Server.  In testing the software, there were a few issues that cropped up around WebSphere proxy testing with the Sametime Proxy component so it can not be used in those scenarios yet.  Overall, it is always better to install a dedicated load balancer that performs IP-spraying in lieu of a round-robin DNS or using the WebSphere proxy server.
Learn More

Sametime Wiki article: Optimizing Sametime’s Name Lookup Solution

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 More

IBM Webcast slides now available for download

I 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 More

Sametime Applets will expire on May 18th – Download and install the updated applets now

The 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.

securitywarning

Learn More