Last updated June 27, 2005
This document contains information for installing the Lotus Sametime Mobile Proxy component for IBM Everyplace Access Version 5.0
ThisReadme contains the following information:
Sametime Mobile Proxy Description:
When using the Sametime Mobile Proxy, mobile users can access and exchange instant messages securely (128-bit encryption) with other users that also are using Lotus Sametime clients such as mobile devices, desktop clients, and other Lotus Sametime Clients on other platforms.
The Lotus Sametime Mobile Proxy application is a Java-based application that is installed either on a Sametime 3.0, or 3.1 server, or another Microsoft Windows based server. The Lotus Sametime Mobile Proxy application accesses a light weight Sametime Mobile protocol via the device's web browser. In order for the Sametime Mobile Proxy to to function on mobile devices, the STMux server component must be installed. STMux creates a pipe that is capable of routing Sametime messages for Java enabled browsers on WEA supported devices.
STMux must be deployed with the Lotus Sametime Mobile Proxy either on an existing Sametime server, or another server. By default this component is installed during your Lotus Sametime 3.0, or 3.1 Server installation.
NOTE: The Lotus Sametime Mobile Client is not accessible from a WAP enabled device.
Minimum requirements for installing the Lotus Sametime Mobile Client and STMux:
Planning for a Lotus Sametime Mobile Extensions installation
Prior to installation you should:
NOTE: If you are unfamiliar with Lotus Notes and Lotus Domino document concepts, refer to your Lotus Notes and Lotus Domino documentation.
Note: After Installation in a Microsoft Windows Server environment, the STLaunch and STMobileSA services will be loaded as Microsoft Windows Services. To start the services please access the Microsoft Windows Services gui available via the Administrative Tools menu to start, stop, configure the way the application starts
Note: The Sametime Mobile Proxy must connect using a direct socket connection to the Sametime server on port 1516. This is a static port dedicated to Sametime server client applications to connect to.
Uninstalling the Lotus Sametime Mobile Proxy:
Note: If the directory does not contain the group name or if it contains more than one group with the same name, STMobile allows all users in the directory to log in. You can remove the setting STMOBILE_ACL_GROUP from the sametime.ini file, or you can leave the default setting in the sametime.ini file allowing STMobile to function without ACL support.
The following default settings and values are added to the STMobile section of the SAMETIME.INI file. To customize your STMobile environment, edit the default settings and values.
SETTING | DEFAULT VALUES | DESCRIPTION |
STMOBILE_HOST | SametimeServerHostName | Sametime Server Host Name that the Sametime Mobile Application connects to |
STMOBILE_MAX_CLIENT_TIMEOUT | 20000 | Client Inactivity Timeout in milliseconds |
STMOBILE_MAX_OPEN_CONNECTION_TIME | 6000000 | Maximum time that Sametime Mobile Application keeps the connection open. The client will be required to reinitialize their connection |
STMOBILE_MAX_THREADS | 3 | Number of working threads |
STMOBILE_MAX_THREAD_TIMEOUT | -1 | -1 will keep thread alive regardless of working state |
STMOBILE_DEBUG_LEVEL | 0 | Debug Trace Levels
0=No Debug Messages or assertions 1=Critical Messages (Assertions on all levels except 0 2=The default level for all unassigned messages 3=Message Level Indicating Output to Console (Less Detail) 4=Message Level Indicating Output to Console (More Detail) 5=Message Level Indicating Output to Console (Most Detail) All Messages |
STMOBILE_LOG_FILE | trace/stmobile.txt | The directory where the file will be stored coupled with the name of the log file to be generated |
STMOBILE_MAX_USERS | 2500 | Maximum nuumber of concurrent users to be handled by the Sametime Mobile Application. All subsequent requests above this threshold are denied |
STMOBILE_ACL_GROUP | SametimeMobileUsers | SametimeMobileUsers Group name that is in the Domino directory that dictates the users that are allowed to login to the Sametime server as a mobile user. |
STMOBILE_VM_ARGS | -Xmx128m -Xms128m-Xgcpolicy:optavgpau | Used to pass configuration arguments to the JVM |
STMOBILE_LOGIN_MAXTRYS | 3 | 0=Disable
1=Maximum Tries 2=Maximum Tries 3=Maximum Tries You may alternatively delete the value to disable this feature |
STMOBILE_LOGIN_BLOCKTIME | 180 | This value dictates the number of seconds required to pass before a user can log back in. You may increase, decrease, or delete this value. If this value is missing but a value is set for STMOBILE_LOGIN_MAXTRYS, STMobile reverts to the default for this setting. A user who tries to log in while in block mode receives a "Logged Out" event message on their device Default Value is set to 180 where 180=180 seconds |
Lotus Domino Server 6.5.1 Additional Requirements
Lotus Domino Server 6.5.1 is not supported with this version of the Sametime Mobile Proxy. The steps outline here are to assist you in configuring Sametime Mobile Proxy with Domino 6.5.1 if you wish to test this unsupported configuration.
To install the Lotus Sametime Mobile Proxy when running Lotus Domino Server 6.5.1 for your own testing purposes you are required to perform the following steps.
More Information: Because Lotus Domino 6.5.1 was not generally available when this version of the Lotus Sametime Mobile Proxy was released, Lotus Domino 6.5.1 is not supported, not tested and may cause issues not known at the time this readme was written. The Lotus Sametime Mobile Proxy Server Application does not recognize the Lotus Domino 6.5.1 Server and thus will not deploy all the required files correctly. The steps above are an unsupported workaround to resolve this problem.