IBM Lotus Instant Messaging and Web Conferencing for Sun Solaris (Sametime 6.5.1) Readme

Last update March 8, 2004


Sections in this document

Getting Started

CD-ROM Contents

System Requirements

Installation Notes 

Setting Up SSL on Solaris 

Known Problems and Recommendations


Getting Started

Note  The information in this Readme file might have been updated since your media was created. Visit the online documentation library for Sametime 6.5.1 to view the latest information. Updates to documentation about early preview or beta releases will be sent directly to those who require them.

Read the following information to get started with IBM Lotus Sametime on Sun Solaris:

Note  Many of the documents are provided on the product CD-ROM in Adobe Portable Document Format [PDF). The PDF files can be browsed with an Adobe Acrobat Reader. If you have not already installed Acrobat Reader, you can download the most current version of the reader from the Adobe Web site at www.adobe.com.

back to top


CD-ROM Contents

The contents of each directory on the two Sametime 6.5.1 for Solaris CDs is listed below.

Sametime 6.5.1 for Solaris, Volume 1

/ (root): this Readme file and install script

/Server: the Sametime 6.5.1 base product

/Languagepack: translated files for language installations

/ReleaseNotes: release notes from the Windows NT Sametime 6.5.1 release (many also apply to the Solaris version) and Asia language release notes.

/Docs: contains the following documents:

Sametime 6.5.1 for Solaris, Volume 2

/ (root): this Readme file

/Client: language versions of the Sametime Connect client

/CommunityMux: files for installing a Community Services multiplexer on a separate Solaris system

/LAP:IBM Licensing tool: Exchange and possibly other Windows installs need the LAP tool to install Sametime properly

/Docs: contains the following document:

ConnectReadme_xx.txt: Sametime Client Connect Readme

securedesktop_readme.txt: Sametime Installer for Secure Desktops Readme

/GSKit: the IBM Global Security Kit needed for managing SSL certificates in an SSL environment

/STConv: contains the following files:

/SecureDesktop: contains the files needed for Secure Desktop

/SIPConnector: contains the files needed for SIP Connector

back to top


System Requirements

See the Sametime 6.5.1 for Sun Solaris Installation Guide (stinstall.nsf or Stinstall.pdf) for the basic list of Sametime server and workstation requirements. The following items are additional requirements not listed in the Installation Guide:

         Sametime 6.5.1 for Solaris uses a graphical installation program that is based on Java. This program requires a Java Runtime Environment (JRE) of version 1.1.4 or higher.

         Running the installation program requires access to an X Window interface. The installation program will not run from a telnet session.

         To install Sametime 6.5.1 for Solaris, you must be logged in as root along with root’s environment settings. To start Sametime properly, you must be logged in as the Notes user, along with the Notes user’s environment settings. If switching from root to the Notes user to start the server, be sure to include the command line switch "-" to switch the environment settings. For example: su - notes

         2GB to 10GB of free disk space is recommended to allow space for converted documents and temp files.

In the Sametime 6.5.1 for Solaris Installation Guide on page 11, in Table 2 (Operating system and browser support), JVM1.4.2 is only listed to support Redhat Linux, and isn't listed to support Win32 and other Unix platforms.

Since JVM1.4.2 is supported, JVM1.4.2 should be added in the support table for the following:

                     Internet Explore 6 on Windows 2000 Professional

                     Internet Explore 6 on Windows XP Professional.

                     Mozilla 1.4.1 on Solaris 8

                     Mozilla 1.4.1 on Windows 2000 Professional

                    Mozilla 1.4.1 on Windows XP Professional

Minimum hardware requirements for Solaris installation

        Sun Blade 1000

        1Gb RAM

        2Gb swap space

back to top


Installation Notes

This section contains additional information that you need to know about installing Sametime 6.5.1 for Solaris.

Pre-Installation Configuration

The installation does not automatically check to ensure that your computer has the disk space necessary to install Sametime. Before installing Sametime, manually check your system to be sure that it has adequate disk space. See the Sametime 6.5.1 for Sun Solaris Installation Guide for the required amount of disk space.

Ensure that Domino 6.5.1 has been installed and successfully started before installing Sametime. Stop Domino before installing Sametime.

Note: Domino 6.0.3 is the minimum version of Domino that may be used for this version of Sametime.

Command Line Install

