��� Lotus Sametime

��� Lotus Sametime

Lotus

®

Sametime

®

Version 7.0

Release Notes

���

G210-2083-00

Note: Before using this information and the product it supports, read the information in "Notices" on page

107.

Third Edition (January, 2006)

This edition applies to IBM® Lotus® Sametime® 7.0, and to all subsequent releases and modifications, until otherwise indicated in new editions.

© Copyright International Business Machines Corporation 1996, 2006. All rights reserved.

US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP

Schedule Contract with IBM Corp.

IBM Lotus Sametime 7 Release Notes Contents

Chapter 1 - About this release .............................................................................

New in this release.....................................................................................................................

Welcome to Lotus Sametime...............................................................................................

Release Notes - availability and formats .............................................................................

Lotus/IBM Web sites containing Sametime documentation ................................................

New Features and Changes for Sametime 7.0 ...................................................................

Backward compatibility ..............................................................................................................

Accessing Sametime Connect help in a mixed release environment ..................................

Product compatibility ..................................................................................................................

Sametime 7.0 does not operate with Domino server in xSP mode .....................................

Sametime Connect for browsers interoperability .................................................................

Chapter 2 - Installation, migration, upgrade, and configuration information ............................................................................................................

Hardware requirements .............................................................................................................

Server and Client hardware requirements ...........................................................................

Supported sound cards and cameras..................................................................................

Software requirements ...............................................................................................................

Library required for application sharing on Linux systems ..................................................

Microsoft VM is not supported .............................................................................................

Notes 6 needed to use calendaring and scheduling with Sametime ...................................

Server and Client software requirements ............................................................................

Installation notes ........................................................................................................................ bin directory in the PATH variable causes installation problems .........................................

Cannot install Sametime and QuickPlace on the same UNIX computer .............................

Install and uninstall issues with Russian Sametime server .................................................

Installing UNIX Sametime servers on Domino partitioned servers ......................................

PDF reader must be installed to view install guide from autorun ........................................

Sametime 7.0 cannot run on a Domino server running in xSP mode..................................

Sametime Connection documents are case-sensitive.........................................................

Translated versions of the installation guide .......................................................................

Warning indicating Domino 7 is required during installation................................................

\U in Domino install path causes Sametime servlet failure..................................................

Upgrade notes ...........................................................................................................................

Chat logging on the Sametime server .................................................................................

Must reconfigure SSL after upgrading from 6.5.1 to 7.0......................................................

Upgrade issue with the Sametime Attachment Conversion server .....................................

Upgrade issues with UNIX Sametime servers.....................................................................

Upgrading IMLU to a full Sametime server..........................................................................

Configuration notes ....................................................................................................................

Changing server administration parameters........................................................................

Configuration servlet is not secure following installation .....................................................

Configuring Sametime to work behing WebSEAL reverse proxy ........................................

Do not replicate the Configuration (stconfig.nsf) database..................................................

Enabling chat logging on UNIX servers ...............................................................................

Enabling QuickPlace or Virtual Classroom to access Sametime ........................................

Encrypting QuickPlace or Virtual Classroom connection with SSL .....................................

Enhance security by disabling RAPFileServlet....................................................................

Forcing Sametime Connect for browsers to use English.....................................................

Running Sametime in the background on AIX.....................................................................

7

7

21

24

24

26

18

18

18

20

16

16

17

18

15

16

16

16

32

32

33

14

14

15

15

11

11

11

11

9

9

9

11

7

8

9

9

4

5

5

5

1

1

2

4

1

1

1

IBM Lotus Sametime 7 Release Notes Contents

Sametime Connect and HTTPS connections on port 443 or 563........................................

Server display color setting must be higher than 256 colors ...............................................

Setting up an LDAP connection to an ActiveDirectory server .............................................

Setting up the SIP Gateway for Sametime on UNIX ...........................................................

Signing Sametime databases..............................................................................................

Uninstallation information...........................................................................................................

Registry key still exists after uninstalling the server ............................................................

Uninstalling Sametime from UNIX .......................................................................................

Chapter 3 - Known limitations, problems, and workarounds ...........................

Limitations ..................................................................................................................................

Installation issues ................................................................................................................

Java VM is not installed with Sametime clients ............................................................

Sametime Connect 2.x and 3.x clients cannot connect ................................................

Accessibility/Section 508 issues..........................................................................................

Can’t tab between text and Meeting Room in Meeting Tester ......................................

Mnemonics disappear during an online meeting ..........................................................

SHIFT+TAB won’t move focus backward through column headers..............................

Meeting Room client issues.................................................................................................

Screen sharing optimization not available with Linux clients ........................................

Sametime server issues ......................................................................................................

Connectivity and log changes occur without server restart...........................................

Linux Client issues...............................................................................................................

Linux Meeting Room client does not support Audio/Video ...........................................

Screen sharing issues on Linux clients .........................................................................

International issues..............................................................................................................

Sametime 7.0 not supported on Turkish locale UNIX servers ......................................

Supported Whiteboard file types ...................................................................................

Known problems and workarounds............................................................................................

Installation issues ................................................................................................................

After Sametime uninstall, reboot before reinstalling Sametime ....................................

Clicking Cancel while installation is copying files..........................................................

Deleting directories following an installation failure ......................................................

Directory has "Enforce consistent ACLs" option selected.............................................

Do not install Sametime multiplexer on a Sametime server .........................................

Opening the install guide (stinstall.nsf) in a Web browser ............................................

Ping the Sametime server before installation (verify DNS setup) .................................

Reinstalling Sametime 7.0 over an existing 7.0 installation ..........................................

Sametime Connect cannot log in to Sametime 2.x or 3.x server ..................................

Sametime installation fails on partitioned Domino server .............................................

Sametime server language does not match Domino server error ................................

Server name cannot include invalid XML characters ....................................................

servlets.properties file renamed during Sametime installation......................................

Set the server home page following installation or upgrade .........................................

Uninstall does not remove staddin parameter from Notes.ini .......................................

Accessibility/Section 508 issues..........................................................................................

Can’t tab between admin client and Domino Directory access .....................................

Missing hotkeys in Sametime Connect for the desktop client .......................................

Tabbing problem in Add to Privacy List dialog box .......................................................

Unable to tab between admin tool and admin Help ......................................................

41

41

41

48

48

49

49

46

46

47

48

45

45

45

46

44

44

44

45

49

49

49

49

50

50

43

43

43

43

42

42

43

43

42

42

42

42

41

41

41

41

33

37

38

39

39

40

40

40

IBM Lotus Sametime 7 Release Notes Contents

Sametime Connect client issues .........................................................................................

Cannot add meeting participant to Sametime Connect List ..........................................

Contact list group names hard to read at 256 colors ....................................................

Disable Connect auto login with multiple user Notes client ..........................................

Do not run both versions of Sametime Connect on the same machine ........................

Do not use "Short name" to log into Sametime Connect ..............................................

Host field cannot contain capital letter when using HTTPS proxy ................................

Invitation indicates no available tools if Connect is closed ...........................................

Locked DLLs require machine reboot to complete Connect install ...............................

Logged out of Sametime (reason 0x80000200) ............................................................

Macintosh Sametime Connect for the desktop client issues .........................................

Meeting cannot be started due to error 0x8000024 ......................................................

No error for empty proxy fields in Sametime Connect for browsers .............................

Problem with chat text in Sametime Connect for browsers ..........................................

Same name appears multiple times in a Contact list ....................................................

Sametime Connect display problems at 256 colors......................................................

Sametime Connect startup screen is upside down .......................................................

User with long name is unable to log in to Sametime Connect .....................................

Meeting Room client issues.................................................................................................

Black boxes appear when sharing some dialog boxes .................................................

Cannot delete an annotated whiteboard file .................................................................

Computer entering standby mode drops audio .............................................................

Empty browser frame or browser crash during client install .........................................

Ensuring that Whiteboard save works on UNIX ............................................................

Excel files and Russian whiteboard issue .....................................................................

Files with embedded objects distort in the whiteboard .................................................

Firewall may block access to whiteboard file ................................................................

HTML files do not display correctly in the whiteboard ...................................................

Initial chat transcripts do not appear in instant meetings ..............................................

Meeting Room client hangs when loading whiteboard/other applet..............................

Menus do not pop up when accessed via mnemonics .................................................

Only one spreadsheet in a file converts to whiteboard format ......................................

Remaining meeting time is not correct for extended meetings .....................................

Repeated saves when converting multiple spreadsheet Excel file ...............................

Tools still available in active meetings ..........................................................................

Whiteboard attachments and invited servers ................................................................

Word or Word Pro file with embedded objects whiteboard issue..................................

Web browser issues ............................................................................................................

Default browser information ..........................................................................................

Meeting names with quotations display incorrectly .......................................................

Mnemonics unavailable after closing New Poll window (Mozilla) .................................

Problem with "Administer the Server" link .....................................................................

SOCKS proxy limitations with the Sun JVM 1.4.1 Plug-in ............................................

Sun Java plug-in does not pick up SOCKS proxy from PAC file ..................................

Sametime server issues ......................................................................................................

A member of a group cannot authenticate when attending a meeting..........................

Access Control Lists are unavailable to the administrator ............................................

Accessing Print Capture help on Windows 2000 systems ............................................

Administration tool unavailable after restarting STPlaces.............................................

59

59

59

60

57

58

59

59

55

56

56

56

55

55

55

55

54

54

54

54

52

52

53

53

50

50

50

50

51

52

52

63

64

64

64

62

62

63

63

65

65

61

62

62

62

60

60

61

61

IBM Lotus Sametime 7 Release Notes Contents

Broadcast connections monitoring does not show multicast users...............................

Broadcast monitoring counts TCP-tunneled streams as Unicast..................................

Cannot import recorded meeting ..................................................................................

Cannot replace a recorded meeting on Solaris server..................................................

Cannot search by first and last names..........................................................................

Changing HTTP port of the Sametime server...............................................................

Changing the Broadcast gateway control port ..............................................................

Community Services HTTP tunneling option not working.............................................

DiagnosticsFileOutput.txt file using too much disk space .............................................

Disconnecting network cable removes moderator privileges ........................................

Disconnections from Community Services with NAT ....................................................

Do not use invalid XML characters in Sametime server names ...................................

Environment variables associated with ststart script file ...............................................

Error when exporting a recorded meeting .....................................................................

HTTP Services and Meeting Services do not start correctly .........................................

HTTPS in URL listed in the meeting details document is incorrect............................... i5/OS (iSeries) Server international issues ...................................................................

Invited servers require same HTTP port number for meeting links...............................

Listed user name appears not active in the public group ..............................................

Maximum online meeting password length ...................................................................

Maximum user and server connections limit off by one ................................................

Meeting name does not appear on connected (or "invited") server ..............................

Meetings are not recorded as expected........................................................................

Meetings do not become active on connected ("invited") server ..................................

Monitoring tab info incorrect for broadcast multicast streams.......................................

Multicast address ranges for Broadcast Services not working .....................................

Must enter full server name to log on to Sametime ......................................................

Mux startup information prints to console instead of log file .........................................

Name Conversion Utility trace messages always output to file ....................................

No meetings in the "Today’s Meetings" view of the Meeting Center.............................

Password protected ID not supported for additional server ..........................................

Renaming the stcenter.nsf database ............................................................................

Restart the server when changing logging options .......................................................

Running Sametime in the background on Solaris .........................................................

Running Sametime in the background on UNIX ...........................................................

Sametime Links application stops with "Out of Memory" error .....................................

Saving recorded meetings to a mapped network drive .................................................

Self registered user cannot change password ..............................................................

Self registration does not work......................................................................................

Service is disabled message when starting the Sametime server ................................

Service is not started message when stopping the Sametime server ..........................

SIP connector not disabled when "Support external User" = False ..............................

SSO for Sametime requires an SSO document named "LtpaToken" ...........................

STLog.nsf on invited server does not record names ....................................................

Stop recording option does not work with Sametime on UNIX .....................................

Subscript out of range 47 error when creating repeating meetings ..............................

Supporting dual LDAP directories with Sametime ........................................................

Unable to attach large whiteboard files to Sametime meetings ....................................

Unable to import a recorded meeting on i5/OS Sametime ...........................................

75

75

76

76

74

74

75

75

73

73

73

74

72

72

72

73

71

71

71

72

68

69

69

69

65

66

66

67

67

67

68

81

81

81

82

79

80

81

81

82

83

77

78

79

79

76

76

77

77

IBM Lotus Sametime 7 Release Notes Contents

Usage Limits and Denied Entry for Broadcast Meetings ..............................................

User cannot save the whiteboard .................................................................................

User ID displays as numbers/characters in Administration Tool...................................

Using Lotus Notes client stops Domino processes on Sametime .................................

Using self-registration with multiple Sametime servers ................................................

Using "Alt+159" accented characters with user registration .........................................

Verifying the version number of a Sametime server .....................................................

Writing server log information to a text file....................................................................

Wrong meeting start time displays when importing a meeting......................................

"Connection Broken" message for Java Sametime Connect logouts ...........................

"Message received when inviting others to a meeting ..................................................

Audio/Video services issues ................................................................................................

Audio performance problems or high audio latency......................................................

Echo cancellation in multiple a/v meetings ...................................................................

Poor audio quality with G.711 audio codec and TCP Tunneling...................................

LDAP issues ........................................................................................................................

Administrator cannot attend meetings or use Sametime databases.............................

Can’t add groups from Domino LDAP directory to presence lists .................................

Configuring LDAP directory settings after installation ...................................................

Group members in Exchange server LDAP directory not online ..................................

Problems with client Contact lists and LDAP Active Directory ......................................

Security issues ....................................................................................................................

Web browser authentication with cascaded address books .........................................

Software Development Kit issues ........................................................................................

Location of Software Development Kit release notes ...................................................

Meeting center page does not show toolkit installation status ......................................

Problem using "Extended Live Names" Sametime C++ Toolkit sample .......................

Problems running Sametime Java Toolkit samples ......................................................

STLinks samples and applications only connect on port 80 .........................................

Enterprise Meeting Server issues........................................................................................

Edited whiteboard not available for display...................................................................

Meeting usage limit issue with the EMS .......................................................................

Users cannot connect to an EMS meeting after server failover....................................

Linux Client issues...............................................................................................................

Changing a user’s online status on Linux systems .......................................................

DBCS limitations/known issues with Sametime Linux clients .......................................

Linux Meeting Room client does not support audio/video ............................................

Log on to Sametime dialog problem with Sametime Connect on Linux ........................

Menu items with checkboxes on Linux systems ...........................................................

Problem selecting menu items on Linux client with Netscape ......................................

Using the Undo Full Screen button with Linux Meeting Room client ............................

AIX issues............................................................................................................................

Killing the ST Mux process on an AIX Sametime server ..............................................

Solaris issues ......................................................................................................................

Audio/Video issue with TLS-enabled SIP Connector ....................................................

International issues..............................................................................................................

Audio/video meetings without video installed (Spanish i5/OS) .....................................

Bitmaps may not display clearly in shared PowerPoint files .........................................

Changing the path where recorded meetings are stored ..............................................

90

90

91

91

90

90

90

90

88

88

89

89

87

87

87

88

86

86

86

86

85

85

85

85

83

83

84

84

84

84

85

94

94

95

95

94

94

94

94

95

95

92

93

93

93

91

91

92

92

IBM Lotus Sametime 7 Release Notes Contents

DateTime format incorrect when admin runs in a Firefox browser ...............................

DBCS user names and meetings on a Solaris server (CJKT) ......................................

Domino admin with Polish or Turkish characters cannot log in ....................................

Excel file display issues with the Russian whiteboard ..................................................

Excel files and Brazilian/Portuguese Print Capture ......................................................

Font issue in Chinese STLinks Toolkit ..........................................................................

French character issue with screen sharing .................................................................

Garbage characters appear in logging field on i5/OS server ........................................

GB18030 issues with Simplified Chinese .....................................................................

General DBCS issues ...................................................................................................

International issues with EMS Meeting Room client Send Web Page ..........................

International issues with Sametime Connect ................................................................

International issues with Sametime Linux clients..........................................................

International issues with the AIX Sametime server .......................................................

Issues with Chinese/Japanese versions of the Meeting Room client ...........................

Issues with Portuguese and Swedish Secure Desktop Installer ...................................

Japanese characters missing in FST file name ............................................................

Japanese Meeting Room client and Firefox browser ....................................................

Java script error importing recorded meetings (Japanese server) ................................

Locale issues when installing the EMS and required software .....................................

Logging into Sametime with Domino alternate names..................................................

Mnemonics/ADA usage ................................................................................................

Polish character display problems in recorded meetings ..............................................

Portuguese, Swedish Secure Desktop installations and Sun VM .................................

Problem attaching whiteboard file that uses GB2312 characters .................................

Problem with whiteboard files with DBCS filenames with EMS ....................................

Problems authenticating admin name with Turkish characters .....................................

Recorded meetings not sorted correctly on Korean EMS.............................................

Sametime Connect for browsers group sorting issue ...................................................

Sametime Connect for desktop does not support unicode display ...............................

Sametime service status displays incorrectly in the admin client .................................

Scrambled characters in the Sametime log ..................................................................

Scroll bars do not appear on the Server Overview page ..............................................

Some logging fields blank on International UNIX servers.............................................

STLinks Toolkit Sample Page cannot display content ..................................................

Using IME with screen sharing .....................................................................................

Whiteboard file issue with UNIX server using Japanese locale ....................................

Chapter 4 - Documentation updates ................................................................... 105

Administrator’s Guide................................................................................................................. 105

Cannot attend audio/video meeting if video limit is reached ...............................................

Corrections for configuring Sametime.ini to support SSL ....................................................

SIP Gateway setup instructions for Sametime on UNIX......................................................

Quick Start Guide.......................................................................................................................

The icon of share a program is incorrect in Quick Start Guide............................................

User’s Guide ..............................................................................................................................

Mnemonic for the Show Startup Log menu option missing .................................................

105

105

105

106

106

106

106

Chapter 5 - Notices and Trademarks .................................................................. 107

Notices .......................................................................................................................................

Trademarks ................................................................................................................................

107

109

100

100

100

101

101

101

101

101

99

99

100

100

98

99

99

99

101

101

101

102

102

102

97

97

98

98

96

96

97

97

95

95

96

96

96

96

96

IBM Lotus Sametime 7 Release Notes

Chapter 1 - About this release

Chapter 1 - About this release

New in this release

Sametime server

Welcome to Lotus Sametime

These Release Notes contain the latest information for the IBM® Lotus® Sametime 7.0 release. The Release Notes include topics about known issues, system requirements, documentation updates, and information not available in other Sametime documentation. Be sure to read the topics in the Things You Need to Know section and the list of known issues in the Troubleshooting section before installing the Sametime software.

Updated versions of the Sametime 7.0 Release Notes are available in the documentation library at the Web site http://www.lotus.com/ldd/doc. The Release Notes available from this Web site contain the most recent information about Sametime 7.0.

Sametime Software Development Kit release notes are provided with each kit. After installation, you can view them on your Sametime server. Visit http://<sametime server name>/sametime/toolkits, click the link for any kit to reach its welcome page, and then click Release Notes.

Sametime server

Release Notes - availability and formats

The Release Notes are available both in the IBM Lotus Notes® database format (STRN70.NSF) and PDF format

(STRN70.PDF) and are installed with the Sametime server.

You can also view the most current version of the Release Notes at the Lotus Developer Domain Web site: http://www. lotus.com/ldd/doc.

Sametime Software Development Kit release notes are provided with each kit. After installation, you can view them on your Sametime server. Visit http://<sametime server name>/sametime/toolkits, click the link for any kit to reach its welcome page, and then click Release Notes.

Sametime server

Lotus/IBM Web sites containing Sametime documentation

The following Web sites are designed to help you locate the latest information on Sametime 7.0:

http://www.ibm.com/lotus/ldd contains a technical webzine with articles for end-users, application developers and systems administrators, and an active discussion cafe with several discussion forums for exchanging ideas

TM about IBM Lotus Domino , Lotus Notes, and Sametime.

http://www.ibm.com/lotus/ldd/doc contains Lotus product documentation in various formats for downloading.

Information about ordering additional documentation, product tips, and documentation feedback forms is also available.

http://www.redbooks.ibm.com contains links to IBM Redbooks that include in-depth information on deploying

Sametime in your environment and using the Sametime Software Development Kit. After accessing this web site, search on "Sametime."

http://www.lotus.com/sametime contains Sametime product and developer information, including the latest information on Sametime developer's tools and the protocols that make online awareness and real-time collaboration possible in Sametime. This Web site includes white papers, reviewer's guides, common questions and solutions, and newsletters relating to Sametime's features and benefits.

1

IBM Lotus Sametime 7 Release Notes

Chapter 1 - About this release

http://www.lotus.com/sametimedevelopers contains the latest tools and information for enabling applications and web sites with Sametime technology. Use this web site to download the latest version of the Sametime

Software Development Kit, work with sample applications, participate in discussions using Sametime technology, learn the latest tips and tricks, and review whitepapers and Redbook information.

http://www.lotus.com/education contains Lotus Education information on all Lotus products, including course descriptions, schedules, Lotus Authorized Education Center locations, and Lotus certification information.

http://www.ibm.com/software/lotus/support contains support information on all Lotus products, including common questions and solutions, user discussions, downloadable files, and Lotus support phone numbers. You can also use this Web site to search the KnowledgeBase for technical information on Lotus products.

To access information on the Web, you must use a Web browser, such as Web Navigator, Netscape Navigator, or

Microsoft® Internet Explorer. If you need information on connecting your Lotus Notes workstation to the Web, contact your Lotus Notes server administrator.

Audio/Video services, Sametime Administration Tool, Sametime Broadcast client, Sametime Connect client, Sametime Meeting Room client,

Sametime server, Web browsers

New Features and Changes for Sametime 7.0

The tables below summarize the most important new features, enhancements, and changes in the IBM Lotus

Sametime 7.0 release.

Feature or Enhancement

IBM Lotus Instant

Messaging Limited Use version of Sametime

New Test Conference connectivity utility

Description

This release of Sametime includes a version of the Sametime product that supports only instant messaging and presence functionality. This version of Sametime is called "IBM Lotus Instant

Messaging Limited Use" and it ships with all Domino 7.0 servers.

This version of Sametime can be integrated with Domino Web Access or Lotus Notes clients to provide instant messaging functionality for Domino applications.

A Sametime Connect for browsers client is also provided with this version of Sametime.

This version of Sametime does not support any Web conferencing or meeting functionality and also does not include the Sametime Connect for the desktop client or the Macintosh Sametime Connect for the desktop client.

Installation instructions for the "IBM Lotus Instant Messaging Limited Use" software are included in the Sametime 7.0 Installation Guide. A separate administrator's guide and end user help are provided with this version of Sametime.

There is no separate version of the Sametime Release Notes for the IBM Lotus Instant Messaging

Limited Use version of Sametime. All release notes in this document that pertain to the Sametime

Connect for browsers client, the Community Services, and instant messaging and presence functionality are valid for the IBM Lotus Instant Messaging Limited Use version of Sametime.

The Test Conference utility is redesigned for Sametime 7.0 to enhance its usability and troubleshooting capabilities. The enhancements to the Test Conference utility include the following:

A new, easy-to-access, wizard user interface that guides users quickly through the various test processes.

More thorough testing processes that test for system compatibility, installation issues, and connectivity problems. The testing processes include the ability to join a test conference on the

LIMWC server.

Better error reporting and logging with explicit and easy-to-understand error messages when problems are encountered.

Logging capabilities that log the activities that occur for both successful and unsuccessful attempts to connect to a Web conference.

2

IBM Lotus Sametime 7 Release Notes Chapter 1 - About this release

Feature or Enhancement

Macintosh version of the

Sametime Connect client

Full integration of instant messaging with Lotus

Domino

Interoperability with IBM

Lotus Team Workplace servers on i5/OS, AIX, and

Solaris

Enterprise Meeting Server upgrades

Description

The Sametime server CD includes a Java version of the Sametime Connect client called "Macintosh

Sametime Connect for the desktop." This version of Sametime Connect can run as a standalone application on Macintosh operating systems. The administrator must manually distribute this file to users for installation on a Macintosh system.

The Macintosh Sametime Connect client does not support and includes no user interface options for the following features that are supported on other versions of Sametime Connect:

Instant meetings

The "Automatically change my status" feature (available from the Options-Preferences-Status tab on other versions of Sametime Connect)

The "Launch at startup" option (available from the Options menu on other versions of Sametime

Connect)

Aside from these differences, the Macintosh Sametime Connect for the desktop client provides the same functionality as the Sametime Connect for browsers client available from the user interface of the Sametime server.

The Sametime 7.0 release supports the integration of instant messaging and presence features into the user interfaces of the following Domino features:

Calendaring and scheduling features of the Lotus Notes client

To Do list feature of the Lotus Notes client

Personal Address Book

Domino Directory

Team Rooms

Discussion databases

For documentation about integrating Sametime functionality with Domino servers and clients, refer to the Domino server documentation.

The Sametime 7.0 release allows you to install and operate the Sametime server on the same computer as a Lotus Team Workplace 7.0 server if both of the servers run on either the i5/OS, AIX, or Solaris operating systems.

The Sametime 7.0 Enterprise Meeting Server (EMS) is a companion product for the Sametime server that supports Sametime Meeting Services clustering. The EMS is a separate product that must be purchased separately from the Sametime server. However, due to the close relationship between the

Sametime server and the EMS, the EMS administration documentation and release notes are included with the Sametime server documentation. The EMS is a J2EE application that is upgraded for the 7.0 release to use the following versions of IBM software:

IBM Universal Database V8.2

IBM WebSphere MQ V5.3.0.8

IBM WebSphere Application Server V5.1.1.2

3

IBM Lotus Sametime 7 Release Notes Chapter 1 - About this release

Feature or Enhancement

Product name change

Description

The previous release of this product was named "IBM Lotus Instant Messaging and Web

Conferencing 6.5.1."

For this release, the product name changes to "Sametime 7.0." Sametime was the original name of this product.

Enhanced installation documentation

IBM Lotus Name

Conversion Utility included with the Sametime server

You use the IBM Lotus Sametime Name Conversion Utility to ensure that name updates you make in a Domino or LDAP directory are also made in Sametime Connect client buddy lists and privacy lists.

The names that appear in Sametime Connect client buddy lists and privacy lists are stored in the vpuserinfo.nsf database on the Sametime server. If you make changes to user or group names that are stored in the directory, you must use this utility to make the same name changes to user and group names that are stored in the vpuserinfo.nsf database. This utility was previously availabe only as a Web download, but is now shipped with the Sametime server. Documentation for this utility is provided in the Sametime 7.0 Administrator's Guide.

STDebugTool.exe documentation

The Sametime 7.0 Installation Guide is enhanced so that installation instructions for Sametime on the

AIX, Solaris, and Windows platforms are provided in a single version of the installation guide. The installation guide also includes additional information to address deployment issues users have encountered during the installation process. A separate version of the installation guide is shipped with the i5/OS version of Sametime.

An STDebugTool.exe utility ships with Windows versions of the Sametime 7.0 server. This utility is available from the <root>:\Lotus\Domino\Sametime directory on a Windows version of the

Sametime server and is used to produce trace files for troubleshooting purposes. The documentation for this utility is available in the Sametime 7.0 Administrator's Guide.

Microsoft VM is not supported

The supported VMs for Sametime clients in the Sametime 7.0 release are the Sun Microsystems

Java VM 1.4.2 and the IBM Java VM 1.4.2.

In Sametime 7.0, the Microsoft VM is not supported for Sametime clients. For the Sametime 7.0 release, the Sametime clients will not block usage by users that have only the Microsoft VM installed. However, this will not be true for future releases. You should install the Sun or IBM JVM

1.4.2 on Sametime client computers.

Backward compatibility

Sametime Connect client

Accessing Sametime Connect help in a mixed release environment

The help that is available from the Sametime Connect client corresponds to the Sametime server to which the client connects rather than the version of Sametime Connect that the user is using. The Sametime Connect client help files are HTML files that are stored on the Sametime server. These help files are not loaded with the Sametime Connect client to a user's local computer. When a user clicks the Help menu in a Sametime Connect client, a browser window opens containing an HTML help file that is loaded from the Sametime server to the Web browser.

The HTML help file loads from the Sametime server that is specified as the Host in the Sametime Connectivity settings of the Sametime Connect client. If the server specified as the Host in the Sametime Connectivity settings is not the same version as the Sametime Connect client, the help files that open will not be the same as the client version.

For example, if a user opens a Sametime 7.0 Connect client that specifies a Sametime 6.5.1 server as the Host in the

Sametime Connectivity settings, and then clicks the Help menu in Sametime Connect, the user sees the help files for the 6.5.1 version of the Sametime Connect client (loaded from the Sametime 6.5.1 server specified as the Host). The user will not see the updated help files for the Sametime 7.0 release.

4

IBM Lotus Sametime 7 Release Notes

Chapter 1 - About this release

Product compatibility

Sametime server

Sametime 7.0 does not operate with Domino server in xSP mode

Service providers can configure a Domino server to run in xSP mode to provide hosted services to small and medium-sized businesses. You cannot install the IBM Lotus Sametime 7.0 server on a Domino server that is configured to operate in xSP mode.

If you install a Sametime 7.0 server on a Domino server running in xSP mode, the Sametime installation will complete successfully, but the Sametime services will not run after the server is installed.

Sametime Connect client

Sametime Connect for browsers interoperability

A Java version of the Sametime Connect client called "Sametime Connect for browsers" became available with

Sametime 2.5. The interoperability issues for "Sametime Connect for browsers" are listed below.

"Sametime Connect for browsers" must be used with Sametime server releases 2.0 or higher.

A user of "Sametime Connect for browsers" must have a 2.0 or higher Sametime server specified as the home server in the Sametime server field of the user's Person document.

The 2.5 and higher releases of the"Sametime Connect for browsers" client are supported on Windows machines only.

5

IBM Lotus Sametime 7 Release Notes Chapter 1 - About this release

6

IBM Lotus Sametime 7 Release Notes Chapter 2 - Installation, migration, upgrade, and configuration information

Chapter 2 - Installation, migration, upgrade, and configuration information

Hardware requirements

Audio/Video services, Sametime Broadcast client, Sametime Connect client, Sametime Meeting Room client, Sametime server

Server and Client hardware requirements

Server requirements

Sametime requires one server computer for Sametime installation that meets these requirements:

Operating system - IBM eServer pSeries (AIX)

V5.2, V5.3

CPU -- Dual 475 MHz, or higher, IBM PowerPC processor recommended; Dual 375 MHz PowerPC processor minimum.

Memory -- 2 GB recommended; 1GB minimum.

Disk space -- 3 GB free disk space recommended to allow space for meetings; 2 GB minimum.

Disk swap space -- 2 GB RAM recommended; 1GB minimum.

Video requirements -- Video card installed. Recommended video display color setting is 16-bit color. The setting must be higher than 256 colors.

Operating system - Sun Solaris V9

CPU -- UltraSPARC III 1 GHz processor, or higher recommended; UltraSPARC III 550 MHz processor minimum

Memory -- 2 GB recommended; 1 GB minimum.

Disk space -- 3 GB free disk space recommended to allow space for meetings; 2 GB minimum.

Disk swap space -- 2 GB RAM recommended; 1GB minimum.

Video requirements -- Video card installed. Recommended video display color setting is 16-bit color. The setting must be higher than 256 colors.

Operating system - Microsoft Windows 2000 Server with Service Pack 4, Windows Advanced Server with Service

Pack 3 and Service Pack 4, Microsoft Windows 2003 Standard Edition, Microsoft Windows 2003 Advanced Edition

CPU -- Intel Pentium III 800 MHz, or higher, recommended.

Memory -- 1 GB recommended; 512 MB minimum.

Disk space -- 1 GB free disk space recommended to allow space for meetings; 500 MB minimum.

Disk swap space -- 1.5 GB RAM recommended; 1G minimum

Network software -- TCP/IP network software installed

Video requirements -- Video card installed. Recommended video display color setting is 16-bit color. The setting must be higher than 256 colors.

7

IBM Lotus Sametime 7 Release Notes

Chapter 2 - Installation, migration, upgrade, and configuration information

Operating system - IBM i5/OS, 5722SS1, V5

R3

CPU -- All processor features are supported for IBM iSeries Models 730, 740, and 8xx

Memory -- 1 GB recommended; 512 MB minimum.

Disk space -- 1 GB free disk space recommended to allow space for meetings; 500 MB minimum.

Disk drives -- Minimum of 4 drives.

Client requirements

The client system requirements for operation with the Sametime 7.0 server (and Multimedia Services) include:

CPU -- Pentium II 266MHz (or higher)

RAM -- 128MB RAM or higher

Additional client requirements for audio/video

Sound card - A full-duplex sound card is required to participate in interactive audio/video meetings. A half-duplex sound card is required to enable a user to listen to an audio meeting that is broadcast by the

Sametime Broadcast Services.

Microphone and speakers - High-quality microphones are recommended. Avoid microphones with on and off switches unless they are of high quality. A headset that contains a boom microphone performs best. If a desktop microphone is used, a unidirectional dynamic microphone that uses batteries is preferred.

Camera - A high-quality USB or PCMCIA PC camera is recommended. Do not use parallel port cameras. On

Windows machines, the camera must support Microsoft Video for Windows.

A camera is optional. Users who do not have a camera can participate in an audio/video meeting. These users can see video images displayed in the Sametime Meeting Room client. When a user without a camera speaks, no video image is displayed in the video component of the Meeting Room client.

Video capturing software - Video for Windows.

Audio/Video services

Supported sound cards and cameras

The Sametime Multimedia Services provide IP audio/video capabilities to Sametime. Sound cards and cameras that work with the Multimedia Services are listed below.

Sound cards

Any correctly installed full-duplex sound card should work with Sametime. The sound cards listed below have been tested with Sametime:

CrystalWare (integrated)

Montego A3D Xstream

SoundBlaster Live Value

ALS120

Aureal Vortex A3D SQ1500

Aureal SB Audio PCI 64V

ES1887 (integrated)

Montego II A3D

Montego II Quadzilla

Rockwell WaveArtist

SoundBlaster PCI 128

SoundBlaster PCI 512

SoundBlaster 32 AWE

SIIG SoundWave Pro PCI

Yamaha DS-XG (integrated)

8

IBM Lotus Sametime 7 Release Notes

Chapter 2 - Installation, migration, upgrade, and configuration information

Creative Crystal PnP Es 1868

Creative Sound Blaster Creative 16 Plug & Play

Creative AWE64

Creative SoundBlaster PCI

Addonic (PCI)

Crystal Audio (DELL onboard sound card)

Crystal SoundFusion PCI Audio Accelerator (IBM Thinkpad® default)

Cameras

A high-quality USB camera that is compatible with Video for Windows and Windows sound cards is recommended.

Software requirements

Linux clients

Library required for application sharing on Linux systems

In order to load Application Sharing native code on Linux platforms, the following library is required on the client machine: libz.so.1, which resides in /usr/lib

Sametime Broadcast client, Sametime Connect client, Sametime Meeting Room client

Microsoft VM is not supported

The supported VM for all Sametime java applet clients in the Sametime 7.0 release is the Sun Microsystems Java VM

1.4.2.

In Sametime 7.0, the Microsoft VM is not supported for Sametime clients. For the Sametime 7.0 release, the

Sametime clients will not block usage by users that have only the Microsoft VM installed. However, this will not be true for future releases. You should install the Sun JVM 1.4.2 on Sametime client computers.

Sametime server

Notes 6 needed to use calendaring and scheduling with Sametime

Lotus Notes/Domino calendaring and scheduling capabilities can be integrated with a Sametime server to enable users to use the Notes calendaring and scheduling features to schedule meetings on a Sametime server.

These capabilities are limited to Lotus Notes R6.x clients and higher. Lotus Notes R5.x clients cannot use the Notes calendaring and scheduling features to interoperate with a Sametime server.

Sametime Broadcast client, Sametime Connect client, Sametime Meeting Room client, Sametime server, Web browsers

Server and Client software requirements

Sametime server software requirements

AIX 5.3

AIX 5.2 - AIX 5.2 requires patch level 2 (5200-02). Access to an XWindow interface is also required for AIX. The installation program will not run from a telnet session.

Solaris 9 (SPARC) - Access to an X Window interface is required for Solaris. The installation program will not run from a telnet session.

OS/400 (i5/OS) - Sametime runs on V5R3

Windows 2000 Standard Edition (Service Pack 4)

Windows 2000 Advanced Edition (Service Pack 3 or 4)

