How can a Lotus Sametime server administrator push down automatic updates to Sametime 7.5.x clients?
Sametime 7.5.x has a new feature that allows administrators to automatically force updates to all of the Sametime 7.5.x Connect clients within the environment.
In general, these updates or patches will come in the form of updated plugins.
In order to automatically force these updated plugins to propagate to all of the 7.5.x Connect clients within the environment, the following steps should be taken.
|Summary of steps|
- Compose a file site.xml. This file (the "update site") will determine which plugins are pushed down to the Connect clients.
- Move the site.xml file to a web server that will host the updated plugins.
- Configure the Sametime server to force clients to check the site.xml for mandatory plugin updates.
- With release 7.5.1, there is the additional step of filling out the provisioning URL in the Policy configuration.
|1. Setting up an update site|
In general, an update site (site.xml) is provided to an administrator when they receive a client-side patch from IBM Support. Therefore, there is no need for the administrator to manually create site.xml.
However, in cases where site.xml is not provided, and a plugin update is available and necessary, the administrator must create their own site.xml using the following instructions.
The Sametime server administrator must set up an update site and fill it with all of the mandatory features which will be updated by all clients connecting to it. This site should be an .xml file with the following template text in it:
<?xml version="1.0" encoding="UTF-8" ?>
<feature url = "" id="" version="">
<category = "" />
<category-def name="" label="" />
XML tag definitions:
feature url = relative path to the update file
id = typically this parameter is set to the name of the plugin feature
version = the version number of the update
category = name of the category type
category-def name = corresponding category with a label assigned
Note: The update file being pointed to by the feature url should be named in the format id_version (for example, ThinkBox_22.214.171.124.zip).
<!--- Example site.xml -->
<?xml version="1.0" encoding="UTF-8" ?>
<feature url=" features/com.ibm.collaboration.realtime.quickresponse.feature_1.1.0.jar"
<category-def name=" Other" label=" Other" />
For more information on creating update sites, please visit Eclipse.
|2. Determining the location of the update site and the updated plugins|
This step assumes the Sametime server will host the update site and the updated plugins.
Note: It is not required that the Sametime server host the update site and the updated plugins. In fact, any web server that can be reached by the users can be used to host the update site and plugins.
However, using the Sametime server to host these files makes these updates instantly available to all those users who can connect to the Sametime server.
- Create a directory on your Sametime server where you will store the client updates. For example, create a directory named STclientupdate in the Domino web server's root directory:
Note: Do not create the directory anywhere within the following directory, as this may cause problems with future Sametime upgrades:
- Store the site.xml and the corresponding plugin updates within the new directory that has been created.
You can create the site and corresponding folders (features and plugins are the recommended names) in the server root. This way, the changes made to the server resources will be instantly visible to any users who can connect to the server. On a Domino Sametime 7.5 server, this location is:
|3. Setting new server attribute for the update site URL|
The administrator must set a new server attribute for the update site url so that clients who log into the server as their primary server will check the server attribute and get the mandatory updates from there. Take the following steps to set the server attribute.
- Using a Notes client, open the stconfig.nsf file located on the Sametime 7.5 server.
- Double-click the 'CommunityClient' document.
- Edit the "URL for UIM Provisioning" field by adding the full path to the update site. Make sure you include http:// in the link. The field does not automatically add it.
URL for UIM Proviosioning: http://
- Save the changes. Restart the server.
The server is now setup to force automatic updates to all 7.5.x Connect clients that login to this specific Sametime server. Note that this step (Step 3) should be performed on all Sametime chat servers in the environment that Sametime 7.5 clients connect to.
|4. Provisioning URL in the Policy|
When a user restarts his client and logs into the pre-configured server as their default community, the following occurs:
- The client logs-in.
- After 60 seconds, the client checks for the server attribute discussed earlier. If it is found, all of the features on the site are compared to the existing found features. If there are some that are missing (they exist on the server but do not exist on the client) the features are downloaded and installed without the user knowing about it, or being able to stop it. This is done in a different thread from the main thread so it should not impact the user experience dramatically (some network traffic will occur here, since the client is contacting the server and the update site, querying for features to install).
- If the Sametime client finds updates to install, it downloads them and installs them. It then asks the user to restart the Sametime client.
What the user sees:
After all the automatic push updates have been downloaded, the client will see the following message:
New Administrator updates have been found and downloaded to your client. Please restart the client now.
This is a non-intrusive message. The user can select to "wait 5 minutes." This clears the message immediately, but the message will return in five minutes. This process can be selected indefinately; however, it is best to press the "Restart Now" button which will restart the Sametime client. The computer is not rebooted, only the Sametime client is restarted.
This was put in place because the download process of updates can be a time-consuming event. This allows the user to finish up any open chats before the Sametime client is restarted.
If the updates have a problem, the user sees an error on the Sametime client.