Some SUN machines may experience problems with Sametime's graphical java installer. There is a script-based command line install option that can be used if you are not able to complete installation of Sametime using the graphical java installer.

  1. Copy "/Server/install.res" to some directory on your harddrive. This is the script file to be used during the install process.
  2. Edit the copy of "install.res" that has been copied to your harddrive. The following values need to be verified or modified:
  3. Instead of running "./install" to start the install program, go to the "/Server" directory and run "java Installer /p ". For example, if you copied "install.res" to "/tmp", you would change to the "/Server" directory and run "java Installer /p /tmp/install.res".

Please note that while this install method does not create any graphical windows, it will attempt to access certain graphical environment variables. You will need X-Windows access to the machine in order for this install method to execute properly.

Availability of Lotus Notes client

If you received a copy of the Sametime 6.5.1 for Solaris CD-ROM media pack, you have received the Domino Designer CD that contains the Lotus Notes client. The Notes client is useful for configuring a Domino server and for some aspects of Sametime server administration. However, it is not required to install and run Domino and Sametime. If you do not have a Notes client, Sametime customers can download a copy from the Passport Advantage Web site: www.lotus.com/passport.

Check the server name in the file/etc/hosts/ before installing Domino

Check the server name in file /etc/hosts/ before install Domino. If it is not a fully qualified domain name, for example solarisserver, please modify to fully qualified domain name, for example solarisserver.domainname.com.

Step missing when setting up an LDAP connection

The IBM Lotus Instant Messaging and Web Conferencing (Sametime) 6.5.1 Administrator's Guide contains a set of instructions that explain the process of "Setting up an LDAP connection after selecting the Domino directory during server installation." Essentially, this process explains how to convert a Sametime server from performing authentication against its Domino directory to performing authentication against an LDAP directory.

One step in this process is titled "Copy and rename the .DLL files" which explains how to copy and rename several files required to support authentication against the LDAP directory. A step is omitted from those instructions. When copying and renaming the .DLL files note that you must also copy the StBrowseLdap.dll file and rename it to StBrowse.dll as described below:

1.      Copy the "StBrowseLdap.dll" file from the directory C:\Sametime\DirectoryBB\Ldap to a working directory.

2.      Rename the "StBrowseLdap.dll" file to "StBrowse.dll."

3.      Copy the renamed STBrowse.dll file to the C:\Sametime directory.

If you do not copy and rename the StBrowseLdap.dll file, the LDAP directory that Sametime is authenticating against cannot be selected in the directory browsing dialog boxes available from Sametime clients.

back to top


Setting Up SSL on Solaris

Follow the steps below to set up SSL for Sametime 6.5.1 on Solaris.

  1. Install the Sametime server and start it. To speed up the setup, you might want to open notes.ini and temporarily remove the staddin task from the "ServerTasks=" line before starting the server. Remember to put this task back after you complete the SSL setup. (Removing the staddin task is optional.)
  2. Create a certificate authority database:
  3. Enable SSL on the Domino server. Using a Notes client, open names.nsf and then open the Server document for the Sametime server. Follow the steps below.
  4. Get the certificate authority text from the server. Open a browser and go to http://servername/ca.nsf. (This URL is case sensitive.) Follow the steps below.
  5. Transfer files to the server. Ftp the following files from their current locations (listed below) to the data directory of your server (for example, the /local/notesdata directory):
  6. To create a key file, run the program Ikeyman on the server. To run Ikeyman:
  7. Stop the server.
  8. Modify the Sametime.ini file.