Windows 2003 Standard Edition

Windows 2003 Advanced Edition

9

IBM Lotus Sametime 7 Release Notes

Chapter 2 - Installation, migration, upgrade, and configuration information

Notes:

On Windows, you must have full administration rights to install Sametime. If not, Sametime 7.0 will not install properly. Also, only Microsoft TCP/IP is supported for Windows.

The video display color setting on the Sametime server must be higher than 256 colors. The recommended video display color setting is 16-bit color.

LDAP directories

IDS 5.1 and 5.2

Domino 6.5 and 7.0

Microsoft Active Directory 2003 (except i5/OS)

Sun ONE Directory 5 (iPlanet 5.1 and 5.2; except i5/OS)

Supported Domino version

Sametime 7.0 must install on a Domino 7.0 server.

Sametime client software requirements

Platforms supported for Sametime Connect clients

Sametime Connect for the desktop -- Windows 2000 Professional (SP4), Windows XP (SP1)

MacIntosh Sametime Connect for the desktop -- MacIntosh OSX 10.3.4 and higher and 10.4.x

Browsers supported

Internet Explorer 6.0 on Windows XP and Windows 2000 Professional

Mozilla 1.7.6 on Windows XP Professional and Windows 2000 Professional 3.0, RedHat Enterprise Linux (REL)

3.0, Novell Linux Desktop (NLD) 9.0

Mozilla Firefox 1.0.1 on Windows XP Professional and Windows 2000 Professional 3.0, RedHat Enterprise Linux

(REL) 3.0, Novell Linux Desktop (NLD) 9.0

Java JDK/JRE supported

Sun JDK and JRE 1.4.2

Sun JRE 1.4.2 or later for Linux

Note: The Microsoft VM is not supported for Sametime clients. With the Sametime 7.0 release, the Sametime clients will not block usage by users that have only the Microsoft VM installed. However, this will not be true for future releases. You should install the Sun or IBM JVM 1.4.2 on Sametime client computers.

Macintosh Sametime Connect for the desktop JRE requirements

Apple JRE 1.4.2 (for MacIntosh OSX 10.3.4 and higher)

Apple JRE 1.4.2 (for MacIntosh OSX 10.4.x)

Note: If you want to run the Sametime 7.0 Administration Tool in Microsoft Internet Explorer 6.0, make the following settings in Microsoft Internet Explorer. You must make these settings regardless of whether Microsoft Internet Explorer is installed on a client or server computer.

In Microsoft Internet Explorer, select the Tools - Internet Options menu item.

Select the Advanced tab.

Clear the check mark from the "Use HTTP 1.1" option.

10

IBM Lotus Sametime 7 Release Notes

Chapter 2 - Installation, migration, upgrade, and configuration information

Installation notes

Sametime server

bin directory in the PATH variable causes installation problems

This issue applies only to Sametime servers that operate on the AIX or Solaris operating system.

Do not include the Domino "bin" directory (/opt/lotus/bin, by default) in the PATH environment variable. Doing so may cause the connector initialization to fail with an error code of 0x1007.

Sametime server

Cannot install Sametime and QuickPlace on the same UNIX computer

Sametime 7.0 for AIX or Solaris does not support a configuration in which Sametime and Quickplace are installed on the same machine.

Sametime server

Install and uninstall issues with Russian Sametime server

When installing the Russian version of the Sametime server, the hotkeys may not operate correctly.

If a user logs in to Windows with a Windows user name that contains Russian characters, the Russian version of the

Sametime Connect client will not install successfully. To correct this problem:

Log in to Windows with a user name that contains English characters

Change the disk file system from FAT32 to NTFS.

When installing the Russian version of the Audio Adapter, the License information displays in English.

If a user logs in to Windows with a Windows user name that contains Russian characters, the Audio Adapter will not install successfully. You must log in to Windows with a user name that contains English characters to install the Audio

Adapter.

Sametime server

Installing UNIX Sametime servers on Domino partitioned servers

This release note describes configuration issues that are specific to installing a Solaris or AIX version of the Sametime server on a partitioned Domino server. Use these instructions, along with the server installation instructions provided in the Sametime Installation Guide, to install Unix versions of Sametime on a partitioned Domino server.

Before installing Domino

Follow these steps before installing Domino:

1. Ensure that each partitioned server has a unique IP address. You can map multiple IP addresses to one network card using the "ifconfig" command. The command syntax is:

ifconfig(device) alias (new IP address) netmask (subnet)

For example:

ifconfig en0 alias 9.3.187.209 netmask 255.255.255.128

2. Ensure that each partitioned server has a DNS name that maps to its unique IP address.

If a DNS name can be resolved to multiple IP addresses, be sure to read the Multi-homed notes.

Note: Although it is not required, IBM Lotus software recommends that each partitioned server be run by a unique user account. Create a new Unix Notes user for each partitioned server that you plan to run. You can also use a single

"Notes" group for all partitions.

11

IBM Lotus Sametime 7 Release Notes

Chapter 2 - Installation, migration, upgrade, and configuration information

Domino Installation

Specify the following when installing Domino:

1. When prompted to install more than one Domino Server on this computer, click Yes.

2. When prompted for the location of the Data directory and the Notes user account, specify a unique location for the Data directory and the appropriate user name for each partitioned server.

Domino Configuration

To configure Domino:

1. After installation, configure each server using the Notes user account. For example, log in as "NotesUser1" and run "/opt/lotus/bin/server" to configure the first server. Then log out, log in as "NotesUser2," configure the second server, and so on.

2. During configuration, make sure that any field referring to the server's name or IP address is set up properly. By default, the IP address and server name fields for each configuration contain the IP address and server name of the server. For each partitioned server, you must update these fields so that they are appropriate for that partition.

3. After configuration for each server is complete, start the first Domino server.

4. Open a browser and browse to the Name and Address Book on the first Domino server.

5. Open the Server document on the first Domino server.

6. Choose the Internet Protocols-HTTP tab and do the following:

- In the Host name field, enter the fully qualified DNS name of the server. (In a Multi-homed environment, do not enter the Host name. Instead enter all IP

addresses that resolve to the DNS name.)

- Enable "Bind to host name."

7. Open the Notes.ini file on the first Domino server, and add the following line:

TCPIP_TcpIpAddress=0,(server_ip):1352

8. Repeat steps 3 through 7 for each partitioned server.

Verify Domino Installation

Verify that each Domino server is correctly installed and configured:

1. Start each partitioned Domino server, one at a time.

2. Verify each server has successfully started.

3. Verify no errors are reported.

4. Stop each Domino server.

5. Proceed to Sametime installation.

Sametime Installation

To install Sametime:

1. Run the Sametime installation program. When prompted, select the Data directory and Notes user account for the first partitioned server.

2. Install Sametime on each of the remaining Domino partitioned servers. Specify the appropriate Data directory and Notes user account for each partitioned server.

12

IBM Lotus Sametime 7 Release Notes

Chapter 2 - Installation, migration, upgrade, and configuration information

Add the Trusted IPs to the Sametime.ini file and stconfig.nsf database on each Sametime server

When the Sametime installations are complete, you must ensure that the IP addresses associated with all network interfaces on the server computer that hosts the partitioned Sametime/Domino servers are known as trusted IP addresses by each Sametime server that operates on each partition. To accomplish this configuration, you must list all of these IP addresses in the Sametime.ini file and Sametime Configuration database (stconfig.nsf) on each

Sametime server.

Follow the instructions below:

1. Use a text editor to open the Sametime.ini file on the first Sametime server.

2. In the [CONFIG] section of the Sametime.ini file, type the parameter VPS_TRUSTED_IPS= and include the a comma-separated list of all IP addresses for all network interfaces on the server. For example:

VPS_TRUSTED_IPS=5.55.251.231,6.66.251.232,7.77.251.233,8.88.251.234,9.99.25

1.238

3. Use a Lotus Notes client to open the Sametime Configuration database (stconfig.nsf) on the Sametime server.

4. Open the CommunityConnectivity document by double-clicking the date associated with the document.

5. In the "Community Trusted IPS" field, enter the same comma-separate list of all IP addresses for all network interfaces on the server.

6. Save and close the CommunityConnectivity document and exit the stconfig.nsf database.

7. Repeat this procedure for each Sametime server running on each Domino partition.

Configure the Network Connectivity settings on each Sametime server

When you have Sametime servers running on partitioned Domino servers, you must ensure that all Host name fields available in the Networks and Ports settings in the Sametime Administration Tool on each Sametime server specify the appropriate values. You must also sure that each Sametime server is configured to use different ports as the Event server port and Token server port.

To accomplish this configuration, you must open the Sametime Administration Tool on each Sametime server and enter the fully-qualified DNS name associated with the server into the Host name fields.

Follow the instructions below:

1. Open the Sametime Administration Tool on the first Sametime server.

2. Select Configuration -> Connectivity -> Networks and Ports.

3. Configure each of the Host name settings on the Networks and Ports tab, and the Event server port and Token server port fields, as instructed below:

Community Services Network - Address for server connections - Host name - Enter the fully-qualified DNS name of the Sametime server on this partition.

Community Services Network - Address for client connections - Host name - Enter the fully-qualified DNS name of the Sametime server on this partition. In a multi-homed environment, enter an IP address to which the fully-qualified DNS name resolves.

Community Services Network - Address for HTTP-tunneled client connections - Host name - Enter the fully-qualified DNS name of the Sametime server on this partition. In a multi-homed environment, enter an IP address to which the fully-qualified DNS name resolves.

Meeting Services Network - Address for server connections - Host name - Enter the fully-qualified DNS name of the Sametime server on this partition.

13

IBM Lotus Sametime 7 Release Notes

Chapter 2 - Installation, migration, upgrade, and configuration information

Meeting Services Network - Address for client connections - Host name - Enter the fully-qualified DNS name of the Sametime server on this partition. In a multi-homed environment, enter an IP address to which the fully-qualified DNS name resolves.

Meeting Services Network - Address for HTTP-tunneled client connections - Host name - Enter the fully-qualified DNS name of the Sametime server on this partition. In a multi-homed environment, enter an IP address to which the fully-qualified DNS name resolves.

Meeting Services Network - Event server port - Enter a unique port number for this value. The port you enter must not be used by any other Sametime server on this computer or by any other process running on this computer for any purpose. This port should be used only as the Event server port by one Sametime server running on one Domino partition. IBM Lotus software recommends using Ports above 9098.

Meeting Services Network - Token server port - Enter a unique port number for this value. This port must not be used by any other Sametime server on this computer or by any other process running on this computer. This port should be used only as the Token server port by one Sametime server running on one Domino partition. IBM

Lotus software recommends using Ports above 9098.

Broadcast Services Network - Broadcast gateway address for client connections - Host name - Enter the fully-qualified DNS name of the Sametime server on this partition. In a multi-homed environment, enter an IP address to which the fully-qualified DNS name resolves.

Broadcast Services Network - Broadcast gateway address for control connections - Host name - Enter the fully-qualified DNS name of the Sametime server on this partition.

Broadcast Services Network - Address for HTTP-tunneled client connections - Host name - Enter the fully-qualified DNS name of the Sametime server on this partition. In a multi-homed environment, enter an IP address to which the fully-qualified DNS name resolves.

Interactive Audio/Video Network - H.323 server communication address - Host name - Enter the fully-qualified

DNS name of the Sametime server on this partition.

Interactive Audio/Video Network - TCP tunneling address for client connections - Host name - Enter the fully-qualified DNS name of the Sametime server on this partition. In a multi-homed environment, enter an IP address to which the fully-qualified DNS name resolves.

Interactive Audio/Video Network - Multimedia control address - Host name - Enter the fully-qualified DNS name of the Sametime server on this partition.

4. Click the Update button and restart the Sametime server for the changes to take effect.

5. Repeat this procedure for each Sametime server running on each Domino partition. Enter the fully-qualified DNS name associated with each of the Sametime servers in the Host name fields listed in step 3.

Sametime server

PDF reader must be installed to view install guide from autorun

When a user runs the demo32.exe on CD 1 to install the Sametime server, an installation screen appears that includes an "Installation Guide" button. User's can click this button to launch a PDF version of the Sametime 7.0 Installation

Guide. If a PDF reader is not installed on the installation server, the PDF version of the install guide cannot be launched from the "Installation Guide" button.

Sametime server

Sametime 7.0 cannot run on a Domino server running in xSP mode

Service providers can configure a Domino server to run in xSP mode to provide hosted services to small and medium-sized businesses. You cannot install the Sametime 7.0 server on a Domino server that is configured to operate in xSP mode.

If you install a Sametime 7.0 server on a Domino server running in xSP mode, the Sametime installation will complete successfully, but the Sametime services will not run after the server is installed.

14

IBM Lotus Sametime 7 Release Notes Chapter 2 - Installation, migration, upgrade, and configuration information

Sametime server

Sametime Connection documents are case-sensitive

A Sametime Adminstrator can create a Connection document of the Connection Type "Sametime" to enable a meeting started on one Sametime server to be simultaneously active on another Sametime server. This functionality is frequently called "invited servers." In this scenario, a meeting is started on one Sametime server and that Sametime server "invites" another Sametime server to the meeting. The server on which the meeting is started is the "source" server and the server that is invited to the meeting is the "destination" server.

The procedure for creating these Connection documents is described in the topic "Creating Connection Records to connect Sametime servers" in the Deploying Multiple Sametime Servers chapter of the IBM Lotus Sametime 7.0

Administrator's Guide.

When creating the Connection document, you must enter the invited server's name in the "Destination server" field of the Connection document. The server name entered in the "Destination server" field must be an exact case-sensitive match with the server name as it appears in the Server document in the Domino directory. If the server name in the

Destination server field is not an exact case-sensitive match with the server name on the Server document, the meeting will not be available on the invited (or destination) server.

For example, when creating a Connection Document to connect two Sametime servers, the administrator must perform the following procedure:

1. Open the Sametime Administration Tool.

2. Choose Configuration-Connectivity-"Servers in this Community."

3. Complete the following fields to create the Connection document:

Destination server - Enter the name of the Destination server in the Domino hierarchical server name format that includes the domain name of the server. For example, "sametimeB.acme.com/ACME."

Destination server IP address - Enter the fully-qualified DNS name or IP address of the destination server. If this field is left blank, meetings started on the source server will not become active on the destination server.

In the example above, the name of the server in the "Destination server" field must be an exact case-sensitive match to the server name on the Server document. If "sametimeB.acme.com/ACME" is entered in the Destination server field of the Connection document, the server name must appear exactly this way in the Server document in the Domino directory. If the Server document lists the name as "SametimeB.acme.com/ACME" or "sametimeB.acme.com/Acme" the destination server cannot be invited to the meeting because the server name is not a case-sensitive match.

Sametime server

Translated versions of the installation guide

With the Sametime 7.0 release, only the English language version of the Sametime 7.0 Installation Guide is shipped with the product. Translated versions of the Sametime Installation Guide can be downloaded from this web site: http://www.lotus.com/ldd/doc.

Sametime server

Warning indicating Domino 7 is required during installation

When you install a Sametime 7.0 server on top of a Domino 7.0 server, you will see the following warning message:

"IBM Lotus Sametime 7.0 requires Domino version 7.0.0 or later".

This message appears even when the Domino version that you have installed is at the 7.0.0 release level. If your installed Domino server is at the 7.0.0 release level, you can ignore this message and continue with the Sametime server installation.

If you do not have a Domino 7.0 server installed, you must upgrade Domino to 7.0, and then install Sametime 7.0 on the Domino server.

15

IBM Lotus Sametime 7 Release Notes

Chapter 2 - Installation, migration, upgrade, and configuration information

Sametime server

\U in Domino install path causes Sametime servlet failure

If a Domino server is installed with a path that includes \U, you cannot install Sametime on this Domino server. An install path that includes a \U causes Sametime servlets to fail (due to to the \U escape sequence).

Upgrade notes

Sametime Connect client, Sametime Meeting Room client, Sametime server

Chat logging on the Sametime server

An API is available to implement chat logging on a Sametime server. The chat logging feature can capture all chat conversations that occur on the Sametime server, including instant messages, chat conferences (chats involving more than two people), and Meeting Room chats. The text of these conversations is stored on the server and retrievable through applications developed with the chat logging API.

Sametime toolkits are available from the IBM Lotus Instant Messaging and Web Conferencing page of the IBM developerWorks web site (www.ibm.com/developerworks).

Sametime server

Must reconfigure SSL after upgrading from 6.5.1 to 7.0

If you have configured the Domino HTTP server of a Sametime 6.5.1 server to support SSL, and you upgrade this server to Sametime 7.0, you must reconfigure the Domino HTTP server to support SSL on the 7.0 server. The Domino

HTTP SSL configuration is lost when you upgrade Sametime 6.5.1 to Sametime 7.0. See the topic "Using SSL with

Sametime" in the "Working with Sametime Security" chapter of the IBM Lotus Sametime 7.0 Administrator's Guide.

Sametime server

Upgrade issue with the Sametime Attachment Conversion server

This issue occurs when all of the following conditions exist:

You are upgrading an AIX or Solaris version of the Sametime 6.5.1 server to Sametime 7.0.

The Sametime 6.5.1 server is configured to use the Sametime Attachment Conversion server and the meetingserver.ini file has been modified accordingly.

The Sametime 6.5.1 server is configured to use an LDAP directory.

The Sametime 6.5.1 server is configured to support SSL for HTTP connections to the Domino Web server.

During the upgrade to Sametime 7.0, the meetingserver.ini file on Sametime 6.5.1 may be overwritten and must be re-configured when the upgrade concludes.

For example, assume the meetingserver.ini file has been configured as follows on the 6.5.1 server to support the

Sametime Attachment Conversion server:

[SOFTWARE\Lotus\Sametime\MeetingServer\ConversionServices]

NumberOfAttachmentConversionServers=1

AttachmentConversionServer1=192.168.4.34:19610

[SOFTWARE\Lotus\Sametime\MeetingServer\Services]

StopWaitTime=30000

StartWaitTime=600000

16

IBM Lotus Sametime 7 Release Notes Chapter 2 - Installation, migration, upgrade, and configuration information

When the upgrade completes, the meetingserver.ini file may be altered as follows:

[SOFTWARE\Lotus\Sametime\MeetingServer\ConversionServices]

NumberOfAttachmentConversionServers=0

AttachmentConversionServer1=0.0.0.0:19610

[SOFTWARE\Lotus\Sametime\MeetingServer\Services]

StopWaitTime=30000

StartWaitTime=120000

Note that in the second example, the upgrade has altered the NumberOfAttachmentConversionServers=,

AttachmentConversionServer1=, and StartWaitTime= settings in the meetingserver.ini file. You must reconfigure these settings after the upgrade completes.

Sametime Meeting Room client, Sametime server

Upgrade issues with UNIX Sametime servers

This release note discusses three upgrade issues that can occur when upgrading UNIX versions of Sametime. These issues are all related to settings in the Sametime.ini file not being updated appropriately by the upgrade process.

1. This issue occurs when upgrading a Solaris Sametime 6.5.1 server to Sametime 7.0 whent the 6.5.1 server is configured to support SSL for connections to the Domino HTTP server.

When the upgrade completes, you must remove the following settings from the Sametime.ini file on the Solaris

Sametime 7.0 server and restart the Sametime server:

SSLManagerClassName= javax.net.ssl.keyStoreType= javax.net.ssl.trustStoreType=

These settings are used by the Sametime 6.5.1 server to support SSL, but are not needed on the Sametime 7.0 server. If these settings remain in the Sametime.ini file after the upgrade completes, the Sametime 7.0 server will not start.

This issue does not occur on AIX versions of the Sametime server.

2. This issue occurs on both Solaris and AIX versions of the Sametime server when the Sametime 6.5.1 server is being upgraded to Sametime 7.0. This issue occurs with Sametime 6.5.1 servers that are configured to support SSL for connections to the Domino HTTP server.

When the Sametime 6.5.1 UNIX server is configured to support SSL, the following setting exists in the Sametime.ini file:

ConfigurationPort=443

The upgrade process will change this setting to the following value:

ConfigurationPort=80

If you want SSL connections to occur on port 443, you must manually change this setting back to port 443 and restart the Sametime server.

3. This issue occurs on both Solaris and AIX versions of the Sametime server when the Sametime 6.5.1 server is being upgraded to Sametime 7.0. This issue occurs with Sametime 6.5.1 servers that are configured to connect to an

LDAP directory.

17

IBM Lotus Sametime 7 Release Notes

Chapter 2 - Installation, migration, upgrade, and configuration information

When the Sametime 6.5.1 UNIX server is configured to connect to an LDAP directory, the following setting exists in the

Sametime.ini file:

DirectoryType=LDAP

The upgrade process will change this setting to the following value:

ConfigurationPort=true

You must manually change this setting back to DirectoryType=LDAP after the upgrade completes if you want the server to access an LDAP directory. Restart the Sametime server after changing this setting.

Sametime server

Upgrading IMLU to a full Sametime server

If you install the IBM Lotus Instant Messaging Limited Use version of Sametime and select LDAP directory as the directory type, and then you upgrade this server to a full Sametime 7.0 server and also select LDAP as the directory type, the original LDAP directory configuration is lost.

You must configure the full version of the Sametime server to access the LDAP directory again after you complete the upgrade.

Configuration notes

Sametime Administration Tool

Changing server administration parameters

With Sametime 7.0, the server administration parameters accessed by the XML-based Sametime Administration Tool are stored in the Configuration database (STCONFIG.NSF) on the Sametime server and in the Sametime.ini file. It is recommended that you use the Sametime Administration Tool to change server administration parameters.

If you directly access the STCONFIG.NSF database or the Sametime.ini file to change a server administration parameter, you must restart the Sametime server before the change will take affect. Generally, you should not change administration settings by accessing the STCONFIG.NSF database with a Lotus Notes client.

Sametime server

Configuration servlet is not secure following installation

The Sametime server contains a configuration servlet that is accessed by several Sametime server processes. This configuration servlet can access server configuration information and is not protected with any security mechanism following a Sametime server installation. You should protect this servlet by configuring Sametime to require authentication for access to the configuration servlet. If you do not require authentication for access to the configuration servlet, an attacker might be able to access this servlet to alter or retrieve server configuration information.

The administrator must perform the following steps to require authentication for access to the configuration servlet:

1. Create or identify a special directory account to use for authentication when accessing the configuration servlet.

2. Edit the Sametime.ini file on the Sametime server.

3. Edit the servlets.properties file in the <Sametime installation>\Data directory on the Sametime server.

4. Add the user name required for authentication to the Access Control List (ACL) of the Configuration database

(stconfig.nsf).

Each of these steps is described in detail below.

18

IBM Lotus Sametime 7 Release Notes

Chapter 2 - Installation, migration, upgrade, and configuration information

Step 1 - Create or identify a special directory account to use for authentication when accessing the configuration servlet

Creating or identifying a directory account is the first of four procedures you must perform to require authentication for access to the configuration servlet.

To authenticate, the Sametime processes must present a user name and password when accessing the configuration servlet. This user name and password must exist in either the person entry of an LDAP directory or the Person document of a Domino Directory (depending on whether your Sametime community uses an LDAP or Domino

Directory).

IBM Lotus software recommends that you create a special account in the directory strictly for the purpose of authenticating access to the configuration servlet. This directory account should be used for no other purpose. For example, you might want to create an account with the user name of "SametimeServletAccess" and specify a password for the account. Creating a special account for this purpose ensures that the account is not tied to a particular user or process and will not be changed inadvertently.

If you prefer, you can use an existing directory account (user name and password) for this purpose.

Step 2 - Edit the Sametime.ini file on the Sametime server

Editing the Sametime.ini file is the second of four procedures you must perform to require authentication for access to the configuration servlet.

After you have created a special directory account (or identified an existing directory account) to use for authentication, you must specify the user name and password associated with this directory account in the

Sametime.ini file on the Sametime server. Follow the instructions below:

1. Use a text editor to open the Sametime.ini file on the Sametime server. The Sametime.ini file is located in the

Sametime installation directory.

Note The default Sametime installation directory is C:\Lotus\Domino. Sametime installs into the same directory as the Domino server.

2. The Sametime.ini file contains a [Config] section. At the bottom of the [Config] section, manually add the following two Sametime.ini file settings by typing them in the Sametime.ini file with the text editor:

SametimeAdminUsername=

SametimeAdminPassword=

The two fields above must specify the user name and password you intend to use for authenticating access to the configuration servlet. Type the appropriate user name and password as the values for these fields. For example, if you created a directory entry for the user name "SametimeServletAccess" with a password of "Sametime," the correct entries in the Sametime.ini file [Config] section would look like this:

SametimeAdminUsername=SametimeServletAccess

SametimeAdminPassword=Sametime

3. Save and close the Sametime.ini file.

Step 3 - Edit the servlets.properties file in the <Sametime installation>\Data directory on the Sametime server

Editing the servlets.properties file is the third of four procedures you must perform to require authentication for access to the configuration servlet.

1. Use a text editor to open the servlets.properties file on the Sametime server. The servlets.properties file is located in the <Sametime installation>\Data directory. (The default is C:\Lotus\Domino\Data.)

2. In the servlets.properties file, locate the line that begins with "servlet.scs.initArgs=". An example of this line is provided below. servlet.scs.initArgs=ServletURL=scs,UnchainedAccessEnabled=true

19

IBM Lotus Sametime 7 Release Notes

Chapter 2 - Installation, migration, upgrade, and configuration information

3. Add the following text to the end of the line identified above:

,AccessControl.Roles=[SametimeAdmin].

After you have added the text, the line should appear as follows: servlet.scs.initArgs=ServletURL=scs,UnchainedAccessEnabled=true,AccessControl.Roles=[SametimeAdmin]

4. Save and close the servlets.properties file.

Step 4 - Add the user name required for authentication to the Access Control List (ACL) of the Configuration database on the Sametime server

Adding the user name required for authentication to the ACL of the Configuration database is the last of four procedures you must perform to require authentication for access to the configuration servlet.

In this procedure, you add the user name associated with the directory entry discussed above to the ACL of the

Configuration database (stconfig.nsf) and provide the user name with the "SametimeAdmin" role in the ACL. An example of this procedure is provided below:

1. Use a Lotus Notes client to open the Sametime Configuration database (stconfig.nsf) on the Sametime server.

2. Choose File-Database-Access Control.

3. Add the user name associated with the directory entry discussed above ("SametimeServletAccess" in this example) to the stconfig.nsf ACL. Provide this user name with the "SametimeAdmin" role in the ACL.

Note The "SametimeAdmin" role is the only credential in the ACL that must be assigned to the user name specified for configuration servlet authentication. It is not necessary to assign a specific access level (such as

Manager or Author) to this user name.

4. Click OK to exit the ACL.

Sametime server

Configuring Sametime to work behing WebSEAL reverse proxy

The administrator's guide contains a "Using reverse proxy or portal servers with the Sametime server" that discusses using Sametime with reverse proxy servers.

If you are deploying Sametime behind a Tivoli WebSEAL reverse proxy server, there are some specific procedures and configurations you must employ to ensure the Sametime server can operate behind the WebSEAL reverse proxy server. These procedures and configurations are discussed below.

To enable a Sametime server to operate behind a WebSEAL reverse proxy server:

1. You must configure the Sametime server to support HTTP tunneling on port 80. For instructions, refer to the

"About HTTP tunneling" section in the "Configuring Sametime Connectivity" chapter of the IBM Lotus Instant

Messaging and Web Conferencing (Sametime) 6.5.1 Administrator's Guide.

2. You must open the stlinks.js file on the Sametime server and modify the following two lines to point to your

WebSEAL reverse proxy server and WebSEAL junction (the WebSEAL junction is "st" in the example below): varII_RProxyName="https://ampc0.support.tivlab.austin.ibm.com" varII_AffinityID="st"

Note: The WebSEAL reverse proxy server must be listening on the default ports of 80 and 443 for the changes above to work.

20

IBM Lotus Sametime 7 Release Notes

Chapter 2 - Installation, migration, upgrade, and configuration information

3. Enable reverse proxy support and specify the WebSEAL junction in the Sametime Administration Tool on the

Sametime 7.0 server.

- Open the Sametime Administration Tool on the Sametime 7.0 server.

- Select Configuration-Connectivity.

- In the "Reverse Proxy Support" section, select the "Enable Reverse Proxy Discovery on the client" setting to enable the reverse proxy support.

- In the "Reverse Proxy Support" section, enter the WebSEAL junction name in the "Server Alias" field. In this example, "st" is the WebSEAL junction name.

4. Create the Tivoli Access Manager WebSEAL junction as shown below: pdadmin> server task webseald-[servername] create -t tcp -h [sametime hostname] -p 80 -i -j -A -F [path to LTPA key]

-Z [LTPA key password]/junction

You cannot use the -w parameter for this setup. Some requests generated by Sametime are not allowed through the junction if the -w exists. You must also ensure that the LTPA key used in the junction is the same LTPA key that the Sametime server uses in its Web SSO Configuration document

After performing these configurations, you should be able to login to https://webseal/stjunction and be prompted by

WebSEAL for authentication. Once authenticated, SSO between WebSEAL and Sametime should work and all requests for Sametime will route through WebSEAL.

Sametime server

Do not replicate the Configuration (stconfig.nsf) database

If you have multiple Sametime 7.0 servers in your Sametime community, you should not replicate the entire

Configuration database (stconfig.nsf) among the Sametime 7.0 servers. Some documents in the Configuration database contain the IP address or host name of a Sametime server and replication of these documents to a different

Sametime 7.0 server will prevent that server from functioning properly.

When you have a multiple Sametime server environment, there are specific administration settings that must be kept consistent across all Sametime servers in the Sametime community. The administrator can use the Sametime

Administration Tool on each Sametime server to manually configure the settings on each Sametime server.

Configuring these settings on each server ensures that the settings that must be consistent across servers are consistent.

Note A Technote has been created that explains how to set up a selective replication of the Configuration database. A selective replication enables you to keep some administration settings consistent across all Sametime servers while not replicating documents in the Configuration database that may cause problems on a different server. Using selective replication prevents the administrator from having to manually configure each Sametime server to ensure all administration settings that must be consistent across servers are consistent. The technote can be found at http://www.ibm.com/support/docview.wss?rs=203&uid=swg21089634.

The settings that should be consistent on each Sametime server in a community are listed below. It is mandatory that some of these settings are consistent across all Sametime servers in a community. For other settings, it is recommended that you maintain consistent settings across all Sametime servers in the community, but it is not mandatory.

Administration settings that must be consistent on all Sametime servers in a community

It is mandatory that the administration settings below have the same values on all Sametime servers in a community.

If these settings are not consistent across all servers, the servers may not function properly or end users may see unexpected behavior when attending meetings on invited servers.

In the Configuration-Community Services tab of the Sametime Administration Tool, the following settings must be consistent on all Sametime servers in the community:

"Number of entries on each page in dialog boxes that show names in the directory"

"How often to poll for new names added to the directory"

"How often to poll for new servers added to the community"

21

IBM Lotus Sametime 7 Release Notes

Chapter 2 - Installation, migration, upgrade, and configuration information

In the Configuration-Community Services tab of the Sametime Administration Tool, the following settings must be consistent on all Sametime servers in the community:

"Anonymous users can participate in meetings or enter virtual places"

"Users of Sametime applications (databases such as stconf.nsf or Web sites) can specify a display name so that they do not appear online as 'anonymous'"

"Default domain name for anonymous users"

"Default name"

"Users cannot browse or search the Directory"

"Users can type names (resolve users and groups) to add them to an awareness list"

"Users can browse the directory (see a list of names) or type names (resolve users and groups)"

"Users can browse the directory to see group content and names, or type names (resolve users and groups)"

In the LDAP Directory settings of the Sametime Administration Tool, all LDAP settings must be consistent on all

Sametime servers in the same community. These settings are used only if your community of users is defined in an

LDAP directory instead of a Domino directory. These settings are listed below.

In the Sametime Administration Tool LDAP Directory settings, all of the following must have the same values across

Sametime servers:

LDAP Directory - Connectivity settings

LDAP Directory - Basics settings

LDAP Directory - Authentication settings

LDAP Directory - Searching settings

LDAP Directory - Group Content settings

Community Services server clusters and consistent administration settings

If you create a Community Services server cluster as described in the IBM Lotus Sametime 7.0 Administrator's Guide, all of the settings described above should be consistent across all Sametime servers in the cluster. Note also that the

Configuration database of every Sametime server in the community should contain the "Cluster Information" document that defines the cluster. You can use a Lotus Notes client to create the Cluster Information document in the

Configuration database on one Sametime server in the community server cluster and then copy and paste the Cluster

Information document into the Configuration databases on all of the other Sametime servers in the community

(including both Sametime servers that operate as part of the cluster and Sametime servers that are not part of the cluster). For more information, see the "Creating Community Services server clusters" chapter of the IBM Lotus

Sametime 7.0 Administrator's Guide.

The Community Connectivity document in the Configuration databases of the Sametime servers contains a

"CommunityTrustedIPs" field. This field holds the IP addresses of Community Services multiplexers that are installed on separate machines. The "CommunityTrustedIPs" field is a security setting that ensures that only Community

Services multiplexers that are specified by the administrator (in the "CommunityTrustedIPs" field) can connect to the

Sametime server. If you have deployed Community Services multiplexers on separate machines in front of a

Community Services cluster, the Community Connectivity document must exist on every Sametime server in the

Community Services cluster. For more information, see the "Creating Community Services server clusters" chapter of the IBM Lotus Sametime 7.0 Administrator's Guide.

There is an exception regarding the Community Connectivity document. If a Sametime server is assigned multiple IP addresses to support HTTP tunneling functionality, the Community Connectivity document must be different on every

Sametime server that uses multiple IP addresses. For more information about this scenario, see "Configuring HTTP tunneling on a machine that uses multiple IP addresses" in the "Configuring Sametime Connectivity" chapter of the IBM

Lotus Sametime 7.0 Administrator's Guide.

When a Sametime server is configured to use multiple IP addresses, the Community Connectivity document contains a

Host Name setting that is specific to an individual server. If you copy this Community Connectivity document to another server, the document will specify the wrong Host Name and will cause connectivity problems. In this scenario, the "CommunityTrustedIPs" fields of the Community Connectivity documents must contain consistent settings on every server in the cluster, but you cannot copy and paste the document. You must use a Lotus Notes client to manually open the Configuration databases on every Sametime server in the Community Services cluster, open the Community

Connectivity documents, and enter the IP addresses of the Community Services multiplexers in the

"CommunityTrustedIPs" fields.

22

IBM Lotus Sametime 7 Release Notes

Chapter 2 - Installation, migration, upgrade, and configuration information

Administration settings that should be consistent on all Sametime servers in a community

If the settings below are not consistent on all Sametime servers in the community, the servers will continue to function. However, it is recommended that you keep these settings consistent on all Sametime servers in a community to ensure consistency of end user functionality and logging functions across all servers in your community.

In the Configuration-Community Services tab of the Sametime Administration Tool, the following settings should be consistent on all Sametime servers in the community:

"Allow Connect users to save their user name, password, and proxy information (automatic login)"

"Display the 'Launch Sametime Connect for browsers'link on the Sametime home page"

"Display the 'Launch Sametime Connect for the desktop' link on the Sametime home page"

In the Configuration-Community Services-Server Features settings of the Sametime Administration Tool, the following settings should be consistent on all Sametime servers in the community:

"Allow authenticated users to transfer files to each other"

"Allow users to send announcements"

In the Configuration-Meeting Services-General settings, the following settings should be consistent across all

Sametime servers in the community:

"Automatically extend meetings beyond scheduled end time when there are still people in the meeting"

"Allow people to choose the screen-sharing tool in meetings"

"Participants can share their screen, view a shared screen, or control a shared screen if the moderator permits"

"Participants can share their screen if the moderator permits or view a shared screen"

"Allow people to choose the whiteboard tool in meetings"

"Allow people to save the whiteboard annotations as attachments to the meeting"

"Allow people to enable the Send Web Page tool in meetings"

"Allow people to choose the Polling tool in meetings"

"Allow people to record meetings for later playback (scheduled meetings only)"

"Allow people to choose NetMeeting (or other T.120-compatible client) for screen sharing and whiteboard instead of Sametime Web-based meeting tools."

"Allow people to schedule Broadcast meetings"

In the Logging-Settings tab of the Sametime Administration Tool, the following settings should be consistent on all

Sametime servers in the community:

Community Server events to log

"Successful logins"

"Failed logins"

"Total number of people logged in and total number of unique names logged in"

"Community Server events and activities"

