Installing Lotus Sametime 7.5 Cumulative Fix Pack 1 (CF1)

About Lotus Sametime 7.5 CF1
Prerequisites
Installation Procedures (Windows, AIX, Solaris and EMS)
Installation Procedures (i5/OS)
Update stpolicy.nsf for new file transfer policy

• Lotus Sametime 7.5 CF1 contains important fixes and is highly recommended for all Sametime 7.5 installations. This package is required for customers who plan to implement the Sametime RTC Gateway or the Sametime Mobile Client.
• Sametime installations that plan to implement the Sametime Mobile Client must install Lotus Sametime 7.5 CF1 before installing the Sametime Mobile Client updates. The Sametime Mobile Client updates should always be done last.
• To view the list of of fixes included in CF1, visit the IBM developerWorks Sametime product page (http://www.ibm.com/developerworks/lotus/products/instantmessaging/) and click on "Lotus Sametime fix list".
• When you use this CF1 package to update your i5/OS Sametime 7.5 server:
  • The Sametime server code is updated
  • Updated versions of the Sametime 7.5 Connect Client are copied to the server. After you install CF1, anyone who downloads the Sametime Connect Client from the server will receive the updated CF1 version of the client.
  
  Note: The Lotus Sametime 7.5 for i5/OS installation guide (stinstall.pdf or stinstall.nsf) includes instructions for "Copying Lotus Sametime Connect to your Sametime server" so that your users can download and install Lotus sametime Connect from the Sametime server. This step is no longer necessary. Sametime Connect clients from earlier versions of the Sametime 7.5 Client CD or Web download (Readme file dated prior to October, 2006) do not include the CF1 fixes. Do not copy these earlier versions of the clients to the Sametime server after installing CF1.
• With Sametime 7.5, administrators can use a batch file to enable silent installation of the Sametime 7.5 Connect Client for end users. You can pre-configure the license agreement, client installation directory and the fully qualified name of the Sametime server. For more information see technote #1245381.
• Users who have previously installed the Sametime 7.5 Connect client do not need to uninstall it before installing the updated version of the client provided with CF1.
• More information about Sametime 7.5 CF1 is available in the updated Lotus Sametime 7.5 Release Notes, available from the online Sametime documentation page (http://www.lotus.com/ldd/notesua.nsf/find/sametime).

• Lotus Sametime 7.5 must already be installed on your system before you install the Sametime 7.5 CF1 package.
• For Windows, AIX and Solaris, you must configure your Sametime server before installing CF1.
• For i5/OS, it is possible to install Sametime 7.5 CF1 either before or after configuring Sametime servers. However, installing CF1 first, before configuring any servers, allows you to avoid some manual steps.

The Lotus Sametime 7.5 CF1 update package is delivered as:

win_bin.zip: Windows fixes for the Domino Program Directory
win_data.zip: Windows fixes for the server data directory

ems.zip: Fixes for the Enterprise Meeting Server

aix_bin.tar: AIX fixes for the installation directory
aix_data.tar: AIX fixes for the server data directory

sol_bin.tar: Solaris fixes for the installation directory
sol_data.tar: Solaris fixes for the server data directory

• Stop the server and apply the files to the server
• Update the UserInfoServlet Configuration
• Restart the server

1. Stop the server and apply the files to the server.

For Windows Sametime server:
1. Stop the server.
2. Back up the contents of the Domino Program Directory (default is C:\program files\lotus\domino) and the server data directory (default is C:\program files\lotus\domino\data). Include the contents of all subdirectories in your backup.
3. Unzip win_bin.zip into the Domino Program Directory.
4. Unzip win_data.zip into the server data directory.
5. Proceed to "Update the Configuration" phase.

For AIX Sametime server:
1. Stop the server.
2. Back up the contents of the installation directory (default is /opt/ibm/lotus/notes/latest/ibmpow) and the server data directory (default is /local/notesdata). Include the contents of all subdirectories in your backup.
3. Untar aix_bin.tar into the installation directory.
4. Untar aix_data.tar into the server data directory.
5. Proceed to "Update the Configuration" phase.

For Solaris Sametime server:
1. Stop the server.
2. Back up the contents of the installation directory (default is /opt/ibm/lotus/notes/latest/sunspa) and the server data directory (default is /local/notesdata). Include the contents of all subdirectories in your backup.
3. Untar sol_bin.tar into the installation directory.
4. Untar sol_data.tar into the server data directory.
5. Proceed to "Update the Configuration" phase.

For Sametime Enterprise Meeting Server:
1. Stop the STCenter, STServer, and STAdmin servers.
2. Back up the .ear files in this directory:
<WebSphere directory>/AppServer/installableApps
3. Unzip ems.zip into the installableApps directory.
4. Install the new .ear files as described in the Sametime 7.5 Administrator's Guide under the heading of "Deploying the STAdmin, STCenter, and STServer Enterprise Archive (EAR) files."
5. Restart the servers.

Follow these steps to update the servlets.properties file on your Sametime server so that UserInfoServlet is initialized when the http service loads.

a. Use a text editor to open the servlets.properties file (located in the Sametime server data directory).

b. Locate the line in the file that begins with "servlets.startup=".

c. Add "UserInfoServlet" to the list of servlets on this line, separating it from the other servlet names with a blank space.

For example:

servlets.startup=bootstrap scs auth admin mmapi stcal fileupload rapfile statistics stconversion Policy NameChange meeting telephony UserInfoServlet

Installation Procedures (i5/OS)

The Sametime 7.5 CF1 update package for i5/OS Sametime servers is built as an i5/OS PTF which must be applied to Sametime 7.5.

PTF number: ST75CF1
Product: 5724J23

• Readme.txt: This Readme file
• ST75CF1: i5/OS binary save file containing the PTF which provides the Sametime 7.5 CF1 updates

1. Establish a 5250 session with the System i server and sign on with the appropriate user profile.

2. Run the following command to create a temporary library on your system:

CRTLIB LIB(MYLIB) TEXT('Library for ST 7.5 CF1 update')

CRTSAVF FILE(MYLIB/ST75CF1) TEXT('ST fix for CF1 ST75CF1')

cd xxxx [change to the directory on your workstation that contains ST75CF1]
ftp: [your system name or IP address]
Name: [Enter your user profile name and press ENTER]
Password: [Enter your password and press ENTER]
ftp>binary
Representation type is binary IMAGE.F
ftp>put ST75CF1 MYLIB/ST75CF1
ftp>quit

6. To load and apply the Sametime PTF that contains the Sametime 7.5 CF1 updates, run the following i5/OS commands:

LODPTF LICPGM(5724J23) DEV(*SAVF) SAVF(MYLIB/ST75CF1)
APYPTF LICPGM(5724J23) SELECT(ST75CF1)

When you install the PTF, the CF1 updates are added to all existing Sametime servers. If you configure a new Sametime server after installing the PTF, the updates are automatically added to the new server.

Note: This step is not necessary for any new Sametime servers that you create in the future. When you configure a Sametime server after installing CF1, the servlets.properties file will contain the updated information.

a. Use a text editor to open the servlets.properties file (located in the Sametime server data directory).

b. Locate the line in the file that begins with "servlets.startup=".

c. Add "UserInfoServet" to the list of servlets on this line, separating it from the other servlet names with a blank space.

For example:

servlets.startup=bootstrap scs auth admin mmapi stcal fileupload rapfile statistics stconversion Policy NameChange meeting telephony UserInfoServlet

Update stpolicy.nsf for new file transfer policy

Prior to CF1, a Sametime policy existed in the Sametime Connect client that controls whether peer-to-peer file transfers are permitted.That is, whether the Connect client should allow file transfers that are sent directly to another Sametime client user without involving the server.

Once CF1 is installed, the Sametime Connect client will check the server for this policy setting instead of checking the client. This allows the server administrator to control the policy. Note that the new server policy for peer-to-peer file transfers is separate from the existing policy, "Allow file transfer", which is used to control file transfers that involve the server.

If you want to allow file transfers between clients that do not involve the server, you must manually update stpolicy.nsf and add the new policy. If you take no action, peer-to-peer transfers will no longer be permitted after CF1 is installed.

• If you do not want to allow client file transfers of any type, use the Sametime Administration Tool to set the "Allow file transfer" policy to "No." You do not need to add the new peer-to-peer policy. No file transfers will be allowed.
• If you want to allow file transfers, use the Sametime Administration Tool to set the "Allow file transfer" policy to "Yes." You can choose to add the new policy so that file transfers can be sent directly when possible, reducing the server workload.
• You also have the option to disallow file transfers that go through the server (by setting "Allow file transfer" to "No"), but still allow peer-to-peer file transfers (by adding the new policy).

If you want to allow peer-to-peer file transfers, complete the following steps to update stpolicy.nsf and add the new policy:

1. From the Notes Administrator client, open stpolicy.nsf (located in the Sametime server data directory).

2. You may have one or more policy documents that need to be updated.

Note: If you add the new policy to any of the policy documents, you must also add it to the default policy document (DefaultPVS). If you add the new policy to one of the other policy documents but do not add it to DefaultPVS, peer-to-peer file transfers will not be allowed. You can still disallow peer-to-peer file transfers as the default by adding the new policy to DefaultPVS with a Value of "0", rather than "1".

a. Open the document and double-click the document to edit it.

b. Starting from the top, locate the first empty ID field and enter the following data (a Value of 1 indicates "yes", specify 0 to indicate "no"):

ID: 2005
Name: Allow peer-to-peer file transfer
Type: 2
Value: 1
Selector: 0

c. Save the document.

Note: Once you have manually updated a policy document, do NOT use the Sametime Administration Tool to edit that document. Editing the document with the Administration Tool will remove the manual updates.