A replay is available for "Configuring and deploying Sametime for mobile users," an Open Mic webcast with Lotus Development and Support Engineers hosted on 27 March 2012.
This document includes a summary of questions and answers from the session, as well as the presentation and recording of the call. Advanced questions and other discussions for this Webcast can be found in this Sametime forum post.
Some other useful technotes on this topic are as follows:
Audio approximate time index:
|Time||Question & answer summary|
|27:20||Fix OBEN-8SDLGS came out recently, primary for Connections integration, but it includes some mobile fixes as well. I notice some blogs speak of it been superseded. Can you speak to that fix?
You do not need or require this fix in order to get started with mobile. However, because it is a newer fix package and does includes fixes to integrate with Connections 126.96.36.199, I recommend you upgrade to that when you get an opportunity. The Sametime team builds fixes for IFR 1 on a reasonably regular basis, in response to customer-reported problems. The fix that supersedes OBEN-8SDLGS was posted 26 March 2012; refer to technote 1588293 for more information.
|29:10||The fix install instructions in technote 1588293 indicate you modify the stproxyconfig.xml file. Do you make that change directly on the proxy server or on the deployment manager?
When you manually modify an xml or configuration file, always do so from the deployment manager, then push the changes out from there. If you go directly to a node and replace the file or update the file there, the changes will be overwritten during the next sync process. We will update the technote.
|30:05||Does this fix conflict with the one you mentioned during the presentation?
No, that TPAE-8S5TPP hotfix is strictly on the system console, not proxy server. There is no conflict.
|30:50||Is it OK to run the DB2 database for system console, feedback, etc. all on the same server?
Yes, the databases themselves can be run on the same DB2 server.
|31:15||Can you control mobile client settings, like to disable chat logging on the local device? Is that a policy?
The panel knows of no policies for setting specific mobile client requirements. There is a policy setting "Allow mobile client" in the Instant Messaging user policy, related just to the ability to use the mobile client.
During the call, a panel member thought there might be a policy for the chat history that could apply to mobile devices but did not recall where. Additional research after the call determined there is no such setting. The chat history settings are flagged IC, which means applying to the installed client (IC) only.
|33:00||Can you run the Sametime Proxy server on an IBM i system?
Yes, you can run on IBM i; it is a supported platform.
|33:25||We are running Sametime Entry. Do we need to upgrade our licensing to Standard to allow for mobile devices?
Yes, you need Standard; the mobile clients are not licensed for the Entry version.
|34:00||We run Sametime 8.0.2 but are not yet ready for a full upgrade to 8.5. Is there a way to get started with Sametime mobile device access?
The mobile device support goes through the Sametime Proxy. The Sametime Proxy is the one talking to the back-end server and will work against older versions of the Community server like 8.0.2. To get started, you would need to set up a Sametime 8.5 proxy server in front of that environment. Your specific company requirements will determine whether the server is in the DMZ or reverse proxy.
The presentation "IBM Sametime 8.5.2 IFR1 Implementation - From Zero To Mobile - Make your boss happy" goes into some details about this particular scenario.
|35:45||You mentioned the photo port during the presentation and in the web chat. How does it work with business cards?
From the web chat:
The photo port is used if you have a reverse proxy before your server that serves up business card photos. If that photo port is 0, then the business card photo URL that is passed from the proxy server itself is used. If the photo port is non-zero, then it will substitute the port on the business card photo URL from the server with that photo port value.
Additional notes from audio:
You can configure the proxy server to send the URL for the business card photo. However, the URL could have a port for an internal address, inside of the company. If you are using a reverse proxy to get to that URL, sometimes there's a need to substitute a port with what the Sametime Proxy server returns in that URL.
As noted, this setting is applicable to reverse proxies, in the case you have a different port than the port used on your URL that you send from the Sametime Proxy server. The parameter allows for the port substitution in the URL. A setting of 0 indicates to leave the URL unchanged. That photo URL has to be accessible externally through the reverse proxy.
The IBM Sametime team will be working to make this parameter and usage easier to understand.
|38:05||This question is not about Sametime. We want to support Sametime on Android devices through the Lotus Mobile Connect client. There is no support for Android yet. Do you know when that's planned?
The panel does not have information on plans for Lotus Mobile Connect for Android. No official plans have been announced, but there was discussion about this topic at Lotusphere. You can review the Lotusphere 2012 materials for information on this product. (The Lotusphere 2012 materials are stored in the Lotus Greenhouse; register for a Greenhouse ID to login and view the materials.)
Web conference chat consolidation:
|1||Is Domino 8.5.3 supported as a base for installation for this version of Sametime Standard, or should I first back-level Domino to 8.5.2 FPx?
Yes, Domino 8.5.3 will allow installation of Sametime 8.5.2 IFR 1.
|2||Is the Proxy Server database supported on IBM i?
[Also in audio]. Yes, refer to the System requirements for IBM i and Preparing to install on IBM i in the product documentation.
|3||Can this be actioned after the Sametime proxy has been installed?
If you are referring to the proxy database, yes, the database creation is done after the Sametime Proxy is upgraded to IFR 1.
|4||We have only a single VMware node defined in our DMZ for installation of ALL the servers required for Sametime Standard (Domino, WAS, ST, ST Proxy, DB2); Is there a technote regarding total CPU count, RAM, DASD requirements for such a configuration?
Check the system requirements, http://www.ibm.com/support/docview.wss?uid=swg27023283, for the supported and related software needed (including memory and CPU). If you need more information, IBM Techline can do specific sizing including hardware needs. Work with a Business Partner or IBM account team to contact Techline.
|5||Is the "Remember the password" option controlled via policy? If a user chooses Remember but corporate policy does not allow, can an administrator change it later?
No, this function is related to the device configuration. The 'remember password' is part of the keychain on the iOS device. There is no policy configuration yet. You cannot affect the user's choice.
|6||Can we get more information on the "photo port" setting and how it works?
Refer to the audio transcript above.
|7||From the iPhone connect install, the "Host Server" has us write the FQDN, while the Android install the "Server" field we had to put the URL - is that accurate?
Correct. On Android connectivity settings, it requires you to enter http:// or https:// to server address. While on iOS, you select a use secure checkbox.
|8||Does the Sametime Proxy server need the DB2 in a stand-alone environment if you just want to connect it to a existing community server?
Yes - If you want the iOS push notifications, you have to have the DB2 database. You can use an existing DB2 infrastructure though.
|9||There shouldn't be a problem for Sametime Entry users to chat with Mobile/Sametime Standard and above?
I can't think of a reason why they couldn't talk to each other. But Entry users cannot use mobile devices.
|10||What is the first step in setting up the Sametime Proxy?
Here are some good references for install and setup for going mobile:
|11||How are updates going to be pushed out to the clients?
The updates are handled by the iOS and Android automatic update process. The native clients for Android or iOS use the application delivery mechanisms for each device platform: iTunes AppStore and GooglePlay.