Meeting Server events to log

"Failed meeting authentications"

"Client connections"

"Connection to other meeting servers in this community"

"Meeting events"

"Meeting server events and activities"

In the Logging-Settings-Capacity Warnings tab of the Sametime Administration Tool, the following settings should be consistent on all Sametime servers in the community:

23

IBM Lotus Sametime 7 Release Notes

Chapter 2 - Installation, migration, upgrade, and configuration information

Capacity Warnings - Sharing in Instant Meetings

"Number of active screen sharing/whiteboard meetings exceeds"

"Number of people in all screen sharing/whiteboard meetings exceeds"

"Number of people in one active screen sharing/whiteboard meeting exceeds"

Capacity Warnings - Sharing in Scheduled Meetings

"Number of active screen sharing/whiteboard meetings exceeds"

"Number of people in all screen sharing/whiteboard meetings exceeds"

"Number of people in one active screen sharing/whiteboard meeting exceeds"

Sametime server

Enabling chat logging on UNIX servers

If you want to enable chat logging on a Sametime 7.0 server that operates on AIX or Solaris, you must enable the chat logging flag in stconfig.nsf:

1. Use your Notes client to open the stconfig.nsf database.

2. In the "Community Services" document, change the "chat logging" flag from "off" to either "relax" or "strict."

3. Save your change and close the stconfig.nsf database.

4. Restart the server.

Sametime server

Enabling QuickPlace or Virtual Classroom to access Sametime

Sametime servers can be deployed in an environment that includes IBM Lotus QuickPlace Servers or the IBM Lotus

Virtual Classroom. In these environments, QuickPlace or the Virtual Classroom will require remote access to servlets on the Sametime server.

To execute a servlet on the Sametime server, a remote user (such as QuickPlace or Virtual Classroom) must be able to authenticate when accessing the servlets. The administrator must manually configure the Sametime and QuickPlace or Virtual Classroom servers to ensure that this authentication can occur.

Note A remote user must authenticate to execute the servlets because the Sametime servlets handle sensitive data, including Sametime configuration settings, API calls that can modify or delete meetings, and meeting materials such as whiteboard files. If no authentication is required, unauthorized users can access the servlets to retrieve or manipulate the data handled by these servlets.

To enable QuickPlace or the VirtualClassroom to execute servlets on the Sametime server:

1. Create or identify a special directory account for authentication when accessing the Sametime servlets.

2. Add an entry to the Configuration database Access Control List (ACL) on the Sametime/Domino server.

3. Populate the appropriate fields in the MeetingServices document in the Sametime server Configuration database

(stconfig.nsf).

4. Create a Sametime.ini file on the QuickPlace or VirtualClassroom server.

Step 1 - Create or identify a special directory account for authentication when accessing the Sametime servlets

Creating or identifying a directory account is the first of four procedures you must perform to enable a QuickPlace or

Virtual Classroom application to authenticate when accessing servlets on the Sametime server.

To authenticate, QuickPlace or the Virtual Classroom must present a user name and password when accessing the

Sametime servlets. This user name and password must exist in either the person entry of an LDAP directory or the

Person document of a Domino directory (depending on whether your Sametime community uses an LDAP or Domino

Directory).

24

IBM Lotus Sametime 7 Release Notes

Chapter 2 - Installation, migration, upgrade, and configuration information

IBM Lotus software recommends that you create a special account (person entry in an LDAP directory or person document in a Domino Directory) strictly for the purpose of authenticating access to the Sametime servlets. This directory account should be used for no other purpose. For example, you might want to create an account with the user name of "SametimeServletAccess" and specify a password for the account. Creating a special account for this purpose ensures that the account is not tied to a particular user or process and will not be changed inadvertently.

If you prefer, you can use an existing directory account (person entry or document containing a user name and password) for this purpose.

Step 2 - Add the user name required for authentication to the ACL of the Configuration database on the Sametime server

Adding the user name required for authentication to the ACL of the Configuration database is the second of four procedures you must perform to enable a QuickPlace or Virtual Classroom application to authenticate when accessing servlets on the Sametime server.

In this procedure, you add the user name associated with the directory entry to the ACL of the Configuration database

(stconfig.nsf) and provide the user name with the "SametimeAdmin" role in the ACL. An example of this procedure is provided below:

1. Use a Lotus Notes client to open the Sametime Configuration database (stconfig.nsf) on the Sametime server.

2. Choose File-Database-Access Control.

3. Add the user name associated with the directory entry discussed in the procedure above

("SametimeServletAccess" in this example) to the stconfig.nsf ACL. Provide this user name with the

"SametimeAdmin" role in the ACL.

Note The "SametimeAdmin" role is the only credential in the ACL that must be assigned to the user name. It is not necessary to assign a specific access level (such as Manager or Author) to this user name.

4. Click OK to exit the ACL.

Note Keep the Configuration database open. You must alter a document in the Configuration database in the next procedure.

Step 3 - Populate the appropriate fields in the MeetingServices document in the Sametime server Configuration database (stconfig.nsf)

Populating the appropriate fields in the MeetingServices document in the Sametime server Configuration database is the third of four procedures you must perform to enable a QuickPlace or Virtual Classroom application to authenticate when accessing servlets on the Sametime server.

