Open Mic webcast replay: Upgrading and Deploying IBM Sametime 8.5.2 - 19 July 2011
IBM hosted an Open Mic webcast with Lotus Development and Support Engineers on 19 July 2011. The topic was "Upgrading and Deploying IBM Sametime 8.5.2."
Advanced questions and other discussions for this Webcast can be found in this Sametime forum entry.
MP3 file, size of 6,827,094 bytes
Click the link to play the recording. Right-click and select Save As to save to your local system for later playback.
Date recorded: 19 July 2011
Audio approximate time index:
|Time||Question & answer summary|
|29:45||In the chat area of the web conference, there are questions and discussion about upgrading Sametime 7.5.1 Community Server to 8.5.2. Can you suggest some good practices?
If you only want chat function, you simply upgrade Domino to version 8.5.2 and upgrade Sametime Community Server to 8.5.2. You don't need to worry about system console or proxy server if you want only chat. The classic meeting architecture can be retained as well.
There are some subtle changes so review Upgrading from Sametime 8.0.x and 7.5.1 for more info. For example, if you have older clients or a mixed client environment, read the information about setting an appropriate security level (VP_SECURITY_LEVEL) so older clients can connect.
If you decide to convert to LDAP, there is documentation for converting vpuserinfo. Moving to LDAP is not required if you just want to retain what function you have in a 7.5x environment. If you want to move to the new architecture, such as use Sametime 8.5 meetings, you need LDAP and to convert buddy lists.
|31:50||What type of server environment, server sizing, would I need for 150 users? We plan to use chat, A/V, meeting rooms. Right now, I have two servers in a cluster, with a Sametime Community server on one of those servers.
IBM offers a service called TechLine, available through your Business Partner or Sales representative, to do sizing based on your requirements and needs. In theory, given the number of users you have, compartmentalizing DB2 separate from your servers running Sametime components is ideal.
|34:50||I set up a brand new 8.5.2 server that works great but has no buddy list information for users. The previous Sametime 8.0.2 environment uses Domino Directory, and my 8.5.2 environ uses Domino LDAP. What is the process to move the vpuserinfo data from the old server to the new server?
The general process is outlined in the product documentation. You will change a couple of files and do some configuration work on the Sametime server itself. Then you run the name change utility to covert those names from Domino format to an LDAP format.
|37:45||How do features compare for Sametime embedded in the Notes standard client (Eclipse-based) versus the Notes basic client? Can we use Sametime Connect client in conjunction with the Notes basic client?
You'll have basic chat and presence awareness but none of the meeting tools for a Notes basic client. Yes, you can run Sametime Connect, the stand-alone client, and your Notes client separately. You won't have Inbox awareness, etc. in Notes because you are not using embedded.
|39:05||Citrix support? What type of support is available for a Notes 8.5.2 standard client with Sametime embedded running over Citrix?
See IBM Sametime Standard and Advanced Client Support for Citrix (#1497511). Sametime embedded does not provide full support for Citrix platform today, but it is part of the future roadmap.
So Citrix user would not be able to join a meeting, outside of using a Web browser to get to a meeting. Correct?
Yes, that's the case.
What about chat and presence awareness?
Yes, those functions work. One reason we say we do not support Citrix, for example, is the problem relaying audio/video through the Citrix client.
|40:20||What is needed for chat on an Android client?
An Android client uses the Sametime Proxy server as means to communicate with the Community server.
|41:30||For LDAP configuration, what's the difference with using Domino Directory with 7.5.1 versus Domino LDAP with 8.5.2 for presence awareness?
There is no difference in the way presence awareness works. The back-end directory is where to get presence awareness info and resolve the users. The back-end data end differs (Domino or LDAP) but the functionality works the same. Note that the new 8.5 components, like SSC for policy management & administration, are dependent on WebSphere, which uses LDAP for its directory tools.
|43:00||We are evaluating a voice-over-IP project at my company. To take advantage of that technology with Sametime, do I have to use WebSphere-based components?
The Sametime Community server runs on top of Domino. To take full advantage of all features in 8.5, for example, A/V or meetings, then you would do the conversion to LDAP for Community Server as well.
|44:00||We use token-based single sign-on (SSO). We are troubleshooting a problem where a user can log in to Sametime but cannot get access to a Sametime meeting in the embedded client. Is 8.5.2 any different?
Certainly, using SSO for meetings is possible in 8.5.1 and 8.5.2 and working at other customers. Sometimes what's needed is a simple tweak to make sure everything lines up, for example, checking a local client configuration setting. IBM can assist you through the PMR process you've already started.
|45:40||When using chat for Android, BlackBerry, or iPhone devices, when is the Sametime proxy server required?
Android and iPhone require the Sametime Proxy server; you have to install that component at least. You do not do a separate WebSphere install; that installation is part of the Sametime install. It lays down the pieces you need.
(Tip: There are specific URLs from the proxy server to use for iPhone or Android. If you enter the Sametime center URL in devices, then chat doesn't work.)
|47:55||I am moving a server from one platform to another, from i5/OS to Windows, as well as moving from Sametime 7.x to 8.5.2. What files should I copy from the Data directory on the old server to the new server?
To be prudent, make a backup of the entire Data directory so you have any file if needed. The important files to include are ones such as vpuserinfo, stconfig.nsf, stconf.nsf (assuming you've already included core Domino files likes names.nsf). There are other files as well; it depends on the configuration that you have and the uses of the Sametime server, for example, mail-in databases for calendaring and scheduling. In this Open Mic forum, there isn't time to fully answer your question so consider posting it to the Sametime forum.
|50:43||Are there any enhancements or changes in installing a Sametime MUX in 8.5.2?
That really hasn't changed in 8.5.2 as far as Sametime MUX is concerned.
|51:10||If you want mobile access for Android devices, should you put the Sametime Proxy server directly on the DMZ? Do I expose it to the Internet or do a reverse proxy? Do you recommend two Sametime proxies: one for internal, one for external?
You can do this setup a couple of different ways. Yes, you can access the Sametime proxy through a reverse proxy. Or you could put a Sametime proxy in your DMZ that tunnels through to your internal Community server in order to open up the Android population to the outside world. Whether to set up two proxies depends entirely on number of users supporting and how you want your traffic to flow.
|52:50||After upgrading the Sametime Community server to 8.5.2 from 8.5.1, we see have higher network traffic than was in 8.5.1. Any thoughts?
Be aware that the units for debug flags, especially for STPresence tasks, have changed from KB to MB with 8.5.2 so you might need to check in your sametime.ini to make sure using the correct flags. IBM can assist you through the PMR process you've already started.
|54:30||Poll question for live attendees|
|54:50||For iNotes users, can I direct the request through the Sametime Proxy server instead of Sametime Community Server with stlinks?
That function is not available in iNotes but is planned for support in future releases. There is a guide to how you can make that setup work, Lotus iNotes Sametime Proxy package. Be aware, though, that setup is a technology preview that is not formally supported.
Web conference chat consolidation:
|1||Does Sametime 8.5.2 have support on AIX and AS400?
AIX and IBM i are supported platforms. For reference, here are the 8.5.2 system requirements: http://www.ibm.com/support/docview.wss?uid=swg27019598
|2||Sametime 7.5.1 end of service is later this year. How do you upgrade a 7.5.1 server that is used for Chat only? We just need chat.
WebSphere is not required to retain basic chat capabilities. It is possible to stay with the Classic Sametime architecture by upgrading Domino to 8.5x and the Sametime community Server
|3||Do we need to take any special care when upgrading 8.0.2 Community server to 8.5.2 Classic server?
There are some considerations you will want to keep in mind. See Upgrading from Sametime 8.0.x and 7.5.1 in the product documentation. For example, we have adjusted the VP_SECURITY_LEVEL settings. Some of the clients older than 7.0 will not work.
|4||What is the reason for choosing a separate cell for every WebSphere-based Sametime part? It all becomes so big, e.g. 3 JVM only for the SSC part.
That is the WebSphere infrastructure. DMgr, nodeagent and the STConsole server are unique server types. In 8.5.2, Sametime servers can be in the SSC cell so this addresses your question (at least partly).
|5||Will Mobile device chat capabilities require more than the classic Sametime architecture?
Mobile client support requires a Standard license. The BlackBerry client requires a BES server and the Android and iOS clients require the Sametime Proxy server.
|6||Do I need only one server for the Classic Sametime architecture?
It depends on your business requirements. How many users does your environment support, what failover / redundancy requirements do you have, etc.
|7||When using Video with 8.5.2, is it possible to restrict the user population which can actually use the video?
You can use policies for this. Access to audio and video can be restricted by policy. Refer to the product documents on managing users with policies.
|8||I have been testing the upgrade to 8.5.2 and I've followed the instructions on this Wiki page but I did not see Upgrade Policies on the Manage Policies page.
You won't see upgrade policies if you are using default policies, hence nothing to upgrade. You will see that option if you have custom policies.
|9||Will the manage access be public group aware?
The Sametime meeting server does not support public groups. We will record this as an enhancement request.
How about the group chat, i.e. persistent chat room in Sametime Advanced? Are there access controls there public group aware as well?
Yes access controls apply to public groups as well in Advanced chat rooms
|10||Can the packet switcher of the Media Manager be clustered with 852?
No - the packet switcher cannot be clustered. You can install multiple instances for redundancy though
|11||How do I go about implementing just the chat portion of Sametime for Lotus 8.5.2?
You can install the community server only.
|12||Does Web AV work in iNotes or DWA?
No, iNotes is still using stlinks. Web AV is for web meetings. so as long as you get into the web meeting on 8.5.2 version, it'll support audio/video.
|13||Can I control other person's screen? I don't see the option on my thick client...is there any setting on server to be turned on?
There's a check box the user that's doing the screen sharing needs to uncheck in order to allow control. Also you'll need to ensure client to client connectivity on TCP 22222. If you're running Java 6 Update 24 or higher, there's a hot fix required on the Meeting server as well
|14||Can you expand on the mobile support. Will these be apps for mobile phones, i.e. Android/iPhone or via the mobile phones browsers?
Today we provide three native mobile clients: presence and IM for Android and BlackBerry and a meetings client for BlackBerry. We provide browser-based support for presence and IM for iOS. Our plan is to, first, extend browser support for meetings on Android and iOS and to provide a native presence and IM client for iOS. Mobile clients are available with Sametime Standard.
Do the mobile apps connect to Sametime Proxy? or the Community server directly?
Android client is a downloaded/installed app - it requires a Sametime Proxy server to download the client and also for the connection - Android cannot connect directly to the Sametime Community server. The iPhone chat functionality is browser based and requires the Sametime Proxy server
|15||Does installing the Sametime Proxy SN (for clustering purpose) on the same physical machine requires separate IP/Host name?
The answer is no
|16||Are the new client features also in the "Integrated client" for Lotus Notes
|17||Does Sametime need its own server? Or can it run on a server with Domino?
Depends on the component. Sametime community server (chat) runs on top of Domino; other components are typically recommended that they be on their own server - for scaling. For proof of concept, they can run on same box as domino (outside changing ports, for any undue conflict).
Community server requires the Domino server, the other components do not require the Domino server but will typically utilize the WebSphere infrastructure instead.
For chat only and access through the Sametime Connect or Notes embedded client, you can use a Domino Server with the Sametime Entry/Standard Community server. If you want web access or access from some of the mobile clients, you'll need a Sametime proxy server
|18||If you are integrating Instant Messaging and meetings from within Quickr - should these be pointing to the proxy server rather than the community and meeting servers?
Quickr uses stlinks and not STProxy for Sametime integration. So you will still point that to the community server still. Quickr is looking to support STProxy integration but this panel doesn't know a timeline for that yet
|19||If we want our users to be able to use mobile clients like presence and IM on Android when they are not connected to our network, does the Gateway in DMZ would allow that??
The Sametime Gateway is used for access to other SIP/XMPP environments. From what you're trying to do, it sounds like you'll need a Sametime proxy in the DMZ
|20||Installed Sametime Proxy PN on the C: and now it doesn't allow me to install SN on the same drive on the same physical machine. Do I need to install SN on the different drive on the same machine? I finally installed SN on different drive.
Depending on the hardware, you may not see a benefit of installing a SN on the same server. In a multi-node on the same server environment you typically use the same hostname but install to a different directory
|21||If I have a cell based 8.5.1 deployment, should I consider trying to upgrade or replace with a new 8.5.2 deployment?
If you want to expand the infrastructure in the future to include other components, you want want to consider starting new. Using the node configuration will allow the security and WAS configuration to be centrally managed
Is there a migration plan for the DB2 tables at all?
Use the same DB2 databases. Follow the upgrade procedure in the documentation, but you don't need to recreate the database.
|22||Your presentation states that WAS FP 18.104.22.168 is needed , however, Technote 1501441 states that WebSphere 22.214.171.124 are needed for 8.5.2. There is no 126.96.36.199 available on Fix Central. Do I have to locate only the listed parts of the 188.8.131.52 ?
Sametime 8.5.2 Ships with 184.108.40.206. The Technote documents what you need to do if you are running an existing version of WebSphere 220.127.116.11 and you want to install Sametime 8.5 2 ON TOP of that.
|23||Is there any plan to include the 8.5.2 embedded client in the Notes 8.5.3 release so we don't have to separately install?
The plan is to include Sametime 8.5.1 out-of-the-box in Notes 8.5.3. that is subject to change. The panel will pass feedback requesting that change to the appropriate folks.
Sametime 8.5.2 does provide an add-on installer for Notes. Such that you could upgrade embedded Sametime to 8.5.2 using the add-on installer. If you use software distribution software like SMS, Miramba, etc, you could bundle the installs together to simulate a single push.
|24||Instead of upgrading from 8.5.1 to 8.5.2, can I do a new 8.5.2 install and keep the meeting room info from the existing DB2 server?
Yes, just point the server to the existing DB2 database for meetings
|25||What version of the embedded client is in Lotus Notes 8.5.2?
|26||Do you need a full Sametime license to use Sametime on an Android or BB? Or is this access included with the Notes Built-in Sametime Clients?
You need a Standard or Advanced license.
For the server, but what about the client Sametime licenses?
Same. You don't get access to the mobile clients with Sametime Entry.
So if we have a Sametime Standard server - the Sametime Built-in client for Notes would cover the client access via Android/BlackBerry.
If you have Sametime Standard you can certainly use the embedded Sametime Connect client on Notes and, yes, you do get access to the mobile clients. If you want to chat using anything other than iNotes or Notes Client, you have to be licensed for Standard/Advanced. Entry does not license you to use mobile devices or Sametime Connect.
|27||Will it be possible with Notes 8.5.3 and beyond to downgrade the client? ie back to 8.0.2 Sametime client in Notes 8.5.3?
I do not believe you can do this
|28||When is Sametime Proxy support coming for iNotes to replace Sametime Links completely?
The iNotes team is working on that but this panel does not know the ETA.
|29||If the integrated client can't be packaged properly with the Notes install, can we please get it added as an option for Smart Upgrade?
You can upgrade the integrated client with smart upgrade - however, you have to bundle it in with either the base Notes upgrade or with a fixpack install
|30||Is meeting server available for BlackBerry client?
We provide a native meetings client for BlackBerry.
A/V plugin can be enabled too?
We do not support VoIP nor video on mobile clients.
More support for:
Lotus End of Support Products
Software version: 8.5, 8.5.2
Operating system(s): AIX, IBM i, Linux, Windows
Reference #: 7021739
Modified date: 28 July 2011
Translate this page: