The first time you sign into developerWorks, a profile is created for you. Select information in your profile (name, country/region, and company) is displayed to the public and will accompany any content you post. You may update your IBM account at any time.

All information submitted is secure.

The first time you sign in to developerWorks, a profile is created for you, so you need to choose a display name. Your display name accompanies the content you post on developerworks.

Please choose a display name between 3-31 characters. Your display name must be unique in the developerWorks community and should not be your email address for privacy reasons.

All information submitted is secure.

My developerWorks:

My notifications:

Sign out

Select a language:

Understanding IBM Lotus Sametime 8.5.1 enterprise architecture and design

Andy Yiu (andy_yiu@us.ibm.com), Managing Consultant, IBM

Andy Yiu is a Managing Consultant with IBM Software Services for Lotus (ISSL). He previously worked with IBM Support as a Technical Team Lead for the Sametime Support team. His main experience is with the Sametime family of products, including Sametime Standard Server, Sametime Gateway, Enterprise Meeting Server, and the Sametime 8.5x technologies. Andy has presented several Web casts and Open Mic sessions on Optimizing the Sametime server, on Enterprise Meeting Server deployment, and on Sametime Client Deployments. You can reach him at andy_yiu@us.ibm.com.

Summary: This white paper describes the various architectural possibilities for an IBM Lotus Sametime 8.5.1 environment. It discusses how each component can be implemented in both a managed and unmanaged configuration, including example deployments, as well as caveats and restrictions for each component.

Date: 30 Mar 2011
Level: Intermediate

Activity: 6327 views
Comments:

Get the download

This white paper describes the various architectural possibilities for an IBM Lotus® Sametime® 8.5.1 environment. It discusses how each component can be implemented in both a managed and unmanaged configuration, including example deployments, as well as caveats and restrictions for each component.

In this white paper