In this procedure, you add the user name and password associated with the directory entry (discussed in "Step 1 -

Create or identify a special directory account for authentication when accessing the Sametime servlets" above) to fields in the MeetingServices document in the Configuration database. Follow the procedure below:

1. If necessary, use a Lotus Notes client to open the Sametime Configuration database (stconfig.nsf) on the

Sametime server.

2. In the right-hand pane, open the MeetingServices document by double-clicking on the date associated with the document.

3. Scroll to the bottom of the MeetingServices document until you see the Remote Services Access heading.

4. Under the Remote Services Access heading, populate the eight fields with the user name and password associated with the directory entry discussed in "Step 1 - Create or identify a special directory account for authentication when accessing the Sametime servlets" above.

For example, if you created a directory entry with a user name of SametimeServletAccess and a password of

Sametime, populate the eight fields under the Remote Services Access heading as shown below:

Meeting Management Username: SametimeServletAccess

Meeting Management Password: Sametime

Recorded Meeting Management Username: SametimeServletAccess

Recorded Meeting Management Password: Sametime

25

IBM Lotus Sametime 7 Release Notes

Chapter 2 - Installation, migration, upgrade, and configuration information

Materials Refresh Username: SametimeServletAccess

Materials Refresh Password: Sametime

Materials Control Username: SametimeServletAccess

Materials Control Password: Sametime

5. Save and close the MeetingServices document, then close the Configuration database.

Step 4 - Create a Sametime.ini file on the QuickPlace or Virtual Classroom server

Creating a Sametime.ini file on the QuickPlace or Virtual Classroom server is the last of four procedures you must perform to enable a QuickPlace or Virtual Classroom application to authenticate when accessing servlets on the

Sametime server.

The Sametime.ini file on the QuickPlace or Virtual Classroom server must contain the parameters that enable

QuickPlace or Virtual Classroom to access the Sametime server. You must create the Sametime.ini file in the

QuickPlace or Virtual Classroom installation directory on the QuickPlace or Virtual Classroom server.

Follow these instructions to manually create a Sametime.ini file in the QuickPlace or Virtual Classroom installation directory.

1. Open a text editor on the QuickPlace or Virtual Classroom server.

2. Use the text editor to create a text file consisting of a [Config] section and the settings listed below (you must manually type all of this information in the file):

[Config]

VPS_Name= (This setting should specify the canonical name of the Domino/Sametime server to which QuickPlace or Virtual Classroom will connect. An example value is VPS_NAME=CN=Sametimeserver/OU=East/O=Acme.)

SametimeCluster= (This setting should also specify the canonical name of the Domino/Sametime server, e.g.:

SametimeCluster=CN=Sametimeserver/OU=East/O=Acme.)

ConfigurationHost= (This setting should specify the fully-qualified DNS name of the Sametime server, e.g.:

ConfigurationHost=Sametimeserver.east.acme.com.)

ConfigurationPort=80 (This setting should specify port 80.)

SametimeAdminUsername= (This setting should specify the name of the user account that was added to the ACL of the Configuration database on the Sametime server in "Step 1 - Add an entry to the Configuration database ACL on the Sametime/Domino server" above.)

SametimeAdminPassword= (This setting should specify the password associated with the administrator account above.)

About encrypting connections to the Sametime server with SSL

The configurations described above ensure that a QuickPlace or Virtual Classroom server on a remote machine can authenticate when accessing the servlets on a Sametime server. Note that the QuickPlace or Virtual Classroom server will transmit the user name and password used for this servlet access in the clear when connecting to the Sametime server. If needed, this connection between the QuickPlace or Virtual Classroom server to the Sametime server can be encrypted with SSL to prevent the user name and password from being passed in the clear. For more information, see

"Encrypting QuickPlace or Virtual Classroom connection with SSL" in the Configuration notes section of these release notes.

Sametime server

Encrypting QuickPlace or Virtual Classroom connection with SSL

Sametime servers can be deployed in an environment that includes IBM Lotus QuickPlace servers or the IBM Lotus

Virtual Classroom. In these environments, QuickPlace or the Virtual Classroom might require remote access to the

Sametime server. This remote access requires QuickPlace or the Virtual Classroom to transmit a user name and password to the Sametime server. This user name and password enables the QuickPlace or Virtual Classroom server to execute servlets on the Sametime server. To prevent unauthorized users from gaining access to this user name and password, you might want to encrypt the connections from the QuickPlace or Virtual Classroom server to the

Sametime server with SSL.

26

IBM Lotus Sametime 7 Release Notes

Chapter 2 - Installation, migration, upgrade, and configuration information

Note This release note describes the procedures you must perform to encrypt QuickPlace or Virtual Classroom connections to a Sametime server with SSL while allowing Web browser users to access the Sametime server with unencrypted HTTP. If QuickPlace or the Virtual Classroom server must connect to a Sametime/Domino server that requires SSL for all connections (including connections from Web browsers), you must perform the procedures described in the release note entitled "Ensuring Sametime servlet access when Domino HTTP requires SSL" in the

Configuration notes section of these release notes.

To encrypt connections from a QuickPlace or Virtual Classroom server to a Domino/Sametime server with SSL (while allowing Web browser users to access the Domino/Sametime server with unencrypted HTTP), perform the procedures below:

1. Ensure the Domino server is enabled for SSL.

2. Obtain the SSL trusted root or SSL server certificate.

3. Import the SSL certificate into the STKeys.jks database

4. Copy the STKeys.jks file containing the SSL certificate from the Sametime server to the QuickPlace or

VirtualClassroom server

5. Add an entry to the Configuration database Access Control List (ACL) on the Sametime/Domino server

6. Populate the appropriate fields in the MeetingServices document in the Sametime server Configuration database

(stconfig.nsf)

7. Create a Sametime.ini file on the QuickPlace or Virtual Classroom server

Each of these procedures is described in detail below.

Step 1 - Ensure the Domino server is enabled for SSL

Ensuring the Domino server is enabled for SSL is the first of seven procedures required to use SSL to encrypt connections from a QuickPlace or Virtual Classroom server to a Sametime/Domino server.

The Domino server on which Sametime is installed must be set up to use SSL. To configure a Domino server for SSL, the administrator sets up the Domino Server Certificate Admin application and ensures that an SSL trusted root certificate and SSL server certificate are available to the Domino server. These procedures are described in the

Domino server administration documentation available at www.lotus.com/ldd/doc.

Note When setting up the Domino/Sametime server to use SSL, the administrator should configure the Internet ports on the Domino/Sametime server to ensure that Web browser users can access the Domino/Sametime server using unencrypted HTTP. For example:

1. Open the Domino/Sametime server Server document.

2. Select Ports-Internet Ports.

3. For "TCP/IP port status," select Enabled. (By default, this setting enables HTTP access over port 80.)

4. For "SSL port status," select Enabled. (By default, this setting enables HTTPS access over port 443.)

5. Save and close the Server document.

Step 2 - Obtaining the SSL trusted root or SSL server certificate

Obtaining the appropriate SSL trusted root or SSL server certificate is the second of seven procedures required to use

SSL to encrypt connections from a QuickPlace or Virtual Classroom server to a Sametime/Domino server.

If the Domino HTTP server is set up to encrypt HTTP connections with SSL, the Domino Server Certificate Admin database on the Domino/Sametime server will already contain two certificates to support SSL connections:

An SSL trusted root certificate signed by a specific Certificate Authority (CA), such as VeriSign.

An SSL server certificate signed by the same CA as the trusted root certificate.

You must obtain a copy of one of these certificates. Later in this process, it is necessary to import one of the certificates described above into the stkeys.jks key store on the Sametime server. To clarify, you must obtain either the same SSL trusted root certificate that the Domino server uses to sign its SSL server certificate or a copy of the

SSL server certificate used by the Domino server.

Note The Domino Server Certificate Admin database must exist on the Domino server if the Domino server is set up for SSL. This database is created from the Server Certificate Admin template (csrv50.ntf). See the Domino server administration documentation for more information about this database.

27

IBM Lotus Sametime 7 Release Notes

Chapter 2 - Installation, migration, upgrade, and configuration information

For specific examples of how to obtain the appropriate SSL trusted root or SSL server certificate, see "Step 1 -

Obtaining the appropriate SSL trusted root or SSL server certificate" in the "Ensuring Sametime servlet access when

Domino HTTP requires SSL" topic in the Configuration notes section of these release notes.

Step 3 - Import the SSL certificate into the STKeys.jks database

Importing the SSL certificate into the STKeys.jks database is the third of seven procedures required to use SSL to encrypt connections from a QuickPlace or Virtual Classroom server to a Sametime/Domino server.

For Windows, AIX and Solaris servers, you use the iKeyman program to import the certificate. For i5/OS servers, you can use iKeyman if you already have it installed and normally use it for managing certificates. Otherwise , you use a qshell command called keytool.

You must import either the SSL trusted root certificate or the SSL server certificate into the STKeys.jks file. You obtained this certificate in the previous procedure.

Two procedures for importing the SSL certificate into the key database are provided below: one procedure applies to a

Sametime server that runs on the Windows, AIX, or Solaris operating system and the other procedure applies to a

Sametime server that runs on the IBM i5/OS operating system. Follow the procedure appropriate for your environment.

Note: Each of these procedures assumes you have exported the required SSL certificate to a file on the local operating system and that you will import this file from a local directory. The IBM IKeyMan program offers several other options for importing SSL certificates, including importing a certificate that has been copied to the Windows clipboard or importing a certificate from a remote network location. For more information about the other options for importing SSL certificates, see the IKeyMan documentation. This documentation is available by selecting Start -

Programs - IBM IKeyMan - Documentation from the Windows desktop.

Importing the SSL certificate to the key database on a Windows, AIX, or Solaris version of the Sametime server

If your Sametime server runs on the Windows, AIX, or Solaris operating system, use this procedure to import the SSL certificate into the STKeys.jks key database:

1. Start the IKeyMan program from the command prompt of the Sametime server:

For AIX/Solaris servers, enter this command:

/Lotus/Domino/WAS51Client/java/jre/bin/java.com.ibm.gsk.ikeyman.IKeyman

For Windows servers, enter this command:

C:\Lotus\Domino\WAS51Client\java\jre\bin\IKeyMan.exe

2. Choose Key Database File - Open.

3. Browse to and select the "STkeys.jks" key database (located in the Sametime server data directory).

4. Enter the password required to access the STKeys.jks file. The default password for the STKeys.jks file is

"Sametime."

5. In the Key database content area, select "Signer certificates." (Signer certificates may be selected by default.)

6. Click the "Add" button.

7. In the "Add Cas certificate from a File" dialog box:

- Verify that "Base64-encoded ASCII data" is selected as the Data type.

- Browse to and select the SSL certificate you want to import.

- Click Open and then click OK.

8. In the "Enter a Label" dialog box, provide a label for the certificate. This label identifies the certificate in the Signer

Certificates list of the IBM IKeyMan program. Click OK

If the certificate is imported successfully, the certificate label displays in the Signer Certificates list.

28

IBM Lotus Sametime 7 Release Notes

Chapter 2 - Installation, migration, upgrade, and configuration information

Importing the SSL certificate to an IBM i5/OS version of the Sametime server

If you already have iKeyman installed and normally use it for managing certificates, you can use it as described in the previous section. Otherwise, you can use a qshell command called keytool that is provided with the i5/OS operating system to import the certificate.

1. If you saved the SSL trusted root or SSL server certificate to your client workstation in the previous step, use ftp or another convenient method to copy it to your i5/OS server. The example in a later step assumes that you have copied it to the Sametime server data directory but this is not required.

2. From any i5/OS command line, run the following command to start qshell: strqsh

3. From qshell, run the following keytool command: keytool -import -alias <certificate_name> -file <file_containing_certificate> -storepass <keystore_password>

-keystore <keystore_name>

You must specify the full pathname to the file containing the certificate and the server keystore. The keytool command example below assumes the following:

- The certificate file name is stserver1cert.

- The server keystore file name is stkeys.jks.

- The password for the stkeys.jks keystore is sametime. (Be sure you are in a secure environment when issuing this command because the command

includes the keystore password.)

- Both the certificate file and the stkeys.jks database are stored in the Sametime server data directory. keytool -import -alias stserver1cert -file /lotus/domino/data/stserver1cert -storepass sametime -keystore

/lotus/domino/data/stkeys.jks

4. After you have imported the certificate, you can use this command to view the list of certificates in the stkeys.jks file to verify that the certificate was imported successfully. keytool -list -storepass sametime -keystore /lotus/domino/data/stkeys.jks

5. Press F3 to exit qshell.

Step 4 - Copy the STKeys.jks file containing the SSL certificate from the Sametime server to the QuickPlace or

VirtualClassroom server

Copying the STKeys.jks file from the Sametime server to the QuickPlace or VirtualClassroom server is the fourth of seven procedures required to use SSL to encrypt connections from a QuickPlace or VirtualClassroom server to a

Sametime/Domino server.

Copy the STKeys.jks file you just created on the Sametime server to the QuickPlace or Virtual Classroom server that will access the Sametime server. You can copy the STKeys.jks file to any directory on the QuickPlace or Virtual

Classroom server. Later in this process, you will specify the location of this STKeys.jks file in the Sametime.ini file on the QuickPlace or Virtual Classroom server.

The recommended directory for the STKeys.jks file is the QuickPlace or Virtual Classroom installation directory.

Step 5 - Add an entry to the Configuration database Access Control List (ACL) on the Sametime/Domino server

Adding an entry to the Configuration database ACL on the Sametime/Domino server is the fifth of seven procedures required to use SSL to encrypt connections from a QuickPlace or Virtual Classroom server to a Sametime/Domino server.

Note This procedure is required to enable QuickPlace or the Virtual Classroom to authenticate when accessing servlets on the Sametime server, regardless of whether you are encrypting connections with SSL. This procedure is also described in the release note entitled "Enabling QuickPlace or Virtual Classroom to access Sametime" in the

Configuration notes section of these release notes. If you have already performed this configuration, skip to step 7 below and ensure that the Sametime.ini file on the QuickPlace or Virtual Classroom server contains the parameters needed to support SSL connections to the Sametime server.

29

IBM Lotus Sametime 7 Release Notes

Chapter 2 - Installation, migration, upgrade, and configuration information

The QuickPlace or Virtual Classroom server must authenticate to execute servlets on the Sametime server. To allow the QuickPlace or Virtual Classroom server to authenticate, you must enter a user name in the ACL of the

Configuration database (stconfig.nsf) on the Sametime server.

When adding this user name to the ACL of the stconfig.nsf database on the Sametime server, ensure that the user name is provided with the:

SametimeAdmin role (mandatory)

Manager access level (recommended)

The name you enter in the ACL of the Configuration database must exist in the Domino Directory or LDAP directory that defines the Sametime community and must have a defined password. See the recommendation below before entering a name in the ACL of the Configuration database.

In a subsequent step, you will enter this user name and password in a Sametime.ini file on the QuickPlace or Virtual

Classroom server.

Recommendation: IBM Lotus software recommends that you create a special account in the directory for remote access to the Sametime servlets. This entry should be used only for the purpose described above. For example, you might create a Person document in a Domino Directory for the user name "SametimeServletAccess" and specify an

Internet password for this user name. You can enter this user name and password in the Sametime.ini file and the ACL of stconfig.nsf, but this directory entry should not be used for any other purpose.

Step 6 - Populate the appropriate fields in the MeetingServices document in the Sametime server Configuration

database (stconfig.nsf)

Populating the appropriate fields in the MeetingServices document in the Sametime server Configuration database is the sixth of seven procedures you must perform to enable a QuickPlace or Virtual Classroom application to authenticate when accessing servlets on the Sametime server.

Note This procedure is required to enable QuickPlace or the Virtual Classroom to authenticate when accessing servlets on the Sametime server, regardless of whether you are encrypting connections with SSL. This procedure is also described in the release note entitled "Enabling QuickPlace or Virtual Classroom to access Sametime" in the

Things You Need to Know section of these release notes. If you have already performed this configuration, skip to step

9 below and ensure that the Sametime.ini file on the QuickPlace or Virtual Classroom server contains the parameters needed to support SSL connections to the Sametime server.

In this procedure, you add the user name and password associated with the directory entry discussed above to fields in the MeetingServices document in the Configuration database:

1. If necessary, use a Lotus Notes client to open the Sametime Configuration database (stconfig.nsf) on the

Sametime server.

2. In the right-hand pane, open the MeetingServices document by double-clicking on the date associated with the document.

3. Scroll to the bottom of the MeetingServices document until you see the Remote Services Access heading.

4. Under the Remote Services Access heading, populate the eight fields with the user name and password associated with the directory entry discussed in "Step 5 - Add an entry to the Configuration database Access

Control List (ACL) on the Sametime/Domino server" above.

For example, if you created a directory entry with a user name of "SametimeServletAccess" and a password of

Sametime, populate the eight fields under the Remote Services Access heading as shown below:

Meeting Management Username: SametimeServletAccess

Meeting Management Password: Sametime

Recorded Meeting Management Username: SametimeServletAccess

Recorded Meeting Management Password: Sametime

30

IBM Lotus Sametime 7 Release Notes Chapter 2 - Installation, migration, upgrade, and configuration information

Materials Refresh Username: SametimeServletAccess

Materials Refresh Password: Sametime

Materials Control Username: SametimeServletAccess

Materials Control Password: Sametime

5. Save and close the MeetingServices document. Also, close the Configuration database.

Step 7 - Create a Sametime.ini file on the QuickPlace or Virtual Classroom server

Creating a Sametime.ini file on the QuickPlace or Virtual Classroom server is the last of seven procedures required to use SSL to encrypt connections from a QuickPlace or Virtual Classroom server to a Sametime/Domino server.

Note This procedure is also required to enable QuickPlace or Virtual Classroom to authenticate when accessing servlets on the Sametime server. If you have already performed the procedure described in the release note entitled

"Enabling QuickPlace or Virtual Classroom to access Sametime" in the Configuration notes section of these release notes, the Sametime.ini file will already exist on the QuickPlace or Virtual Classroom server and it will not be necessary to create it as described below. However, it will be necessary to add the settings to the Sametime.ini file required to support SSL. The additional settings required to support SSL are listed below.

The Sametime.ini file on the QuickPlace or Virtual Classroom server must contain the parameters that enable the

Sametime server to be accessed using SSL. You must create the Sametime.ini file in the QuickPlace or Virtual

Classroom installation directory on the QuickPlace or Virtual Classroom server.

Follow these instructions to manually create a Sametime.ini file in the QuickPlace or Virtual Classroom installation directory.

1. Open a text editor on the QuickPlace or Virtual Classroom server.

2. Create a text file consisting of a [Config] section and the settings listed below:

[Config]

VPS_Name= (This setting should specify the canonical name of the Domino server to which QuickPlace or Virtual

Classroom will connect. An example value is VPS_Name=CN=Sametimeserver/OU=East/O=Acme.)

SametimeCluster= (This setting should also specify the canonical name of the Domino server, e.g.:

SametimeCluster=CN=Sametimeserver/OU=East/O=Acme.)

ConfigurationHost= (This Sametime.ini setting should specify the fully-qualified DNS name of the Sametime server, e.g.: ConfigurationHost=Sametimeserver.east.acme.com.)

ConfigurationPort=443 (This setting should specify port 443.)

ConfigurationSSLEnabled=true

SSLManagerClassName=com.lotus.sametime.configuration.IBMJSSE14Manager (This Sametime.ini parameter must specify the IBMJSSE14Manager class exactly as shown.)

javax.net.ssl.keyStore=c:/lotus/domino/stkeys.jks (This setting must specify the complete file path, including the filename, of the stkeys.jks file on the QuickPlace or Virtual Classroom server.)

javax.net.ssl.trustStore=c:/lotus/domino/stkeys.jks (This Sametime.ini file setting must also specify the complete file path, including the filename, of the stkeys.jks file on the QuickPlace or Virtual Classroom server.)

javax.net.ssl.keyStorePassword=sametime (This Sametime.ini file setting must specify the password of the stkeys.jks file. The default password is "sametime.")

javax.net.ssl.keyStorePassword=sametime (This Sametime.ini file setting must specify the password of the stkeys.jks file. The default password is "sametime.")

31

IBM Lotus Sametime 7 Release Notes

Chapter 2 - Installation, migration, upgrade, and configuration information

SametimeAdminUsername= (This Sametime.ini setting should specify the name of the user account that was added to the ACL of the Configuration database on the Sametime server in "Step 5 - Add an entry to the

Configuration database ACL on the Sametime/Domino server.")

SametimeAdminPassword= (This Sametime.ini setting should specify the password associated with the administrator account above.)

3. After creating the text file containing the parameters described above, save the file to the QuickPlace or Virtual

Classroom installation directory under the name "Sametime.ini."

This concludes the procedures required to use SSL to encrypt connections from a QuickPlace or Virtual Classroom server to a Sametime server (while allowing Web browsers to access the server via unencrypted HTTP).

Tip If you add another QuickPlace or Virtual Classroom server to your environment, you can copy the stkeys.jks file and the Sametime.ini file that you created in this procedure to the newly-added server. Using the existing files prevents you from having to perform all eight steps above each time you add a new QuickPlace or Virtual Classroom server to your environment.

Sametime server

Enhance security by disabling RAPFileServlet

IBM Lotus software recommends that you enhance the security of the Sametime 7.0 server by disabling the

RAPFileServlet following the Sametime 7.0 installation.

To disable the RAPFileServlet, you must remove an entry from the the servlet.properties file in the Data subdirectory of the Sametime installation directory. (The default location of the servlet.properties file is C:\Lotus\Domino\Data.)

To disable the RAPFileServlet:

1. Open a text editor on the Sametime server machine.

2. Use the text editor to open the servlet.properties file in the C:\Lotus\Domino\Data directory (or <Sametime install directory>\Data).

3. Locate the following servlets.startup line at the bottom of the servlet.properties file. servlets.startup=bootstrap scs auth admin mmapi stcal fileupload rapfile

4. In the line above, delete the "rapfile" text string. The correctly edited line will appear as follows: servlets.startup=bootstrap scs auth admin mmapi stcal fileupload

5. Save and close the servlets.properties file.

6. Restart the Sametime server for the change to take effect.

Sametime Connect client

Forcing Sametime Connect for browsers to use English

You can force the Sametime Connect for browsers client to display its user interface in the English language (or any other language) regardless of the language specified by the client computer operating system or Sametime server computer operating system.

For more information, refer to tech note 1096091 created for the Sametime server. To access this tech note:

1. Browse to www.ibm.com/support.

2. Select "Software" link to get support for software.

3. In the field provided, search software support for the tech note 1096091.

32

IBM Lotus Sametime 7 Release Notes

Chapter 2 - Installation, migration, upgrade, and configuration information

Sametime server

Running Sametime in the background on AIX

To run Sametime in the background on AIX, you must install the X Virtual Frame Buffer (Xvfb).

1. Install the XVFB packages from your OS cds:

- OpenGL.OpenGL_X.dev.vfb.05.01.0000.0000  OR EQUIVALENT

- X11.vfb.05.01.0000.0000  OR EQUIVALENT

2. Login in from a terminal shell as root and run the following:

/usr/bin/X11/X -vfb -x GLX -x abx -x dbe -force :1 &

3. You can verify that the VFB is running properly by typing:

/usr/lpp/X11/Xamples/bin/xprop -display machinename:1 -root | grep VFB

You should see the following: XVFB_SCREEN(STRING) = "TRUE"

You can assign any number except 0 in place of the number "1" in the above example. 

This is the display number you wish to have associated with this instance of the XVFB.  The machinename is the name of your AIX machine.

Follow these instructions to run Sametime in the background:

1. Login as notes.

2. Modify the notes user .profile or equivalent  to add the ${BINDIR} from ststart to the LD_LIBRARY_PATH and to the PATH environment variables.

3. Logout and log back in.

4. Set the DISPLAY variable to the display number you used above:

For example: export DISPLAY=machinename:1

5. From the data directory, run the command:

nohup /opt/lotus/bin/server < /dev/null > /dev/null 2>&1 &

( This example assumes /opt/lotus/bin is the $LOTUSDIR in ststart).

6. Exit the telnet session or the xwindows session.

Sametime Connect client

Sametime Connect and HTTPS connections on port 443 or 563

This release note discusses issues pertaining to Sametime Connect client connectivity on port 443. These issues include:

Connecting to the Community Services on port 443 when the Domino HTTP server is configured to listen for SSL connections on port 443

Sametime 2.5 Connect client compatibility issue when connecting to a Sametime 7.0 server on port 443 or 563

Sametime 7.0 Connect client compatibility issue when connecting to a Sametime 2.5 server on port 443 or 563

Community Services multiplexer on Sametime 7.0 server does not forward HTTPS connections on port 443 to the

Domino HTTP server

33

IBM Lotus Sametime 7 Release Notes

Chapter 2 - Installation, migration, upgrade, and configuration information

Connecting to the Community Services on port 443 when the Domino HTTP server is configured to listen for SSL

connections on port 443

Sametime installs on a Domino server. Web browser users connect to the Domino HTTP server when accessing the

Sametime server. If the Domino HTTP server is configured to support SSL for Web browser connections, the Domino

HTTP server is usually configured to listen for these HTTPS connections on port 443 or port 563.

Some Sametime Connect clients may operate in networks that require the clients to connect to the Internet or intranet through an HTTPS proxy. Many network environments that require users to connect through an HTTPS proxy only allow outbound connections to occur on port 443. If a Sametime Connect client operates in such an environment, the following configurations must exist on the Sametime Connect client and the Sametime server for the connection to be successful:

In the Sametime Connect client Sametime Connectivity tab:

The "Community port" setting must specify port 443.

The "Use proxy" and "Use HTTPS proxy" settings must be selected. The IP address or DNS name of the HTTPS proxy server and port number used to connect to the HTTPS proxy server are also specified.

In the Sametime Administration Tool on the Sametime server, the Community Services Network - Address for

HTTPS-tunneled client connections - Port number setting must specify port 443.

With these configurations, the Sametime Connect client connects to the HTTPS proxy, and the proxy connects to the

Sametime server on behalf of the Sametime Connect client. The connection from the proxy server to the Sametime server Community Services occurs on port 443. The Community Services on the Sametime server must be configured to listen for the HTTPS connections on port 443 to ensure the connection can succeed.

Note The configurations above enable Sametime Connect to establish a connection to a Sametime server through an

HTTPS proxy server. The HTTPS connection method is used to establish the connection but the data passing over this connection is not encrypted with SSL.

If the Domino HTTP server is also configured to listen for HTTPS connections on port 443, a conflict occurs because the Sametime Community Services are also configured to listen for HTTPS connections on the same port number.

In this scenario, you must assign an additional IP address to the Sametime server to ensure that both Web browser users and Sametime Connect client users can connect to the Sametime server on port 443. This configuration requires the following steps:

Bind the DNS name for the Sametime server to the Sametime HTTP server.

Add a new IP address to the Sametime server machine.

Map the new IP address to a new DNS name for the Sametime Community Services. This configuration is performed on the DNS server.

Use the Sametime Administration Tool to add the new DNS name to the Community Services connectivity settings on the Sametime server. This configuration enables the Community Services to listen for HTTPS connections on the new DNS name.

Configure the Sametime Connect clients to connect to the new Community Services DNS name.

Note The configuration described below can enable either a Sametime 2.5 (or higher) Connect client to connect to a

Sametime 7.0 server on port 443 or 563.

Step-by-step instructions for these configurations are provided below.

Step 1 - Bind the base DNS name for the Sametime server to the Sametime HTTP server.

1. Open the Sametime Administration Tool and select Configuration-Connectivity-Networks and Ports-Configure

HTTP services on a Web page in its own window. The HTTP section of the Server document in the Domino

Directory opens and displays in a separate window on the computer.

34

IBM Lotus Sametime 7 Release Notes

Chapter 2 - Installation, migration, upgrade, and configuration information

2. Under the Basics heading in the "Host name" field, enter the base DNS name for the Sametime HTTP server (for example, www.sametime1.com).

Under the Basics heading In the "Host name" field, also enter 127.0.0.1. This entry is required for the Sametime

Administration Tool to operate in this configuration. Place a comma between the DNS name of the HTTP server and the 127.0.0.1 entry (e.g. www.sametime1.acme, 127.0.0.1)

3. Click "Save & Close" at the top of the Server document. After the document closes, close the Server-Servers view of the Domino Directory.

Step 2 - Add a new IP address to the Sametime server machine.

To add a new IP address to the Sametime server, you can either install an additional Network Interface

Card (NIC) in the Sametime server machine or assign multiple IP addresses to a single NIC.

To assign multiple IP addresses to a single NIC on a Windows machine:

1. Open the Windows Control Panel.

2. Click the Protocols tab.

3. Select TCP/IP Protocols-Properties-Specify an IP Address.

4. Click the Advanced tab.

5. Use the Advanced IP Addressing screen to assign multiple IP addresses to a single NIC.

Step 3 - Set up your DNS server to map the IP address to a DNS name for Sametime Community Services.

After you have added a new IP address to the Sametime server, set up your DNS server to map the new IP address to a DNS name for the Sametime server Community Services.

For the Community Services, map the IP address to the DNS name "community-xxx.xxx.xxx" (where xxx.xxx.xxx is the

DNS name that was bound to the Sametime HTTP server in step 1 above).

For example, you would map the new IP address to the DNS name "community-www.sametime1.com."

Step 4 - Configure the HTTPS-tunneling settings in the Sametime Administration Tool

You must specify the new DNS name and port number for Community Services HTTPS connections in the Sametime

Administration Tool.

1. Open the Sametime Administration Tool and select Configuration-Connectivity-Networks and Ports.

2. In the Community Services Network-Address for HTTPS-tunneled connections settings, specify the following:

Host name: community-xxx.xxx.xxx (Where xxx.xxx.xxx is the DNS name that was bound to the Sametime HTTP server. For example, community-www.sametime1.com.)

Port number: 443

With this configuration, the Sametime Community Services multiplexer will listen for HTTPS-tunneled connections on host name community-www.sametime1.com on port 443.

Step 5 - Configure the Sametime Connect clients to connect to the new DNS name of the Community Services

To connect to a Sametime server configured to listen for HTTPS connections on the host name and port specified above, the Sametime Connect client must have the following settings in the Sametime Connectivity tab:

The "Host" setting must specify community-www.sametime1.com.

Note If a Sametime 2.5 Connect client connects to a Sametime 7.0 server using HTTPS on port 443 or 563, it is only necessary to enter the server name (www.sametime1.com) in the "Host" setting of the Sametime 2.5 Connect client. For example, enter "www.sametime1.com" instead of "community-www.sametime1.com" in the "Host" field.

For more information, see "Sametime 2.5 Connect client compatibility issue when connecting to a Sametime 7.0 server on port 443 or 563" below.

35

IBM Lotus Sametime 7 Release Notes

Chapter 2 - Installation, migration, upgrade, and configuration information

The "Community port" setting must specify 443.

"Use proxy" and "Use HTTPS proxy" must be selected. Enter the host name and port on which the Sametime

Connect client connects to the HTTPS proxy.

Sametime 2.5 Connect client compatibility issue when connecting to a Sametime 7.0 server on port 443 or 563

The Sametime 2.5 Connect client is designed to use HTTPS tunneling on ports 443 or 563 to connect to a server that uses multiple IP addresses.

When a Sametime 2.5 server is configured to listen for HTTPS-tunneled client connections on port 443 or 563, the server listens for Community Services connections on the server name "Community-servername." For example, if your

Sametime 2.5 server is named sametimeserver.acme.com, the server listens for HTTPS-tunneled Community Services connections on ports 443 or 563 on the server name "Community-sametimeserver.acme.com." The Sametime 2.5 server is hard-coded to prepend the string "Community-" to its server name when listening for Community Services connections on ports 443 or 563. This design in the Sametime 2.5 server accomodates the multiple IP address issues discussed in "Connecting to the Community Services on port 443 when the Domino HTTP server is configured to listen for SSL connections on port 443" above.

The Sametime 2.5 Connect client is also hard-coded to prepend the string "Community-" to its Host setting when its

"Community port" setting specifies port 443 or 563. For example, assume the following settings exist in the Sametime

Connectivity tab of a Sametime 2.5 Connect client:

Host - "sametimeserver1.acme.com"

Community port - Either port 443 or port 563 is specified.

With this configuration, the Sametime 2.5 Connect client attempts the connection to the server name

"Community-sametimeserver1.acme.com" even though the string "sametimeserver1.acme.com" is entered in its Host setting.

Because the Sametime 2.5 Connect client automatically prepends the string "Community-" to its host name, it is not necessary to enter the string "Community-servername" in the Sametime 2.5 Connect client when this client connects to a Sametime 7.0 server that is configured to listen for HTTPS connections on multiple IP addresses.

Note also that when a Sametime 7.0 server listens for HTTPS-tunneled connections from Sametime 2.5 Connect clients, the additional DNS name assigned to the Community Services on the Sametime 7.0 server must begin with the "Community-" string, as described in "Connecting to the Community Services on port 443 when the Domino HTTP server is configured to listen for SSL connections on port 443" above. If the Sametime 7.0 Community Services DNS name does not begin with the "Community-" string, the Sametime 2.5 Connect client cannot connect to the Sametime

7.0 server.

Sametime 7.0 Connect client compatibility issue when connecting to a Sametime 2.5 server on port 443 or 563

If a Sametime 7.0 Connect client connects via HTTPS-tunneling to a Sametime 2.5 server on port 443 or 563, the

Sametime 7.0 Connect client does not prepend the "Community-" string to its host name when making the connection to the Sametime 2.5 server.

The Sametime 2.5 server is hard-coded to prepend the string "Community-" to its server name when listening for

HTTPS connections on port 443 or 563. To ensure the Sametime 7.0 Connect client can connect to the Sametime 2.5

Community Services on port 443 or 563, the string "Community-" must be manually added to the Host name in the

Sametime Connectivity tab in the Sametime 7.0 Connect client.

Manually adding the "Community-" string to the Host name in the Sametime 7.0 Connect client ensures that the client attempts the connections on the name on which the Sametime 2.5 server listens for the connections.

For example, to ensure a Sametime 7.0 Connect client can connect on port 443 or 563 to the Sametime 2.5 server named "sametimeserver1.acme.com," the following settings must exist in the Sametime Connectivity tab of the

Sametime 7.0 Connect client:

Host - "Community-sametimeserver1.acme.com."

Community port - Either port 443 or port 563 is specified. (Specify the port on which the Sametime

2.5 server listens for HTTPS-tunneled connections.)

36

IBM Lotus Sametime 7 Release Notes

Chapter 2 - Installation, migration, upgrade, and configuration information

Community Services multiplexer on Sametime 7.0 server does not forward HTTPS connections on port 443 to the

Domino HTTP server

A Sametime 7.0 server can simulaneously listen for HTTP connections to multiple services on port 80 when the

Sametime server machine includes a single IP address. For example:

A Web browser can connect to the Domino HTTP server on a Sametime server on port 80.

A Sametime Connect client can make an HTTP-tunneled connection to the Sametime Community

Services on port 80.

A Sametime Meeting Room client can make HTTP-tunneled connections to both the Sametime

Community Services and Meeting Services on port 80.

All of these connections can occur to the same DNS name using port 80. On a Sametime 7.0 server, it is not necessary to assign separate IP addresses to the HTTP Services, Community Services, and Meeting Services to enable connections to all services to occur using a single DNS name on port 80. The design of the Community Services multiplexer on a Sametime 7.0 server makes this capability possible. The Community Services multiplexer can listen for HTTP connections from Web browsers, Sametime Connect clients, and Sametime Meeting Room clients on port

80. The Community Services multiplexer examines these connections and then forwards the connections to the appropriate service. For example, the Community Services multiplexer forwards the Web browser connections to the

Domino HTTP Server, the Community Services connections to the Community Services, and the Meeting Services connections to the Meeting Services.

Note that the Community Services multiplexer on a Sametime 7.0 server cannot listen for connections on port 443 or

563 and then forward these connections to the Domino HTTP server. The Community Services multiplexer can forward

HTTP connections on port 80 to the Domino HTTP server, but not connections on port 443 or 563. For this reason, a

Sametime 7.0 server must be assigned multiple IP addresses when both the Domino HTTP server and the Sametime

Community Services on the Sametime server must listen for connections on port 443 or 563.

Note The Community Services multiplexer on a Sametime 7.0 server also cannot listen for HTTPS connections to the

Sametime Meeting Services or Community Services on ports 443 or 563 and forward these connections to the

Community Services and Meeting Services. HTTPS-tunneling to the Sametime Meeting Services is not supported.

Sametime Meeting Room clients cannot connect to the Sametime Meeting Services through an HTTPS proxy server.

Sametime server

Server display color setting must be higher than 256 colors

The server machine on which Sametime is installed must have a video card installed and a display color setting must be higher than 256 colors. A 16-bit color setting is recommended.

The following problems can occur if the server machine has a display color setting of 256 colors or less.

The images in whiteboard attachments do not display correctly on the whiteboard.

Users cannot save the whiteboard.

The Meeting Room client opens with a gray whiteboard.

Screen-sharing buttons are disabled in the Meeting Room client.

Audio/Video features do not work.

When a user attends a meeting, an additional Meeting Room client opens in a different window and flashes periodically.

The license utility fails to run.

Shortly after these problems appear, meetings on the Sametime server may fail to become active.

37

IBM Lotus Sametime 7 Release Notes

Chapter 2 - Installation, migration, upgrade, and configuration information

Sametime server

Setting up an LDAP connection to an ActiveDirectory server

You can set up an LDAP connection to an ActiveDirectory server; however, certain modifications to ActiveDirectory are required. Follow these procedures to use ActiveDirectory with Sametime.

Planning

1. Choose whether to allow anonymous read access to your ActiveDirectory Users.

2. If you do not allow anonymous read access to your ActiveDirectory, assign read privileges to a newly-created or existing ActiveDirectory username.

ActiveDirectory Procedures

1. Note the Base DN for the ActiveDirectory Users tree (for example, CN=Users,dc=ad,dc=mycompany,dc=com).

2. Using the ActiveDirectory Users and Computers tool, navigate to the Users container.

3. Open the Properties dialog of the Users container and select the Security tab.

4. Choose Add to add a new security privilege to this container.

5. A Choose Users dialog box appears.

- If you allow anonymous access to your ActiveDirectory, select "Everyone." Click Add and OK.

- If you restrict read access to an ActiveDirectory username, select that username. Click Add and OK.

6. The top-level Security dialog box appears. Select the appropriate username.

- If you allow anonymous access to your ActiveDirectory, select "Everyone."

- If you restrict read access to an ActiveDirectory username, select that username.

- For either username, ensure that only Read permissions are checked.

7. Click Advanced.

8. The Access Control Settings dialog box appears. Select the appropriate username and click View/Edit.

9. The Permission Entry for Users dialog box appears. Select the "Apply onto" pull-down menu. Change "This object only" to "This object and all child objects." Click OK.

10. Complete all remaining dialog boxes by clicking OK.

Sametime installation/configuration procedures

After you have performed the ActiveDirectory procedures described above, you must configure the Sametime server to access the directory on the ActiveDirectory server. Follow the procedures described in the "Using LDAP with the

Sametime server" chapter of the IBM Lotus Sametime 7.0 Administrator's Guide to enable Sametime to connect to the

ActiveDirectory server.

Note: You must be knowledgeable about the ActiveDirectory directory schema to configure Sametime to access the

ActiveDirectory server.

Important: After performing the procedures described in the administrator's guide, you must also configure an additional parameter in the Configuration database (stconfig.nsf) to enable Sametime to operate with Active Directory.

For more information, see "Problems with client Contact lists and LDAP Active Directory" in the Troubleshooting -

Sametime Server - LDAP issues section of these Release Notes.

38

IBM Lotus Sametime 7 Release Notes

Chapter 2 - Installation, migration, upgrade, and configuration information

Sametime Connect client, Sametime server

Setting up the SIP Gateway for Sametime on UNIX

The Sametime 7.0 Administrator's Guide includes instructions for setting up the SIP Gateway on a Sametime server that is installed on a server running a Microsoft Windows or IBM i-Series operating system. However, the administrator's guide does not discuss setting up the SIP Gateway when a Sametime server operates on a UNIX server.

If you want to set up the SIP Gateway for Sametime on either the AIX or Solaris operating system, you can use the instructions in the Sametime 7.0 Administrator's Guide that explain how to set up the SIP Gateway in the Windows environment. Specifically, you use the instructions in the "Setting up the SIP Gateway functionality (Windows environment)" section of the "Enabling the SIP Gateway" chapter of the Sametime 7.0 Administrator's Guide to set up the SIP Gateway on AIX/Solaris.

The procedure to set up the SIP Gateway for a Sametime server on AIX or Solaris is exactly the same as the procedure required to set up the SIP Gateway for a Sametime server installed on a Windows operating system. However, administrators should note the following when setting up the SIP Gateway for a Sametime server on AIX/Solaris.

In one step of this set up procedure, the administrator must install the SIP Connector software on a separate machine from the Sametime server. The administrator should be aware that the SIP Connector software available on the

AIX/Solaris CDs must be installed on a server running the Windows operating system. The procedure to install the SIP

Connector on Windows is described in the administrator's guide.

To summarize this issue:

You can use the "Setting up the SIP Gateway functionality (Windows environment)" instructions in the Sametime

7.0 Administrator's Guide to enable the SIP Gateway for a Sametime server running on an AIX or Solaris operating system.

When installing the SIP Connector on a separate machine from the Sametime server, you must install the SIP

Connector on a server running the Windows operating system as described in the administrator' s guide. The SIP

Connector runs only on Windows and cannot be installed on a server that runs an AIX or Solaris operating system.

Sametime server

Signing Sametime databases

Some Sametime databases contain agents that access the Directory and provide authentication support for

Sametime. Agents within these databases are signed by the "Sametime Development/Lotus Notes Companion

Products" ID.

If the security policies of your organization require you to re-sign databases with a different ID, you must re-sign the following Sametime database and templates:

STCONF.NTF

STDISC50.NTF

STTEAM50.NTF

STSRC.NSF

After re-signing these files, ensure that the signer you have used is listed in the Directory ACL and in the "Run unrestricted agents" field of the Sametime server Server document.

The minimal Directory ACL requirements for the signer ID are:

Access: Reader

Roles: [Group Creator], [Group Modifier], [UserCreator], [UserModifier]

39

IBM Lotus Sametime 7 Release Notes Chapter 2 - Installation, migration, upgrade, and configuration information

Uninstallation information

Sametime server

Registry key still exists after uninstalling the server

After you uninstall the Sametime server, the following registry key still exists. You can manually delete this registry key.

HKLM\SOFTWARE\Lotus\Sametime\MeetingServer\Services

Sametime server

Uninstalling Sametime from UNIX

If your Sametime server operates on the AIX or Solaris operating system, you cannot uninstall Sametime while leaving

Domino installed on the server. To uninstall Sametime, remove the directories which contain both the Domino server and the Sametime server.

40

IBM Lotus Sametime 7 Release Notes Chapter 3 - Known limitations, problems, and workarounds

Chapter 3 - Known limitations, problems, and workarounds

Limitations

Installation issues

Sametime Meeting Room client, Sametime server, Web browsers

Java VM is not installed with Sametime clients

Sametime clients require either the IBM or Sun JVM 1.4.2 to function correctly. This VM is not installed with the

Sametime clients.

If a user's computer does not have any VM installed, the user's browser will display a blank page when the user attempts to attend a meeting. In this scenario, the user must download and install the Sun JVM 1.4.2 or IBM JVM

1.4.2.

Sametime Connect client, Sametime server

Sametime Connect 2.x and 3.x clients cannot connect

The Sametime 7.0 server includes a security feature that may prevent Sametime Connect clients from earlier

Sametime releases from connecting to a Sametime 7.0 server.

The administrator configures this security feature using the following settings in the Sametime.ini file in the

C:\Lotus\Domino directory on the Sametime server:

VP_SECURITY_LEVEL=70

VP_SECURITY_ALLOW_USER=0

The configuration shown above ensures that only Sametime Connect 7.0 clients can connect to the Sametime server.

To enable Sametime Connect clients from earlier Sametime releases to connect to the Sametime 7.0 server, you must configure the two Sametime.ini settings as discussed in the "Prohibiting logins from insecure clients to the server" section in the "Configuring the Community Services" chapter of the IBM Lotus Sametime 7.0 Administrator's Guide

(sthelpad.nsf).

Accessibility/Section 508 issues

Web browsers

Can't tab between text and Meeting Room in Meeting Tester

When testing a meeting, an end user cannot tab between the Meeting Room and the help text in the browser window.

41

IBM Lotus Sametime 7 Release Notes

Chapter 3 - Known limitations, problems, and workarounds

Sametime Meeting Room client

Mnemonics disappear during an online meeting

During an online meeting, you can press the Alt+w and Alt+s keys to switch between the whiteboard and screen sharing tools. Note that if you use these keys to make more than four total switches during a meeting, the mnemonics may disappear from the Meeting Room client and all keyboard shortcuts may become inoperable in the Meeting Room client.

Sametime Meeting Room client

SHIFT+TAB won't move focus backward through column headers

Pressing SHIFT+TAB does not move the focus backward through the column headers in the Participant List or the

Participant List details.

Meeting Room client issues

Linux clients

Screen sharing optimization not available with Linux clients

The Windows version of the Meeting Room client includes an "Optimize for Image Quality" setting and an "Optimize for

Performance" setting available from the Tools - Preferences - Screen Sharing tab of the Meeting Room client.

The Linux version of the Meeting Room client does not support these screen sharing optimization features.

Sametime server issues

Sametime Administration Tool

Connectivity and log changes occur without server restart

You should not change the Community Services Network host name or port number settings on the

Configuration-Connectivity-Networks and Ports tab in the Sametime Administration Tool unless you want the changes to take effect. The "Networks and Ports" configuration tab contains text that indicates it is necessary to restart the

Sametime server for changes on the tab to take effect. However, changes on this tab can take effect without a server restart.

Consider the following scenario:

1. An administrator opens the Configuration-Connectivity-Networks and Ports tab in the Sametime Administration

Tool and changes the Community Services Network-Address for HTTP-tunneled connections-Port number setting from 8082 to 80.

2. The administrator clicks the Update button on the Networks and Ports tab.

3. The administrator then decides that the port number change should not be implemented immediately and decides to wait to restart the server to finish implementing the port number configuration change.

Note that any change to the Community Services Network connectivity settings on the "Networks and Ports" tab will take effect without a server restart. The update will occur according to the time interval specified in the "How often to poll for new servers added to the Sametime Community (minutes)" setting located on the Configuration-Community

Services tab of the Sametime Administration Tool.

Changing the Community Services Network connectivity settings on the "Networks and Ports" tab of the Sametime

Administration Tool changes the data that is sent to the Community Services multiplexer and might cause connectivity problems or affect server peformance. If you change Community Services Network connectivity settings, you should restart the server immediately.

42

IBM Lotus Sametime 7 Release Notes

Chapter 3 - Known limitations, problems, and workarounds

The following Community Services and logging configuration settings will also be updated according to the time interval specified in the "How often to poll for new servers added to the Sametime Community" setting. You should not alter these configuration settings in the Sametime Administration Tool unless you want the changes to go into effect.

All settings on the following tabs of the Sametime Administration Tool will be updated without a server restart:

The Configuration-Community Services tab

The Configuration-Community Services-Anonymous Access tab

The Logging Settings-General tab

The Logging Settings-Capacity Warnings tab

Linux Client issues

Linux clients

Linux Meeting Room client does not support Audio/Video

Sametime Meeting Room clients that run in the Mozilla browser on a Linux operating system do not support audio/video.

Linux clients

Screen sharing issues on Linux clients

The following issues apply to the screen sharing tool when the Meeting Room client runs in a Mozilla browser on a

Linux computer:

If the meeting moderator selects the "Share a program" icon in the Meeting Room client and then selects an application to share, the meeting attendees will see the moderator's entire screen in their Meeting Room clients instead of just the shared application.

When the moderator shares a program, the Stop sharing and Allow control buttons do not appear in the upper-left corner of the Meeting Room client.

International issues

Linux clients, Sametime server

Sametime 7.0 not supported on Turkish locale UNIX servers

You cannot install an AIX or Solaris version of Sametime 7.0 on a server set to the Turkish locale.

Sametime Meeting Room client, Sametime server

Supported Whiteboard file types

The following file types are supported by the whiteboard. These files can be attached to a meeting and automatically converted for display in the whiteboard.

If users need to attach unsupported files to a meeting, use the Print Capture Utility to convert the files for display in the whiteboard.

File Type

Ami Pro 3.x

Bitmap

CCITT Group 3 Fax

Extension

.SAM

.BMP

.TIF

43

IBM Lotus Sametime 7 Release Notes Chapter 3 - Known limitations, problems, and workarounds

CompuServe Graphics Interchange Format

Computer Graphics Metafile

Hypertext Markup Language (HTML)

JPEG file

Lotus 1-2-3 3.0, 4.0, 5.0, 6.x, R9

Lotus 1-2-3 97 and 98, R9

Lotus 1-2-3 for Macintosh

Lotus 1-2-3 for OS/2

Microsoft Word for Macintosh 2.0, 3.0

Microsoft Word for Windows 6.0, 7.0, 97, Office 2000

Paintbrush/DCX (multi-page PCX)

PICT and PICT2 Graphics

Portable Network Graphics

Revisable Form Text

Rich Text Format

Sametime Print Capture File

Sametime Whiteboard

Tagged Image File Format

Text file

Windows Metafile Graphic

WordPerfect 5.x, 6.x, 7.x,8

WordPerfect for Macintosh 2.0, 3.0

WordPerfect Graphics

.GIF

.123

.DOC

.PCX

.PCT

.RTF

.PNG

.RFT

.FST

.SWB

.TIFF, .TIF, .EPS

.TXT, .BAT, .INI

.WMF

.WPD

.CGM

.HTM, .HTML

.JPEG, .JPG, .JPE

.WK*, .123

Lotus Freelance for OS/2

Lotus Freelance

Lotus PIC

Lotus WordPro 96/97, R9

Microsoft Excel 2.x, 3.0, 4.0, 5.0, 7.0, 97, Office 2000

Microsoft PowerPoint 4.x, 7.0, 97

.PRS

.LWP

.WG2

.PRE, .PRZ

.PIC

.XLS

.PPT

.WPG

Known problems and workarounds

Installation issues

Sametime server

After Sametime uninstall, reboot before reinstalling Sametime

If you uninstall a Sametime server, reboot the server machine completely before attempting to reinstall the Sametime server.

If you do not reboot the server machine before attempting to reinstall Sametime, the installation may return an error indicating that a service is marked for deletion and this service will not be added by the installation.

Note: You should reboot the server machine even if all Sametime services were stopped when you uninstalled the

Sametime server.

44

IBM Lotus Sametime 7 Release Notes Chapter 3 - Known limitations, problems, and workarounds

Sametime server

Clicking Cancel while installation is copying files

If you click the Cancel button while the Sametime server is copying Community Services or Meeting Services files during the Sametime server installation, you might see a dialog box with the following message: "Setup has detected that unInstallShield is in use. Please close UnInstallShield and restart Setup." If you see this dialog box, click the OK button. The uninstallation will uninstall the files that were copied to the server by the installation program before you elected to cancel the installation.

If you click the Cancel button while the installation program is copying other files, the installation may exit without displaying any dialog box. In this case, the uninstallation should also uninstall any files that had been copied. You may want to check the Windows Add/Remove Programs feature to verify that the Sametime server is not listed as an installed program. If the Sametime server is listed as installed, use the Windows Add/Remove Programs feature to uninstall the server.

Sametime server

Deleting directories following an installation failure

If the installation fails, delete the Sametime directory from your hard drive. If the Sametime directory is not present,

InstallShield has already deleted it. Run the uninstallation program to ensure all Sametime components are deleted from the Sametime server machine and install Sametime again.

Sametime server

Directory has "Enforce consistent ACLs" option selected

The administrator must add the signer "Sametime Development/Lotus Notes Companion Products" to the ACL of the

Directory on the Sametime server. This signer is required so that Sametime agents in Sametime databases can interact with the Directory as needed.

If a Directory is replicated to a Sametime server from another Domino server, and the Directory has the "Enforce a consistent ACL across all replicas of this database" option selected, replication between a Domino server and a

Sametime server will be broken. The replication is broken because the Directory ACL on the Sametime server has different ACL settings than the Directory on the Domino server.

If your Domino environment requires you to use the "Enforce a consistent ACL across all replicas of this database" option, you must manually modify the ACLs of the Directories in the domain to ensure that Directory replication can occur from the Domino server(s) to the Sametime server. Specifically, you may need to manually add the "Sametime

Development/Lotus Notes Companion Products" signer to all Directories involved in the replication scheme in your environment. The signer must have the same access level and permissions in the Directories on the Domino servers as it has on the Sametime server.

Note: The Sametime server 7.0 uses the same Domino Directory as Domino server release 7.0. Do not replicate earlier versions of the Domino Directory to the Sametime server.

Sametime server

Do not install Sametime multiplexer on a Sametime server

Sametime 7.0 provides an installation option that allows you to install a Sametime Community Services multiplexer without installing a Sametime server or any other Sametime components.

This installation option enables you to install the Community Services multiplexer on a separate machine from the

Sametime server. When the multiplexer operates on a separate machine from the Sametime server, the multiplexer machine is dedicated to maintaining the Sametime Community Services client connections while the Community

Services on the Sametime server perform all other Community Services processing functions. This configuration distributes the workload required to support the Community Services among multiple servers and enables a Sametime server to support a larger number of Community Services users.

45

IBM Lotus Sametime 7 Release Notes Chapter 3 - Known limitations, problems, and workarounds

Do not install a Sametime Community Services multiplexer on the same machine as a Sametime server. When you install a Sametime server, a Community Services multiplexer is also installed with the Sametime server. If you perform a separate installation of a Community Services multiplexer on a Sametime server, the Sametime server will contain two multiplexers and will not function correctly. No error message is displayed if you attempt to install a Community

Services multiplexer on a Sametime server.

The separate Community Services multiplexer installation should be performed only on a machine that does not already include Sametime.

Sametime server

Opening the install guide (stinstall.nsf) in a Web browser

You can open the NSF version of the Sametime 7.0 Installation Guide from a Web browser by entering the following

URL in your Web browser: http://<sametime server name>/doc/stinstall.nsf

Note that when the stinstall.nsf file is opened from a Web browser, the Search function of the install guide will not work until you use a Lotus Notes client to create a full-text index of the stinstall.nsf file.

The Search function will work correctly if you open the stinstall.nsf file in a Lotus Notes client. A PDF version of the installation guide is also available on the product CD.

Sametime server

Ping the Sametime server before installation (verify DNS setup)

Before installing the Sametime server, you must ensure the Sametime server is appropriately registered in DNS. From a client machine, ping the Sametime server using both the short host name and the fully-qualified DNS name. You must get a response from the Sametime server machine using either the hostname or the fully-qualified DNS name.

For example, if the hostname is "burrito" and the full DNS name is "burrito.databeam.com," typing the following commands should get the same results: ping burrito ping burrito.databeam.com

Pinging burrito.databeam.com [8.88.888.88] with 32 bytes of data:

Reply from 8.88.888.88: bytes=32 time=30ms TTL=122

Reply from 8.88.888.88: bytes=32 time=20ms TTL=122

Reply from 8.88.888.88: bytes=32 time=30ms TTL=122

Reply from 8.88.888.88: bytes=32 time=30ms TTL=122

Sametime server

Reinstalling Sametime 7.0 over an existing 7.0 installation

You can reinstall Sametime 7.0 over an existing Sametime 7.0 server without uninstalling the existing Sametime 7.0 server. You might want to reinstall Sametime 7.0 over an existing Sametime 7.0 server to correct the following problems:

Restore Sametime files that have been mistakenly moved or deleted.

Reset all Sametime configuration settings to their default values if the server has been configured incorrectly.

If you are reinstalling Sametime 7.0 over an existing Sametime 7.0 server, and you must specify an LDAP directory as the directory type used for the Sametime server, you should delete the LDAP configuration changes that were implemented by the original installation before beginning the reinstallation.

The procedures you perform to delete the LDAP configuration changes depend on whether the Domino server was or was not configured for LDAP access at the time the original Sametime installation occurred.

46

IBM Lotus Sametime 7 Release Notes

Chapter 3 - Known limitations, problems, and workarounds

LDAP configuraton changes performed by the Sametime installation

If you select the LDAP directory type during a Sametime installation, the Sametime installation automatically configures the Domino server to access the LDAP directory you specify during the installation. The LDAP configurations performed by the Sametime server installation depend on whether the Domino server on which

Sametime is installed is or is not configured to support LDAP access.

If the Domino server on which you are installing Sametime is not configured to support LDAP access, and you select the LDAP directory type, the Sametime installation automatically performs the following configurations:

A Directory Assistance database (da.nsf) is created by the Sametime installation on the Domino server on which

Sametime resides.

A Directory Assistance document is created in this da.nsf database. This document is configured by default to enable the Sametime server to connect to the LDAP directory on the LDAP server specified during the Sametime installation.

The filename da.nsf is written in the "Directory Assistance database name" field in the Server document of the

Domino server on which Sametime is installed. This entry must exist in the Server document to enable the

Domino server to use directory assistance.

If the Domino server on which you are installing Sametime is configured to support LDAP access, and you select the

LDAP directory type, the Sametime installation automatically creates a document in the existing Directory Assistance database that points to the LDAP directory on the LDAP server specified during the Sametime installation.

Deleting the LDAP configuration changes before reinstalling Sametime

If you are reinstalling Sametime 7.0 over an existing Sametime 7.0 installation, and you are required to select the

LDAP directory during the reinstallation, you must delete the LDAP configuration changes performed by the original

Sametime installation before beginning the reinstallation. The deletions required depend on whether the Domino server on which Sametime was installed was or was not configured for LDAP access at the time Sametime was installed. To delete the LDAP configuration changes, do the following:

If the Domino server was not configured for LDAP access when the original Sametime installation occurred:

Delete the da.nsf database created by the Sametime installation.

Delete the "da.nsf" entry created by the Sametime installation in the "Directory Assistance database name" field of the Server document.

If the Domino server was configured for LDAP access when Sametime was installed:

Delete the Directory Assistance document in the Directory Assistance database on the Domino server. This

Directory Assistance document, which was created by the Sametime installation, points to the LDAP server you specified during the Sametime installation.

Sametime server

Sametime Connect cannot log in to Sametime 2.x or 3.x server

If you have installed Critical Fix 1 (CF1) on a Sametime 2.x or 3.x server, a Sametime Connect 7.0 client cannot log in to that Sametime server.

There are two workarounds for this problem:

Workaround 1

Replace the original StSecurity.exe file on the Sametime 2.x or 3.x server with the StSecurity.exe file that is included with the Sametime 7.0 server.

In a multiserver configuration, note the following:

You must replace the StSecurity.exe file on every Sametime server on which CF1 has been applied.

Set the security level of all the servers where CF1 has been applied to the version of the oldest Sametime server.

You must set the security level of the VP_SECURITY_LEVEL parameter of the Sametime.ini file to 20, 25, 30, or

31.

47

IBM Lotus Sametime 7 Release Notes Chapter 3 - Known limitations, problems, and workarounds

You can find more information about the security level parameter in technote 1145812. The security level parameter is also discussed in the "Prohibiting logins from insecure clients to the server" section of the "Configuring the

Community Services" chapter of the Sametime 7.0 Administrator's Guide.

Workaround 2

Disable CF1 on all servers on which it has been applied.

Sametime server

Sametime installation fails on partitioned Domino server

This issue applies to Domino and Sametime servers that operate on the Windows platform. If the user selects the multiple partition option during the Domino server installation, the Sametime installation will fail when you attempt to install Sametime on that Domino server. The Sametime server setup program will return a language error and an error stating the server name cannot be found.

Sametime server

Sametime server language does not match Domino server error

Sametime 7.0 requires the Domino Directory design available with the Domino 7.0 server release. If you are upgrading from a previous Sametime release to Sametime 7.0, make sure that the Domino server on which you are installing

Sametime 7.0 is upgraded to Domino version 7.0.

When you upgrade the Domino server version to 7.0, you must also be sure to upgrade the design of the Domino

Directory to version 7.0. It may be necessary to manually upgrade the directory design to 7.0. Note that if you customized the previous version of the Domino directory, all customizations are lost when you replace the directory design.

If you install Sametime on a Domino server that uses a directory version earlier than 7.0, you may see an error during the installation indicating that "the language of the Sametime server does not match the language of the Domino server."

Sametime server

Server name cannot include invalid XML characters

Sametime must be installed on a Domino server. When installing the Domino server that will host the Sametime server, you must provide a hierarchical name for the Domino server. The Domino server name cannot include any of the following characters in either the server name component or the organization component:

"

;

>

<

&

'

Examples of invalid server names are included below:

SametimeServer/B&O

SametimeServer/WorldO'Fun

Sametime>Server/Acme

Sametime;Server1/Acme

These naming restrictions exist because of limitations associated with XML processing and escaped characters. The characters listed above should not be present in the name of any Domino/Sametime server.

If a Sametime server name includes one of the characters above, the server will not function correctly.

48

IBM Lotus Sametime 7 Release Notes

Chapter 3 - Known limitations, problems, and workarounds

Sametime server

servlets.properties file renamed during Sametime installation

Sametime includes a version of the servlets.properties file used by the Domino servlets engine.

If you install Sametime on the same machine as another Lotus product that includes the Domino servlets engine (such as the Lotus Discovery Server), the Sametime installation will install its own servlets.properties file and change the name of any existing servlets.properties file to servlets.properties.old.

If you modified the original servlets.properties file (now named servlets.properties.old), you must make those same modifications in the new servlets.properties file added by the Sametime installation.

Sametime server

Set the server home page following installation or upgrade

After installing the Sametime server, you should set the Sametime server home page (STCENTER.NSF) as the home page of the Domino server on which Sametime is installed.

Note Setting the Sametime server home page as the home page of the Domino server enables a user to enter the DNS name (http://servername) of the server in the Web browser URL locator to access the Sametime features. If you do not perform this procedure, users must enter http://servername/STCenter.nsf in the Web browser URL locator to access the Sametime server home page.

To set the server home page, open the Server document for the Domino server on which Sametime is installed. In the

Server document, select the Internet Protocols - HTTP tab. Enter STCENTER.NSF in the "Home URL" field of the

"Mapping" section of the Server document. Save the Server document and restart the Domino server for the change to take effect.

Sametime server

Uninstall does not remove staddin parameter from Notes.ini

Uninstalling the Sametime server does not remove the staddin parameter from the Notes.ini file of the Domino server.

You can manually delete staddin from the Notes.ini file after uninstalling Sametime.

Accessibility/Section 508 issues

Sametime Administration Tool

Can't tab between admin client and Domino Directory access

Once users access the Domino Directory - Access control from the Sametime administration client, they cannot use the keyboard to move focus back to the administration client. Users must close the browser window, then restart the browser and log on to the administration client again.

Sametime Connect client

Missing hotkeys in Sametime Connect for the desktop client

In Sametime Connect for the desktop, the following hotkeys, or mnemonics, are missing. Users can still tab to each of these controls.

The Alert Me When button in the Specific Alerts section of the Alerts tab. Users access the Alerts tab by choosing

Options - Preferences.

The OK and/or Cancel buttons in the following situations:

The My Available Tools dialog box that appears after users log on to Sametime Connect for the desktop.

The Edit Nickname dialog box.

The Rename Personal Group dialog box.

The Add to/Replace List dialog box.

The Send Announcement dialog box.

49

IBM Lotus Sametime 7 Release Notes

Chapter 3 - Known limitations, problems, and workarounds

Sametime Connect client

Tabbing problem in Add to Privacy List dialog box

In Sametime Connect for the desktop, if a user enters a name with multiple matches in the Directory while adding a name to the Who Can See If I Am Online List, a list of these matches appears in the Add to Privacy List dialog box.

When users tab to this list, there is no visible indication that the list has focus. Even though the focus is not visible at first, users can use the arrow keys to move through the names in the list once the list has focus. Once users use the arrow keys to move trhough the names, the focus will become visible.

Sametime Administration Tool

Unable to tab between admin tool and admin Help

Once users opens the administrator's Help from the Sametime administration tool, they are unable to use the keyboard to move the focus back to the administration tool. Users can press ALT+F4 to close the browser window, then restart the browser and log on to the administration client again. Users can also download the PDF version of the administrator's guide from the Lotus Developer Domain Web site at http://www.ibm.com/lotus/ldd .

Sametime Connect client issues

Sametime Connect client

Cannot add meeting participant to Sametime Connect List

Users may be unable to add a user who appears in the Participant List of the Sametime Meeting Room client to the

Connect List of the Sametime Connect for browsers client.

Users add a meeting participant to the Connect List of the Sametime Connect client by selecting the Meeting - People

- Add to Connect List menu item in the Sametime Meeting Room. This menu option may not function properly in the

Sametime Connect for browsers client and users may be unable to add meeting participants to the Connect List using this feature.

Users can be added to the Connect List of the Sametime Connect for browsers client using the Add button or the

People - Add menu item of the client.

Sametime Connect client

Contact list group names hard to read at 256 colors

If you use a Sametime Connect client on a computer that has a 256 color display setting in the Windows Control

Panel, group names may display in different colors in the Sametime Connect contact list. The color in which group names display is affected by other applications that are open in the background.

To avoid this problem, specify a color display setting that is higher than 256 colors in the Windows Control Panel.

Sametime Connect client

Disable Connect auto login with multiple user Notes client

A problem can occur if the automatic login feature of Sametime Connect is enabled and a Lotus Notes client is installed in a "Multiple User" configuration. With this configuration, it is possible for one user to click on a Sametime

Connect bookmark icon in the Lotus Notes client and log in to Sametime Connect as a different user.

If Lotus Notes can be installed in a Multiple User configuration, the automatic login feature of Sametime Connect should be disabled by the administrator to prevent this problem from occurring.

The steps below illustrate a scenario in which a user can be logged on to Sametime Connect as another user.

1. A user logs into the Windows operating system as User 1.

2. User 1 installs the Sametime Connect client. During this installation, the user specifies the Sametime server to which the Sametime Connect client will connect (for example, sametimeserver1.acme.com).

50

IBM Lotus Sametime 7 Release Notes

Chapter 3 - Known limitations, problems, and workarounds

3. User 1 logs into Sametime Connect using the User Name and Internet password specified for the user in the

Domino Directory on the Sametime server.

4. User 1 installs the Lotus Notes client using the Notes "Multiple User" option.

5. User 1 starts Lotus Notes for the first time and runs the Notes setup program.

Note A Sametime Connect icon appears in the Bookmark list of Lotus Notes.

6. User 1 clicks on the Sametime Connect icon in the Bookmark list, enters the User Name and Internet password from the Person document, and logs on to the Sametime Connect client.

7. In the Sametime Connect client Options-Logon Information menu item, User 1 selects "Log on automatically" to enable the automatic log on features of Sametime Connect.

8. A different user logs into the Windows operating system as User 2.

9. User 2 installs the Lotus Notes client using the Notes "Multiple User" option. Following the installation, User 2 runs the Lotus Notes setup program.

10. The Sametime Connect icon appears in the Bookmark list of the Lotus Notes client launched by User 2. The

Bookmark may appear even though User 2 has not installed Sametime Connect.

11. When User 2 clicks on the Sametime Connect icon in the Bookmark list in Lotus Notes, User 2 is automatically logged into Sametime Connect as User 1.

To prevent this problem, the administrator must disable the automatic log on feature on the Sametime server to which the Sametime Connect clients connect. The administrator must disable the automatic log on feature for both

"Sametime Connect for browsers" and "Sametime Connect for the desktop."

To disable the automatic logon feature for "Sametime Connect for browsers:"

1. Open the Sametime Administration Tool.

2. Choose Configuration-Community Services.

3. Clear the check mark from the "Allow Connect users to save their user name, password, and proxy information" setting.

To disable the automatic logon feature for "Sametime Connect for the desktop:"

To disable the automatic logon feature for "Sametime Connect for the desktop," you must run the Sametime Client

Packager application on the Sametime server. The Sametime Client Packager application includes an option that enables you to disable the automatic logon feature for all "Sametime Connect for the desktop" clients that are downloaded from the Sametime server.

Sametime Connect client

Do not run both versions of Sametime Connect on the same machine

Sametime 7.0 includes two versions of the Sametime Connect client. These versions are "Sametime Connect for the desktop" and "Sametime Connect for browsers." ("Sametime Connect for the desktop" is written in the C++ language and "Sametime Connect for browsers" in written in the Java language.)

It is best if users do not have both of these clients open simultaneously on the same machine. If both of these clients are open on the same machine, users may experience problems when adding names or groups to the contact list in

Sametime Connect for browsers.

51

IBM Lotus Sametime 7 Release Notes Chapter 3 - Known limitations, problems, and workarounds

Sametime Connect client

Do not use "Short name" to log into Sametime Connect

IBM Lotus software recommends that users log into Sametime Connect using an entry in the "User name" field of a user's Person document.

Users should not log in to Sametime Connect using an entry in the "Short name/User ID" field of the user's Person document. Users attempting to log in using an entry in the "Short name/User ID" field might see an "Unable to access

Sametime due to incorrect logon" error. This error appears consistently for short names that are three characters or less.

Sametime Connect client

Host field cannot contain capital letter when using HTTPS proxy

A user can configure the Sametime Connect for browsers client to connect to the Sametime server through an HTTPS proxy by selecting the Use Proxy -> Use HTTPS proxy option in the Options -> Preferences -> Sametime Connectivity tab of the client.

When Sametime Connect for browsers is configured to connect via an HTTPS proxy, the Host field in the Options ->

Preferences -> Sametime Connectivity tab must specify the Sametime server name using all lower case letters. If the

Host field contains a capital letter, the Sametime Connect for browsers client cannot connect to the Sametime server through the HTTPS proxy.

Sametime Connect client

Invitation indicates no available tools if Connect is closed

When you invite a user to an instant meeting, the invitation dialog box displays the available tools (microphone, speaker, camera) that the invited user has installed on his or her computer. A check mark beneath a tool indicates the tool is available on the user's machine and an X indicates the tool is unavailable on the user's machine.

If you invite a user to an instant meeting, and the invited user is not currently running the Sametime Connect client, question marks appear for all of the available tools. These question marks might appear even when the user's machine has the tools installed. The invited user can still use the tools in the instant meeting even though the question marks in the invitation dialog indicate that the tools are not available.

Question marks can also indicate that the user has not entered information about the audio/video tools or that the user is using a version of Sametime Connect that does not support audio and video. A user without audio and video tools can still participate in a Sametime meeting.

Sametime Connect client

Locked DLLs require machine reboot to complete Connect install

The Sametime Connect client installation replaces some operating system DLL files and then registers Sametime OCX files. The Sametime OCX files can only be registered successfully if the DLL files are replaced by the Sametime

Connect client installation. If the DLL files are locked by the operating system, you must reboot the system before the

Sametime OCX files can be registered and the installation can complete.

The end result of this problem is that the user may need to install Sametime Connect twice to successfully install the

Sametime Connect client.

If this problem occurs, the error message "Installation has not completed due to locked system DLLs - Please reboot and install again" displays during the first installation attempt. The user can install the Sametime Connect client again and the installation should conclude successfully after the second installation.

Explanation

When the DLL files are locked by the operating system, the system must be rebooted so that the DLLs can be replaced by the installation. The Sametime OCX files cannot be registered until the DLLs are replaced. After the DLLs are replaced, and the system rebooted, you can rerun the installation. Rerunning the installation enables the Sametime

OCX files to be registered because the new DLLs are now present on the system.

52

IBM Lotus Sametime 7 Release Notes

Chapter 3 - Known limitations, problems, and workarounds

Sametime Connect client

Logged out of Sametime (reason 0x80000200)

The Sametime 7.0 server includes a security feature that can prevent Sametime Connect clients from earlier

Sametime releases from connecting to a Sametime 7.0 server. For detailed information about this feature, review the

"Prohibiting logins from insecure clients to the server" section in the "Configuring the Community Services" chapter of the IBM Lotus Sametime 7.0 Administrator's Guide.

The administrator configures this security feature using the following settings in the Sametime.ini file in the

C:\Lotus\Domino directory on the Sametime server:

VP_SECURITY_LEVEL=30

VP_SECURITY_ALLOW_USER=0

The configuration shown above ensures that only Sametime Connect clients from Sametime releases 3.0 and higher can connect to the Sametime server. When the Sametime server is configured in this way, and a user attempts to connect to the Sametime server using a Sametime Connect 2.5 client, the following error appears to the Sametime

2.5 Connect user:

"Logged out of Sametime (reason 0x80000200)"

This error message does not appropriately describe the problem and should read as follows:

"Application version does not match the server version. Please upgrade"

To avoid the error message, the user should upgrade to a Sametime Connect 3.0 (or higher) client.

Sametime Connect client

Macintosh Sametime Connect for the desktop client issues

This release note lists general issues with the Macintosh Sametime Connect for the desktop client:

This issue occurs when the "Display a message box when I successfully add a person or group" option is checked in the Macintosh Sametime Connect client. If a user opens the Add Person or Group window, clicks the Directory button, and then attempts to add multiple users or groups from the directory to the Contact list, the Sametime

Connect client hangs.

Using the vertical scroll bars to scroll the text that appears in the transcript pane of the Macintosh Sametime

Connect client may cause the text to disappear from the transcript pane. This problem occurs when the user either receives or sends a lengthy instant message that fills up the entire transcript pane. To workaround this problem, do not use the vertical scroll bars to scroll the text. Instead, use the mouse to select (highlight) the text in the transcript pane and then drag the mouse up or down to scroll the text. You can also use the up or down arrow keys on the keyboard to scroll the text.

This issue may occur when the Macintosh Sametime Connect for the desktop client is deployed into the same community as the Windows version of the Sametime Connect for the desktop client or the Sametime Connect for the browsers client. In this environment, a problem may occur because the Macintosh Sametime Connect for the desktop client does not support the instant meeting functionality supported by the other versions of Sametime

Connect.

The Windows version of the Sametime Connect client and the Sametime Connect for the browser client both provide the functionality to invite users to instant meetings. Users of these clients can see the users of Macintosh

Sametime Connect for the desktop as online users in their Contact lists but have no way of distinguishing

Macintosh Sametime Connect for the desktop users from users of other versions of the Sametime Connect client.

In this scenario, it is possible for a user of the Windows version of the Sametime Connect client or the Sametime

Connect for browsers client to click on a Macintosh Sametime Connect users name to start a chat, and then after chatting for a while, invite the Macintosh user to an instant meeting or an n-way chat. If this occurs, the chat session is terminated for both the Macintosh and Windows Sametime Connect clients. An instant meeting, or n-way chat window, starts for the user of the Windows version of Sametime Connect but not for the Macintosh user. The Windows user receives no indication that the Macintosh user cannot join the meeting or n-way chat.

In the Announcement dialog of the Macintosh Sametime Connect for the desktop client, the following Tip text appears: "Type Ctrl + Enter to start a new line." This text should read "Type Ctrl + Return to start a new line." The keyboard key is labeled "Return" on the Mac but "Enter on the PC.

53

IBM Lotus Sametime 7 Release Notes

Chapter 3 - Known limitations, problems, and workarounds

The following issues occur in the "Alert me when selected person becomes available" dialog. The word "Notify" appears twice in this dialog box. The letter "y" in this word may be truncated in the user interface. The "Cancel" button that appears at the bottom of this dialog may also be truncated.

In the Options > Preferences > Alerts settings of the Macintosh Sametime Connect for the desktop client, users can select a "Bring the message window to the front" option. This option may not always work correctly. When user receives an instant message, the instant message window may not appear at the front of other applications, even though the user has selected this option.

This issue applies to the Chinese, Simplified Chinese, Japanese, and Korean (CJKT) versions of the Macintosh

Sametime Connect for the desktop client. When you are using IME, and typing text into the Send Text pane, you must press the "Shift+Return" keys to commit the text in the Send Text pane to IME. If you press only the Return key, the text is sent but is not committed to IME.

Sametime Connect client

Meeting cannot be started due to error 0x8000024

When starting an instant meeting from Sametime Connect or responding to an invitation to attend an instant meeting, a user may see the error message "The meeting cannot be started due to the following error 0x8000024. Please contact your system administrator."

Either the user starting the meeting or the user attending the meeting is disconnected from the Sametime server. To fix the problem, the disconnected user should restart the Sametime Connect client.

Sametime Connect client

No error for empty proxy fields in Sametime Connect for browsers

If a user does not correctly configure the proxy settings in the Sametime Connect for browsers Sametime Connectivity settings, the user receives no notification that a problem exists.

Specifically, when a user selects the "Use proxy" option for the "Connection type" in the Sametime Connect client

Options - Preferences - Sametime Connectivity tab, and leaves the the Proxy server "Host" and "Port" fields empty, no error message appears upon closing the dialog box. The Sametime Connect client attempts a direct connection

(Sametime protocol over TCP/IP) to the Sametime server. If the direct connection is successful, the user receives no notification that the connection did not occur through a proxy server.

Sametime Connect client

Problem with chat text in Sametime Connect for browsers

This problem occurs with Sametime servers that operate on the AIX or Solaris operating system.

When using "Sametime Connect for browsers," a user might not see his or her own chat text in the "Type your text" area of the chat window. However, the text will still be sent correctly.

This problem, which is common in Java applications, arises when the foreground color is not specified and the background is set to white. To correct this problem, modify the source code to include specifications for foreground colors.

Sametime Connect client, Sametime server

Same name appears multiple times in a Contact list

If the Sametime server is configured to connect to the LDAP Active Directory, a problem may occur where the same user's name appears more than once in the Contact list of Sametime clients.

For more information about this issue, see the release note titled "Problems with client Contact lists and LDAP Active

Directory" in the Troubleshooting - LDAP issues section of these release notes.

54

IBM Lotus Sametime 7 Release Notes Chapter 3 - Known limitations, problems, and workarounds

Sametime Connect client

Sametime Connect display problems at 256 colors

If the display settings on a user's machine are set to 256 colors, some elements of the Sametime Connect user interface may not display properly. For example, Group names in the Connect buddy list may be obscured by black highlighting and difficult to read. 16-bit color settings are recommended.

Sametime Connect client

Sametime Connect startup screen is upside down

When a user starts the Sametime Connect client, the startup bitmap image may appear upside down for users that have certain video cards. This is a rare problem limited to a few video cards.

Users can prevent this problem by adjusting the Video (or Display) settings available in the Windows Control Panel. In the Display settings, the users should set the "Hardware Acceleration" setting to none.

Sametime Connect client

User with long name is unable to log in to Sametime Connect

Users with extremely long names in the "User Name" field of the Person document may not be able to log into

Sametime Connect for the desktop. If a user's log in name is too long, the following error message displays: "Unable to access Sametime due to incorrect login. Please try again or contact your system administrator."

To work around this issue, you can enter a shortened version of the user's name in either the "User Name" field or the

"Short name/UserID" field of the user's Person document. The user can enter this shortened name when logging into

Sametime Connect.

Meeting Room client issues

Sametime Meeting Room client

Black boxes appear when sharing some dialog boxes

Avoid sharing applications within an application. In some applications, users can select a menu item that launches a separate application. Here are two common examples of opening a separate application from within Microsoft Word:

A user selects File-Page Setup to launch the Page Setup application.

A user selects Insert-Picture-Clip Art to launch the Clip Art application.

In each of these cases, the end user may think of Page Setup and Clip Art as dialog boxes within Microsoft Word, but they are actually separate applications. If the user opens the Page Setup or Clip Art application, these applications will appear as black boxes to other meeting attendees.

This problem occurs because the screen sharing tool hides the windows of other applications when the Share a

Program option is used to share one specific application.

The workaround for this issue is to use the "Share My Entire Screen" or "Share Part of My Screen with a Frame" option instead of the "Share a Program" option when sharing applications.

55

IBM Lotus Sametime 7 Release Notes

Chapter 3 - Known limitations, problems, and workarounds

Sametime Meeting Room client

Cannot delete an annotated whiteboard file

The following scenario illustrates this problem:

1. A user attaches a whiteboard file to the New Meeting form so that the file can be displayed during the meeting.

The file name is presentation.rtf.

2. The user displays the file during the meeting and uses the whiteboard drawing tool to annotate the whiteboard.

3. The user saves the whiteboard file.

After the user saves the whiteboard, the saved whiteboard file names are Presentation_Annotated.rtf and

Presentation_Sametime.swb. The user can delete the original files attached to the whiteboard but cannot delete the

Presentation_Annotated.rtf and Presentation_Sametime.swb files that result from the whiteboard save.

Sametime Meeting Room client, Sametime server

Computer entering standby mode drops audio

If a user is presenting during a Sametime meeting, and that user's computer enters the standby mode during the presentation, the audio may no longer function.

If a presenter is only transmitting audio and video, or sharing a screen or whiteboard presentation with no keyboard or mouse activity, the presenter's computer may enter standby mode. When a computer enters standby mode, network activity stops and the presenter is disconnected from the meeting.

Similarly, if there is no keyboard or mouse activity, and the presenter is sharing the screen, the screen saver may activate on the presenter's computer. Other participants in the meeting will see the presenter's screen saver.

Users may want to disable the power saver and screen saver features if their meeting presentations will require little mouse or keyboard activity.

Sametime Meeting Room client

Empty browser frame or browser crash during client install

Some problems may occur when installing the Sametime Meeting Room client if the user is running Norton AntiVirus

2000 and is using the Auto Protect feature or the Live Update feature of Norton AntiVirus 2000. These problems only occur when a user is running both the Internet Explorer browser and the Norton AntiVirus program.

Note: These problems do not occur with Norton AntiVirus 2001 or later.

If a user has the Auto Protect feature of Norton AntiVirus 2000 enabled, Internet Explorer may crash (in naveng32.dll) when the user attends a meeting and agrees to install the Sametime Meeting Room client. This problem occurs with versions of Windows that are earlier than Win2000 Professional. The user can disable the Auto Protect feature before agreeing to install the Sametime Meeting Room client.

Windows 2000 Professional

The following problem can occur when the user allows the Live Update feature to update Norton AntiVirus 2000 on the

Windows 2000 Professional platform. (The user can prevent these problems by disabling the Live Update feature of

Norton AntiVirus 2000.)

After joining a meeting the user receives two dialogs where the user agrees to download the Sametime Meeting Room client and responds to a security warning. After responding to these dialogs, an empty browser frame may remain displayed on the screen and the CPU reports 0% usage. The machine remains in this state indefinitely.

If this occurs, the user should close both browser windows, restart the browser, and join the meeting again. The user will receive the client download and security warning dialogs again. After responding "yes" at the security warning dialog, the user will join the meeting successfully.

56

IBM Lotus Sametime 7 Release Notes

Chapter 3 - Known limitations, problems, and workarounds

Sametime server

Ensuring that Whiteboard save works on UNIX

When a Sametime server runs in the background on either the AIX or Solaris platforms, users cannot save Whiteboard files unless you install the X Virtual Frame Buffer. Installing the X Virtual Frame Buffer is required to run a Sametime server in the background.

Instructions for installing the X Virtual Frame Buffer on both the AIX and Solaris platforms are provided below.

AIX PLATFORM

Use these instructions to install the X Virtual Frame Buffer and configure the Sametime server to run in the background on AIX.

Installing and run the X Virtual Frame Buffer on AIX

Use these instructions to install the X Virtual Frame Buffer on AIX.

1. Install the XVFB packages from your OS cds:

- OpenGL.OpenGL_X.dev.vfb.05.01.0000.0000 OR EQUIVALENT

X11.vfb.05.01.0000.0000 OR EQUIVALENT

2. Login in from a terminal shell as root and run the following:

/usr/bin/X11/X -vfb -x GLX -x abx -x dbe -force :1 &

3. You can verify that the VFB is running properly by typing:

/usr/lpp/X11/Xamples/bin/xprop -display machinename:1 -root | grep VFB

You should see the following: XVFB_SCREEN(STRING) = "TRUE"

Note: You can assign any number except 0 in place of the number "1" in the above example. This is the display number you wish to have associated with this instance of the XVFB. The machinename is the name of your AIX machine.

Configure the Sametime server to run in the background on AIX

Once you have the X Virtual Frame Buffer running, use the instructions below to configure the Sametime server to run in the background on AIX.

1. Login as notes.

2. Modify the notes user .profile or equivalent to add the ${BINDIR} from ststart to the LD_LIBRARY_PATH and to the PATH environment variables.

3. Logout and log back in.

4. Set the DISPLAY variable to the display number you used above, eg:

export DISPLAY=machinename:1

5. From the data directory, run the command: "nohup /opt/lotus/bin/server < /dev/null > /dev/null 2>&1 &" (

This assumes /opt/lotus/bin is the $LOTUSDIR in ststart).

6. You may exit the telnet session or the xwindows sesssion.

57

IBM Lotus Sametime 7 Release Notes

Chapter 3 - Known limitations, problems, and workarounds

SOLARIS PLATFORM

Use these instructions to install the X Virtual Frame Buffer and configure the Sametime server to run in the background on Solaris.

Installing and run the X Virtual Frame Buffer on Solaris

Use these instructions to install the X Virtual Frame Buffer on Solaris.

Xvfb is already installed on Solaris 9 in /usr/openwin/bin. Solaris 8 users will need to obtain a separate implementation of Xvfb.

1. Login in from a terminal shell as root and run the following:

/usr/openwin/bin/Xvfb :1 -screen 0 1280x1024x8 &

You might get a message saying "No such file or directory", but this is normal.

2. You can verify that the VFB is running by typing:

ps -ef | grep vfb

You should see the Xvfb process running.

Note: You can assign any number except 0 in place of the number "1" in the above example. This is the display number you wish to have associated with this instance of the XVFB.

Configure the Sametime server to run in the background on Solaris

Once you have the X Virtual Frame Buffer running, use the instructions below to configure the Sametime server to run in the background on Solaris.

1. Login as notes.

2. Modify the notes user .profile or equivalent to add the ${BINDIR} from ststart to the LD_LIBRARY_PATH and to the PATH environment variables.

3. Logout and log back in.

4. Set the DISPLAY variable to the display number you used above, eg:

DISPLAY=machinename:1 export DISPLAY

5. From the data directory, run the command: "nohup /opt/lotus/bin/server < /dev/null > /dev/null 2>&1 &" (

This assumes /opt/lotus/bin is the $LOTUSDIR in ststart).

6. You may exit the telnet session or the xwindows sesssion.

Sametime Meeting Room client

Excel files and Russian whiteboard issue

With Russian versions of the Sametime Meeting Room client whiteboard tool, the contents of Microsoft Excel files may not display correctly.

58

IBM Lotus Sametime 7 Release Notes Chapter 3 - Known limitations, problems, and workarounds

Sametime server

Files with embedded objects distort in the whiteboard

Microsoft Word and Lotus Word Pro files that contain embedded objects may not display correctly after being converted to Whiteboard files. Generally, this behavior occurs when there are no printer drivers installed on the

Sametime server. To prevent this problem, install a printer driver on the Sametime server. (Any printer driver can be installed; it is not necessary to connect the server machine to an actual printer).

Some of the problems that may occur if there is no printer driver installed include:

Embedded images (such as GIF files) may not display or display as gray boxes

Pages appear compressed or are scaled incorrectly

Pages containing embedded objects do not display

Images and headings are displaced on the pages

Sametime Meeting Room client

Firewall may block access to whiteboard file

When a user attaches a file to the whiteboard during an active meeting, the Sametime server generates a URL to this file that includes two dots in the string, as shown below:

/../

Many firewalls are configured to block URLs that include the character string shown above. URLs that include these strings are sometimes used for malicious purposes. If a client operates behind a firewall configured to block these

URLs, the client cannot access the whiteboard file.

Sametime Meeting Room client

HTML files do not display correctly in the whiteboard

The whiteboard will display an HTML file as a text file if the <HTML> tag is removed from the beginning of the HTML file before the file is attached to a meeting for conversion to the .FST file format supported by the whiteboard. If the

<HTML> tag is not removed, the whiteboard attempts to display the HTML file as a Web browser would. Complex html pages containing multiple frames and images may not display correctly in the whiteboard when the <HTML> tag is left in the file.

If the <HTML> tag is removed from the beginning of the file, the html file displays the text-based source code of the html file in the whiteboard. In some cases, the first page of the html file will display as the last page when the file is converted into a whiteboard presentation.

Sametime Connect client, Sametime Meeting Room client

Initial chat transcripts do not appear in instant meetings

Users can begin a chat session and then start an instant meeting from the chat session by adding a collaborative activity (such as screen sharing, the whiteboard, or audio/video) to the chat. Adding a collaborative activity to a chat session launches the Sametime Meeting Room client on each user's computer and starts the instant meeting.

If two (or more) users begin a chat session and then start an instant meeting from the chat, a chat transcript of the chat activity that preceded the meeting does not appear in the chat area of the Sametime Meeting Room client.

Sametime Meeting Room client, Sametime server

Meeting Room client hangs when loading whiteboard/other applet

If a user attempts to attend a meeting, and the Sametime Meeting Room client hangs while loading the whiteboard or other Java component, the client may be unable to resolve the server name because of a problem in the Server document for the Sametime server. Specifically, the short name of the server may be listed in the Ports section of the

Server document instead of the fully-qualified DNS name.

59

IBM Lotus Sametime 7 Release Notes

Chapter 3 - Known limitations, problems, and workarounds

To verify that the fully-qualified DNS name is listed in the "Ports" section of the Server document, follow the instructions below:

1. Use a Lotus Notes client or Domino Administrator client to open the Domino Directory (names.nsf) that contains the Server document for the Sametime server.

2. Open the Server document for the Sametime server.

3. Select the "Ports" tab.

4. Select the "Notes Network Ports" tab.

5. Check the "Net Address" for the TCPIP port. The "Net Address" column must specify the fully-qualified name of the

Sametime server (e.g., sametimeserver.acme.com).

6. If the short name of the server (e.g. sametimeserver) is listed in the "Net Address" column, replace it with the fully-qualified DNS name of the server.

Sametime Meeting Room client

Menus do not pop up when accessed via mnemonics

When users press mnemonic keys (shortcut keys) to activate menu options in the Sametime Meeting Room, the menus do not pop up. The menus are activated, but the activation is not visible to users. For example, if a user presses t, then u, then p to activate the Tools - Audio - Increase Speaker Volume menu option, the Tools menu and the Audio pull-right menu do not appear on the screen.

Mnemonic keys do work correctly, even though the menu activation is not visible.

Sametime server

Only one spreadsheet in a file converts to whiteboard format

If you convert a Microsoft Excel or Lotus 123 file for display on the whiteboard by attaching it to the meeting during the meeting creation process, and the Excel or 123 file contains multiple spreadsheets, only the first spreadsheet of the Excel or 123 file will display in the whiteboard. The remaining spreadsheets in the file will not convert to the whiteboard format.

If you want to convert a Microsoft Excel or Lotus 123 file that includes multiple spreadsheets so that all of the spreadsheets in the file can be displayed in the whiteboard, use the Sametime Print Capture utility to convert the file to the format required by the whiteboard.

Note: When using the Sametime Print Capture utility to convert a Microsoft Excel file containing multiple spreadsheets to the file to the format required by the whiteboard, the user is prompted to enter a file name for the file in a File/Save dialog box. After naming the file, the user will see repeated prompts to save the file (as each spreadsheet is being converted). At these repeated prompts the user has the option to either "replace" the file or

"append" to the file. The user should choose the "append" option at these prompts. Choosing the append option when prompted for repeated saves ensures that the multiple Excel spreadsheets can be displayed from a single whiteboard file.

Sametime Meeting Room client

Remaining meeting time is not correct for extended meetings

The Sametime Administration Tool includes a Meeting Services configuration setting titled "Automatically extend meetings beyond the scheduled end time." This setting ensures a meeting is automatically extended for a 15-minute time interval if users are still attending the meeting at the scheduled end time for the meeting.

Note: The time interval for which a meeting is extended is configurable by the administrator. The default interval is 15 minutes.

If a meeting is automatically extended, the remaining meeting time does not display correctly in the View-Remaining

Meeting Time menu option of the Meeting Room client.

However, the total duration of a meeting appears in the lower-right corner of the Meeting Room client. When a meeting is extended, a plus (+) sign appears in front of the meeting duration in the lower-right corner of the client.

60

IBM Lotus Sametime 7 Release Notes

Chapter 3 - Known limitations, problems, and workarounds

For example, if a meeting is originally scheduled to last one hour, the duration of the meeting displays as 00:01:00 after the meeting has lasted one hour. At one hour and one minute, the meeting duration displays as +00:01:01.

The plus sign indicates that users will have until +00:01:15 to conclude their business in this meeting. The administrator may want to make meeting moderators aware that the plus sign in the lower right corner of the Meeting

Room client indicates that the meeting is operating in the extended mode and that the meeting will end when the administrator-specified extension interval has elapsed.

Sametime Meeting Room client, Sametime server

Repeated saves when converting multiple spreadsheet Excel file

The following problem has been seen when using versions of Microsoft Excel that are earlier than the Microsoft

Office2000 version.

When using the Sametime Print Capture utility to convert a Microsoft Excel file that includes multiple spreadsheets to the file format required by the whiteboard, the user is prompted to enter a file name for the file in a File/Save dialog box.

After naming the file, the user will see repeated prompts to save the file (as each spreadsheet is being converted). At these repeated prompts the user has the option to either "replace" the saved file or "append" to the saved file. The user should choose the "append" option at these prompts. Choosing the append option when prompted for repeated saves ensures that the multiple Excel spreadsheets can be saved to and displayed from a single whiteboard file.

Sametime Administration Tool, Sametime Meeting Room client

Tools still available in active meetings

The following options in the Configuration - Meeting Services settings of the Sametime Administration tool determine which tools are available to end users:

"Allow people to choose the whiteboard tool in meetings"

"Allow people to choose the screen sharing tool in meetings"

"Allow people to choose the 'Send Web Page' tool in meetings"

"Allow people to choose the Polling tool in meetings"

If the administrator removes the check mark from any of the options listed above, the associated tool will not be available in Sametime meetings. However, any meetings that already included the tool when the administrator removed the checkmark will continue to use the tool. For example, if an end user is attending a meeting that includes the whiteboard, and the administrator removes the check mark from the "Allow people to choose the whiteboard tool in meetings" option, the end user will be able to continue using the whiteboard for the duration of the active meeting.

No new meetings will be able to include the whiteboard.

Sametime Meeting Room client

Whiteboard attachments and invited servers

The following information applies to whiteboard attachments on invited servers:

Users who are attending a meeting on an invited server cannot attach files to the whiteboard during the meeting.

To attach a whiteboard file, the Moderator must be attending the meeting on the server on which the meeting was created.

Users who are attending a meeting on an invited server cannot see saved whiteboard files on the Meeting Details document. All whiteboard attachments are saved on the server on which the meeting was created. Although a user who is attending the meeting from an invited server can save a whiteboard file, he or she will not see the file on the Meeting Details document of that server. The user must go to the Meeting Details document on the server on which the meeting was created to see the file.

Note The server on which the meeting was created is listed in the Locations field of the Meeting Details document on each server that is in the meeting.

61

IBM Lotus Sametime 7 Release Notes

Chapter 3 - Known limitations, problems, and workarounds

Sametime Meeting Room client

Word or Word Pro file with embedded objects whiteboard issue

If a Microsoft Word or Lotus Word Pro file contains embedded objects (such as a GIF file or spreadsheet file), and is attached to a meeting for display in the whiteboard, the file may not display correctly in the whiteboard. The following display problems have been seen with Word and Word Pro files with embedded objects that are converted for display on the whiteboard:

Pages containing an embedded image may not be present in the converted file

A page containing an embedded image may be present but the embedded image is not

Pages may not be scaled correctly

Embedded objects may appear but are out of place or compressed

Tables appear compressed or have other display problems

Web browser issues

Web browsers

Default browser information

When a user attempts to start or attend an instant meeting, the browser specified as the Windows default browser is launched on the user's local computer. You should be aware of the following information about the default browser:

If no browser is set as the default in Windows, users cannot start an instant meeting from Sametime Connect or attend an instant meeting by responding to an invitation.

If Netscape Navigator is set as the Windows default browser when a user installs Sametime Connect, and the user later uninstalls Netscape, the user will be unable to start or attend instant meetings.

When a user installs Netscape Navigator, Netscape automatically becomes the Windows default browser.

If Microsoft Internet Explorer is set as the Windows default browser when a user installs Sametime Connect, and the user later uninstalls Microsoft Internet Explorer, the user will be unable to start or attend instant meetings.

Microsoft Internet Explorer checks to see if it is the default browser each time that it is started. A dialog box that allows the user to select Microsoft Internet Explorer as the default browser appears each time Microsoft Internet

Explorer launches. If the user has disabled this dialog box, do the following to make the dialog box display when the browser launches:

1. From Microsoft Internet Explorer, choose Tools - Internet Options.

2. Click the Programs tab.

3. Select the "Internet Explorer should check to see whether it is the default browser" check box.

4. Restart Microsoft Internet Explorer.

Web browsers

Meeting names with quotations display incorrectly

If a meeting name includes double quotations (") or accent marks, the meeting name may not display correctly in the

Monitoring features of the Sametime Administration Tool.

Microsoft Internet Explorer users must change the default font of the Web browser to enable meeting names with accented characters to display correctly. Suggested default font settings to resolve this problem include MS Gothic or

MS Mincho.

Sametime Meeting Room client

Mnemonics unavailable after closing New Poll window (Mozilla)

The following issue may occur regarding the New Poll Window when a user runs the Meeting Room client in the Mozilla browser. A user clicks the New button to launch a New Poll window, then closes the window, and presses the Enter key to close the confirmation dialog. The user then presses the Alt key to see the mnemonics for the New Poll window, but the mnemonics do not display.

The only workaround that will enable the mnemonics to display is to press the Tab key several times. Pressing the Tab key several times returns the focus to the Meeting Room client and enables the mnemonics to display.

62

IBM Lotus Sametime 7 Release Notes

Chapter 3 - Known limitations, problems, and workarounds

Sametime Administration Tool

Problem with "Administer the Server" link

When using Microsoft Internet Explorer, the "Administer the server" link might not take users directly to the Sametime

Administration Tool. Instead, the link might return users to the Sametime Welcome page. If this happens, click

"Administer the server" again.

Sametime Broadcast client, Sametime Meeting Room client, Web browsers

SOCKS proxy limitations with the Sun JVM 1.4.1 Plug-in

If a Sametime Meeting Room or Broadcast client runs in a Web browser that operates with the Sun JVM 1.4.1 Plug-in, users may experience some connectivity problems when attempting to connect to a Sametime server through a

SOCKS proxy server.

These problems can occur if the Sun JVM 1.4.1 Plug-in is configured in either of the following ways:

The "Use browser settings" option is selected in the Sun JVM Plug-in Proxies tab and the Web browser proxy settings specify a SOCKS proxy server.

The "Use browser settings" option is disabled in the Sun JVM Plug-in Proxies tab and the connectivity settings

(host and port) on the Sun JVM Proxies tab specify a SOCKS proxy server.

Connectivity issue #1

The following issue applies to a scenario in which the Sametime clients and Sametime server operate on the same local network and the clients are configured to establish connections through a SOCKS proxy server.

If the specified SOCKS proxy server is configured to handle connections to external networks and cannot route connections from machines on its local network to other machines on the same local network, all of the following will be true:

The Sametime client will not attempt a direct TCP/IP connection to the Sametime server. This connection attempt is not possible due to limitations of the Sun Java Plug-in.

The connection attempt from the Sametime client to the Sametime server through the SOCKS proxy will fail.

If an HTTP proxy server is also configured in the web browser proxy settings or the Sun JVM Plug-in Proxies tab, the Sametime client will not be able to connect to the Sametime server through the HTTP proxy.

In this scenario, only a direct HTTP-tunneled connection between the Sametime client and the Sametime server can succeed.

If the Sametime server is located in a different external network, the Sametime client operating behind the SOCKS proxy can establish connections with the external Sametime server through the SOCKS proxy server.

If you remove the SOCKS proxy settings (from the Web browser proxy settings or the Sun JVM Plug-in Proxies tab), the

Sametime clients can bypass the proxy and establish a direct TCP/IP connection with the Sametime server.

Connectivity issue #2

No matter what SOCKS proxy port number is specified in the Web browser proxy settings or the Sun JVM Plug-in

Proxies tab, the Java Plug-in always attempts connections to the SOCKS proxy server using port 1080. The SOCKS proxy server must be configured to listen for these connections on port 1080 or the connections will fail.

Sametime Broadcast client, Sametime Connect client, Sametime Meeting Room client

Sun Java plug-in does not pick up SOCKS proxy from PAC file

If an Internet Explorer Web browser runs with the Sun JVM 1.4.1 Java Plug-in, do not use a Proxy Auto-Configuration file to enable IE to connect to servers through the SOCKS proxy server.

The Sun Java Plug-in cannot use PAC file settings to establish connections through a SOCKS proxy server. Any

Sametime Java applet client running under this configuration will also be unable to connect to a Sametime server through the SOCKS proxy server.

63

IBM Lotus Sametime 7 Release Notes Chapter 3 - Known limitations, problems, and workarounds

To make PAC files work under the Sun Java Plug-in, you must set your PAC file settings by using the Java Plug-in

Control Panel (available from the Windows Control Panel). In the Java Plug-in Control Panel, select the "Proxies" tab and unselect the "Use browser settings" option. Then specify the Auto Proxy Configuration URL (PAC file) in the field provided. This configuration ensures the Java Plug-in maintains its own settings and does not rely on the browser for them.

Sametime server issues

Sametime server

A member of a group cannot authenticate when attending a meeting

The Sametime end user interfaces include applets that enable a user to browse Directories and enter individual or group names in a Restrictions list to restrict attendance to a meeting. Users can also browse the Directory and add individual or group names to a Presenters list when setting up a Broadcast meeting.

If a user adds a group to the Restrictions or Presenters list, the group must exist in the primary Directory (the

Directory in which the Sametime server is registered) on the Sametime server that is being accessed.

If a user is a member of a group, and the group is defined only in a secondary Directory that is pointed to from

Directory Assistance, members of that group cannot authenticate when accessing the Sametime server. (In this situation, the primary Directory exists on the Sametime server and the Sametime server contains a Directory

Assistance database that points to the secondary directories. If the group is defined only in the secondary directories, members of that group cannot authenticate.) This problem occurs because of a known Domino problem regarding authentication of group members in secondary directories. This problem should be resolved in future releases.

Sametime Administration Tool

Access Control Lists are unavailable to the administrator

Sametime administrators can use the Sametime Administration Tool to access the Access Control Lists (ACLs) for databases on the Sametime server. To access the ACLs, the administrator chooses Domino Directory - Access Control

(or LDAP Directory - Access Control) from the Sametime Administration Tool.

If the ACLs are unavailable to an administrator, it may be necessary to add the administrator's name (or administrator's group) to a "File Protection Document" in the Domino Directory.

CGI scripts for the Sametime Administration Tool ACL applet are stored in the "adm-bin" directory on the Sametime server. The adm-bin directory is protected by a "File Protection Document" that is stored in the Domino Directory. This

File Protection Document controls who can read, write, or execute programs that are stored in the adm-bin directory.

To enable a Sametime administrator to use the ACL applet in the Sametime Administration Tool, you must ensure that the administrator's name (or administrator's group) appears in this File Protection Document.

Note: If you are running the Sametime Administration Tool in an Internet Explorer Web browser, see the note at the bottom of this topic before performing this procedure.

To add an administrator's name (or administrator's group) to the File Protection Document:

1. Use a Lotus Notes client to open the Directory on the Sametime server.

2. Select Configuration - Web - Web Configurations.

3. Click the twistie to the left of the Sametime server name.

4. Click the twistie to the left of "Domino Server."

5. Double-click on the document named "Access to C:\Lotus\Domino\Data\domino\adm-bin" to open the File

Protection Document.

6. Click "Edit File Protection."

7. Click the Access Control tab.

8. Click the "Set/Modify Access Control List" button. The Access Control List dialog appears.

9. Select the arrow to the right of the "Name" box to browse the list of names and groups in the Directory. The

Names box appears.

64

IBM Lotus Sametime 7 Release Notes

Chapter 3 - Known limitations, problems, and workarounds

10. Select the Directory for the Sametime server.

11. Select the administrator's name (or administrator's group) from the list of Directory entries and click OK.