Open the Sametime.ini file (located in the server's data directory) and make the following changes under the [Config] section of the file. If a setting is already in the file, change the value as indicated below.

  1. Restart the server. If you removed staddin from the notes.ini task list in step 1, make sure you reinsert staddin before restarting.

 

back to top


Known Problems and Recommendations

Problems when shutting down the server

When shutting down the Sametime server, the Domino console might report a fatal error and freeze all threads. If this problem occurs, follow the steps below to continue the shut-down.

  1. Log in as the root user. Run the following command: $ /opt/lotus/bin/nsd -kill [-nolog]
    The optional -nolog flag prevents an nsd kill log file from being created.
  2. If the Domino console is still frozen, run the following set of commands: $ ps -u notes | tail +2 | awk '{print $2;}' | xargs kill -9

SSL for LDAP and SSL for SIP is not supported in Sametime Solaris

You cannot use SSL for LDAP or SSL for SIP with this version of Sametime.

Problem with server deinstallation

You cannot deinstall Sametime while leaving Domino installed on the server. To deinstall Sametime, remove the directories which contain Domino and Sametime.

Must enable chat logging

If you want to use chat logging with Sametime 6.5.1 for Solaris, you must enable the chat logging flag in stconfig.nsf:

  1. Open the stconfig.nsf databased in your Notes client.
  2. Change the "chat logging" flag under the "Community Services" heading from "off" to "relax" or "strict".
  3. Save your change and close the stconfig.nsf database.
  4. Restart the server.

Issue with writing server log information to a text file

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”.

Error in the LDAP section of the Sametime Administrator's Guide

The topic "Where to start searching for people" in the "Using LDAP with the Sametime server" section of the Sametime Administrator's Guide contains an error. This topic gives an example value of "o=servername" for the "Scope for searching for a person" setting when using a Domino directory. This example value should read "o=organizational" instead of "o=servername."

Problem with chat text in "Sametime Connect for browsers"

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.

Japanese text unreadable

Japanese text for Sametime 6.5.1 for Solaris is unreadable or displays as "garbage text" 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.

Screen sharing buttons disabled after installing SmartUpdate

If you are using a Netscape browser and you install SmartUpdate, the screen-sharing buttons in the Sametime Meeting Room are sometimes disabled when you attend your first meeting after installing SmartUpdate. To fix this problem, leave the meeting and reattend. The screen-sharing buttons should be enabled.

Sametime services fail when configuring LDAP for Solaris

When configuring Sametime 6.5.1 for Solaris to work with LDAP, you will see several messages indicating that Sametime services have failed. These messages are normal, and will not impede the LDAP configuration. To ensure that Sametime for Solaris works with LDAP directories, install Sametime and start the Sametime server. When you see the failure messages, ignore them and continue with the steps outlined in Chapter 4 of the Sametime 6.5.1 for Sun Solaris Installation Guide, "Using LDAP Directories with Sametime," then restart the Sametime server.

If the Sametime failures cause a problem (for example, if you are unable to create the Directory Assistance database),follow the steps below to start the necessary portions of the Domino server and complete the LDAP configuration:

  1. Stop the Sametime server.
  2. Remove "staddin" from the "Tasks" list in notes.ini.
  3. Start the server.
  4. Make all necessary configuration changes, outlined in Chapter 4 of the Sametime 6.5.1 for Sun Solaris Installation Guide.
  5. Stop the server.
  6. Put "staddin" back in the "Tasks" list in notes.ini.
  7. Start the server.

Environment variables associated with "ststart" script file

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.

Using the Domino "bin" directory in the PATH variable causes installation problem

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.

Option to limit recorded meetings not available

In the Meeting Services settings of the Sametime Administration Tool, there is an option to "Stop Recording when this much space is left (MBytes)." Although this option appears in the user interface, Solaris does not support it. Implementation of this option would have a detrimental effect on Sametime performance.

Using the Sametime Administration Tool to Set up Invited Servers (Meeting Servers that Are Connected)

You can use the Sametime Administration Tool to allow a Sametime server to "invite" another server to a meeting. When you set up invited servers, a meeting can be active on more than one server at a time. To set up invited servers for Solaris:

  1. Install two or more servers in the same Domino domain.
  2. Log into the Sametime Administration Tool on the server that you want to use as the "inviting" server. (The server which will connect to the "invited" server through a connection document.)
  3. Choose Configuration-Connectivity. Click on the "Servers in this Community" tab.
  4. Enter the name of the server that you want to invite in the "Destination server" field. For example, enter charon/tostada.
  5. Enter the fully-qualified domain name in the "Destination server IP address" field. For example, enter charon.lab.databeam.com.
  6. Click on Add.
  7. Make sure names.nsf is replicated.
  8. Restart the server.
  9. To verify that a meeting is active on both servers, create a meeting on the first server. When creating the meeting, select the invited server on the Locations tab of the New Meeting page. Save the meeting and then verify that you can attend it on both servers.

Error when exporting a recorded meeting

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.

Cannot install Sametime and Quickplace on the same machine

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

Sametime 6.5.1 for Solaris not supported for Turkish locale

Installing Sametime for Solaris on a server set to a Turkish locale is not currently supported in the 6.5.1 release.

Sametime Administration Tool might display status incorrectly for non-English locales

If you are using a non-English locale browser to administer the Sametime server, the Server Overview feature in the Sametime Administration Tool might display the status of the first Sametime service incorrectly.

Need to set the hard drive limit to allow for file descriptors

For Sametime to function properly on the Solaris operating system, a large number of file descriptors are required. Ensure that these are available by setting the hard limit to 65,535 in the /etc/system file. In the section labled * set: add the setting: set rlim_fd_max=65535

Install the latest version of Java Virtual Machine (JVM)

Sametime makes use of the Java Virtual Machine (JVM) on the Solaris operating system. It is highly recommended that administrators install the latest J2SE patches from Sun for their JVM.

back to top