Client automatic update process
To ensure all clients have the same features, enable the update policy key to have the server push updates out to the IBM® Sametime® clients.
Setting up automatic updates
When the user
logs in from the client, the client looks in the preferences.ini file
located in the update plugin (com.ibm.collaboration.realtime.update\preferences.ini)
root directory for the existence of the runme
property.
If the property is present and is set to true,
then the update plugin continues. The client then checks the policy
key CONNECT_UPDATE_URL on the default Sametime Community Server.
If the server is 7.5.x or later then you, as Administrator, can define
the policy to tell the client where the update site is located.
If the policy key is not set on the server, it is missing for one of two reasons:
- The administrator did not set the key in the policy settings on
the Sametime System
Console. The key is set in the Sametime update site URL field.
From the Sametime System
Console click Manage Policies - Instant Messaging tab. Select the
policy and click Edit. Note: For more information about the Instant Messaging policy settings, see the topic Sametime Instant Messaging user policy settings.
- The Sametime Community Server is a pre-7.5.1 version.
If the key is not found, the client will search the preferences.ini file located in the update plugin (com.ibm.collaboration.realtime.update\preferences.ini) root directory for the adminUpdatePolicyURL value. The client then silently downloads all updated features it finds in the administrator's update site and installs them. Updates of features from this site are required so the client does not have the option of not installing them. Once installation is complete, the user receives a message announcing that new updates have been installed and that the user should restart the Sametime client. The user can click the restart button or press a five-minute delay button. If the user is involved in chats with other users, he or she can continue to delay at five-minute intervals as long as needed. After the restart, the client checks again to see if there are more updates, and if it finds none, the user is not interrupted again. This update process takes place each time the user restarts the client and logs in into the default server.