12. From the Access: radio buttons, select the "Write/Read/Execute access (POST and GET method)" option.

13. Click Next.

14. Click OK.

15. Save and Close the File Protection Document.

You must restart the server for this change to take effect.

Note: If you are using Internet Explorer, and the names of databases do not appear in the ACL list in the Sametime

Administration Tool, you may need to type a valid filename in the Filename box of the Access Control List, and click the Access button to make the entire list of databases appear. The list of databases may not appear in the Access

Control List until you have manually typed in a valid filename.

1. Start Internet Explorer and open the Sametime Administration Tool on the Sametime server.

2. Select Domino Directory (or LDAP Directory) - Access Control.

3. Enter a valid Sametime filename in the "Filename:" box of the Access Control List. (For example, type

STCONF.NSF in the "Filename:" box.)

4. Click the Access button.

If the list of databases still does not appear, restart Internet Explorer, access the Sametime Administration Tool, and select the

Domino Directory - Access Control link. The filenames should appear in the Access Control list.

Sametime server

Accessing Print Capture help on Windows 2000 systems

On a Windows 2000 system, the Sametime Print Capture help is difficult to access.

If you are using the Sametime Print Capture application to create files for display on the whiteboard, you can access the Print Capture help system in the following way:

1. Open the Windows program and the document you want to display on the whiteboard.

