Deploying Sametime 7.0 Connect for browsers on a Sametime 7.5.x or 8.0.x server

This document contains the following sections:

For all Sametime 7.5.x, 8.0x servers:

• Downloading the Sametime 7.0 Connect for Browsers code

• Deploying Sametime 7.0 Connect for Browsers on a Sametime 7.5.x server
• Enabling the Connect for Browsers link on the Sametime 7.5.x, 8.0x server home page

• Deploying Sametime 7.0 Connect for Browsers on a Sametime 7.5.x, 8.0x server managed by EMS
• Enabling the Connect for Browsers link on Sametime 7.5.x, 8.0x servers managed by EMS

There are two versions of Connect for Browsers available:

• Sametime 7.0 Connect for Browsers: Sametime 7.0 Java Connect client for browsers

• Sametime 7.0 Connect for Browsers (Windows Telephony Toolkit - enabled version): javaconnect_tel.zip is attached below in this document
  
  Note: The javaconnect_tel.zip file does not contain applets signed with the latest IBM certificate so you will see expiration warning messages if using after May 18, 2009 (expiration details). If you need an updated version of Sametime 7.0 Connect for Browsers that is Telephony enabled, then open a service request with IBM Support.

• For all server platforms

<server_data_directory>\domino\html\sametime

• For AIX and Solaris Sametime servers

chown -R notes:notes <server_data_directory>/domino/html/sametime/javaconnect
chmod -R 755 <server_data_directory>/domino/html/sametime/javaconnect

• For i5/OS Sametime servers

CHGOWN OBJ('<server_data_directory>/domino/html/sametime/javaconnect') NEWOWN(QNOTES)
CHGOWN OBJ('<server_data_directory>/domino/html/sametime/javaconnect/*') NEWOWN(QNOTES)

Enabling the Connect for Browsers link on the Sametime 7.5.x, 8.0x server home page

Complete the following steps so that the "Launch Connect for Browsers" link will appear on the Sametime server home page:

1. Open STConfig.nsf on the Sametime server.

2. Open the CommunityClient document.

3. Set 'Launch Connect link' to 'true' and save the document.

4. Restart the Sametime server so that the change takes effect.

If the Sametime 7.5.x, 8.0x server is part of a Meeting Services cluster managed by a Lotus Enterprise Meeting Server, the process for deploying Sametime Connect for Browsers is the same as described earlier ("Deploying Sametime 7.0 Connect for Browsers on a Sametime 7.5.x, 8.0x server") with the following exceptions:

• If the Sametime server has already been added to the Meeting Services cluster controlled by EMS, you must remove it before deploying Sametime Connect for Browsers and re-add it to the cluster afterwards.
• When you enable the Connect for Browsers link in a later step, it will be enabled for every server in the Meeting Services cluster. Therefore, you should deploy Sametime Connect for Browsers on every Sametime server in the cluster.

Enabling the Connect for Browsers link on Sametime 7.5.x, 8.0x servers managed by EMS

Complete the following steps so that the "Launch Connect for Browsers" link will appear on the server home page of each Sametime server in the Meeting Services cluster:

1. Start the DB2 Command Line Processor on the EMS machine.

2. At the db2= > command prompt, type the command required to connect to the DB2 database used by the EMS.

3. Once connected, type the following command at the db2=> command prompt::

UPDATE STCONFIG.ORGANIZATION SET CONNECTLINK_EN = '1';

4. Terminate the connection to the DB2 database and close the DB2 command prompt window.

5. You must restart the STCenter application server in order for the configuration change to take effect.

• Sametime 7.0 Connect for Browsers: Sametime 7.0 Java Connect client for browsers
• Sametime 7.0 Connect for Browsers (Windows Telephony Toolkit - enabled version): javaconnect_tel.zip