2. Choose File - Print (or equivalent command).

3. In the Print dialog box, select Sametime Print Capture as the printer.

4. Select the pages you want to print, and then click OK or Print.

5. When the Sametime Print Capture dialog box appears, click the help button.

The "Windows Help" window appears. Click the "Contents" or "Index" button from that window to access the Print

Capture help topics.

Sametime Administration Tool

Administration tool unavailable after restarting STPlaces

If the ST Places Windows service stops, you will be unable to access the Sametime Administration Tool. The Sametime

Administration Tool remains unaccessible even if you restart the ST Places service.

If the STPlaces services stops, you must restart the Sametime server to regain access to the Sametime Administration

Tool.

Sametime Administration Tool, Sametime server, Web browsers

Broadcast connections monitoring does not show multicast users

The Sametime Administration Tool includes a Monitoring - Broadcast Connections - Connected Broadcast Users graph. This graph should display the number of users connected to the Sametime server with a Sametime Broadcast client.

If a user is attending a broadcast meeting, and receives broadcast meeting streams through unicast UDP or through

TCP tunneling, the user is counted in the Connected Broadcast Users graph.

65

IBM Lotus Sametime 7 Release Notes Chapter 3 - Known limitations, problems, and workarounds

If a user is attending a broadcast meeting, and receiving the broadcast meeting streams through multicast UDP, the user does not appear in the Connected Broadcast Users graph.

The Connected Broadcast Users graph counts the number of Broadcast call control connections. When a user receives broadcast meeting streams through multicast, the user initially establishes a Broadcast call control connection but this control connection is severed when the user begins receiving the streams through multicast. When a user receives streams via multicast, the user may be counted briefly in the Connected Broadcast Users graph but will not appear in the graph once the control connection is severed.

For more information on the Broadcast client connection process, see the topic "Broadcast client connection process" in the "Configuring Sametime Connectivity" chapter of the IBM Lotus Instant Messaging and Web Conferencing (Sametime)

6.5.1 Administrator's Guide.

Sametime Administration Tool, Sametime server

Broadcast monitoring counts TCP-tunneled streams as Unicast

The Sametime Administration Tool includes a Monitoring -General Server Status-Total Broadcast Streams chart.

Sametime can transmit broadcast streams in three ways:

Unicast UDP

TCP Tunneling

HTTP tunneling

The Total Broadcast Streams monitoring chart contains a "Unicast streams" section that reports the number of unicast broadcast streams that are sourced from the Broadcast Services of the Sametime server. Note that the "Unicast streams" section also counts any streams that are transmitted using TCP-tunneling.

When viewing the "Unicast streams" section of the Total Broadcast Streams monitoring chart, the administrator should be aware that the Unicast streams section reports both the number of broadcast streams that are transmitted using

Unicast UDP and the number of streams transmitted using TCP-tunneling. In a network in which UDP is not available, and all broadcast streams must be transmitted using TCP-tunneling, all broadcast streams are counted as "Unicast streams."

For more information about TCP and UDP in Broadcast meetings, see the topic "Broadcast client connection process" in the "Configuring Ports and Network Connectivity" chapter of the IBM Lotus Sametime 7.0 Administrator's Guide.

Sametime Administration Tool, Sametime server

Cannot import recorded meeting

If you have never recorded a meeting on a Sametime server, you may not be able to import a recorded meeting to that server.

For example, assume you have two Sametime servers (Sametime server 1 and Sametime server 2). You have recorded meetings on Sametime server 1 but have never recorded a meeting on Sametime server 2. You can use the "export a recorded meeting" feature to export a meeting from Sametime server 1 to a network drive. If you use the import feature on Sametime server 2 to import the meeting, you may receive an error when attempting to save the meeting on Sametime server 2.

This problem occurs because the C:\Sametime\MeetingArchive directory in which the Sametime server stores recorded meeting files (or .RAP files) is not created until the user records a meeting.

To prevent this problem, perform either of the following procedures on the Sametime server on which meetings have not been recorded:

Record a test meeting for the purpose of creating the C:\Sametime\MeetingArchive directory.

Use Windows Explorer to manually create the C:\Sametime\MeetingArchive directory.

66

IBM Lotus Sametime 7 Release Notes

Chapter 3 - Known limitations, problems, and workarounds

Once the C:\Sametime\MeetingArchive directory exists on the Sametime server, you can import meetings to that directory. For related information, see "Changing the directory for Record and Playback (.RAP) files" in the "Things you need to know" section of these release notes.

For more information about managing recorded meeting files, see "Managing recorded meetings (Record and

Playback)" in the "Configuring the Meeting Services" chapter of the IBM Lotus Sametime 7.0 Administrator's Guide.

Sametime server

Cannot replace a recorded meeting on Solaris server

Sametime includes a "Replace Recorded Meeting" option which can be used to replace an existing version of a recorded meeting with a backup version of a recorded meeting. The "Replace Recorded Meeting" option does not work on the Solaris version of the Sametime server.

Sametime server

Cannot search by first and last names

Sametime users can search the Directory on the Sametime server to add users to the presence list in Sametime

Connect, to add users to the Who can see me list in Sametime Connect, or to restrict attendance to a meeting in the

Sametime Meeting Center.

When searching for users in the Directory, users should search by last name only, not first name and last name. For example, to locate John Smith in the Directory, users must search on the name Smith, not John Smith. Searches by first name and last name are not supported in Sametime 7.0 unless you write a Java class to define the directory searching logic. For more information, see the "Using Java classes to customize LDAP directory searches" topics in the

"Using LDAP with the Sametime server" chapter of the administrator's guide.

Sametime server

Changing HTTP port of the Sametime server

If you change the port number of the Sametime HTTP server to a port other than port 80, note the following:

Users connected to the Sametime server cannot start instant meetings from the Participant List of the Sametime

Meeting Center. If a user is attending a meeting, the user cannot start an instant meeting (or "nested meeting") with another user who is attending a meeting.

If SSL is also enabled, and an administrator logs into the Sametime Meeting Center with a user name and password that does not belong to an administrator, the administrator cannot also access the Sametime

Administration Tool using the administrator name and password without first closing the browser. For example, an administrator cannot log in to the Sametime Meeting Center as user John Smith and then attempt to open the

Sametime Administration Tool using a different name and password that provides the administrator with access to the Sametime Administration Tool. If the administrator is logged into the Sametime Meeting Center as user

John Smith, the administrator must start a new instance of the Web browser to log into the Sametime

Administration Tool using the administrator's user name and password.

To change the HTTP port number in the Sametime Administration Tool:

1. Choose Configuration - Connectivity.

2. Select "Configure HTTP Services on a Web page in its own window."

3. Select "Ports."

4. Select "Internet Ports." The TCP/IP port number for the HTTP server is located under the "Web (HTTP/HTTPS) column of settings.

5. Change the port number under the "Web (HTTP/HTTPS)" column to the new port number.

6. Select "Internet Protocols."

7. Select "Domino Web Engine."

8. Under the "Generating References to this server" section, change the Port number setting to the new port number.

9. Click "Save and Close" to save the Server document.

10. Restart the server for the change to take effect.

67

IBM Lotus Sametime 7 Release Notes

Chapter 3 - Known limitations, problems, and workarounds

After changing the HTTP port number in the Sametime Administration Tool, you must also change the HTTP port number specified in the Tokens database on the Sametime server. To change the HTTP port number in the Tokens database:

1. Open STAuthT.nsf in the Sametime/Data directory.

2. Under the User Name column, open the SAMETIMESERVERHTTPPORT entry.

3. Enter the new value for the HTTP port in the Token field.

4. Save your changes.

Sametime Administration Tool

Changing the Broadcast gateway control port

The Broadcast gateway control port setting in the Sametime Administration Tool controls the port on which the

Sametime Broadcast Gateway Controller connects to the Broadcast Gateway. The default setting for this TCP port is

8083.

If you change the Broadcast gateway control port setting in the Sametime Administration Tool, you must also change the port setting in the Windows Registry. If you do not also change the port setting in the Windows Registry, all

Broadcast clients will be immediately disconnected from the server.

To change the port setting in the Windows Registry:

1. Run Regedit on the Sametime server.

2. Change the [HKEY_LOCAL_MACHINE\SOFTWARE\Lotus\Sametime\Broadcast Gateway] "ControlPort" = setting to match the port number that is specified in the "Broadcast gateway control port" setting of the Sametime

Administration Tool.

3. Restart the Sametime server.

Sametime server

Community Services HTTP tunneling option not working

This issue applies only to the IBM Lotus Instant Messaging Limited Use version of the Sametime server. This version of the Sametime server ships with all Domino 7.0 servers and supports only instant messaging and presence; this version of Sametime does not support Web conferences.

On this version of the Sametime server, the following issue occurs regarding the Community Services HTTP tunneling option in the Sametime Administration Tool:

1. Open the Sametime Administration Tool

2. Select Configuration -> Connectivity -> Network and Ports

3. Select the ·Enable the Sametime Connect for browsers client to try HTTP tunneling to the Community Server after trying other options· setting.

4. Click the Update button.

In this scenario, the "Enable the Sametime Connect for browsers client to try HTTP tunneling to the Community Server after trying other options" setting remains unchecked after you click the Update button.

After you perform the four steps above, restart the Sametime server to put the change into effect. Note that even after you restart the Sametime server, the "Enable the Sametime Connect for browsers client to try HTTP tunneling to the

Community Server after trying other options" setting may still appear as unchecked in the admin UI. However, the setting is actually in effect.

The stconfig.nsf database, which stores the admin settings, does get updated in the scenario above. However, the

Sametime Administration Tool UI does not always indicate the change is in effect.

68

IBM Lotus Sametime 7 Release Notes

Chapter 3 - Known limitations, problems, and workarounds

Sametime server

DiagnosticsFileOutput.txt file using too much disk space

Sametime is configured to generate diagnostics information by default. This diagnostic information is recorded in the

DiagnosticsFileOutput.txt file on the Sametime server. If you find that the DiagnosticsFileOutput.txt file is using too much disk space on the Sametime server, you can disable the creation of this file. To disable the

DiagnosticsFileOutput.txt file, use the instructions below.

1. Open Windows Explorer on the server machine.

2. Open the C:\Sametime\Data directory.

3. Open the servlet.properties file. (This is a text file that can be opened with any text editor.)

4. Remove the following text from each servlet entry: Enable.Diagnostics.Notify=true

Note: Before making the changes above you may want to save a backup copy of the servlet.properties file and store it in a different directory. You can use this backup copy to locate all appearances of the Enable.Diagnostics.Notify=true text if you want to enable the creation of the DiagnosticsFileOutput.txt file at a later date.

Sametime Meeting Room client, Sametime server

Disconnecting network cable removes moderator privileges

If you disconnect your network cable from your computer while attending a meeting, you may lose your moderator privileges. After you plug the network cable back in, you may need to leave the meeting entirely and then re-attend the meeting to regain your moderator privileges.

The following scenario illustrates this issue:

1. You attend a meeting as a moderator (using the Meeting Room client ).

2. During the meeting you accidentally disconnect your network cable.

3. You reconnect the network cable and then press the "Reconnect" button in the Meeting Room client to connect to the meeting. After reconnecting to the meeting, your moderator privileges are no longer available.

Clicking the "Reconnect" button does not restore the moderator privileges. To regain your moderator privileges, you must exit the meeting completely and then re-attend the meeting with the Meeting Room client.

Sametime Connect client, Sametime server

Disconnections from Community Services with NAT

To accommodate environments that include a Virtual Private Network (VPN) set up to use Network Address

Translation (NAT), changes have been made to the Sametime Java toolkit and a configuration flag

(VPS_IGNORE_UNKNOWN_CLIENT_IP) has been added to the Sametime.ini file on the Sametime server.

In previous releases of Sametime, a user attempting to log in to Community Services from two different machines was disconnected at both machines. For example, a user could not log in to Community Services from a Sametime

Connect client installed on client machine A and then open a Web browser on client machine B and connect to

Community Services using the Sametime Connect for browsers client.

This characteristic of the Community Services resulted in the following problem, which involves a user accessing an enterprise network through a VPN using NAT:

1. A user could be logged into the Sametime Community Services from the Sametime Connect for the desktop client

(a C++ application), or the Sametime Meeting Room client (a signed Java applet).

2. If a user also logged into Community Services from any application developed with the Sametime Toolkit, all of the user's connections to Community Services could be disconnected (even if all of the connections originated from the same machine).

Note: Sametime applications developed with the Sametime Toolkit are unsigned Java applets.

69

IBM Lotus Sametime 7 Release Notes

Chapter 3 - Known limitations, problems, and workarounds

Explanation

The problem described above can occur when a user is accessing an unsigned Java applet and connecting to the

Community Services through a proxy server. This situation can cause the Community Services to read two IP addresses for one client.

The Community Services can determine a client's IP address in two ways:

1. The Community Services can receive the IP address from the client. For example, a C++ application

(Sametime Connect for the desktop) and a signed Java applet (the Sametime Meeting Room) both calculate their own IP addresses and send them to the Community Services. If a client specifies its own IP address, the

Community Services use this address to identify the client.

2. If a client does not specify its IP address, the Community Services can use the client's socket to calculate the

IP address.

An unsigned Java applet (an application developed with the Sametime Toolkit) may not specify its IP address when connecting to the Community Services. If the unsigned Java applet connected through a proxy server, the IP address on the socket may be the IP address of the proxy server and not the IP address of the unsigned Java applet's host machine. As a result, it appears as though the same user has connected to the

Community Services from two different IP addresses (the IP address of the Sametime Connect host machine and the IP address of the proxy server). The Community Services therefore severs all of the user's connections.

To solve the problem described above, the following changes have been made for Sametime 2.5 (and later releases) regarding Community Services connectivity:

TheJava toolkit has been changed so that an application created with the toolkit (an unsigned Java applet) will never report an IP address.

The configuration flag VPS_IGNORE_UNKNOWN_CLIENT_IP has been added to the Sametime.ini file on the

Sametime server. This configuration flag is enabled by default.

When the VPS_IGNORE_UNKNOWN_CLIENT_IP flag in the Sametime.ini file is enabled (default setting), and a Sametime client does not report an IP address, the Community Services allow the client to connect.

The Community Services do not determine if the user is logged in from another machine. This configuration prevents the Community Services from disconnecting a user because the proxy server's IP address is different from the IP address that the Sametime Connect for the desktop client reports.

The configuration described above allows a user to log into Community Services from two different machines, if one of the logins originates from an unsigned Java applet. This configuration can be very confusing for the end user and should be avoided if possible.

Note: When the VPS_IGNORE_UNKNOWN_CLIENT_IP flag is enabled, it is still not possible for a user to log into Community Services from two Sametime Connect clients (or two Meeting Room clients) on two different machines. For example, a user cannot start a Sametime Connect for the desktop client on client machine A, and then attend a meeting using a Meeting Room client on client machine B. Both the Sametime Connect for the desktop client and the Sametime Meeting Room client report their IP addresses to the Community

Services. If the IP addresses are reported, the Community Services ensure that the same user is not logged in from two different locations. The Community Services forego this check when the IP address is not reported, as is the case with unsigned Java applets created from the Sametime toolkit.

When the VPS_IGNORE_UNKNOWN_CLIENT_IP flag is not enabled, and a Sametime client does not report an IP address, the Community Services use the client's socket to get the IP address. The Community

Services also determine if the same user is logged in from a different IP address. If the user is logged in from two different IP addresses, the new log in disconnects the existing log in.

As a result, when the VPS_IGNORE_UNKNOWN_CLIENT_IP flag is not enabled, a user may be disconnected from Community Services even though all Community Services connections originate from the same machine. This disconnection occurs if the unsigned Java applet connects to the Community Services through a proxy server while the user is connected to Community Services from either the Sametime Connect client or the Sametime Meeting Room client.

When the VPS_IGNORE_UNKNOWN_CLIENT_IP flag is not enabled, a user is also disconnected when attempting to log into Community Services from two Sametime clients that report IP addresses to the

Sametime server, if the two clients are on different machines. (Both the Sametime Connect for the desktop client and the Sametime Meeting Room client report IP addresses to the Sametime server.) This is the same scenario described in the note above.

70

IBM Lotus Sametime 7 Release Notes

Chapter 3 - Known limitations, problems, and workarounds

Sametime server

Do not use invalid XML characters in Sametime server names

Sametime will not work if any server in a community includes invalid XML characters in the server name. Do not use the following characters in any Sametime server name:

> < & ' " ;

Sametime server

Environment variables associated with ststart script file

This issue applies to only to Sametime servers that operate on the AIX or Solaris operating systems.

The "ststart" script file sets some important environment variables before launching the server executable

(/opt/lotus/bin/server). If you want to launch the server automatically, add the "ststart" environment variables to the

Domino user's profile before launching the executable. You must add these variables to the user's profile for Sametime to work correctly.

Sametime server

Error when exporting a recorded meeting

This issue applies to Sametime servers that run on the AIX or Solaris operating system.

If the administrator changes the default location for recorded meetings, anyone who attempts to export a recorded meeting will receive the following error:

HTTP Web Server: Item Not Found Exception.

To solve this problem, the person who is exporting the file (either the Moderator or the administrator) must add the recorded file name to the URL that appears during the export attempt. The recorded file name is the file name that the administrator entered when changing the default location for recorded meetings.

In the example below, the Moderator must add the file name "record" to the URL for the exported meeting:

1. The administrator chooses Administer the Server-Configuration-Meeting Services, then clicks on the General tab.

2. In the field labeled "Save recorded meetings in the following location," the administrator enters: &ltdata directory path>/all_recorded_meetings/record.

All recorded meetings will be saved in the "all_recorded_meetings" folder, under the data directory. Meeting names will be saved in the following format: record(meeting_ID)_recorded.rap

3. When the Moderator tries to export the .rap file, the following error appears:

HTTP Web Server: Item Not Found Exception.

The URL in the browser is http://&ltserver

>/stconf.nsf/(ExportRecodingArchives)/(id)/$file/(meeting_id)_recorded.rap?OpenElement&login.

4. To export the file, the Moderator must add the file name to the URL: http://&ltserver>/stconf.nsf/($ExportRecodingArchives)/(id)/$file/record

(meeting_id)_recorded.rap?OpenElement&login.

Note: The administrator must supply the Moderator with the file name before the Moderator can enter the file name in the URL.

5. A "File Download" dialog box appears, and the Moderator can save the .rap file to his or her local machine.

71

IBM Lotus Sametime 7 Release Notes Chapter 3 - Known limitations, problems, and workarounds

Sametime server

HTTP Services and Meeting Services do not start correctly

After the Sametime server is started, you may see the HTTP service hang on initialization which also prevents the

Meeting Services from starting.

This problem occurs when the Sametime.ini file includes a line that begins with a semi-colon. For example, a line in the sametime.ini file may begin with:

;CommentLine

To prevent this problem, remove all lines from the sametime.ini file that have a semi-colon (;) as the first character.

Sametime server

HTTPS in URL listed in the meeting details document is incorrect

If you have set up one Sametime server to encrypt Web browser connections with SSL, and you have created a

Connection document of the Connection type "Sametime" to connect this SSL-enabled Sametime server to a Sametime server that is not encrypting Web browser connections with SSL, the following problem may occur:

When the SSL-enabled Sametime server invites the other (non SSL-enabled) Sametime server to a meeting, the meeting details document in the Sametime Meeting Center will indicate that the URL of the non-SSL Sametime server begins with Https: when the URL actually begins with Http:. Users attempting to attend the meeting on the non

SSL-enabled Sametime server using the URL that begins with Https: will not be able to connect to the server.

Users can still access the non-SSL Sametime server using the correct URL that begins with Http: and attend the meeting. However, this URL will not be listed on the meeting details page. Only the incorrect URL beginning with

Https: is listed on the meeting details page.

To avoid this problem, it is recommended that you maintain a consistent environment for SSL. If you have enabled one Sametime server to encrypt Web browser connections using SSL, you should also enable your other Sametime servers to use SSL.

Note: An administrator can create a Connection document of the Connection type "Sametime" to enable a meeting started on one Sametime server to become simultaneously active on another Sametime server. This functionality is frequently referred to as "invited servers" and is described in the "Deploying Multiple Sametime Servers" chapter of the

IBM Lotus Instant Messaging and Web Conferencing (Sametime) 6.5.1 Administrator's Guide.

Sametime server

i5/OS (iSeries) Server international issues

The following issues may occur with International versions of the i5/OS (iSeries) Sametime server.

DBCS characters may display as garbage characters in the Sametime Administration Tool pages.

The Macintosh Sametime Connect for the desktop client may not load buddy lists correctly from the i5/OS server.

Sametime server

Invited servers require same HTTP port number for meeting links

When one server invites another server to a meeting, both servers should use the same HTTP port number. If the servers use different HTTP ports, the links to the invited server will be incorrect in the Meeting Details document.

For example, assume that Sametime server A uses HTTP port number 8088 and Sametime server B uses HTTP port number 80. A meeting is created on Sametime server A. Sametime server A invites Sametime server B to the meeting.

The Meeting Details document for the meeting on Sametime server A contains a link to the meeting on Sametime server B. Sametime server A appends the HTTP port number that it uses (port number 8088) to this link instead of the port number that Sametime server B uses (port 80), and the link does not function correctly.

72

IBM Lotus Sametime 7 Release Notes Chapter 3 - Known limitations, problems, and workarounds

Sametime server

Listed user name appears not active in the public group

If a user is listed in a Group document, the name in the Group document must be the first name that appears in the

User name field of the Person document. If the first name in the User name field is not used in Group documents, the user will always appear to be offline when the group is opened in a Sametime presence list.

For example, assume a user's name is listed in the User name field of the Person document as:

Tom Smith/West/Acme

Tom Smith

When including the user in a Group document, you should enter the name in the Group document as Tom

Smith/West/Acme (the first name that appears in the User name field).

Generally, self registered users will always have the shortened version of the name (Tom Smith) listed first in the User name field of the Person document.

If the shortened form of the name appears first in the User name field, then the shortened form of the name should also be used when adding the user to a Group document.

Sametime server

Maximum online meeting password length

When creating a password for an online meeting in the Meeting Center, the maximum password length is 80 characters.

Sametime Connect client, Sametime Meeting Room client

Maximum user and server connections limit off by one

If you have set a limit in the "Maximum user and server connections to the Community server" option in the

Configuration - Community Services settings of the Sametime Administration Tool, users might be unable to connect when they reach the number specified as the limit (rather than the number one above the limit). For example, if the administrator has set the limit to 50, the 50th user might not be able to connect.

Sametime server

Meeting name does not appear on connected (or "invited") server

A Sametime Administrator can create a Connection document of the Connection Type "Sametime" to enable a meeting started on one Sametime server to be simultaneously active on another Sametime server. This functionality is frequently called "invited servers" as one server "invites" another server to the meeting.

The procedure for creating these Connection documents is described in the topic "Creating Connection Records to connect Sametime servers" in the "Deploying Multiple Sametime Servers" chapter of the IBM Lotus Sametime 7.0

Administrator's Guide.

When creating a Connection Document to connect two Sametime servers, it is important that the Domino domain name is used along with the server name in the Source server and Destination server fields of the Connection document. For example, if the name of the source Sametime server (the server on which the meeting is started) is

SametimeA.acme.com, and the domain name is ACME, the server should be specified as

SametimeA.acme.com/ACME in the Source server field of the Connection document. Similarly, if the name of the destination server (the server being invited to the meeting) is SametimeB.acme.com and its domain is ACME, the server should be specified as SametimeB.acme.com/ACME in the Destination server field.

If the domain name is not included in the Source and Destination fields of the Connection document, the meeting name will not appear on the invited server.

Note: You should also disable the replication features in the Connection document when creating a Connection document of the Connection Type "Sametime." For more information, see the topic "Disable replication for 'invited servers' Connection documents" in the Troubleshooting - Sametime server issues section of these release notes.

73

IBM Lotus Sametime 7 Release Notes

Chapter 3 - Known limitations, problems, and workarounds

Sametime server

Meetings are not recorded as expected

The Sametime server includes a record and playback feature that allows the Sametime server to record a meeting and store the recorded meeting in a Sametime Record and Playback (.RAP) file on the Sametime server. The administrator enables the record and playback feature by selecting the "Allow people to record meetings for later playback" setting in the Configuration - Meeting Services - General settings of the Sametime Administration Tool.

After selecting the "Allow people to record meetings for later playback" setting, the administrator can either accept the default settings or change the settings for the following two recorded meeting options.

Save recorded meetings in the following location - This field specifies the default directory in which Sametime

.RAP files are stored. The default setting is C:\Sametime\MeetingArchive\.

If you change the default directory to a different directory, you will not receive notification if the new directory does not exist or cannot be created. If the directory you specify does not exist or cannot be created, meetings will not be recorded.

If you change the directory setting in the "Save recorded meetings in the following location" field, use Windows

Explorer to verify that the directory specified in the field exists on the Sametime server, or to create the directory if necessary.

Stop recording when this much disk space is left (Mbytes) - This setting specifies the amount of free disk space

(in Megabytes) that must exist on the Sametime server for the recording of meetings to continue. If meetings are not being recorded, verify that there is enough free disk space on the server.

For more information about the record and playback feature, see "Managing recorded meetings (Record and

Playback)" in the "Configuring the Meeting Services" chapter of the IBM Lotus Sametime 7.0 Administrator's Guide.

Sametime server

Meetings do not become active on connected ("invited") server

If you have created a Connection document to connect Sametime server A to Sametime server B, and a meeting started on Sametime server A does not become simultaneously active on Sametime server B as expected, verify that you have entered the DNS host name or IP address of the destination Sametime server (Sametime server B) in the

"Optional network address" field of the Connection document that connects these two Sametime servers.

The "Optional network address" field is not an optional field. This field is required when creating a Connection document (of the Connection Type "Sametime") that connect two Sametime servers.

Note: A Connection document of the Connection Type "Sametime" enables a meeting started on one Sametime server to be simultaneously active on another Sametime server. This functionality is frequently called "invited servers" as one

Sametime server "invites" another Sametime server to a meeting. These Connection documents can be created from a

Lotus Notes client or the Connectivity - Servers in this Community settings of the Sametime Administration Tool.

If this field is left blank, the server also will not appear as available in the Locations tab of the New Meeting page in the

Sametime Meeting Center.

Sametime Administration Tool, Sametime Broadcast client

Monitoring tab info incorrect for broadcast multicast streams

The Monitoring tab of the Sametime Administration Tool might display incorrect statistics for the number of multicast and unicast streams in broadcast meetings. Multicast streams might be incorrectly counted as unicast streams.

74

IBM Lotus Sametime 7 Release Notes

Chapter 3 - Known limitations, problems, and workarounds

Sametime Administration Tool, Sametime server

Multicast address ranges for Broadcast Services not working

If you have a multicast-enabled network, the Sametime Broadcast Services can use multicast to transmit broadcast meeting streams on the network. A Sametime administrator can use the Sametime Administration Tool to enable the multicast functionality and enter a range of Class D multicast IP addresses to be used by the Broadcast Services.

The Broadcast Services randomly select an IP address from the range of IP addresses specified by the Sametime administrator in the Sametime Administration Tool. The Broadcast Services then begin transmitting data to the selected multicast address at a multicast-enabled router. The Sametime Broadcast clients "join" the multicast address to receive the broadcast meeting streams.

When specifying the range of available multicast addresses in the Sametime Administration Tool, the administrator must ensure that the IP addresses specified for multicast use do not contain a low octet with a value of zero.

To view the multicast address range settings, open the Sametime Administration Tool and select Configuration -

Connectivity - Networks and Ports and scoll to the "Broadcast Services Network" settings. The "Multicast addresses start at IP address" and the "Multicast addresses end at IP address" fields allow you to define the range of available multicast IP addresses.

In both the "Multicast addresses start at IP address" and the "Multicast addresses end at IP address" fields, you enter an IP address that contains four octets (for example, www.xxx.yyy.zzz). If the lowest octet (zzz in the example) is zero in either the "Multicast addresses start at IP address" or the "Multicast addresses end at IP address" field, the multicast address range settings do not work. Verify that the lowest IP octet in both of the multicast address range fields has a value between 1 and 255, but not 0.

Sametime server

Must enter full server name to log on to Sametime

If an end user is able to access the Sametime Welcome page but is having trouble logging on to Sametime, he or she should enter the full DNS name of the Sametime server in the browser. For example, enter www.sametime.east.com.

Sametime server

Mux startup information prints to console instead of log file

When the Community Service multiplexer is started on an AIX or Solaris Sametime server, the startup messages are printed to stdout and appear on the console. These messages are not recorded in a log file.

To record these messages, administrators can use standard UNIX administration procedures to direct the stdout output to a text file.

If the administrator is concerned that recording this output to a text file will consume too much disk space, the

/dev/null command can be used to prevent the output from being recorded in a text file.

Sametime server

Name Conversion Utility trace messages always output to file

If you enable trace message reporting for the Name Conversion Utility, the trace messages are always written to a text file. You cannot output these messages to the monitor.

The following instructions from the Sametime 7.0 Administrator's Guide explain how to enable trace message reporting for the Name Conversion Utility:

1. Use a text editor to open the Sametime.ini file located in the Sametime server installation directory.

2. In the Sametime.ini file, enable trace reporting by setting the following parameter as shown:

NAME_CONV_TRACE_DEBUG=1

3. Save and close the Sametime.ini file.

4. Open the NameConvUtil.ini file in the Sametime server Data directory.

75

IBM Lotus Sametime 7 Release Notes Chapter 3 - Known limitations, problems, and workarounds

5. Use the VP_USERS_TRACE_STDOUT parameter to determine the output location for the trace messages:

Set VP_USERS_TRACE_STDOUT=0 to output trace messages to a file in the <Sametime server installation>\Trace directory.

Set VP_USERS_TRACE_STDOUT=1 to output trace messages to the monitor.

6. Save and close the NameConvUtil.ini file.

Note that the VP_USERS_TRACE_STDOUT flag does not function as described above. The trace messages are always output to a file in the <Sametime server installation>\Trace directory regardless of how the

VP_USERS_TRACE_STDOUT flag is configured. You cannot output trace messages to the monitor by setting

VP_USERS_TRACE_STDOUT=1.

Sametime server

No meetings in the "Today's Meetings" view of the Meeting Center

If no meetings appear in the "Today's Meetings" view of the Sametime Meeting Center, see the release note titled

"Subscript out of range 47 error when creating repeating meetings" in the Sametime server issues section of these release notes.

Sametime server

Password protected ID not supported for additional server

After installing the first Domino/Sametime server, do not enable password protection for the server.id of any additional Domino server that you install (for the purpose of supporting a Sametime server).

If password protection is enabled on the server.id of the additional Domino/Sametime server, Domino, Sametime, and

TCPIP will consistently hang on that server.

To disable password protection on the server.id, open a Notes client on the additional server and select

Files-Tool-User ID-Disable password.

Sametime server

Renaming the stcenter.nsf database

The stcenter.nsf database contains the Sametime server home page (or the Sametime Welcome page). If you rename the stcenter.nsf database, or replace it with a different home page, you must ensure that the links in Sametime databases such as stconf.nsf (the Sametime Meeting Center) and streg.nsf (the self-registration database) are also altered to point to the new home page.

If you rename the stcenter.nsf database or use a new Lotus Notes database as the home page, you must also change the "Home URL" setting in the Internet Protocol - HTTP - Mapping section of the Server document in the Domino

Directory to point to the renamed or new database.

If you use an HTML file instead of a Lotus Notes database as a home page, leave the "Home URL" setting on the Server document blank. Enter the name of the HTML page in the "Default home page" setting in the Internet Protocols - HTTP

- R5 Basics settings of the Server document. All links in other Sametime databases must also be altered to point to the HTML page.

Sametime Administration Tool

Restart the server when changing logging options

The Sametime Administration Tool contains settings that enable the administrator to log Sametime information to either a database or a text file. These settings include the "Enable logging to a Domino database" check box or the

"Enable logging to a text file" check box located in the Logging - Settings menu of the Sametime Administration Tool.

If the administrator changes the logging settings (switches from a database to a text file, or from a text file to a database), the administrator must restart the Sametime server for the change to take effect.

76

IBM Lotus Sametime 7 Release Notes

Chapter 3 - Known limitations, problems, and workarounds

Sametime server

Running Sametime in the background on Solaris

To run Sametime in the background on Solaris, you must install the X Virtual Frame Buffer (Xvfb).

1. Xvfb is already installed on Solaris 9 in /usr/openwin/bin

2. Login in from a terminal shell as root and run the following:

/usr/openwin/bin/Xvfb :1 -screen 0 1280x1024x8 &

Note: If you see a message saying "No such file or directory", ignore the message.

3. You can verify that the VFB is running properly by typing:

ps -ef | grep vfb

You should see the Xvfb process running.

You can assign any number except 0 in place of the number "1" in the above example. 

This is the display number you wish to have associated with this instance of the XVFB. 

Follow these instructions to run Sametime in the background:

1. Login as notes.

2. Modify the notes user .profile or equivalent  to add the ${BINDIR} from ststart to the LD_LIBRARY_PATH and to the PATH environment variables.

3. Logout and log back in.

4. Set the DISPLAY variable to the display number you used above:

For example: DISPLAY=machinename:1

5. From the data directory, run the command:

nohup /opt/lotus/bin/server < /dev/null > /dev/null 2>&1 &

( This example assumes /opt/lotus/bin is the $LOTUSDIR in ststart).

6. Exit the telnet session or the xwindows session.

Sametime server

Running Sametime in the background on UNIX

To run a Sametime server in the background on either the AIX or Solaris platform, you must first install and run the X

Virtual Frame Buffer.

For more information, see the release note titled "Ensuring that Whiteboard save works on Unix" in these release notes.

Sametime server

Sametime Links application stops with "Out of Memory" error

The Sametime Links application may stop unexpectedly or display an out of memory error if the amount of memory allocated to the Sametime Links application is not sufficient to support the number of users allowed to access the application.

To solve this problem you may need to add memory to the server. After adding memory to the server, you must also configure the appropriate settings in the Sametime.ini file to ensure that the proper amount of memory is allocated for

Sametime Links.

Note: The Sametime.ini file is located in the C:\Lotus\Domino directory of the Sametime server.

77

IBM Lotus Sametime 7 Release Notes

Chapter 3 - Known limitations, problems, and workarounds

The two configuration settings in the Sametime.ini file relevant to this problem are:

STLINKS_MAX_USERS=2500 (This setting determines the maximum number of users that can access the

Sametime Links application.)

STLINKS_VM_ARGS= -Xmx128m -Xms128m -Xgcpolicy:optavgpause (This setting determines the amount of memory allocated to the Sametime Links application.)

In the configuration shown above, a maximum of 2500 users can access Sametime Links and 128 MB of memory is allocated to the Sametime Links application. The Sametime Links application should provide acceptable performance in this configuration.

If you intend to support more than 2500 Sametime Links users you may need to add memory to your server and then configure the settings in the Sametime.ini file appropriately.

For example, if you want to allow 10000 users to access Sametime Links, you should ensure the Sametime server has

1 GB of memory installed on the machine and that 512 MB of that memory is allocated to Sametime Links. To support this scenario, you must configure the Sametime.ini settings as shown below:

STLINKS_MAX_USERS=10000

STLINKS_VM_ARGS= -Xmx512m -Xms512m -Xgcpolicy:optavgpause

This configuration allows 10000 users to access the Sametime Links application and allocates 512 MB of memory to the application.

To prevent this out of memory condition with the Sametime Links application, use the following guidelines for users and memory.

To support 2500 users, you should have a minimum of 512MB of memory installed on the Sametime server machine and 128MB of this memory should be allocated to the Sametime Links application. In this scenario, the appropriate configurations in the Sametime.ini file are:

STLINKS_MAX_USERS=2500

STLINKS_VM_ARGS= -Xmx128m -Xms128m -Xgcpolicy:optavgpause

To support 10000 users, you should have a minimum of 1 GB of memory installed on the Sametime server machine and 512MB of this memory should be allocated to the Sametime Links application. In this scenario, the appropriate configurations in the Sametime.ini file are:

STLINKS_MAX_USERS=10000

STLINKS_VM_ARGS= -Xmx512m -Xms512m -Xgcpolicy:optavgpause

Sametime server

Saving recorded meetings to a mapped network drive

An administrator can specify the network location where the Sametime server saves recorded meeting files (RAP files).

The administrator specifies this network location in the "Save recorded meetings in the following location" field available from the Configuration->Meeting Services->General tab of the Sametime Administration Tool.

The administrator can specify a folder on a mapped network drive as the network location to store recorded meeting files. To do this, the administrator creates a mapping to a network drive and folder from the Sametime server machine operating system and then specifies the mapped network drive and folder in the "Save recorded meetings in the following location" field of the Sametime Administration Tool.

If an administrator specifies a folder on a mapped network drive as the location for recorded meeting files, one of the following must be true:

The operating system security settings must be configured so that "Everyone" has the "Full" access level to the shared folder on the mapped network drive.

The "Lotus Domino Server (LotusDominoData)" service must be modified to run as a specific user that has been granted access to the shared drive (instructions are provided below).

78

IBM Lotus Sametime 7 Release Notes

Chapter 3 - Known limitations, problems, and workarounds

If you choose the latter option, you can use these instructions to ensure that the Lotus Domino Server service runs as a specific user that is granted access to the shared drive:

1. From the Sametime server machine, select Control Panel->Administrative Tools->Services.

2. Right click on the "Lotus Domino Server" service and select "Properties."

3. From the "LogOn" tab, do the following:

- Change the "Log on as:" option from the default value of "LocalSystem account" to "This account."

- Enter the login and password credentials for an account that is authorized to access the shared drive.

Sametime server

Self registered user cannot change password

Domino includes an Update to More Secure Internet Password... option that allows an administrator to upgrade a user's Internet password to a more secure password format. (The administrator selects this option by opening a user's

Person document with a Lotus Notes client and selecting Actions - Upgrade to More Secure Internet Password

Format.)

If the administrator selects this option for a self-registered Sametime user, the user cannot change their Internet

Password from the Self Registration feature on the Sametime server. The administrator should not use the Update to

More Secure Internet Password... feature to upgrade a user's Internet password to a more secure password format.

Sametime server

Self registration does not work

If you have followed the instructions in the IBM Lotus Sametime 7.0 Administrator's Guide to enable self registration, note that the administrator's guide does not state that the "Create Documents" privilege must be selected in the Domino

Directory ACL to enable self registration.

To enable self registration, verify that all of the following conditions exist:

The signer "Sametime Development/Lotus Notes Companion Products" is added to the ACL of the Domino

Directory on the Domino 6.0.2 server.

The "Sametime Development/Lotus Notes Companion Products" signer is assigned the "Author" access level in the

Domino Directory ACL.

The "Sametime Development/Lotus Notes Companion Products" signer has the following Roles assigned in the

Domino Directory ACL: Group Creator, Group Modifier, User Creator, User Modifier.

The "Create Documents" privilege is selected in the Domino Directory ACL.

Sametime server

Service is disabled message when starting the Sametime server

An IBM Lotus Instant Messaging Limited Use version of the Sametime server is shipped with all Domino 7.0 servers.

This version of the Sametime server supports instant messaging and presence but does not support Web conferences.

When starting the IBM Lotus Instant Messaging Limited Use version of the Sametime server, you will see several messages indicating that various services are disabled. These messages are normal for this version of the Sametime server and do not indicate a problem. An example of these messages is provided below:

06/23/2005 03:27:33 PM Sametime: Building service start order from dependencies...

06/23/2005 03:27:33 PM Sametime: Found event server service.

06/23/2005 03:27:33 PM Sametime: Starting services...

06/23/2005 03:27:33 PM Sametime: Starting event server service.

06/23/2005 03:27:40 PM Sametime Server: Running

06/23/2005 03:27:46 PM Sametime: Service [Telephony Service] is disabled.

06/23/2005 03:27:46 PM Sametime: Starting service [Java Services].

06/23/2005 03:27:46 PM Sametime: Process 2744 created.

06/23/2005 03:27:48 PM Sametime: Service [Java Services] started successfully.

06/23/2005 03:27:48 PM Sametime: Service [Configuration Bridge] is disabled.

06/23/2005 03:27:48 PM Sametime: Service [Event Bridge] is disabled.

06/23/2005 03:27:48 PM Sametime: Service [Logger] is disabled.

79

IBM Lotus Sametime 7 Release Notes Chapter 3 - Known limitations, problems, and workarounds

06/23/2005 03:27:48 PM Sametime: Service [Token Server] is disabled.

06/23/2005 03:27:48 PM Sametime: Service [T.120 MCU] is disabled.

06/23/2005 03:27:48 PM Sametime: Service [Whiteboard Server] is disabled.

06/23/2005 03:27:48 PM Sametime: Starting service [Statistics Server].

06/23/2005 03:27:49 PM Sametime: Service [Statistics Server] started successfully.

06/23/2005 03:27:49 PM Sametime: Service [Shared Object Server] is disabled.

06/23/2005 03:27:49 PM Sametime: Service [Material Manager] is disabled.

06/23/2005 03:27:49 PM Sametime: Service [Capacity Monitor] is disabled.

06/23/2005 03:27:49 PM Sametime: Service [Calendar Service] is disabled.

06/23/2005 03:27:49 PM Sametime: Service [Broadcast Gateway] is disabled.

06/23/2005 03:27:49 PM Sametime: Service [Broadcast Controller] is disabled.

06/23/2005 03:27:49 PM Sametime: Service [A/V MMP] is disabled.

06/23/2005 03:27:49 PM Sametime: Service [Interactive Streamed Media Service] is disabled.

06/23/2005 03:27:49 PM Sametime: Service [H.323 MCU] is disabled.

06/23/2005 03:27:49 PM Sametime: Service [Activity Provider] is disabled.

06/23/2005 03:27:49 PM Sametime: All services started successfully.

06/23/2005 03:27:49 PM Sametime: Server startup successful.

Sametime server

Service is not started message when stopping the Sametime server

An IBM Lotus Instant Messaging Limited Use version of the Sametime server is shipped with all Domino 7.0 servers.

This version of the Sametime server supports instant messaging and presence but does not support Web conferences.

When stopping the IBM Lotus Instant Messaging Limited Use version of the Sametime server, you will see several messages indicating that various services are not started. These messages are normal for this version of the

Sametime server and do not indicate a problem. An example of these messages is provided below:

06/23/2005 03:42:31 PM Sametime: Shutdown detected.

06/23/2005 03:42:31 PM Sametime: Stopping services...

06/23/2005 03:42:31 PM Sametime: Service [Activity Provider] is not started.

06/23/2005 03:42:31 PM Sametime: Service [H.323 MCU] is not started.

06/23/2005 03:42:31 PM Sametime: Service [Interactive Streamed Media Service] is not started.

06/23/2005 03:42:31 PM Sametime: Service [A/V MMP] is not started.

06/23/2005 03:42:31 PM Sametime: Service [Broadcast Controller] is not started.

06/23/2005 03:42:31 PM Sametime: Service [Broadcast Gateway] is not started.

06/23/2005 03:42:31 PM Sametime: Service [Calendar Service] is not started.

06/23/2005 03:42:31 PM Sametime: Service [Capacity Monitor] is not started.

06/23/2005 03:42:31 PM Sametime: Service [Material Manager] is not started.

06/23/2005 03:42:31 PM Sametime: Service [Shared Object Server] is not started.

06/23/2005 03:42:31 PM Sametime: Stopping service [Statistics Server].

06/23/2005 03:42:31 PM Sametime: Service [Statistics Server] stopped.

06/23/2005 03:42:31 PM Sametime: Service [Whiteboard Server] is not started.

06/23/2005 03:42:31 PM Sametime: Service [T.120 MCU] is not started.

06/23/2005 03:42:31 PM Sametime: Service [Token Server] is not started.

06/23/2005 03:42:31 PM Sametime: Service [Logger] is not started.

06/23/2005 03:42:31 PM Sametime: Service [Event Bridge] is not started.

06/23/2005 03:42:31 PM Sametime: Service [Configuration Bridge] is not started.

06/23/2005 03:42:31 PM Sametime: Stopping service [Java Services].

06/23/2005 03:42:32 PM Sametime: Service [Java Services] stopped.

06/23/2005 03:42:32 PM Sametime: Service [Telephony Service] is not started.

06/23/2005 03:42:32 PM Sametime: Stopping event server service.

06/23/2005 03:42:32 PM Sametime: Service stopped.

06/23/2005 03:42:32 PM Sametime: All services stopped successfully.

80

IBM Lotus Sametime 7 Release Notes Chapter 3 - Known limitations, problems, and workarounds

Sametime server

SIP connector not disabled when "Support external User" = False

When your Sametime server is set up to communicate with external users using the integrated i5/OS SIP connector, changing "Support External users" to false in the CommunityGateway document of the Sametime configuration database does not take effect when the time for Refresh from Configuration expires. Users on the server where the configuration was changed are still able to see presence information for external users but cannot initiate a chat.

However, they can respond to chats initiated by external users.

In order to disable SIP, you must edit the STCommLaunch.dep file in the server data directory. Enter a "#" as the first character in the line containing StSIPCon. Save the file and restart the Sametime server.

Sametime server

SSO for Sametime requires an SSO document named "LtpaToken"

To support Single Sign-On for a Sametime server, the Domino server on which Sametime is installed must use an SSO configuration document named "LtpaToken." This document must be applied to the group of servers that includes the

Sametime servers.

If the SSO configuration document named LtpaToken does not exist, users may be able to log in to the server successfully but may experience problems when attempting subsequent actions that require authentication by token.

For example, a user may be able to log in successfully and begin creating a new meeting. However, if the user attempts to restrict access to the meeting by using the Add or Remove people option on the Security tab of the meeting creation page, the user will not be allowed to perform that action. Problems of this type occur because the action the user is attempting to perform require an authentication token named LtpaToken.

This problem can occur even when the

ST_TOKEN_TYPE=

setting in the Notes.ini file specifies a token name other than LtpaToken.

Sametime server

STLog.nsf on invited server does not record names

If one Sametime server invites another Sametime server to a meeting, the invited server does not record the names of meeting participants in its Sametime log database (STLog.nsf).

You must create a Connection document of the Connection type "Sametime" to enable one Sametime server to invite another Sametime server to a meeting. You can also use the Configuration - Connectivity - Servers in this Community settings of the Sametime Administration Tool to create these Connection documents. For more information, see the

"Deploying Multiple Sametime Servers" chapter of the IBM Lotus Sametime 7.0 Administrator's Guide.

Sametime server, Enterprise Meeting Server and server clusters

Stop recording option does not work with Sametime on UNIX

The Configuration - Meeting Services - General settings of the Sametime Administration Tool include a "Stop recording when this much disk space is left (Mbytes)" setting that is intended to stop a meeting from being recorded if the available disk space on the server falls below and administrator-defined threshold.

This setting is not operational for a Sametime 7.0 server that operates on the AIX or Solaris operating system.

Sametime server

Subscript out of range 47 error when creating repeating meetings

If a user creates a repeating meeting that includes an invalid day for the specified date range, the user sees a

"Subscript out of range 47(ListSort)" error. For example, assume a user schedules a meeting to repeat every Monday and then selects a date range that runs from 08/28/2005 to 09/02/2005 (or Tuesday through Sunday). Since there is no Monday in the specified range of 8/28/2009 to 9/2/2009, the user sees the error "Subscript out of range

47(ListSort)" error after clicking the OK button to save the meeting.

The meeting appears in the Scheduled and All Meetings views of the Sametime Meeting Center and cannot be deleted from the Meeting Details document for the meeting. You must use a Lotus Notes client to delete the Meeting

Document for this meeting.

81

IBM Lotus Sametime 7 Release Notes

Chapter 3 - Known limitations, problems, and workarounds

If a repeating meeting is scheduled with an invalid day for the specified date range, the meeting may also corrupt the

"Today's Meetings" view of the Sametime Meeting Center so that no meetings appear in that view. Meetings scheduled with an invalid day in the date range will usually list the year as "-2" when displaying the scheduled date of the meeting in the Sametime Meeting Center. For example, if you see a meeting in the Sametime Meeting Center that is scheduled to start on 10/30/-2, it is likely that this meeting was scheduled in the manner described above.

The "Today's Meeting" view of the Sametime Meeting Center will function properly if you use a Lotus Notes client to delete the Meeting Details document for the meeting. To use the Lotus Notes client to delete the Meeting Details document:

1. From the Start menu of the Sametime server, open the Lotus Notes client. (Choose Start - Run, browse to

C:\Lotus\Domino\nlnotes.exe, and click OK.)

2. Choose File - Database - Open.

3. Select "Local" in the Server drop-down box.

4. Select the Sametime 3.0 Online Meeting Center database (stconf.nsf) and click Open.

5. From the View menu, select "Go To."

6. Select the "All Meetings" view.

7. In the right-hand pane, right-click on the Meeting document for the meeting and select "Clear."

8. Select the "View - Refresh" menu item and select "Yes" to delete the Meeting document.

9. Close the Lotus Notes client.

Sametime server

Supporting dual LDAP directories with Sametime

If the Domino server on which Sametime is installed is configured to support dual LDAP directories, you must also configure the Sametime server to support this directory configuration. To enable a Sametime server to support dual

LDAP directories, you must modify both the Domino server Notes.ini file and the Sametime server Sametime.ini file.

In the Notes.ini file on the Domino server, type in the following settings and values:

ST_UID_PREFIX=*

ST_UID_POSTFIX=*

In the Sametime.ini file on the Sametime server, type the following setting and value into the [DIRECTORY] section:

ST_DB_LDAP_DEREF=3

Sametime server

Unable to attach large whiteboard files to Sametime meetings

When a user attempts to attach a large whiteboard file to a meeting, the user's Web browser may return an error indicating the action is not possible or that the file is too large.

The Domino server configuration limits the size of these files to 10000 Kilobytes by default. To prevent this problem, you must adjust the Domino configuration settings to allow larger files to be posted. To adjust the appropriate Domino server configuration settings:

1. In the Domino directory on the Domino/Sametime server, open the Server document for the Domino/Sametime server.

2. Select the "Internet Protocols" tab.

3. Under the HTTP tab, change the HTTP Protocol Limits -> Maximum size of request content setting from 10000K to an appropriate (higher) value. This setting should specify the size in kilobytes of the largest whiteboard file that you want to allow users to attach to a Sametime meeting.

82

IBM Lotus Sametime 7 Release Notes

Chapter 3 - Known limitations, problems, and workarounds

4. Select the Internet Protocol -> Domino Web Engine tab.

5. In the POST Data -> Maximum POST Data field, enter the same value that you specified in step 3 above. This setting should also specify the size in kilobytes of the largest whiteboard file that you want to allow users to attach to a Sametime meeting.

6. Save and close the server document and restart the Domino/Sametime server.

Sametime server

Unable to import a recorded meeting on i5/OS Sametime

Before you can import a recorded meeting to a Sametime i5/OS server, you must first record a meeting on that server.

The default location for storing recorded meetings is the MeetingArchive directory in the Sametime server Data directory. The MeetingArchive directory is created on the i5/OS server when the first meeting is recorded. If a meeting has never been recorded on the server, the MeetingArchive directory will not exist. Any attempt to import a recorded meeting will fail with a "Path not found" error if the MeetingArchive directory has not been created.

Sametime server

Usage Limits and Denied Entry for Broadcast Meetings

The Sametime Administration Tool contains "Usage Limits and Denied Entry for Broadcast Meetings" settings. These settings are accessible from the Configuration - Audio/Video - Usage Limits and Denied Entry options of the Sametime

Administration Tool and are designed to limit the number of users of the Sametime Broadcast Services.

Administrators should limit the number of users to prevent a large number of users from taxing the server CPU or bandwidth capabilities of the network to the point where meeting performance degrades.

The Usage Limits and Denied Entry for Broadcast Meetings settings allow you to limit the number of:

Audio connections

Video connections

Data connections (screen share and whiteboard)

If a meeting includes multiple activities, users will be rejected once the lowest limit that is specified for any of the activities included in the meeting is reached.

For example, assume a broadcast meeting includes audio, video, and data (screen sharing/whiteboard) and the Usage

Limits and Denied Entry for Broadcast Meetings settings limit the audio connections to 30 users, video connections to

30 users, and data connections to 40 users. When the 31st user attempts to join the Broadcast meeting, the user will be rejected. The user cannot receive the data (screen sharing/whiteboard) portion of the meeting even though that limit is set to 40.

If the Broadcast meeting included only data activities, 40 users would be allowed to join the meeting and the 41st user attempting to join the Broadcast meeting would be rejected.

Sametime Meeting Room client, Sametime server

User cannot save the whiteboard

If a user cannot save the whiteboard, verify that the following two options are selected in the Sametime Administration

Tool Configuration - Meeting Services - General settings:

Allow people to choose the whiteboard in meetings

Allow people to save whiteboard annotations as attachments to the meeting

If both of these settings are selected, and the user still cannot save the whiteboard, see the release note titled "Server display setting must be higher than 256 colors" in the Configuration notes section of these release notes.

83

IBM Lotus Sametime 7 Release Notes

Chapter 3 - Known limitations, problems, and workarounds

Sametime Administration Tool

User ID displays as numbers/characters in Administration Tool

The Sametime Administration Tool contains several logging pages that contain a User ID column. If a user authenticates when accessing the Sametime server, the User ID column displays one of the following:

A Lotus Notes User ID in canonical format

A User Name from a Person document in a Domino directory

A distinguished name from an LDAP directory

If a user does not authenticate and accesses Sametime as an anonymous user, the User ID column displays a series of numbers and characters to represent the anonymous user. For example, an anonymous user may be represented by a series of numbers and characters such as 3810 0c065e13c in the User ID column.

Sametime server

Using Lotus Notes client stops Domino processes on Sametime

A Lotus Notes setup client is automatically installed on the Windows Sametime server during the Sametime server installation. An administrator can start this Notes client on the Sametime server from the Windows desktop by choosing Start - Run and browsing to the C:\Lotus\Domino\nlnotes.exe file. Administrators can use this Lotus Notes setup client to change administration settings in the Domino Directory on the Sametime server and access other

Domino databases on the Sametime server.

Occasionally, launching this Lotus Notes client on the Sametime server may kill the Domino processes running on the

Sametime server. You should not launch this Lotus Notes client during times of heavy server usage. If the Domino process are killed, you must restart the server.

Sametime server

Using self-registration with multiple Sametime servers

You can install multiple Sametime servers in a Domino environment and synchronize the multiple servers to function as a single community. Part of this procedure involves enabling the Directory to replicate between the Sametime servers.

Note: For more information on synchronizing multiple Sametime servers to function as a single community, see the

"Deploying Multiple Sametime Servers" chapter of the IBM Lotus Sametime 7.0 Administrator's Guide.

If you have enabled the Directory to replicate between multiple Sametime servers, and you are also using the self-registration feature, you should enable the self-registration feature on only one of the Sametime servers. (Allowing users to self register from different Sametime servers in a multiple server environment creates duplicate groups in the

Directory. For example, you might see two groups named Sametime Web Users.)

Sametime server

Using "Alt+159" accented characters with user registration

Sametime includes a self-registration feature that enables anonymous users to create Person documents in the

Domino directory on the Sametime server. The self registration feature allows users to enter a User name (first, middle, and last) and Internet password.

Avoid using the "Alt+159" DOS character code in the self-registration interface. Using the "Alt+159" DOS character code in the "Last name" or "Password" fields of the self registration interface on the Sametime server causes the following problems:

Users will receive a "User not authenticated" error when attempting to use the password containing the "Alt+159" character to authenticate with the Sametime Meeting Center.

Users will receive an error message if they try to enter a name containing the "Alt+159" character in the "Last name" field of the self-registration interface.

Note: Generally, DOS character codes should not be used with Sametime. Lotus recommends using Windows code page 1252 with Sametime. With Windows code page 1252, the keyboard combination "Alt+0131" generates the same character as the "Alt+159" DOS character code. Note that using the Windows code page will not prevent the problems described above. The "Alt+0131" and "Alt+0159" Windows code page character may also produce these problems.

84

IBM Lotus Sametime 7 Release Notes

Chapter 3 - Known limitations, problems, and workarounds

Sametime server

Verifying the version number of a Sametime server

If you do not know which version of Sametime is installed, you can use the following URLs to display the Sametime server version numbers:

For Sametime 1.0 and 1.5 servers, the server version number can be accessed through the URL http://servername/buildinfo.txt

For Sametime 2.0 and higher servers, the server version number can be accessed through the URL http://servername/sametime/buildinfo.txt

Note: servername is the name of the Sametime server.

Sametime server

Writing server log information to a text file

This issue applies only to Sametime servers that operate on the AIX or Solaris operating systems.

The Sametime Administration Tool allows you to control where log events are recorded. If the administrator enables logging to a text file, the “Path to log text file” field should also include a filename (for example: “/logfiles/log.txt”).

This configuration generates a log file with a name such as “log_07_Dec_2002.txt”. If no filename is specified with the path, the resulting file would be named “_07_Dec_2002”.

Sametime server

Wrong meeting start time displays when importing a meeting

The Sametime server enables a user to record a Sametime meeting and then export the recorded meeting file

(exporting the file involves saving and renaming the file to a local drive or network drive). The user can then import this recorded meeting file to different Sametime servers to make the recorded meeting available from these servers.

When the user imports the meeting, the meeting start time will display in a read-only field in a meeting creation screen. Note that the meeting start time may be incorrect and will not reflect the start time of the original meeting.

There is no workaround for this problem.

Sametime Administration Tool

"Connection Broken" message for Java Sametime Connect logouts

The Sametime Administration Tool includes a Logging-Community Logins/Logouts view that describes the reasons for logins or logouts to the Community Services. The Community Logins/Logouts view might erroneously report a logout reason of "Connection Broken" when users logout of the Java version of Sametime Connect ("Sametime Connect for browsers").

If a user running Sametime Connect for browsers performs any of the following actions, the Community

Logins/Logouts view might indicate "Connection Broken" as the reason for the logout:

The user logs off "Sametime Connect for browsers."

The user exits "Sametime Connect for browsers."

The user closes the Web browser window in which "Sametime Connect for browsers" is running.

The Community Logins/Logouts view should indicate the reason for these type of logouts is "Normal exit" instead of

"Connection Broken." The administrator can ignore the "Connection Broken" message for these logouts.

Sametime Connect client, Sametime server

"Message received when inviting others to a meeting

The message "You are not allowed to browse the directory because you are not a registered user" may appear when an anonymous user attending a meeting attempts to invite another user to the meeting using the "Meeting - Invite others" option in the menu bar of the Sametime Meeting Room client.

This error message appears when the Configuration - Community Services - Anonymous Access settings in the

Sametime Administration Tool are set to prevent anonymous users from browsing the Directory. (The Meeting - Invite others option contains Directory browsing features.)

85

IBM Lotus Sametime 7 Release Notes

Chapter 3 - Known limitations, problems, and workarounds

To prevent this error message from occurring you must configure the Anonymous Access settings in the Sametime

Administration Tool to enable anonymous users to browse the Directory. To do this, make sure that the "Users cannot browse the Directory" check box in the Configuration - Community Services - Anonymous Access settings of the

Sametime Administration Tool is not selected.

Audio/Video services issues

Sametime server

Audio performance problems or high audio latency

Audio performance problems or high audio latency are sometimes caused by other applications running on a client machine. To prevent these audio problems, it may be necessary to boost the Sametime process (browser and Java

Runtime Environment) to enable the Sametime audio threads to operate at the priority level needed to support low latency audio. You can view a tech note concerning the is issue at: http://www.ibm.com/support/docview.wss?rs=203&uid=swg21159157

Audio/Video services

Echo cancellation in multiple a/v meetings

If two users are participating in more than one audio/video meeting at once, echo cancellation might not work between the two users. For example, if User 1 and User 2 are both attending a scheduled audio/video meeting, and

User 1 begins an instant audio/video meeting with User 2, echo cancellation might not work for either user.

Audio/Video services, Sametime server

Poor audio quality with G.711 audio codec and TCP Tunneling

The Sametime Multimedia Services transmit audio streams using the UDP transport. If UDP is unavailable on a network (either disabled at the routers or firewall), the Multimedia Services tunnel the UDP audio streams through the

TCP transport.

If a client receives the audio stream through a TCP tunneled connection with the Sametime server, and the G.711 audio codec is also being used in the meeting, the client may experience poor audio performance. The G.723 audio codec should be used whenever you expect users to attend an audio meeting through TCP tunneled connections.

Note: The G.711 audio codec is specified in the Configuration - Audio/Video Services - Connection Speed Settings of the Sametime Administration Tool. Generally, the administrator selects the "Meetings with LAN/WAN users" connection profile and selects the 64Kbps "Audio bit rate" setting to select the G.711 audio codec. The G.711 codec is then used in the meeting if an end user de-selects the "People are attending this meeting using a modem" option in the Locations tab of the New Meeting page. (De-selecting this setting invokes the "Meetings with LAN/WAN users" connection profile.)

If your network environment requires that users receive the audio streams via TCP tunneled connections, you must configure the settings in the Sametime Administration Tool so that the G.723 codec is always used in audio/video meetings.

To configure the Audio/Video Services Connection Speed Settings so that the G.723 codec is always used in a meeting, you can do the following:

In the Configuration - Audio/Video - Connection Speed Settings of the Sametime Administration Tool, ensure that the "Type of connection speed settings to use for the default in scheduled and instant meetings" is set to

"Meetings with modem users." ("Meetings with modem users" is the default setting.) This step ensures that the

G.723 audio codec is used by default in all instant audio meetings.

In the Configuration - Audio/Video - Connection Speed Settings of the Sametime Administration Tool, ensure that the "Meetings with modem users" option located beneath the "Audio/Video and Broadcast Connection Speeds" heading has an "Audio bit rate" setting of 6.3Kbps. (6.3Kbps is the default setting.)

86

IBM Lotus Sametime 7 Release Notes

Chapter 3 - Known limitations, problems, and workarounds

(Optional) In the Configuration - Audio/Video - Connection Speed Settings of the Sametime Administration Tool, the administrator can set the "Meetings with LAN/WAN users" option located beneath the "Audio/Video and

Broadcast Connection Speeds" heading to use an "Audio bit rate" setting of 6.3Kbps. (64Kbps is the default setting.) In addition, set the "Video bit rate" to 16Kbps and the "Screen sharing and whiteboard bit rate for broadcast meeting only" to 16Kbps.

Performing this optional step ensures that the G.723 audio codec is used in a meeting regardless of whether the end user selects the "People are attending using a modem" option when setting up a meeting in the Sametime

Meeting Center. If you do not perform this optional step, users who deselect the "People are attending using a modem" option when setting up a meeting will invoke the "Meetings with LAN/WAN users" connection speed settings, which use the G.711 codec by default.

LDAP issues

Sametime server

Administrator cannot attend meetings or use Sametime databases

If you have set up Sametime to connect to an LDAP directory, you must manually add the Sametime administrator to the LDAP directory to enable the administrator to:

Start or attend meetings on the Sametime server.

Use Sametime Discussion or TeamRoom databases on the Sametime server.

The Sametime administrator is specified during the Sametime server installation. The installation creates a Person document for the administrator in the Domino directory on the Sametime server. The administrator is authenticated against the Domino directory when accessing the Sametime Administration Tool.

When Sametime is configured to connect to an LDAP server, all users of the Meeting Services and Community Services are authenticated against entries in the LDAP directory. The Sametime administrator is not added to the LDAP directory by the Sametime installation. As a result, by default, the Sametime administrator can access the Sametime

Administration Tool but cannot start or attend meetings on the Sametime server or use Discussion or TeamRoom databases.

To enable the administrator to create and attend meetings on the Sametime server or use Sametime

TeamRoom/Discussion databases, you must manually create an entry for the administrator in the LDAP directory to which Sametime connects.

For more information about Sametime and LDAP, see the "Using LDAP with the Sametime server" section of the IBM

Lotus Sametime 7.0 Administrator's Guide.

Note: To add a new administrator when Sametime is configured to connect to an LDAP server, you must add the administrator to the Domino directory and provide the administrator with the appropriate ACL settings in the

Sametime databases. For more information, see "Adding a new Sametime administrator" in the "Using the Sametime

Administration Tool" chapter of the IBM Lotus Sametime 7.0 Administrator's Guide.

Sametime server

Can't add groups from Domino LDAP directory to presence lists

If you have configured Sametime to connect to an LDAP directory on a Domino server, and you are unable to add public groups to presence lists in Sametime Connect or other applications, you may need to remove entries from some of the LDAP settings in the Sametime Administration Tool.

If users cannot add groups from a Domino LDAP directory, verify that the following settings have no entry in the

Sametime Administration Tool. If an entry exists, remove it so that the value for the setting is blank.

Where to start searching for people (Located in the LDAP Directory - Basics settings of the Administration Tool)

Where to start searching for groups (Located in the LDAP Directory - Basics settings of the Administration Tool)

You will need to restart the Sametime server after removing the entries from these settings.

87

IBM Lotus Sametime 7 Release Notes

Chapter 3 - Known limitations, problems, and workarounds

Sametime server

Configuring LDAP directory settings after installation

The LDAP search and authentication functionality may not work by default after you install the Sametime server. You must modify the LDAP Directory settings in the Sametime Administration Tool so that these settings are appropriate for the schema of the LDAP Directory Sametime is accessing.

For more information about configuring the LDAP Directory settings, see the "Using LDAP with the Sametime server" section of the IBM Lotus Sametime 7.0 Administrator's Guide (sthelpad.nsf). You can access the .nsf version of the

Administrator's Guide from the "Help" link of the Sametime Administration Tool.

Sametime server

Group members in Exchange server LDAP directory not online

If you set up Sametime to connect to an LDAP server, and you specify a Microsoft Exchange server as the server containing the LDAP directory to be used by the Sametime community, a problem may occur that prevents members of a group in the LDAP directory from appearing online in Sametime client presence lists.

For example, a Sametime Connect user may add a group defined in the LDAP directory on the Exchange server to the presence list in Sametime Connect. The group name in the presence may always indicate "No online people" even though some members of the group are actually online.

This problem occurs because the Exchange server is not publishing the group content attribute of the LDAP directory.

(Exchange servers do not publish the group content attribute by default.)

To solve this problem, the administrator should use the Microsoft Exchange Administration Tool to configure the

Exchange server to publish the group content attribute.

1. From the Microsoft Exchange Administration Tool select "Configuration."

2. Double-click "DS Site Configuration."

3. Click the "Attributes" tab.

4. In the Attributes list, check the "Members" attribute and click "OK" for the change to take effect.

Sametime Connect client, Sametime server

Problems with client Contact lists and LDAP Active Directory

If you have configured the Sametime server to connect to an Active Directory (LDAP) server, you must also configure the "Attribute of a person entry that defines the internal ID of the Sametime user" parameter in the Configuration database (stconfig.nsf) of the Sametime server. This parameter must specify the "DistinguishedName" directory attribute.

If you do not configure the "Attribute of a person entry that defines the internal ID of the Sametime user" parameter, you may see the following problems:

Awareness for some users does not work.

A user's name appears multiple times in the same Contact list.

This parameter is not discussed in any Sametime documentation so you must perform an additional procedure if you are following the instructions in the Sametime documentation that explain how to set up a connection to an LDAP server. For example, to configure a Sametime server to connect to an Active Directory LDAP server:

1. Review the release note titled "Setting up an LDAP connection to an Active Directory server" in these release notes to ensure Active Directory is configured to work with Sametime.

2. Perform all procedures discussed in the "Setting up an LDAP connection" section of the "Using LDAP with the

Sametime server" chapter of the IBM Lotus Sametime 7.0 Administrator's Guide to enable the Sametime server to connect to the LDAP server. Then use the following steps to configure the additional parameter in the stconfig.nsf database.

3. Use a Notes client to open the stconfig.nsf database on the Sametime server.

88

IBM Lotus Sametime 7 Release Notes

Chapter 3 - Known limitations, problems, and workarounds

4. Open the "LDAPServer" document in the stconfig.nsf database.

5. In the "Attribute of a person entry that defines the internal ID of the Sametime user" field, enter the value

"DistinguishedName" and save the document.

6. Close the stconfig.nsf database and restart the Sametime server.

Configuring the server in this way ensures that the Sametime server authentication and search operations always return the value stored for a user in the "DistinguishedName" attribute of the user's person entry in the Active

Directory.

Explanation

To function properly, the Sametime server LDAP directory search and authentication operations must return an internal userID when a user authenticates or adds another user to a Contact List. Sametime requires this userID to be precisely the same string (an exact case-sensitive and space-sensitive match) each time it is returned.

If the "Attribute of a person entry that defines the internal ID of the Sametime user" field is left blank, the Sametime authentication and search operations use the full DN of the user's person entry (not the DistinguishedName attribute) as the userID. Active Directory does not guarantee that the DN will always be returned in the same case-sensitive and space sensitive format.

For example, a user can log in to the server using the lower case distinguished name "cn=john smith,cn=users,dc=ad,dc=com." If another user adds John Smith to a Contact list using the upper case distinguished name "CN=JOHN SMITH,CN=USERS,DC=AD,DC=COM", awareness on John Smith will not work. This problem occurs because Active Directory does not enforce case-sensitivity when returning the DN. Active Directory returns the DN using the same case and spacing that was entered by the user when authenticating to the server or adding the user to the Contact List. Since the Sametime server requires that the internal userID be precisely the same each time it is returned, it assumes that the lower-case John Smith and the upper-case John Smith are different users and awareness does not function properly. This issue may cause John Smith's display name to appear more than once in a user's

Contact list.

Active Directory guarantees that the DistinguishedName attribute is always returned in the same case-sensitive format so these awareness problems do not occur if the DistinguishedName attribute is used as the internal userID of the

Sametime user instead of the DN.

Security issues

Sametime server

Web browser authentication with cascaded address books

This release note applies for Sametime servers set up to operate in a cascaded Directory environment. For Web browser users to be properly authenticated by the server, the following entry must exist in the server's notes.ini file:

NoMABForWebNames=1

Note It is best to set up Directory Assistance on the Sametime server when Sametime is operating in a Domino domain that includes multiple Directories. Generally, you should not use cascaded Directories on a Sametime server.

89

IBM Lotus Sametime 7 Release Notes Chapter 3 - Known limitations, problems, and workarounds

Software Development Kit issues

Sametime server

Location of Software Development Kit release notes

The Sametime SDKs are available from the Lotus section of the IBM developerWorks web site

(www.ibm.com/developerworks).

Sametime Software Development (SDK) release notes are provided with each kit. After you install a toolkit, you can access the toolkit release notes from the Release Note link on the Welcome page (index.html) of the toolkit.

Sametime server

Meeting center page does not show toolkit installation status

When you click the SDK link at the bottom of the meeting center page on the Sametime server, the resulting page does not indicate whether the toolkits are installed, or provide links to the main page for each toolkit. However, you can still download the toolkits from IBM developerWorks ( http://www.ibm.com/developerworks/lotus/products/instantmessaging/). If a toolkit has been installed on the

Sametime server, you can navigate to its main page at the default location, http://<Sametime_ServerURL>/sametime/toolkits/<ToolkitName>/index.html, where ToolkitName is one of the following:

Java Toolkit:

st70javatk

C++ Toolkit:

st70cpptk

COM Toolkit:

st70comtk

Sametime Links Toolkit:

st70linkstk

Community Server Toolkit:

st70commsrvrtk

Directory and Database Access Toolkit:

st70ddatk

Sametime server

Problem using "Extended Live Names" Sametime C++ Toolkit sample

When a user logs in with the "Extended Live Names" sample program in the Sametime C++ toolkit, you cannot invite the user to join a chat from a Sametime meeting room.

Sametime server

Problems running Sametime Java Toolkit samples

Developers might experience problems running the Sametime Java Toolkit samples that use the Meeting Services API, such as: Meeting Applet - Chat and Audio; Meeting Applet - Chat, Audio, and Video; Broadcast; and Meeting Room.

Sametime server

STLinks samples and applications only connect on port 80

On the i5/OS, AIX, and Solaris platforms, the STLinks samples provided with the Sametime server, and applications created with the STLinks toolkit, must use HTTP on port 80 to connect to the Sametime Server.

To ensure that STLinks applications can connect to the Sametime server, one of the following configurations must exist:

The Sametime/Domino HTTP server must be configured to listen for HTTP connections on port 80.

The Sametime Community Services must be configured to listen for HTTP-tunneled connections on port 80.

If the HTTP server is configured to listen for HTTP connections on a port other than port 80, and the Community

Services are also configured to listen for HTTP-tunneled connections on port other than 80 (or are not listening for

HTTP-tunneled connections at all), the STLinks applications will not connect to the server.

90

IBM Lotus Sametime 7 Release Notes

Chapter 3 - Known limitations, problems, and workarounds

Enterprise Meeting Server issues

Enterprise Meeting Server and server clusters

Edited whiteboard not available for display

If you attach a whiteboard file to a meeting on the Enterprise Meeting Server (EMS), and then edit this file and reattach it while the meeting is active, the edited version of the whiteboard file will not be available for display during the meeting. The scenario below illustrates this problem:

1. A user creates a meeting on the EMS and selects the Start Now option to start the meeting immediately.

2. While the meeting is active, the user attaches a file named whatever.bmp to the meeting.

3. As expected, the file appears on the Meeting Details page and is available for display in the whiteboard during the meeting.

4. The user makes edits to the whatever.bmp file on the local operating system and saves the file again.

5. The user attaches this edited version of the whatever.bmp file to the meeting.

6. A duplicate entry for the whatever.bmp file appears on the Meeting Details page. However, the edited version of the whatever.bmp file does not appear in the whiteboard and cannot be displayed in the whiteboard. The only available whatever.bmp file is the original one that was attached in step 2 above.

Enterprise Meeting Server and server clusters

Meeting usage limit issue with the EMS

An administrator can use the EMS Administration Tool to set Meeting Services usage limits for Sametime servers that are attached to the EMS and operate as part of a Meeting Services cluster. For example, the administrator can specify a maximum number of meetings that can be active in the server cluster at any one time.

When an end user schedules a meeting, a Booking Agent component on the EMS determines if the meeting exceeds the maximum number of meetings for the cluster as specified by the administrator. For example, if the administrator has set the maximum number of meetings at 50 and an end user attempts to schedule the 51st meeting for a specific time slot, the end user receives a message to schedule the meeting for a different time.

Note that the Booking Agent assumes that each meeting will be active the entire time for which it is scheduled. If an end user schedules a meeting to last two hours, the Booking Agent assumes this meeting will be active the full two hours even if the meeting ends one hour early.

Because of this issue, the EMS may prevent end users from scheduling meetings when the number of meetings active on the server is less than the maximum number of meetings allowed by the administrator. This scenario can occur when meetings end earlier than their scheduled time. To further illustrate this issue, consider the scenario below:

1. The administrator sets a maximum active meeting limit of 50 meetings.

2. End users have scheduled meetings so that 50 meetings should be active between 8 AM and 10 AM.

3. Twelve meetings that were scheduled to end at 10 AM actually end at 9 AM so that only 38 meetings are active on the server from 9 AM to 10 AM.

4. Any user attempting to schedule a meeting for the 9 AM to 10 AM time slot will be rejected even though the actual number of active meetings on the server is less than 50. This issue occurs because the Booking Agent assumes that each meeting remains active for the entire time it was originally scheduled.

Enterprise Meeting Server and server clusters

Users cannot connect to an EMS meeting after server failover

If a user is attending a meeting that occurs on a Sametime server attached to the EMS, and the Sametime server hosting the meeting fails, the EMS performs the operations needed to start the meeting on a different Sametime server so that the meeting remains available to the end users.

91

IBM Lotus Sametime 7 Release Notes Chapter 3 - Known limitations, problems, and workarounds

In this scenario, a Reconnect button becomes available on the end user's screen at the time the Sametime server fails.

If the user selects this Reconnect button, the expectation is that the Meeting Room client will reload to the user's screen and the meeting will continue on the different Sametime server. However, when the user clicks the Reconnect button, the Meeting Room client does not reload and the user does not join the meeting on the different Sametime server.

To reconnect to the meeting, the user must close the dialog box containing the Reconnect button, return to the

Meeting Details page, and then click the Attend the Meeting link to reload the Meeting Room client. The client then connects to the meeting that the EMS has started on the different Sametime server.

Linux Client issues

Linux clients

Changing a user's online status on Linux systems

On Linux systems, there is no way to change a user's online status. This problem can be fixed by using the version of the 1.4 Java plugin supplied by IBM on our Web site.

Linux clients

DBCS limitations/known issues with Sametime Linux clients

This section lists the limitations and known problems with Linux clients.

Netscape crashes with Sun JRE 1.4.1 plugin

A Netscape 7.02 browser that operates with the Sun JRE 1.4.1 Plug-in may crash when you click menu items in the

Meeting Room client or Java Sametime Connect. The workaround for this problem is to use the Sun JRE 1.4.0_03

Plug-in with the Netscape 7.02 browser.

MRC window refresh issue

When you open the Meeting Room client, you may only see the Screen sharing/Whiteboard panel. Resize the Meeting

Room client window or click the maximum button in the Meeting Room client window to display the entire Meeting

Room client.

Problems related to Sun JRE

There is a problem in the Sun JVM 1.4.0_03 with converting Unicode to DBCS native code for display in the window titles. This problem causes the DBCS meeting name to display incorrect characters (such as all question marks or unreadable characters) in the Window titles. The Sun JRE 1.4.1 Plug-in does not have this issue.

Some DBCS characters in the invitation dialog sent from the Meeting Room client display as incorrect characters

(such as all question marks or unreadable characters) in a Netscape browser that operates with the Sun JRE 1.4.0 plugin. The Sun JRE 1.4.1 plugin does not have this issue.

The Screen sharing tool cannot display application titles that contain DBCS characters well in the Netscape browser with the Sun JRE 1.4.0 Plug-in. The Sun JRE 1.4.1 Plug-in does not have this issue.

The search function in the Directory applets does not work due to issues with the Sun JRE.

Users that log in to the Sametime Meeting Center using DBCS characters cannot launch the Meeting Room client from a Web browser that uses the Sun JRE 1.4.0 Plug-in. The Sun JRE 1.4.1 Plug-in does not have this issue.

92

IBM Lotus Sametime 7 Release Notes

Chapter 3 - Known limitations, problems, and workarounds

The DBCS users cannot start a test meeting from Java Sametime Connect or the Sametime Meeting Center from a web browser that uses the Sun JRE 1.4.0 Plug-in. The Sun JRE 1.4.1 Plug-in does not have this issue.

<Japanese only>

You cannot enter a Japanese message with FEP on chat/instant-meeting client on the Linux OS. When sending a chat message to a user who is away, incorrect characters (such as all question marks or unreadable characters) will display in the away message window.

<Korean only>

You cannot type Korean characters in the fields below.

The search field of Directory applets

The login field of Java Sametime Connect and the Sametime Meeting Center

Chat panel in Java Sametime Connect and the Meeting Room Client

The reminding message field of "Alert me..." function in Java Sametime Connect

This problem occurs because the AWT component is not well defined in the Korean font.property file

The Korean characters in the data entry fields of Java Sametime Connect display incorrectly (for example, the characters display as all question marks or unreadable characters). This problem occurs because of insufficient definition in the font.property file.

The Korean characters in the chat text field and attachment list fields display incorrectly. This problem occurs because of insufficient definition in the font.property file.

The Korean strings display incorrectly in the polling tab of the Broadcast client.

<Simplified Chinese only>

Some DBCS strings in the menu items of Java Connect or the Meeting Room client are truncated resulting in truncated words within the menus.

The Korean index in help is not working

<Korean only>

Clicking the Korean character in the index of End User Help will not jump you to the appropriate location in the index.

Sametime Meeting Room client

Linux Meeting Room client does not support audio/video

The Linux version of the Sametime Meeting Room client does not support audio/video.

Linux clients

Log on to Sametime dialog problem with Sametime Connect on Linux

When Sametime Connect for browsers runs on the Linux operating system, the "Log on to Sametime" dialog box (and other dialog boxes in the Sametime Connect client) may contain incorrect or unreadable characters. This problem has been seen in the Russian and Polish language versions of Sametime Connect for browsers on Linux and appears to be a font handling problem in the Linux operating system.

Linux clients

Menu items with checkboxes on Linux systems

Menu items that have a corresponding checkbox associated with them do not work under Linux. This is a known Java problem dealing with pop up menus.

On Linux systems, this problem can be fixed by using the version of the 1.4 Java plugin supplied by IBM on our Web site.

93

IBM Lotus Sametime 7 Release Notes

Chapter 3 - Known limitations, problems, and workarounds

Linux clients

Problem selecting menu items on Linux client with Netscape

On Linux systems, selecting an item from a menu may crash Netscape. This is a known Java problem.

This problem can be fixed by using the version of the 1.4 Java plugin supplied by IBM on our Web site.

Linux clients

Using the Undo Full Screen button with Linux Meeting Room client

When a user is attending an online meeting with the Linux Meeting Room client, the user can select a View-Make

Shared Area Full Screen option to expand the Meeting Room client browser window to the full screen mode.

After expanding the Meeting Room client browser window, the "Undo Full Screen" button does not appear in the expanded window and may give the user the impression that it is impossible to return the window to its previous, smaller state.

Note that the "Undo Full Screen" button is available from a browser window that appears behind the expanded, full-screen version of the Meeting Room client window. The user can return the browser window to its previous state, but must navigate to the window that is behind the expanded Meeting Room client window to do so.

AIX issues

Sametime server

Killing the ST Mux process on an AIX Sametime server

When the Sametime Multiplexer (ST Mux) process is installed as a standalone application on the AIX operating system, you cannot kill the ST Mux process by typing quit or exit at the server console.

To kill the ST Mux process, you must grep for the process and then use the kill command to terminate the process.

For example, you can enter ps -ef | grep stmux and then kill -9 to terminate the process.

Solaris issues

Sametime server

Audio/Video issue with TLS-enabled SIP Connector

The following issue occurs when all of the following are true:

SIP Connectors are deployed to enable two Sametime communities to communicate using SIP (Sametime

Community 1 and Sametime Community 2).

The SIP Connectors in each community are configured to support TLS connections on port 5061. (To support TLS encryption for the SIP Connectors, you open the ExternCommunity document in the stconfig.nsf database on the

Sametime server and select either "Mandatory" or "Enabled" as the Encryption level.)

User 1 is connected to Sametime Community 1 and User 2 is connected to Sametime Community 2. These two users communicate and have presence capabilities with each other through the services provided by the SIP

Connectors deployed in each community.

94

IBM Lotus Sametime 7 Release Notes

Chapter 3 - Known limitations, problems, and workarounds

User 1 invites User 2 to a meeting that includes audio/video.

User 2 attends the meeting, and while the meeting is active, User 2 closes the Meeting Room client and then relaunches the Meeting Room client and reattends the meeting.

In this scenario, User 1 will appear as offline to User 2 when User 2 reattends the meeting, even though User 1 is actually online. User 1 will appear as online to User 2 only if you restart the STCommunity Launch SA and ST SIP

Connector SA services.

This problem does not occur if the SIP Connectors in each community are not configured to use TLS.

International issues

Sametime server

Audio/video meetings without video installed (Spanish i5/OS)

On Spanish versions of the Sametime i5/OS server, the following issue occurs:

If a user selects the Audio/Video option when creating a meeting, but Video capabilities are not installed on the server, a script error displays.

Sametime Meeting Room client

Bitmaps may not display clearly in shared PowerPoint files

If bitmap images are inserted into a PowerPoint (PPT) file, the bitmap images may not display clearly when the PPT file is displayed from the Meeting Room client whiteboard.

Sametime server

Changing the path where recorded meetings are stored

An administrator can open the Sametime Administration Tool, select Configuration -> Meeting Services -> General, and use the "Save recorded meetings in the following location" field to change the location where recorded meetings are stored.

If you change the default recorded meeting storage path, you must add a slash "/" to the end of the path. If you do not include a slash, the meeting may not be recorded properly.

Sametime Administration Tool

DateTime format incorrect when admin runs in a Firefox browser

If a Mozilla Firefox browser is used to access the Sametime Administration Tool on any international version of the

Sametime server, the DateTime format may not display correctly in the administration tool pages.

Sametime server

DBCS user names and meetings on a Solaris server (CJKT)

With CJKT language versions of the Sametime Solaris server, some DBCS user names may display as garbage characters when attending a meeting.

If a user with one of these DBCS names schedules a meeting, and then attends it, the user does not receive moderator privileges because the user's name displays as garbage characters. Also, this user cannot end the meeting; the meeting must run its entire scheduled course.

To avoid this issue, users with these DBCS names should use an English version of their user name when attending and scheduling meetings.

95

IBM Lotus Sametime 7 Release Notes

Chapter 3 - Known limitations, problems, and workarounds

Sametime Administration Tool

Domino admin with Polish or Turkish characters cannot log in

When Sametime operates on an operating system set to the Polish or Turkish locale, and a Domino administrator has a user name that includes local characters, this administrator cannot log in to Sametime.

Sametime Meeting Room client

Excel file display issues with the Russian whiteboard

With Russian versions of the Sametime Meeting Room client, Excel files attached to the whiteboard may not display correctly.

Sametime server

Excel files and Brazilian/Portuguese Print Capture

The following issue occurs with the Brazilian/Portuguese version of the Print Capture utility. When you print an Excel file to the FST format so that the file can be attached to the whiteboard, the table lines, and the column names or row names may not display correctly when the file is displayed in the whiteboard.

Sametime server

Font issue in Chinese STLinks Toolkit

The following issue occurs in Chinese versions of the STLinks Toolkit:

When a user logs in to the STLinks sample page and clicks another user's name to start a chat, the font in the status bar may get smaller.

Sametime Meeting Room client

French character issue with screen sharing

When a user shares an application with a remote user, and the remote user inputs French characters into the shared application, the characters may not work correctly in the shared application.

Sametime server

Garbage characters appear in logging field on i5/OS server

This issue has been seen on the following language versions of the i5/OS Sametime server: Chinese, Japanese,

Spanish, and French. This issue may also occur with other language versions of the server.

1. Open the Sametime Administration Tool, and select Logging > Community Logins/Logouts

2. The "Reason" field may be populated with either garbage characters or English characters instead of the character appropriate for the locale.

Sametime Broadcast client, Sametime Connect client, Sametime Meeting Room client

GB18030 issues with Simplified Chinese

Some Sametime components may have problems caused by GB18030 in Simplified Chinese versions of Sametime clients.

96

IBM Lotus Sametime 7 Release Notes

Chapter 3 - Known limitations, problems, and workarounds

Sametime Broadcast client, Sametime Connect client, Sametime Meeting Room client, Enterprise Meeting Server and server clusters

General DBCS issues

The following DBCS issues occur with Asian language versions of Sametime clients.

If a user sends a Web page during a meeting, and the Web page URL includes DBCS characters, the URLs may not display correctly to the users that receive it.

If a meeting is being recorded and a user enters DBCS characters on the whiteboard, the DBCS characters may not display correctly when the recorded version of the meeting is played back.

If an FST file is attached to the whiteboard, and the path to this FST file includes DBCS characters, the path may not display correctly.

If a user with a name that includes DBCS characters attends an N-way chat, the DBCS user name may appear truncated in the participant's pane of the N-way chat window. The DBCS user name may appear as "?..".

When Sametime runs on UNIX or i5/OS servers, a user name with DBCS characters may not display in the

Meeting Room participant list or the Sametime Connect client.

If you are using the Sametime Enterprise Meeting Server (EMS), users should not use DBCS characters in meeting names. This is a limitation of the WebSphere Application Server on which the EMS runs.

Enterprise Meeting Server and server clusters

International issues with EMS Meeting Room client Send Web Page

This issue may occur for these language versions while attending a meeting on a Sametime server connected to the

EMS:

S.Chinese, T.Chinese, French, Finnish, Korean, Danish, Swedish

When using the Meeting Room client 'Send Web Page' feature to send URLs to meeting attendees, non-encoded URLs may display to the end users.

Sametime Connect client

International issues with Sametime Connect

In the Sametime Connect for browsers client, users can pass the cursor over icons in the client to display tool tips. In translated versions of this Sametime Connect client, the tool tips may stop functioning correctly. You can correct this problem by shutting down the Sametime Connect client and then launching it again.

If a Sametime Connect for browsers user enters a Turkish character in the "Add to Connect List" dialog box, the search for this user may fail.

In Russian versions of the Sametime Connect for the desktop client and the Sametime Connect for the browsers client,

Unicode (U+00AD) characters entered into the client may not display correctly.

In Dutch versions of the Sametime Connect client, the Alert mesage dialog that indicates a user has changed status may be so small that it is difficult to view.

Linux clients

International issues with Sametime Linux clients

With the Finnish language version of the Linux Sametime Meeting Room client, the local characters in Window titles may display as square boxes or blanks.

With the Polish language version of the Linux Sametime Meeting Room client, some menus may display garbage characters.

DBCS characters or local characters may display as garbage characters in the Sametime Administration Tool when this tool is opened from a Web browser that runs on the Linux operating system.

97

IBM Lotus Sametime 7 Release Notes

Chapter 3 - Known limitations, problems, and workarounds

When playing back a recorded meeting in a Russian version of the Linux Sametime Broadcast client, garbage characters may display in meeting presentations. Garbage characters may also display in other Sametime Java applet clients that run on Linux. To prevent this from occurring, use this workaround:

1. Install the IBM JVM 1.4.2.

2. Open a command window, and change to the Web browser plugins directory.

3. Run the following command: ln -s <IBM jvm root dir>/jre/bin/libjavaplugin_ojigcc3.so libjavaplugin_oji.so

4. Change the locale to ru_RU.iso88595

5. Launch the browser.

Sametime server

International issues with the AIX Sametime server

The following issues may occur with International versions of the AIX Sametime server.

With Chinese versions of the AIX Sametime server, some local characters on the Sametime Administration Tool pages may display as garbage characters.

With Japanese versions of the AIX Sametime server, the font of Japanese characters sent from the Sametime Connect for Windows client may not be consistent with the default font settings of the user's computer.

With Japanese versions of the AIX Sametime server, status messages that display in the Sametime Connect for browsers client may display as garbage characters.

With Japanese versions of the AIX Sametime server, text may appear unreadable or display garbage characters. This issue occurs because the Japanese font properties file (font.properties.ja) does not include any definition for JIS X

0201. To fix this problem, install a TrueType JIS X 0201 font and modify the font.properties.ja file accordingly.

If the operating system is set to a DBCS language locale, you cannot install the AIX Sametime server. The operating system must be set to a SBCS language locale to install the server.

Sametime Meeting Room client

Issues with Chinese/Japanese versions of the Meeting Room client

The following issues occur on Japanese and Chinese versions of the Sametime Meeting Room client:

When attending a Web conference, different font sizes may appear for buttons and menu items. (Japanese,

Simplified Chinese, Traditional Chinese)

When replaying a recorded meeting, different font sizes appear for the menu items and the status bar. (Simplified

Chinese)

When attending a Web conference, users may see absonant (mismatched) fonts in some sentences. (Simplified

Chinese)

Sametime Broadcast client, Sametime Meeting Room client

Issues with Portuguese and Swedish Secure Desktop Installer

The Portuguese and Swedish versions of the Secure Desktop Installer may not successfully install clients on a

Windows XP operating system that uses the Sun JVM.

Run the Secure Desktop Installer with the Microsoft VM installed on the client computer. After the installation completes, install the Sun JVM to support the Sametime clients.

98

IBM Lotus Sametime 7 Release Notes Chapter 3 - Known limitations, problems, and workarounds

Sametime Meeting Room client

Japanese characters missing in FST file name

Some Japanese characters may not appear in a whiteboard file saved in the FST format.

Sametime Meeting Room client

Japanese Meeting Room client and Firefox browser

When the Japanese Meeting Room client runs in the Firefox Web browser, the following issues may occur:

Users cannot paste Japanese characters into the chat field.

Japanese characters entered into the chat field may not be transmitted properly to other meeting participants.

Sametime server

Java script error importing recorded meetings (Japanese server)

On Japanese versions of the Sametime server, users may see JavaScript errors when importing a recorded meeting.

To prevent this issue, delete the Temporary Internet files from the system.

Enterprise Meeting Server and server clusters

Locale issues when installing the EMS and required software

Operating system and locale issues can prevent you from successfully installing the EMS and all of its associated software. For some languages, you must install the native language version of the operating system and then switch the operating system locale to the US locale before installing the EMS. For other languages, you must install the US version of the operating system and then switch the operating system locale to the native language locale before installing the EMS. Follow the guidelines below when installing International versions of the EMS.

For Japanese, Korean, and Simplified Chinese versions:

1. Install the native language version of the operating system.

2. Switch the operating system from the native locale to the US locale.

3. Install DB2, WebSphere MQ, and the WebSphere Application Server with the locale set to US.

4. Install the language version of the EMS with the locale set to US.

5. Configure the EMS and connect Sametime servers to the EMS with the locale set to US.

6. Change the locale for all servers to the native language locale.

7. Start all servers with the language set to the native language locale.

For Russian, Polish, Danish, and Norwegian versions:

1. Install the US version of the operating system.

2. Switch the operating system from the US locale to the native operating system locale.

3. Install DB2, WebSphere MQ, and the WebSphere Application Server.

4. Install the language version of the EMS.

5. Configure the EMS and connect Sametime servers to the EMS.

6. Start all servers with the language set to the native language locale.

Sametime server

Logging into Sametime with Domino alternate names

With Asian language versions of Sametime 7.0, a user can enter a name from the "Alternate Name" field of the user's

Person document to log on to the Sametime Connect client, browse the directory, and perform search functions.

Awareness does not work for a user logged in with an Alternate Name. The Alternate Name will not display in the presence lists of any Sametime clients.

99

IBM Lotus Sametime 7 Release Notes

Chapter 3 - Known limitations, problems, and workarounds

Sametime Meeting Room client

Mnemonics/ADA usage

This release note discusses ADA issues for International versions of the Sametime server.

Due to technical limitations, the mnemonics in the menus of Sametime clients will not display. For detailed information about mnemonics available in specific dialog boxes, see the topic "Mnemonics" in the Sametime User's

Guide available from the Documentation link on the Sametime server home page.

Do not use the ALT key as a mnemonic key to activate menu options. Use the ALT key to turn the mnemonics on or off.

Mnemonics are also turned off when the user enters a valid mnemonic to activate a menu option.

Sametime Meeting Room client, Sametime server

Polish character display problems in recorded meetings

When playing back a recorded meeting, some Polish characters in the whiteboard may not display correctly.

Sametime Meeting Room client

Portuguese, Swedish Secure Desktop installations and Sun VM

The Portuguese and Swedish versions of the Secure Desktop Installer may not successfully install Sametime client applications on a computer configured with the Windows XP operating system and the Sun JVM.

To workaround this issue, ensure the Microsoft VM is installed and active on the client system, and then use the

Secure Desktop Installer to install the Sametime applications.

Sametime Meeting Room client

Problem attaching whiteboard file that uses GB2312 characters

On Chinese versions of the Sametime server, users may experience problems attaching a whiteboard file to a meeting if the file contains GB2312 characters.

To enable users to attach whiteboard files containing GB2312 characters:

1. Stop the Sametime server.

2. Install the Sun Microsystems JVM 1.5. (This JVM installs to c:\program files\java\jre1.5.0_04.)

3. Copy the jre1.5.0_04 directory to the Domino directory. (The copied directory will reside at c:\Program

Files\lotus\domino\jre1.5.0_04.)

4. Start the Sametime server.

5. Use the example below to modify a registry entry so that it points to this new JVM:

Set the HKEY_LOCAL_MACHINE\SOFTWARE\Lotus\Sametime\MeetingServer\Services\JavaServiceManager\Path registry entry to "jre1.5.0_04/Bin/Java.exe"

6. Restart the Domino server.

Enterprise Meeting Server and server clusters

Problem with whiteboard files with DBCS filenames with EMS

This problem occurs when a user schedules a meeting from the user interface of the EMS, and attaches a whiteboard file that has a filename containing DBCS characters.

When a user attempts to download this file from the Meeting Details document, the File Download dialog displays the message "You are downloading the file..." and includes a file name that is different from the real file name.

100

IBM Lotus Sametime 7 Release Notes Chapter 3 - Known limitations, problems, and workarounds

Sametime Administration Tool

Problems authenticating admin name with Turkish characters

The Sametime server might not be able to authenticate a Sametime Administration Tool user whose name contains

Turkish characters.

Sametime server

Recorded meetings not sorted correctly on Korean EMS

The following issue may occur when searching for meetings from the user interface of the Korean EMS:

1. From the Meeting Center, select "All Meetings" in the search field and click the Search button.

2. In the meeting list, select "Status."

Meetings that have a status of "Finished," "Active," or "Scheduled," are grouped together but meetings that have a status of "Recorded" appear at various places in the list and are not grouped together under a single instance of the

"Recorded" heading.

Sametime Connect client

Sametime Connect for browsers group sorting issue

In the Sametime Connect for browsers client, the group sorting does not include language-specific character sorting order.

Sametime Connect client

Sametime Connect for desktop does not support unicode display

The Sametime Connect for the desktop client does not support unicode display of special characters.

Sametime Administration Tool

Sametime service status displays incorrectly in the admin client

If you are using a browser set to a non-English locale to administer the Sametime server, the Server Overview feature in the Sametime Administration Tool might display the status of the first Sametime service incorrectly.

Sametime server

Scrambled characters in the Sametime log

When Sametime 7.0 is installed on an International language version of Domino, enable UTF8 for HTML output. If

UTF8 for HTML output is not enabled, the meeting names in some views of stlog.nsf become scrambled.

Sametime Administration Tool

Scroll bars do not appear on the Server Overview page

This issue occurs on Japanese versions of the Sametime server. If you use a Firefox browser to view the Server

Overview page in the Sametime Administration Tool, the scroll bars may not display near the title of the page.

You can scroll the page by clicking on the page and then using the mouse to drag it up or down.

Sametime server

Some logging fields blank on International UNIX servers

This issue occurs on all International versions of the Solaris Sametime server.

In the Logging - Community Logins/Logouts page, the Application Type fields and Reason fields are blank.

Note that information will appear in these fields after the IBM Lotus Web Conferencing Audio Adapter for Premiere

Conferencing 7.0 is installed.

101

IBM Lotus Sametime 7 Release Notes

Chapter 3 - Known limitations, problems, and workarounds

Sametime server

STLinks Toolkit Sample Page cannot display content

With Russian versions of the Sametime server, the Sample Page of the STLinks Toolkit may have problems displaying content.

To prevent this issue:

1. Use a text editor to open the Res.js file in the following directory:

<root>\Lotus\Domino\Data\domino\html\sametime\stlinks\Ru

2. Switch the system input to EN.

3. Find the line: ERR_MSG[0x80002001] = " "

4. In the line above, type this text string within the double quotes:

%s chose not to be disturbed now and cannot be contacted. \r\nYou can try again when %s becomes active.

For example:

ERR_MSG[0x80002001] = "%s chose not to be disturbed now and cannot be contacted. \r\nYou can try again when %s becomes active. "

5. Find the line: TIP_OFFLINE = " ".

In this line, type this text string within the double quotes:

%s is offline

For example:

TIP_OFFLINE = "%s is offline"

Sametime Meeting Room client

Using IME with screen sharing

With Asian language versions of the Sametime Meeting Room client screen sharing tool, you can use IME on both the client computer that is hosting an application and the client computer that is sharing an application to enter characters in a shared application.

However, because the IME mode of the operating system may cause some applications to behave differently than others, it is highly recommended that you use IME on the host computer to enter the characters.

To control IME on the host computer, you can use combinations such as "Ctrl+ALT", "Ctrl+Shift", and "Ctrl+Space."

Korean-only note:

Korean users must use the the Korean key combinations that correspond to those described above. The behavior is the same as pressing the corresponding keys on the host computer.

Sametime server

Whiteboard file issue with UNIX server using Japanese locale

The following scenario illustrates a whiteboard save problem that can occur when an AIX or Solaris Sametime server is configured to use the Japanese (EUC-JP) locale.

1. During a meeting, a user saves a whiteboard file so that the file is saved and available from the Meeting Details document when the meeting ends.

102

IBM Lotus Sametime 7 Release Notes

Chapter 3 - Known limitations, problems, and workarounds

2. After the meeting has ended, the user accesses the Meeting Details document and then saves this whiteboard file to the local operating system (Windows - Japanese).

3. The user creates a new whiteboard meeting on the Sametime server and attempts to attach the whiteboard file on the local operating system to the new Sametime meeting.

The user will see an error when attempting to attach the whiteboard file to the new meeting. The process of attaching the file does not complete successfully.

103

IBM Lotus Sametime 7 Release Notes Chapter 3 - Known limitations, problems, and workarounds

104

IBM Lotus Sametime 7 Release Notes

Chapter 4 - Documentation updates

Chapter 4 - Documentation updates

Administrator's Guide

Audio/Video services

Cannot attend audio/video meeting if video limit is reached

Several topics in the "Configuring the Audio/Video Services" section of the IBM Lotus Instant Messaging and Web

Conferencing (Sametime) 7.0 Administrator's Guide include the following statement:

You can set a maximum number of video connections that is smaller than the maximum number of audio connections.

When the video limit is reached, users can communicate with audio, but video is unavailable.

This statement needs to be clarified as follows:

If a user attempts to enter an instant meeting that includes audio and video, and either the audio or video limit is reached, the user will not be able to use either audio or video. However, if the administrator has set the video limit to be higher than the audio limit, the user can attempt to attend the meeting using audio only (without video), and the call will succeed.

This statement is included in the following topics:

"Setting a maximum number of interactive audio connections for all instant meetings"

"Setting a maximum number of interactive video connections for all instant meetings"

"Setting a maximum number of interactive audio connections for all scheduled meetings"

"Setting a maximum number of interactive video connections for all scheduled meetings"

Sametime server

Corrections for configuring Sametime.ini to support SSL

The "Working with Sametime Security" chapter of the administrator's guide contains a set of instructions that explain how to ensure access to Sametime servlets when the Domino server requires SSL for all connections.

One step in these instructions indicates that you must add the following lines to the Sametime.ini file:

Javax.net.ssl.keyStore=<path>\stkeys.pfx

Javax.net.ssl.trustStore=<path>\stkeys.pfx

Javax.net.ssl.keyStorePassword=<your password>

Javax.net.ssl.trustStorePassword=<your password>

Note that when adding these lines to the Sametime.ini file, you cannot use the uppercase "J" at the start of each line.

You must use the lower case "j" as shown in the example below: javax.net.ssl.keyStore=<path>\stkeys.pfx javax.net.ssl.trustStore=<path>\stkeys.pfx javax.net.ssl.keyStorePassword=<your password> javax.net.ssl.trustStorePassword=<your password>

Sametime server

SIP Gateway setup instructions for Sametime on UNIX

You can set up the SIP Gateway for a Sametime server that runs on the AIX or Solaris operating systems, although this procedure is not discussed in the Sametime 7.0 Administrator's Guide.

For information about this set up procedure, see the release note titled "Setting up the SIP Gateway for Sametime on

UNIX" in these release notes.

105

IBM Lotus Sametime 7 Release Notes

Chapter 4 - Documentation updates

Quick Start Guide

Sametime Meeting Room client, Sametime server

The icon of share a program is incorrect in Quick Start Guide

1. Go to http://<Sametime_server>/sametime/stquickstartguide/

H_SHARE_INFORAMTION_DURING_SAMETIME_MEEINGS_8404_OVER.html#H_SHARE_INFORAMTION_DURING_S

AMETIME_MEEINGS_8404_OVER_MIDTOPIC_394449977629408373

2. "Screen Sharing " help is displayed.

The icon of share a program is incorrect.

User's Guide

Sametime Meeting Room client

Mnemonic for the Show Startup Log menu option missing

The Sametime end user help available from the Documentation link on the Sametime server home page contains a

"Mnemonics in the Meeting Room" topic that describes all mnemonics associated with menus in the Meeting Room client.

This topic does not list the mnemonic associated with the "Show Startup Log" option in the Conference menu of the

Sametime Meeting Room client.

The mnemonic associated with the Show Startup Log option is the keyboard letter H.

106

IBM Lotus Sametime 7 Release Notes

Chapter 5 - Notices and Trademarks

Chapter 5 - Notices and trademarks

Notices

Audio/Video services, Sametime Administration Tool, Sametime Broadcast client, Sametime Connect client, Sametime Meeting Room client, Linux clients, Sametime server, Enterprise Meeting Server and server clusters, Web browsers

Notices

This information was developed for products and services offered in the USA. IBM may not offer the products, services, or features discussed in this document in all countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to:

IBM Director of Licensing

IBM Corporation

North Castle Drive

Armonk, NY 10504-1785

U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country/region or send inquiries, in writing, to:

IBM World Trade Asia Corporation Licensing

2-31 Roppongi 3-chome, Minato-ku

Tokyo 106, Japan

The following paragraph does not apply to the United Kingdom or any other country/region where such provisions are inconsistent with local law:

INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY

OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF

NON-INFRINGEMENT, MERCHANTABILITY, OR FITNESS FOR A PARTICULAR PURPOSE.

Some states do not allow disclaimer of express or implied warranties in certain transactions; therefore, this statement may not apply to you.

This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice.

Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this

IBM product, and use of those Web sites is at your own risk.

IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you.

107

IBM Lotus Sametime 7 Release Notes Chapter 5 - Notices and trademarks

Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information that has been exchanged, should contact:

Lotus Software

IBM Software Group

One Rogers Street

Cambridge, MA 02142

USA

Such information may be available, subject to appropriate terms and conditions, including in some cases payment of a fee.

The licensed program described in this document and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement, or by any equivalent agreement between us.

Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems, and there is no guarantee that these measurements will be the same on generally available systems.

Furthermore, some measurements may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment.

Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements, or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility, or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products.

All statements regarding IBM's future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only.

This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental.

108

IBM Lotus Sametime 7 Release Notes Chapter 5 - Notices and trademarks

Trademarks

Audio/Video services, Sametime Administration Tool, Sametime Broadcast client, Sametime Connect client, Sametime Meeting Room client, Linux clients, Sametime server, Enterprise Meeting Server and server clusters, Web browsers

Trademarks

IBM, the IBM logo, AIX, DB2, Domino, Freelance, Freelance Graphics, iSeries, i5/OS, Lotus, Lotus Instant Messaging and Web Conferencing, Lotus Notes, LotusScript, Notes, 1-2-3, OS/400, Quickplace, S/390, Sametime, SmartSuite,

WebSphere, Workplace, Workplace Managed Client, z/OS, and zSeries are trademarks or registered trademarks of

IBM Corporation in the United States, other countries, or both.

Additional IBM copyright information can be found at: http://www.ibm.com/legal/copytrade.shtml

Java and all Java-based trademarks and logos are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.

Microsoft, Windows, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both.

Intel and Pentium are trademarks of Intel Corporation in the United States, other countries, or both.

The Graphics Interchange Format(c) is the Copyright property of CompuServe Incorporated. GIF(sm) is a Service

Mark property of CompuServe Incorporated.

UNIX is a registered trademark of The Open Group in the United States and other countries.

Linux is a trademark of Linus Torvalds in the United States, other countries, or both.

Other company, product and service names may be trademarks or service marks of others.

109

Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertisement

Table of contents