Stinstall

Lotus Sametime
Version 7.0
Installation Guide
G210-2078-00
Note: Before using this information and the product it supports, read the information in "Notices" on page 35.
First Edition (August, 2005) This edition applies to IBM Lotus Sametime 7.0, (product number L-GHUS-5Z7NTN), and to all subsequent releases and modifications, until otherwise indicated in new editions. Copyright International Business Machines Corporation 1996, 2005. All rights reserved. US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
Contents
Chapter 1. Sametime 7.0 Installation Overview . . . . . . . . . . . . . . 1
Sametime Installation Roadmap . System Requirements . . . . . . . . . . . . . . . . . 1 . 2 Uninstalling the Sametime Server . Windows . . . . . . . . AIX and Solaris . . . . . . . . . . . . . . . . . . . . . . 18 . 18 . 18
Chapter 4. Upgrading to Sametime 7.0

Upgrading to Sametime 7.0 . . . . . . . .
19
. 19
Chapter 2. Preparing the Domino Server for Sametime Installation . . . . . . . 3

Preparing the Domino Server for Sametime Domino Server Checklist . . . . . Installation Notes . . . . . . . . Setting the AIX or Solaris Environment . Determine the Directory Type. . . . . Possible Scenarios for Sametime Installation . . . . . . . . . . . . . . . . . . . . . . . . 3 3 4 4 5 5
Chapter 5. Installing other Sametime 7.0 features . . . . . . . . . . . . . 21

Installing Other Sametime Features . . . . . Installing the Sametime Connect Client Packager . Using the Sametime Client Packager Application . Downloading and Installing Sametime Connect . Installing the Session Initiation Protocol (SIP) Connector . . . . . . . . . . . . . . . . . . 21 21 21 23
Chapter 3. Installing Sametime 7.0 . . . 7

Sametime Server Installation Overview . . . . Installing Sametime . . . . . . . . . . . Before You Begin . . . . . . . . . . . Run the Install CD . . . . . . . . . . Install Options . . . . . . . . . . . . Remote AIX or Solaris Installation . . . . . Installing Sametime 7.0 on Domino Partitioned Servers . . . . . . . . . . . . . . Set up Domino Web SSO Authentication Between the Domino Server and Sametime Server . . . Configuring the Sametime Server to Access the LDAP Directory . . . . . . . . . . . . Troubleshooting LDAP Configuration Information . . . . . . . . . . . . Altering the Directory Assistance Document . Configuring the LDAP Directory Settings . . Populating the Domino Directory . . . . . . In a New Domino Domain . . . . . . . In an Existing Domino Domain . . . . . . Verifying the Domino Server Document Settings . Testing the Sametime Server . . . . . . . . Validate Creating a New Meeting . . . . . Validate Screen Sharing . . . . . . . . Starting and Stopping the Sametime 7.0 Server . On Windows . . . . . . . . . . . . Starting a Sametime Server on AIX or Solaris . Stopping a Sametime Server on AIX or Solaris . . . . . . . 7 7 7 7 8 9
. 23
Chapter 6. Troubleshooting . . . . . . 25
Troubleshooting Sametime 7.0 Installation . . . . 25
Chapter 7. Installing and Setting Up Domino for Sametime . . . . . . . . 29

Domino Installation Overview . . . . . . . Installing Domino on Windows . . . . . . Installing the Domino Server on AIX or Solaris Adding a Domino Server to an Existing Domino Domain. . . . . . . . . . . . . . Setting Up the Domino Server . . . . . . Installing and Configuring the Notes Client and Domino Administrator Client . . . . . . . 29 . 29 31 . 32 . 32 . 33
. 9 . 11 . 12 . . . . . . . . . . . . . . 12 12 13 14 14 14 15 16 16 17 17 17 17 18
Chapter 8. Notices . . . . . . . . . . 35
Trademarks . . . . . . . Third Party Notices . . . . . For the XSL and XML Parser and For DSIG base64 . . . . . . For STLport . . . . . . . For MD5 hash . . . . . . For Log4J Logging . . . . . . . . . . . . . Processor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 37 37 37 38 39 39
Index . . . . . . . . . . . . . . . 41
iii
iv
IBM Lotus Sametime 7.0 Installation Guide
Chapter 1. Sametime 7.0 Installation Overview

The IBM Lotus Sametime 7.0 Installation Guide provides an administrator with all instructions needed for successfully installing and setting up IBM Lotus Sametime 7.0 version on a Windows, AIX, or Solaris platform. This chapter includes the system requirements and a roadmap that outlines the tasks required to install and set up Sametime 7.0.

Sametime Installation Roadmap

The installation and setup instructions in this guide apply to both the full version of Lotus Sametime 7.0 and the IBM Lotus Instant Messaging Limited Use version of Sametime. The Instant Messaging Limited Use version of Sametime ships with all Domino 7.0 servers and cannot be purchased separately. If you are installing the Instant Messaging Limited Use version of the Sametime server into a community that also includes the standard version of the Sametime server, see the topic Using the IBM Lotus Instant Messaging Limited Use version of Sametime with standard Sametime servers in the Sametime Administration Guide that is provided with the Instant Messaging Limited Use version of Sametime. This topic describes the configurations necessary to ensure that these two versions of the Sametime server can co-exist in the same community. Sametime 7.0 must be installed on a Domino 7.0 server. This guide provides you with general instructions for installing Domino, and with the setup required to install Sametime. However, if you have never installed and set up a Domino server, it is strongly recommended that you refer to the Domino Administrator 7 help to get a full understanding of how to install and set up a Domino server. To download or view the Lotus Domino 7.0 Administrator Help, go to http://www.ibm.com/developerworks/lotus. After you have installed Domino, but before you run the server setup, you should refer to this guide to determine which options you need to select during server setup to prepare your Domino server for use as a Sametime server. Note: For the most up-to-date information regarding Sametime installation, see the Sametime release notes posted on the web at www.ibm.com/developerworks/lotus. Roadmap These are the tasks required to install Sametime. 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. Verify hardware and software requirements. Install the Domino server. Complete the Domino server checklist. If you are installing Sametime on AIX or Solaris, set up the AIX or Solaris Domino server environment. Determine the directory type. Install Sametime. Configure the Sametime server to access the LDAP directory. Populate the Domino directory. Test the Sametime 7.0 server. Deploy the Sametime Connect client.
System Requirements
Before you install Sametime 7.0, install the supported hardware and software. When possible, use the recommended usage rather than the minimum to improve performance. For the most recent Sametime and Domino server system requirements, see the release notes that shipped with this product. This topic describes the system requirements for the Sametime 7.0 server and client computers for all three platforms. The installation and setup instructions in this guide apply to both the full version of Lotus Sametime 7.0 and the Lotus Instant Messaging Limited Use version of Sametime. The Instant Messaging Limited Use version of Sametime ships with all Domino 7.0 servers and cannot be purchased separately. If you are installing the Instant Messaging Limited Use version of the Sametime server into a community that also includes the standard version of the Sametime server, see the topic Using the IBM Lotus Instant Messaging Limited Use version of Sametime with standard Sametime servers in the Sametime Administration Guide that is provided with the Instant Messaging Limited Use version of Sametime. This topic describes the configurations necessary to ensure that these two versions of the Sametime server can co-exist in the same community. Operating system patches, service packs, and other updates are not specified in the information that follows. Note that operating system vendors frequently release updates. For the most recent information regarding updates, see the Lotus Knowledge Base online at http://www3.ibm.com/software/lotus/support/ or contact your local Lotus Support representative. The requirements listed here are for a Sametime server.
Chapter 2. Preparing the Domino Server for Sametime Installation

This chapter provides you with information you need to know about the Domino server before you install Sametime. It also outlines the options you must select during the Domino server setup to prepare the Domino server for Sametime installation, as well as the changes you must make to the Domino Server document.
Preparing the Domino Server for Sametime

You must install the Domino 7.0 server before you can install Sametime 7.0. If you have not installed a Domino 7.0 server, refer to Installing Domino for instructions. After you have installed Domino 7.0 on your server (or upgraded an existing Domino server to 7.0) you need to set up your Domino server for use as a Sametime server. Before you install Sametime, go through the Domino server checklist and Installation Notes below to make sure the Domino server is ready for Sametime installation, and that you have the information you need to install Sametime. If you are installing Sametime on an AIX or Solaris Domino server, see the topic Setting the AIX or Solaris Environment.
Domino Server Checklist

v Make sure that the Domino server.id does not have a password. When you installed Domino, if you provided a password for the server.id, you must remove the password. Or, if you have a copy of the server.id file without a password saved locally, you can replace the server.id in the data directory of the server before you set up the server. To remove a password from a server.id, log in to the Notes client using the server.id. Then choose - File - Security - User Security and reset the password to be empty. v Make sure that the Domino server has the HTTP server task enabled. v Make sure you have an Internet password. You must have an Internet password in order to access the Sametime 7.0 components of the server during Sametime installation. v Make sure you know the name of the Domino server. If you do not know the Domino server name, you can find it in the Server document. Verify that Domino has a fully-qualified host name -- for example server.company.com. v Ensure that the client computers can ping the Sametime 7.0 Domino server using the fully qualified name (for example, from a command prompt execute the command ping sametime1.acme.com). This step ensures that the computer is registered in DNS or the name is in a hosts file. v Make sure you know the location of the Domino program and data directories. v Make sure you know the type of directory (Domino Directory or LDAP directory) that you are going to use. v For AIX and Solaris, make sure that the Domino server was installed as root. v Temporarily disable any screen savers and turn off any virus-detection software on the server computer reserved for Sametime server installation. v Make sure that all applications on the computer reserved for Sametime 7.0 installation (including Domino Server Administration and the Web browser) are closed. Otherwise, you might corrupt any shared files and the installation program might not run properly. v Ensure that the Domino services are stopped. v Back up all customized data files (.ntf, .mdm, .scr, .bmp, .mac, .smi, .tbl). v Make backup copies of: all ID files, NAMES.NSF, NOTES.INI, DESKTOP.DSK, and PUBNAMES.NTF. v Make sure that the Domino server has been started at least once. This is necessary to ensure that the required databases are successfully created and initialized.
Installation Notes
v The Sametime 7.0 installation will prompt you to replicate a Configuration database from an existing Sametime 7.0 server. This option is relevant only if you are installing the Sametime 7.0 server into an environment in which other Sametime 7.0 servers are already operating. When selected, this option performs a one-time replication of the Configuration database (STCONFIG.NSF) from an existing Sametime 7.0 server to the Sametime 7.0 server you are installing. The Configuration database stores the configuration and administration settings that are set from the Sametime 7.0 Administration Tool. Replicating this database ensures that the newly-installed Sametime 7.0 server has administration settings that are consistent with existing Sametime 7.0 servers. In multiple Sametime 7.0 server environments, it is essential that some administration settings remain consistent across all Sametime 7.0 servers. For more information about setting up multiple Sametime 7.0 server environments, see Chapter 14, Deploying Multiple Sametime 7.0 Servers in the IBM Lotus Sametime 7.0 Administrators Guide. v For optimal performance, the Sametime 7.0 Domino server should be placed at a centrally-located network backbone to reduce the number of network hops between clients and the server. Ideally, there should be no more than one WAN hop for every possible client to server connection. Clients that make multiple WAN hops to connect to the server will experience slower performance than clients connecting through a LAN or making one WAN hop to the server. For organizations that have large networks, it may be necessary to install multiple Sametime 7.0 servers to reduce the number of WAN hops for clients. For more information about working with multiple Sametime 7.0 servers, see Chapter 14, Deploying Multiple Sametime 7.0 Servers of the IBM Lotus Sametime 7.0 Administrators Guide. v Sametime 7.0 for AIX will run on pSeries or RS/6000 servers that support AIX 5.2 with the patch level 2 (5200-02) and have enough capacity to support Sametime 7.0 and Domino implementations. Like most platforms, there are price/performance and response time advantages to running Domino and Sametime 7.0 on the newer technology server models. v You must install the language version of Domino that corresponds to the language version of Sametime 7.0 you plan to install. Instructions for installing language versions are available on the language pack CD. For example, if you plan to install the French version of Sametime 7.0, you must install either one of the following: The French version of Domino The Global English version of Domino plus the French language files from the Domino Language Pack
Setting the AIX or Solaris Environment

Make sure you have read and completed the Domino checklist. To make sure your AIX or Solaris Domino server is ready to install Sametime, make sure of the following: v You must log in as root to install Sametime, and the root user must be part of the Domino group. To verify this, type the following, where <dominoUserName> is the name of the root user.
groups <dominoUserName>
For example, if you type groups notes, you get the return value of notes, which means that the user name notes is a part of the group notes. v Verify that the Domino user is a part of the Domino group. Type the following command:
groups <dominoUserName>
where <dominoUserName> is replaced by the username listed in (1). For example, if you type group notes, you will get the value notes, which specifies that the username notes is part of the group notes. v Verify that Java is in your $PATH. To find out the location of Java, type the following command:
which java
If Java is not found, then you must find the location of Java on your server and add it to your $PATH environment variable. Note that this cannot be a Java that is a part of the Domino installation.
v Verify that the lotus bin directory (by default /opt/ibm/lotus/bin) is not in your $PATH environment variable. The server will not start up correctly if the lotus bin directory is in your $PATH. v verify that your $CLASSPATH includes /<Path to CD1>/Server. Type the following command.
echo $CLASSPATH
The value displayed should include /<PATH to CD1>/Server or a period (.) by itself, which stands for the current directory. v Verify the correct Java version. The Java version must be greater than 1.3.1. Type the following command:
java -version
v Verify the amount of disk space you have. Make sure that the file system has at least 1GB of disk space. Type the following command:
type "df -k"
Note: If you are not installing from a CD, you must also consider the disk space required for the *.tar install files and the unpacked install files, which needs approximately 2GB of disk space. v AIX only -- The Input Output Completion Protocol (IOCP) must be installed and configured. If not, it will not allow the Domino setup to begin, and you will get the following error: Warning: Your system is not configured with I/O Completion Ports. I/O Completion Ports must be installed in order to run the Domino 7 Server. Install and make available I/O Completion Ports and restart your system. Refer to Lotus Knowledgebase Technote 1086556 for detailed instructions on how to install/configure IOCP.
Determine the Directory Type

Sametime can operate with either an LDAP directory or a Domino directory. Before you start the installation, you need to know which directory type you will be using. The install procedure will vary depending on which type of directory that you select. v LDAP -- If your organization uses LDAP directories, you must select LDAP as the directory type during the Sametime server installation. After the Sametime server installation completes, you must configure the server to access the LDAP directory (or directories) used in your environment. If you choose to use LDAP as the directory type, the LDAP server name, port number, base DN and bind authentication credentials (optional) will be required during the Sametime installation. Please obtain these from your LDAP Administrator prior to installing Sametime. v Domino Directory -- If your organization uses Domino Directories, the Sametime server accesses the Domino Directory of the Domino server on which Sametime is installed. Sametime can also use directory assistance on the Domino server to access other Domino Directories of interest. If you installed the Domino server that will support Sametime as the first server in a Domino domain, you must populate the Domino Directory with a community of users after the Sametime server installation completes. If you installed the Domino server as an additional server in a Domino domain, the Domino Directory that was replicated during the Domino installation contains the community of users. For more information about populating the Domino Directory, see the topic Populating the Domino Directory. For information about setting up an LDAP directory, see the topic Configuring the Sametime server to access the LDAP directory.
Possible Scenarios for Sametime Installation

There are several scenarios that are possible when you install Sametime. You can, for example, install Sametime on a Domino server in a new Domino domain, or in an existing Domino domain. In all scenarios, you must install Sametime 7.0 on a Domino 7.0 server. You can do the following:
Chapter 2. Preparing the Domino Server for Sametime Installation
v Set up a Domino server in a new Domino domain and add Sametime 7.0 to that server. In this scenario, the Sametime server is configured on a Domino server and uses the Domino Directory for directory services. v Add a Domino server to an existing Domino domain and then add Sametime 7.0 to that server. A Sametime community can include more than one Sametime 7.0 server. If you have a large number of Sametime users, you can install multiple Sametime servers for load balancing and to reduce network usage. However, you must install it on one server at a time. For example, if you have three Domino servers installed and you want to install Sametime 7.0 on all three Domino servers, you would have to do three separate Sametime installs. v Use an LDAP directory. You can configure Sametime to connect to an LDAP directory on a third-party server instead of using the Domino Directory. When Sametime is configured to connect to an LDAP directory, Sametime users are managed in an LDAP directory on another server. v Install Sametime on a partitioned server. Installing Sametime on a partitioned server is supported for AIX and Solaris only. For information regarding the differences in how Sametime accesses the Domino Directory based on whether you are installing in a new domain or an existing one, see the topic Populating the Domino Directory. For more information on the different types of Sametime deployment, refer to the IBM 7.0 Administrators Guide.
Lotus
Sametime
Chapter 3. Installing Sametime 7.0

This chapter describes the tasks and provides step-by-step instructions for installing and setting up Sametime 7.0 on a Windows, AIX or Solaris platform.
Sametime Server Installation Overview

The tasks listed here assume that you have installed the Domino server. If you have not already done so, install and setup the Domino 7.0 server before proceeding. For information on installing a Domino server, see Installing Domino. The Sametime installation procedure applies to both the full version of Lotus Sametime 7.0 and the IBM Lotus Instant Messaging Limited Use version of Sametime. The Instant Messaging Limited Use version of Sametime ships with all Domino 7.0 servers. This version of Sametime is only available with Domino and cannot be purchased separately. If you are installing the Instant Messaging Limited Use version of the Sametime server into a community that also includes the standard version of the Sametime server, see the topic Using the IBM Lotus Instant Messaging Limited Use version of Sametime with standard Sametime servers in the Sametime Administration Guide that is provided with the Instant Messaging Limited Use version of Sametime. This topic describes the configurations necessary to ensure that these two versions of the Sametime server can co-exist in the same community. To install and set up a Sametime server: v Install Sametime 7.0 v Set up Domino Web SSO authentication between the Domino server and Sametime server v If you are using an LDAP Directory, configure the Sametime server to access the LDAP directory v If you are using a Domino directory, populate the Domino Directory v Verify the Domino Server document configuration v Test the Sametime server installation v Start and Stop the Sametime 7.0 server
Installing Sametime
Use the following procedure to install the Sametime 7.0 server from the installation CD. The instructions for installing on Windows, AIX, or Solaris are the same unless noted otherwise.
Before You Begin

Before you begin installation: v Shut down the Domino server. v Review the information in the Domino server checklist to make sure you have the information you will need during the installation.
Run the Install CD

Windows: Insert the Sametime 7.0 Installation CD into the CD-ROM drive of the server. The CD loads and then the main dialog box displays. Choose the install options. If you are installing from an image, extract the image and double click on Server\setupwin32.exe. AIX or Solaris:
AIX and Solaris commands are case sensitive; type them exactly as shown. 1. Insert the Sametime 7.0 Installation CD into the CD-ROM drive of the server or download the installation images. 2. Mount the CD on your server using the System Management Interface Tool (SMIT) or the following command, where /cdrom is the mount point for the CD and /dev/cd0 is the device information for the CD-ROM drive:
mount -r -v cdrfs /dev/cd0 /cdrom
If you are using a downloaded image for installation, please extract the files to a temporary directory. 3. If you are using a downloaded image to install, continue to step 4. Change the directory of the installation programs on the CD, using the following command, where /cdrom is your actual mount point:
cd /cdrom/CD1/server
4. Start the installation process with this command:

./setup{platform}.bin platform = aix or solaris
5. Choose the install options.
Install Options
1. Select the appropriate language. 2. Click Install the Sametime 7.0 Server. 3. Read through and follow the instructions on directions the following screens, click Next to progress to the next screen. v IBM Software License Agreement v Welcome 4. If the Domino language and the Sametime 7.0 language are different then a dialog box will display a warning message indicating the languages are different. You can continue or cancel the installation at this time. 5. If the Sametime 7.0 Server Requires IBM Lotus Domino dialog box displays, Domino 7.0 was not found. Click Cancel, install the appropriate version of Domino and then restart the installation procedures. For information on installing the Domino 7.0 server, see Installing Domino. For complete instructions on installing and setting up a Domino server, see the Lotus Domino Administrator 7 help. To download or view the Lotus Domino 7.0 Administrator Help, go to http://www.ibm.com/developerworks/lotus. 6. Read through the License agreement and follow the instructions on the screen. 7. The Setting up the Directory Type dialog allows you to select whether you want the directory type to be Domino or LDAP. If you selected the LDAP directory as your directory type, additional configurations are required on the Sametime 7.0 server to enable the server to function with an LDAP directory. For more information about these additional configurations, see the Using LDAP with the Sametime 7.0 server chapter of the IBM Lotus Sametime 7.0 Administrators Guide. 8. In the Sametime 7.0 Server Connectivity dialog box: v If the check box is disabled (unchecked), the Sametime clients communicate with the Sametime server Meeting Services on port 8081 and the Sametime server Community Services on port 1533. v If the box is enabled (checked), all Sametime client data, except A/V data, will be tunneled to the Sametime server via HTTP on port 80. You may need to enable this option if Sametime clients must connect to the server through a network that blocks TCP communications on ports 8081 and 1533. For more information about client connectivity issues, see the Configuring Sametime Connectivity chapter of the IBM Lotus Sametime 7.0 Administrators Guide.
9. Click Next. A screen confirming your selected settings will appear. Click Install to start copying the files. A progress bar displays and the installation program completes the setup; a Congratulations dialog box displays. 10. Select the server ID when prompted. By default the id file (server.id) should be in the servers Data directory. 11. Start the Domino server. The Sametime 7.0 server starts automatically when the Domino server starts. 12. Once the Sametime 7.0 server is running, you can select the Welcome to Sametime 7.0 icon on the Windows desktop to access the Sametime 7.0 server home page. Note: The Sametime 7.0 server installation automatically enables the Single Sign-On functionality on the Domino server. If you experience single sign-on or authentication problems following the Sametime 7.0 server installation, review the Authentication by token using LTPA and Sametime 7.0 tokens section in the Working with Sametime 7.0 security chapter of the IBM Lotus Sametime 7.0 Administrators Guide.
Remote AIX or Solaris Installation

If you are installing Sametime remotely, your Domino server requires these additional setup steps.
X-Windows Environment
To install Sametime from a remote Windows workstation, you must install the X-Windows Environment on the remote workstation: 1. Install cygwin from www.cygwin.com 2. Select and install the X11 packages during the cygwin installation Make sure the X-Windows session is running: 1. Launch the cygwin bash shell 2. In the bash shell that is launched, type the following:
startx
3. In the X-Windows session that is created when you type this command, type:
xhost +
AIX or Solaris Environment:

You must verify that the DISPLAY environment variable is set (this is required for a remote installation). To do so, type the following:
echo $DISPLAY
This should return the IP address of the remote workstation. For example:
> echo $DISPLAY > 9.41.113.167:0.0
To set the DISPLAY environment variable, use the IP address of the workstation followed by :0.0. For example:
> DISPLAY=9.41.113.167:0.0 > export DISPLAY
Installing Sametime 7.0 on Domino Partitioned Servers

This section provides installation and setup information for configuring Sametime 7.0 in a Domino partitioned server environment. Note: Installing Sametime in a Windows environment on a partitioned server is unsupported.
Pre-Domino Installation
Follow these steps before installing Domino: 1. Ensure that each partitioned server has a unique IP address. On AIX or Solaris, you can map multiple IP addresses to one network card using the ifconfig command. The syntax is as follows: v Create the following file, etc/hostname.hme0:1 (you will see that etc/hostname.hme0 is already created, this represents the physical address) v In this new file type the fully qualified name of the logical address for the second IP you are assigning this machine. v Then type ifconfig hme0 plumb v Then type ifconfig hme0:1 plumb v Then type ifconfig hme0:1 <new logical IP address> up v After that you can type ifconfig -a and both IPs should be present. 2. Ensure that each partitioned server has a DNS name that maps to its unique IP address. 3. To ensure that each partitioned server is run by a unique user account, create a new UNIX notes user for each partitioned server that you plan to install.
Domino Installation
When installing Domino: 1. Choose to install a Domino Enterprise Server. 2. When prompted to install more than one Domino Server on this computer, click Yes. 3. When prompted for the location of the data directory and the Notes user account, be sure to use a unique location for the data directory and the same 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 notes and run /opt/lotus/bin/http httpsetup to configure the first server. Then log out, log in as notes, configure the second server, and so on. 2. During configuration, make sure that any field referring to the servers 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 first server. For each additional server, you must update these fields. Note: When prompted for the Net Address on the Network and Communications Settings screen, ensure that Use ports selected below is selected in the Network Options section. Otherwise, the Domino server will not accept any change to the Net Address field. 3. After configuration for each server is complete, start the first Domino server. 4. Open a browser and go to the servers Name and Address Book. 5. Choose Server-Servers and open the Server document for this particular Domino server. 6. Choose Internet Protocols - HTTP and fill in the Host name with the fully-qualified name of the server, then enable Bind to host name. 7. For each server, open the notes.ini file and add the following field: TCPIP_TcpIpAddress=0,(server_ip):1352. 8. Repeat steps 3-7 for each partitioned server.
Sametime 7.0 Installation

To install Sametime 7.0: 1. Run the Sametime 7.0 installation program. When prompted, select the data directory and user account for the first partitioned server. 2. When prompted for the Servers Domain Name, enter the dotted IPv4 Address. DO NOT enter the Domain Name.
10
3. Continue through the rest of the installation. 4. After the installation is complete, repeat steps 1 and 2, substituting the data directory and user account for each partitioned server.
Sametime 7.0 Configuration

To configure Sametime 7.0, complete the steps below for each partitioned server: 1. Edit the sametime.ini file. Under [Config], add VPS_TRUSTED_IPS=(insert a comma-separated list of dotted IPv4 addresses that resolve to the server). 2. Start the Sametime 7.0 server. Go to the Sametime 7.0 Welcome page and click on Administer the Server. 3. Choose Configuration-Connectivity. 4. Enter the dotted IPv4 Address of the server in each host name field. 5. Using a Notes Client, open stconfig.nsf on the Sametime 7.0 server. 6. Modify Community Trusted IPS found in the CommunityConnectivity document to equal the comma-separated list of dotted IPv4 addresses that resolve to the server. 7. Stop the server. Note: When entering values for the Event Server port and the Token Server port, ensure that the values are unique and that they are not in use by another Sametime 7.0 server.
Set up Domino Web SSO Authentication Between the Domino Server and Sametime Server
Domino single sign-on (SSO) authentication allows Web users to log in once to a Domino or WebSphere server, and then access any other Domino or WebSphere server in the same DNS domain that is enabled for single sign-on (SSO) without having to log in again. In a multiple server environment, it is possible that one or more servers in your Domino domain are already configured for Domino SSO, and the Domino Directory already contains a Domino Web SSO configuration document. When you install Sametime, it creates a Web SSO configuration document called LtpaToken unless one already exists in the Domino directory. If an LtpaToken configuration document already exists, Sametime does not attempt to alter it. Configure the Domino Server for Web SSO Complete the steps in this section if your Domino server is not configured for Web SSO, and you want to use the Web SSO document that Sametime creates to configure it. 1. From the Domino Administrator or a Notes client, File - Database - Open. Browse to the Domino server and type NAMES.NSF in the FIlename field. Click Open. Note: If you attempt to open this document from Domino Administrator Configurations tab, Web Web Configurations view, the Web SSO Configuration document will not display. 2. Expand the list of Web SSO Configurations. 3. Double click the Web SSO Configuration for LtpaToken document to open it in edit mode. 4. Update these fields as necessary: v Configuration name -- Enter LtpaToken. v DNS Domain -- make sure this is the fully-qualified domain suffix of the Sametime server. For example, if the servers fully qualified name is server.domain.com, the .domain.com should be entered in this field. Ensure that the leading period (.) is present in front of the domain suffix. v Organization -- Leave this field blank. v Participating servers -- Add the Sametime server and other servers that belong to the SSO realm to the list.
11
5. After entering the information, select Keys and do one of the following: v Create a Domino SSO Key v If you are using WebSphere in your environment, select Import WebSphere LTPA Keys, and then enter the LTPA Token password. Note: When adding servers to the Participating servers field, click the arrow and choose the name from an Address Book when possible. If this is not possible, make sure that you use the full hierarchical name when you add a server (for example, Server1/Acme where CN=Server/O=Org). Note: If you import a WebSphere LTPA Token, a field displays the LDAP server name and port. Make sure that there is a backslash (\) before the port number. For example, ldap.domain.com\:389.
Configuring the Sametime Server to Access the LDAP Directory

If you selected LDAP as the directory type, you must configure the Sametime server so that it has access to the LDAP directory, using the information and procedures in these topics: v Troubleshooting LDAP Configuration v Alter the Directory Assistance document v Configure the LDAP Directory settings The Sametime server can connect to multiple LDAP servers. If you need to create a connection to an additional LDAP server, see the topic Adding or removing an LDAP server in the Using LDAP with the Sametime server chapter of the IBM Lotus Sametime 7.0 Administrators Guide.
Troubleshooting LDAP Configuration Information

When configuring Sametime 7.0 to work with LDAP, you will see several messages indicating that Sametime 7.0 services have failed. These messages are normal, and should not impede the LDAP configuration. To ensure that Sametime 7.0 works with LDAP directories, install Sametime 7.0 and start the Sametime 7.0 server. When you see the failure messages, ignore them and continue the setup process. Then restart the Sametime 7.0 server. If the Sametime 7.0 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 7.0 server. 2. Remove staddin from the Tasks list in the Sametime servers notes.ini file. 3. Start the server. 4. Make all necessary configuration changes to the Directory Assistance document and Sametime Configuration databases. 5. Stop the server. 6. Put staddin back in the Tasks list in the Sametime servers notes.ini file. 7. Start the server.
Altering the Directory Assistance Document

This procedure is the first of two procedures you must complete to set up an LDAP connection from the Sametime server to an LDAP server. The Sametime server installation creates a Directory Assistance database (da.nsf) on the Sametime server. This database contains a Directory Assistance document that enables Sametime to connect to the LDAP
12
server to authenticate Web browser users. To ensure that the Base DN for search setting in this Directory Assistance document is set appropriately for the LDAP directory used in your environment, follow these steps: 1. From the Notes client, File - Database - Open. 2. Select the Sametime server. 3. Select the Directory Assistance database (da.nsf), and then click Open. 4. Double-click the name of the Directory Assistance document for the LDAP server to open the document. 5. Click the LDAP tab. 6. In the Base DN for Search field, enter one of the following, based on the type of LDAP directory used in your environment: v Domino directory -- In Domino Directory LDAP environments, leave this field blank. v Microsoft Exchange 5.5 directory -- An example value is OU=ServerName,O=NTDomainName, where ServerName is the Windows server name and NTDomainName is the Windows NT Domain (for example, OU=Acmeserver1,O=NTAcmedomain). This example assumes that the directory is using the default directory schema. If you have changed the schema of the Microsoft Exchange 5.5 directory, the entry in this field must reflect the new schema. v Microsoft Active Directory -- An example value is DC=DomainName, DC=com. v Sun One Directory server -- Use the format O= followed by the organizational unit that was specified during the server setup. If you are uncertain about this entry, use the administrative features of the server to determine the appropriate entry. v Tivoli Directory Server / IBM SecureWay directory - An example value is DC=DomainName, DC=com. 7. Click Save and Close to save the Directory Assistance document.
Configuring the LDAP Directory Settings

This procedure is the second of two procedures you must complete to set up an LDAP connection from the Sametime server to an LDAP server. Configure the LDAP Directory settings to ensure that the Sametime 7.0 server can search and authenticate against entries in the LDAP directory. You use the Sametime Administration Tool to configure the LDAP Directory settings. Follow the steps below to open the Sametime Administration Tool and configure the LDAP Directory settings: 1. From a Web browser, type the following address, where servername.domain.com is the fully qualified name of your Sametime 7.0 server:
http://servername.domain.com/stcenter.nsf
2. Click Administer the Server. 3. Select LDAP Directory. Note: If you see Domino Directory instead of LDAP Directory, you must restart your Sametime 7.0 server so that the changes you made to the Configuration database take effect. If this setting is still Domino Directory after restarting the server, rerun the Sametime installer and make sure that LDAP is chosen as the directory type. 4. Modify the LDAP Directory settings to match your LDAP environment. For detailed information about configuring the LDAP Directory settings, see the topic LDAP directory settings in the Using LDAP with the Sametime server chapter of the IBM Lotus Sametime 7.0 Administrators Guide.
13
Populating the Domino Directory

It is necessary to populate the Domino Directory only if you have selected the Domino Directory as the user repository and have installed the Domino server as the first server in a Domino domain. In this scenario, the directory will not include any users other than the Administrator, so you must create the Sametime community by adding users to the directory. To add a Sametime user to the Domino Directory, you must create a Person document for the user in the directory that includes (at minimum) a Last Name, a User Name and an Internet password. You can use any of the following tools to populate the Domino Directory: v A Lotus Notes client v A Domino Administrator client v The Sametime server self registration feature For detailed information about adding users, see Managing users in the Domino Directory in the Using Domino Directories chapter of the IBM Lotus Sametime 7.0 Administrators Guide.
In a New Domino Domain

When you set up a Domino server in a new Domino domain and add Sametime: v There are no users in the Domino Directory at the time the server is created. v The server is in its own Domino domain (also known as a Sametime 7.0 Community) and cannot access Domino servers outside the Sametime 7.0 Community. You cannot establish a connection to any existing Domino mail or application servers outside of this community. v You can add new users after initial setup by using the Sametime 7.0 Administration Tool, connecting to an LDAP directory server, or enabling self-registration and allowing users to register themselves. Using the Sametime 7.0 Administration Tool or self-registration will create person documents in the Domino Directory, but neither of these methods will create Notes user IDs for the Sametime 7.0 users. For more information about using the Sametime 7.0 Administration Tool or allowing self-registration, see the IBM Lotus Sametime 7.0 Administrators Guide (sthelpad.pdf or sthelpad.nsf). v Users only see other users online if they are registered in the same community. v You can create additional Sametime 7.0 servers and add them to this Sametime 7.0 Community to balance the Meeting Services load and distribute users among the Sametime 7.0 servers to balance the Community Services load.
In an Existing Domino Domain

When you add a Domino server to an existing Domino domain and then add Sametime: v Users from the Domino Directory appear in the directory on the Sametime 7.0 server. However, before they can use Sametime 7.0, you need to update each entry to specify their home server and Internet password. In this case, self-registration should not be enabled since duplicate IDs for the same users might be created. v The Domino Directory is shared by servers in the Domain. Users can access the directory from the Sametime 7.0 Web interface and change settings. This way of setting up a Domino server poses a greater security risk than setting up a new Sametime 7.0 server in its own community. v You add new Sametime 7.0 users after the initial setup by replicating your directory from the Domino server to the Sametime 7.0 server. You should not replicate from the Sametime 7.0 server to the Domino server. v Users can see all members registered in the Domino Directory and determine if they are online.
14
Verifying the Domino Server Document Settings

After you have installed Sametime on a Domino server, the Server document should be set up properly for Sametime. However, you will need to However to make sure the Server document has been set up correctly, you can edit the Server document and verify these settings. Although most of these settings are populated for you, you need to add the name of the Web SSO Configuration on the Internet Protocols - Domino Web Engine tab. Edit the Server Document 1. Open the Domino Administrator client on your Windows machine and click the Configuration tab. 2. Expand the Server section and then click All Server Documents. 3. Open the Server document for the Domino server on which you are installing Sametime. Use the table below to verify the appropriate values for the fields in the Server document.
Basics tab Fully qualified Internet host name Action This field is completed after Domino server install, and should contain the fully qualified host name as known by the DNS server. In a test environment, the local hosts table can be used as well as DNS. Note: This CANNOT be a numeric IP address. Load Internet configurations from Server\Internet Sites documents Directory Type Disabled Make sure this field says Primary Domino Directory. If this field contains Configuration Directory, please shutdown the Domino Server and replicate names.nsf from a master server. Master servers have a Directory Type of Primary Domino Directory. If you are unsure about a server, check the Directory Type field in the Server document. Security tab Administrators This field is completed after Domino server install, and should contain the name of the Sametime administrator. If not, click the arrow to select a name from an address book. Must have the Sametime administrator name. Default is Fewer name variations with higher security, the recommended setting for tighter security. Select More name variations with lower security if Domino Directory authentication is being used and you want users to be able to use short names. Access server Leave this field blank if possible. If you do include entries, you must add the following to the list of trusted directories: Sametime Development/Lotus Notes Companion Products Run unrestricted methods and operations After you install Sametime, this field should include these entries: v The name of the server v The name of the administrator v Sametime Development/Lotus Notes Companion Products Ports - Notes Network Ports tab
Administer the server from a browser Internet authentication
15
Basics tab Port
Action TCPIP Note: This must be typed exactly as shown in all uppercase letters or you will not be able to add Sametime 7.0 to this server. TCP The fully qualified host name known by the DNS server (this should be the fully qualified Internet host name on the Basics tab above). For example, stdom1.acme.com. Note: This CANNOT be a numeric IP address. Enabled
Protocol Net Address
Enabled Ports - Internet Ports - Web tab TCP/IP port number TCP/IP port status Name & password Anonymous Internet Protocols - HTTP tab Host name
80 (or 8088 if tunneling is being used) Enabled Yes Yes
The fully qualified host name as known by the DNS server (this should be the fully qualified Internet host name on the Basics tab above). For example, stdom1.acme.com. Note: This CANNOT be a numeric IP address. Enabled (in iSeries configurations) Disabled (in AIX, Solaris, or Windows configurations)
Bind to Host name
Allow HTTP clients to browse databases Home URL DSAPI filter file names Internet Protocols - Domino Web Engine tab Session Authentication Web SSO Configuration
Yes (for portals, otherwise, not necessary) /stcenter.nsf If this field is set to NDOLEXTN (Domino Offline Services), remove the value. and leave this field to blank.
Multiple Servers (SSO) LtpaToken Note: This field may be left blank after Sametime installation. Make sure this field is completed. Domino Servlet Manager
Java servlet support
4. If you make changes, click Save and Close. 5. Stop and restart the Domino server for the changes to take effect.
Testing the Sametime Server

Once the server is set up, use the following procedures to ensure that Sametime 7.0 is functioning properly:
Validate Creating a New Meeting

Use this procedure to create a new meeting. For more detailed information, click the Help link on the left side of the New Meeting page in the Meeting Center. 1. From the Welcome to Sametime 7.0 page, click Schedule a Meeting. The New Meeting page displays 2. Choose a meeting type. For test purposes, you can leave the default meeting type of collaboration. 3. Enter a name for the meeting.
16
4. 5. 6. 7.
Leave your name in the Moderator field. Click Start Now. Choose a duration for the meeting. For test purposes, a short meeting should suffice. Click Save. The meeting starts.
Note: If the Meeting Details page displays and the meeting does not begin, click the Refresh button in your browser. The meeting starts in a separate browser window.
Validate Screen Sharing

After entering the meeting, click Screen Sharing and then Share my entire screen. A small floater box with two buttons should appear. You can validate that screen sharing is working by using a second computer and joining the meeting you have created by navigating to http://servername.domain.com/stcenter.nsf and clicking Attend a Meeting. Click the name of meeting that was just created and you should be able to join the meeting. Once you are in the meeting, the you should be able to see the screen of the initial computer that was used to create the meeting. More information regarding screen sharing and using the meeting room client can be found by clicking on Documentation on the Welcome to Sametime 7.0 page and then select Sametime 7.0 Meetings. See Presenting Information with Screen Sharing in the IBM Lotus Sametime 7.0 Users Guide. You have completed the procedures required to install Sametime 7.0 on Domino. Users in the Sametime 7.0 community can now use the Meeting Center to create and attend online meetings. Users in the Sametime 7.0 community who have installed Sametime Connect can also start to use instant meetings and chat with others in the community.
Starting and Stopping the Sametime 7.0 Server On Windows

To manually start or stop the server from the Windows desktop: 1. Select Start - Administrative Services - Component Services. 2. In the Services dialog box, select Services (Local). Right-click Lotus Domino Server (LotusDominoData) and select Start or Stop. Another way to start the server is from Start Programs - Lotus Applications - Lotus Domino Server. You can also stop the server by typing quit at the Domino Server Console. Note: If you installed on Domino, you need to stop the Domino server to stop the Sametime 7.0 services. The steps for starting an Sametime 7.0 server are the same as those for starting a Domino server.
Starting a Sametime Server on AIX or Solaris

To start an Sametime 7.0 server on AIX or Solaris: 1. Log in to the system as the default Domino user. Make sure the default path and environment are set correctly. 2. Start the Sametime 7.0 server by issuing the following server command. Note that starting the Sametime 7.0 server might take a few minutes.
./ststart
The ststart script file sets some important environment variables before launching the server executable (/opt/ibm/lotus/bin/server). If you want to launch the server automatically, add the ststart environment variables to the Domino users profile before launching the executable. You must add these variables to the users profile for Sametime 7.0 to work correctly.
17
Stopping a Sametime Server on AIX or Solaris

The steps for stopping an Sametime 7.0 server are the same as those for stopping a Domino server. To stop an Sametime 7.0 server: 1. Return to the terminal session where Domino was started. 2. If the prompt character > is not present, press the Enter key once to be presented with a prompt character. Then enter the command quit and press the enter key. Stopping the Sametime 7.0 server might take a few minutes. When shutting down the Sametime 7.0 server, the Domino console might report a fatal error and freeze all threads. If this problem occurs, follow the steps below to continue the shutdown. v Log in as the root user. Run the following command. Use the optional -nolog flag to prevent an nsd kill log file from being created.
$ /opt/lotus/bin/nsd -kill [-nolog]
v If the Domino console is still frozen, run the following set of commands:
$ ps -u notes | tail +2 | awk {print $2;} | xargs kill -9
This series of commands will kill all processes owned by the notes user.
Uninstalling the Sametime Server

Before you uninstall the Sametime server, it is always good practice to back up any important files.
Windows
To remove the Sametime server: 1. Stop the Domino / Sametime server before removing it. For instructions, see Starting and Stopping the Sametime 7.0 server. 2. From the Windows Start menu, select Settings - Control Panel - Add/Remove Programs. 3. Select Sametime 7.0 Server from the list and click Add/Remove. Click Yes when prompted to remove the Sametime 7.0 server. 4. When the Windows uninstall program completes, click OK to exit the reinstall program.
AIX and Solaris

For AIX and Solaris, you need to do the following: When you remove Sametime 7.0 from a Domino server, all files related to Sametime that were added to the Domino server data directory or were created while running Sametime components are removed. Updates that were made to the address books (including person documents, server documents, and changes to the Access Control List) are not removed. To remove Sametime, you need to remove both the Lotus directory and the Notes data directories.
18
Chapter 4. Upgrading to Sametime 7.0

This chapter includes step-by-step instructions for upgrading a previous version of Sametime to Sametime 7.0. Sametime 7.0 supports upgrades from Sametime 3.0, 3.1, and 6.5.1. If you have an earlier version of Sametime and want to upgrade to Sametime 7.0, you must uninstall the earlier version and follow the instructions in Chapter 2, Installing Sametime.
Upgrading to Sametime 7.0

Sametime 7.0 supports upgrades of Sametime 3.0, 3.1, and 6.5.1. If you have an earlier version of Sametime and want to upgrade to Sametime 7.0, you must uninstall the earlier version and follow the instructions for installing Sametime, earlier in this guide. Also, if you have installed Sametime on an earlier version of Domino and you want to upgrade to Sametime 7.0, you must upgrade the Domino server to Domino 7.0. After you have completed the Domino upgrade, you can install Sametime 7.0 on the Domino 7.0 server. See the section on installing Sametime for installation instructions.
19
20
Chapter 5. Installing other Sametime 7.0 features

This chapter describes other features that are available with Sametime 7.0. These features are not installed when you do the basic installation. These have to be done as separate installations. The instructions for the installation of these features are the same for the Windows, AIX and Solaris platforms.
Installing Other Sametime Features

Sametime 7.0 offers several other features that are available with Sametime 7.0. These features are not installed when you do the basic installation and must be installed separately. The instructions for the installation of these features are the same for the Windows, AIX and Solaris platforms. These addition features are located on installation CD in the following directories: v The Sametime Connect Client Packager files are in the /SametimeClientPackager directory. v The Session Initiation Protocol (SIP) Connector installation files are in the /SIPConnector directory. v The LDAP Directory installation files are in the /LDAP directory.
Installing the Sametime Connect Client Packager

The Sametime Connect client contains a presence list from which instant messaging sessions and instant meetings can be started. As part of your Sametime 7.0 roll out, you might want to instruct members of the community to download the Sametime Connect client from the Sametime 7.0 server and install the client on their local machines. The Sametime Connect client contains a variety of settings that affect the user features and network connectivity of the client. The Sametime 7.0 Client Packager application on the Sametime 7.0 CD allows you to customize and pre-configure the settings of the Sametime 7.0 Connect client so that end users do not have to configure these settings themselves. Run the Sametime 7.0 Client Packager application to ensure that each Sametime Connect client downloaded from the server is appropriately configured for your network environment. For further instructions, see: v Using the Sametime Client Packager application v Downloading and installing Sametime Connect
Using the Sametime Client Packager Application

The Sametime Client Packager application allows you to customize the Sametime 7.0 Client installation package for your users. You can determine whether or not the client includes support for optional features as well as connectivity and firewall settings (such as server name and port, and proxy server settings if applicable). If you do not create a customized installation package, each user will have to enter the connectivity settings. Note: This procedure creates a self extracting installation file named SametimeClient.exe. After creating the SametimeClient.exe file, you should place the file in the following directory on the Sametime 7.0 server C:\lotus\domino\data\domino\html\sametime. The file must have the name SametimeClient.exe. Placing the file in this location enables end users to access the pre-configured version of Sametime 7.0 Connect from the links available on the Sametime 7.0 server home page. You can prepare the self-extracting installation file as follows: 1. Obtain the SametimeClientPackager.exe file from the Sametime 7.0 CD2 and double-click this executable file. The package self-extracts.
21
2. Read the Welcome screen. You can click Cancel to exit the Setup at any time; click Next to continue. 3. Read the license agreement. Click Yes to accept the license agreement and run the packager. 4. You will be prompted to enter information in a series of dialog boxes. The information you are prompted to enter depends on your responses to the requested information. For example, if you select No proxy, then you will not be prompted to enter proxy settings. Enter the information as follows: a. Client Setup Location - Select the folder to which the created package will be written. b. Default Client Installation Location - Select the default folder to which the user installs the client, for example C:\Program Files\Lotus\Sametime Client. c. Select Features -- Choose Directory Browsing to include the corporate directory in the Sametime 7.0 Connect client. When you choose this option a Directory button is added to the Add Person or Group and Add to Invitation dialog boxes. d. Connect.ini File -- Optionally select a connect.ini file to be copied to the Sametime 7.0 Client setup file. If you supply an INI file, the connection information is automatically set up for each user. A simple way to create the INI file (located in the client installation directory) is to copy the file to another location, open it with a text editor and delete any unneeded information (for example, logic name and password). Note that when a user installs Sametime 7.0 Connect with an installation package containing a connect.ini file, any existing connect.ini file will be overwritten. Note: If you supply a connect.ini file, the Packager will proceed to step n (Creating package). If you do not want to supply an INI file, leave this field blank and continue to step e. Automatic Logon -- Allow users to save their user name, password, and proxy information to the INI file. Sametime Connectivity -- Specify the name or IP address and port number of the home Sametime 7.0 server. Enable shortcut key for launching or restoring the Connect client -- Allow users to minimize or bring up the connect clients using keystrokes only. Sametime Connection Type -- Choose the type of connection for the Sametime 7.0 Connect client: direct connection, direct connection using HTTP protocol, or proxy connection. If you selected a proxy connection, specify the proxy type and settings in the next two dialog boxes. Sametime 7.0 Proxy Type -- If you chose to use a proxy connection in the previous step, choose the proxy through which the users Sametime 7.0 Connect clients will connect to the Sametime 7.0 server. You can choose HTTPS, SOCKS4, SOCKS5, or HTTP.
e. f. g. h.
i.
j. Sametime 7.0 Proxy Server Settings -- Specify the name or IP address and port number of the proxy server. k. Allow installation with no user interaction -- Choose this option to run the install with all of the default settings. Selecting this option requires no user interaction during the install process. l. Keep-Alive Message Timeout -- This option checks the connectivity between Sametime 7.0 Connect and the Sametime 7.0 server, allowing the receipt of timely notification of disconnection from the server. Specify a time in seconds (default is 60 seconds); specify zero (0) to disable the feature. m. Silent install -- allows the Connect client to be installed silently without user interaction. n. Create Package -- Your current settings are summarized. Click Next to start copying the files. The client installation package is created and written to the location you specified. o. Packaging Complete -- Notifies you that the package has been created. Click Finish. Note: The settings specified from the client packager are used by all Sametime 7.0 Connect for the desktop clients downloaded from the server. However, the settings specified from the client packager do not apply to the Sametime 7.0 Connect for browsers clients that are loaded to end users from the server.
22
Downloading and Installing Sametime Connect

Users download Sametime Connect (sametimeclient.exe) from the Welcome to Sametime page. A user accesses the Welcome to Sametime page by entering http://servername.domain.com (where servername.domain.com is the name of the Sametime 7.0 server) in the URL locator of the Web browser. Note: Each user must have an Internet password in their Person document in the Domino Directory or an entry in the LDAP Directory before using Sametime Connect. The Internet password is required to log on to Sametime Connect. You might need to inform users of their Internet passwords. Follow these steps to download Sametime Connect: 1. From the Sametime server home page, click Download. 2. When the Download page displays, click Download the Sametime Connect for the desktop. 3. Run the Sametime Connect for the desktop installation. 4. The Welcome dialog box displays. Click Next to begin the installation. Follow the instructions on the installation screens. 5. When the Choose an Sametime 7.0 server name dialog box displays, enter the fully qualified DNS name (for example, sametime.acme.com) or the IP address of the Sametime 7.0 server. Click Next. Note: Step 5 might not be necessary if you have run the Sametime Client Packager application. 6. The Start Copying Files dialog box displays. Click Next. 7. Click Finish when the files have been copied. After Sametime Connect is installed, validate that you can connect by starting the Sametime Connect client and logging on to the server.
Installing the Session Initiation Protocol (SIP) Connector

Deploying a SIP Connector and enabling the Session Initiation Protocol (SIP) Gateway are optional procedures you can perform if you want users in your Sametime community to share presence and instant messaging capabilities with users in another SIP-enabled community. The SIP Connector must be installed on a different machine than an Sametime 7.0 server. The SIP Connector must be configured to connect to the Sametime 7.0 server to communicate with the SIP Gateway on the Sametime 7.0 server. A SIP Gateway resides on the Sametime 7.0 server by default following the Sametime 7.0 server installation. The SIP Connector must be installed before the SIP Gateway functionality is available to users in your community. You can enable this functionality to allow users in your community to communicate with users in another Sametime 7.0 community that contains a 7.0 server with the SIP Gateway functionality enabled. Note: The SIP Gateway functionality enables users in your community to communicate with users in any other instant messaging community that supports the SIP/SIMPLE protocol. MSN Messenger communities might support the SIP/SIMPLE protocol at some point in the future. Before installing the SIP Connector, consider the following: v The system requirements for the SIP Connector machine are the same as the system requirements for the core Sametime 7.0 server. For more information, see the System requirements section of this guide (stinstall.nsf) on the Sametime 7.0 server CD. v If the users in your community do not need to use the Internet to communicate with users in another community, you can install the SIP Connector on any Internet machine that has a LAN or WAN connection to the Sametime 7.0 server. The SIP Connector machine must be able to establish a TCP/IP connection to the Sametime 7.0 server on port 1516. The SIP Connector must be able to receive connections from other SIP-enabled communities on the TCP/IP port 5060 (the default SIP port).
Chapter 5. Installing other Sametime 7.0 features
23
v If the SIP Connector must connect to other SIP-enabled communities using the Internet, you can install the SIP Connector on a machine outside your corporate firewall that is available to Internet users. If you position the SIP Connector outside the firewall, the SIP Connector machine must be able to initiate connections to the Sametime 7.0 server machine inside the firewall. (The default port for these connections is port 1516). It might be necessary to configure the firewall with a set of access rules that establish trust between the Sametime 7.0 server and SIP Connector machines. (For example, the access rules might allow those machines to connect to each other through the firewall but prevent other machines from connecting to them). v If your Sametime 7.0 community includes multiple Sametime 7.0 servers, it is only necessary to install one SIP Connector to service the multiple SIP Gateways operating on your Sametime 7.0 servers. The SIP Connector connects to one of the Sametime 7.0 servers and creates channels to the SIP Gateways on all Sametime 7.0 servers through intraserver connections between the Sametime 7.0 servers. You can also install multiple SIP connectors. For example, if you want users in your community to connect to two separate SIP-enabled communities, you might want to install two separate SIP Connectors. Installing multiple SIP Connectors can spread the connection handling load among multiple machines; each SIP Connector handles the incoming and outgoing connections for only one of the external communities. You can configure each SIP Connector to connect to a different Sametime 7.0 server in your community. You can also install multiple SIP connectors and configure them to handle connections for the same SIP-enabled community. Such a configuration ensures that a SIP Connector is available if one SIP Connector machine fails. To install the SIP Connector feature: 1. Insert the Sametime 7.0 Installation CD2 into the CD-ROM drive of a machine that does not have Sametime 7.0 installed. 2. Obtain the SIP Connector EXE file from the Sametime 7.0 CD and double-click this executable file. The package self-extracts. 3. Read the Welcome screen. You can click Cancel to exit the Setup at any time; click Next to continue. 4. Read the license agreement. Click Yes to accept the license agreement and run the package. 5. During the installation, you must enter the following: v The IP address or DNS name of an Sametime 7.0 server. This address enables the SIP Connector and the SIP Gateway on the Sametime 7.0 server to communicate. v A SIP Connector name. SIP Connector configuration data is organized under this name. The SIP Connector requires this name to get its configuration parameters. You can enter the DNS name of the Sametime 7.0 server as the SIP Connector name. The SIP Connector configuration parameters are stored in a CommunityConnector document in the stconfig.nsf database on the Sametime 7.0 server. You create this document later in this process. 6. At the next dialog box, Start Copying Files, click Next. 7. At the next dialog box, Setup Complete, click Finish. 8. Start the Sametime 7.0 server. For more information on Community Services, see the Configuring the Community Services chapter inthe IBM Lotus Sametime 7.0 Administrators Guide.
24
Chapter 6. Troubleshooting
This chapter gives information about problems that you may encounter when you are installing or running Sametime 7.0. If you need toverify which version of the IBM Lotus Sametime 7.0 (Sametime 7.0) Server you have installed, open your browser and in the Address field, type: http:// servername.domain.com /Sametime 7.0/buildinfo.txt. Substitute your Sametime 7.0 servers name for servername.domain.com.
Troubleshooting Sametime 7.0 Installation

Many of these solutions reference Technotes. You can check for Technotes at http://www.ibm.com/software/support. Problem You have just installed Sametime 7.0, but the Sametime 7.0 Meeting Server services fail to start. You see the following in the Misc Events view in the log.nsf:
05:53:43 05:53:49 05:54:33 05:54:33 05:54:33 05:54:33 05:54:33 Sametime 7.0 Server: Running Finished updating usage statistics Sametime 7.0: Service failed to initialize in allowed time Sametime 7.0: Service [Java Services] failed to start. Sametime 7.0: One or more services failed to start. Sametime 7.0: Server startup failed. Sametime 7.0: Stopping services. Shutting down...
Solution If you are installing on the AIX or Solaris platforms, please check the following: Create a new Directory Assistance database and add the filename to the Sametime 7.0 Server document. Create a new LDAPServer form in the Sametime 7.0 Configuration (stconfig.nsf) database. Please refer to Technote 1098735 for common resolutions to these types of issues. Problem You see error messages similar to the following while attempting to start the stmux directly:
$ stmux exec(): 0509-036 Cannot load program stmux because of the following errors: 0509-150 Dependent module libvpk.so could not be loaded. 0509-022 Cannot load module libvpk.so. 0509-026 System error: A file or directory in the path name does not exist.
Solution In order for the Sametime 7.0 Community MUX to start correctly, the $PATH environment variable must include the path to the MUX binaries, and the $LIBPATH must include the path to the libraries needed for the stmux executable. Problem On occasion, the Sametime 7.0 server on the AIX or Solaris platform does not terminate all Sametime 7.0 processes upon server shutdown.
25
Solution As a workaround to this problem, run the following script on the server:
#!/usr/bin/sh DOMINO_PROGRAM_DIR=/opt/lotus ps -ef |grep $DOMINO_PROGRAM_DIR | awk {print $2} | xargs kill -9
To 1. 2. 3.
execute the script, do the following: Save the script on the server. Change to the directory where the script is saved. Launch the script by typing: ./<scriptname> where <scriptname> is the name of the file where the script was saved.
Dependencies: v The script should be run by the Domino user. v The Domino user must have permission to run the script. v The path for sh at the top of the script must be changed to the correct value if /usr/bin/sh does not exist. The DOMINO_PROGRAM_DIR environment variable at the top of the script needs to be modified to the appropriate value, if the default installation settings were not used. Problem Some IP addresses in the Sametime 7.0.log file are printing backwards on the Sametime 7.0 AIX server with a stand-alone Sametime 7.0 Community Multiplexer (MUX). For example, instead of 123.123.123.123, you see 321.321.321.321. Solution In rare cases, the IP address will be printed incorrectly in reverse order. There is no workaround to this problem, but it does not negatively effect performance. Problem You are unable to log in to administer the server link on the stcenter.nsf page via the browser. Solution Try these suggestions: v Make sure that you are using the fully qualified Internet host name in the format of http://server.domain.com to access the server from the browser. Using the short name like http://server will cause authentication to fail. v Check the Fully Qualified Domain name under the Basics tab and Ports - Notes Networks Ports - Net Address fields to ensure the proper name is being used. v Check the following fields in the Web SSO Configuration document. If these settings are not set correctly, it may be necessary to delete and recreate the document. The Sametime server is listed in the Participating Servers field The Token name is set to LtpaToken The DNS Domain is set correctly For additional suggestions, see Technote 1086545. Problem Several services such as the Sametime Meeting Server, ST Users and ST Directory do not launch successfully.
26
Solution The server is most likely being started using Windows Terminal Services or Remote desktop. Do not use these terminal programs to administer the server as the Sametime Server may not be able to communicate over certain ports due to operating system restrictions. See Technote 1106554 for more information. Problem During the Sametime Setup, you encounter the following error: Error encountered in the local server Indexing help index on Doc\sthelpad.nsf Solution 1. Remove the HKEY_LOCAL_MACHINE\SOFTWARE\Lotus\Sametime registry key. 2. Remove entries from the notes.ini containing Sametime or st in them, including the line starting with StProgramDirectory. 3. Reboot Windows. 4. Install Sametime 7.0 again. 5. Run STSetup again. You should get through the setup without error. In some cases, it may also be necessary to delete the full text index (FTI) of the database. The easiest way to delete a FTI is to view the Data directory via the Operating System (OS) and delete the folders that contain the full text information you are interested in. Directories that contain FTI end with *.ft and begin with the OS name of the database. The full text index is stored in a folder called \Domino\Data\Doc\sthelpad.ft. Deleting the folder deletes the full text index. Problem During the Sametime Setup, you encounter the following error: Error updating JavaUserClasses in notes.ini. After clicking OK, the Sametime server is not installed. In some cases, the JavaUserClasses line of the notes.ini is present and other times it is empty. Removing the line and attempting to reinstall results in the same problem. Copying a JavaUserClasses line from a good install of Sametime does not help. Solution To 1. 2. 3. work around this issue, complete the following steps: Make sure Domino is not running. Edit the notes.ini file and remove the javauserclass parameter. Replace that parameter with:
DominoBypassFlag=-vnver6
4. Save the NOTES.INI and restart the install. You should now be able to rung stsetup.exe from the lotus\domino directory (this .exe runs the configuration portion of the Sametime setup). After the setup is complete, the flag can be removed from the notes.ini and Sametime will be setup correctly.
Chapter 6. Troubleshooting
27
28
Chapter 7. Installing and Setting Up Domino for Sametime

This chapter provides instructions for setting up an existing Domino 7.0 server for installation of a Sametime 7.0 server. Domino 7.0 must be installed before you install Sametime. If you have not already installed a Domino 7.0 server, this chapter provides general instructions for installing a Domino 7.0 server on Windows, AIX, and Solaris. For complete instructions on installing a Domino server, see the Lotus Domino 7.0 Administrator help. To download or view the Lotus Domino 7.0 Administrator Help, go to http://www.ibm.com/developerworks/lotus.
Domino Installation Overview

This section provides general instructions for installing Domino 7.0. However, if you have never installed and set up a Domino server, it is strongly recommended that you refer to the Domino Administrator 7 help to get a full understanding of how to install and set up a Domino server. For complete instructions on installing a Domino server, see the Lotus Domino 7.0 Administrator help. To download or view the Lotus Domino Administrator 7 Help, go to http://www.ibm.com/developerworks/lotus. You can install a Domino server and configure it for Sametime, on the following platforms: v Install a Domino server on the Windows platform v Install a Domino server on an AIX or Solaris platform v Set up the Domino server v Install and set up the Domino Administrator and Notes clients.
Installing Domino on Windows

You must install the Sametime 7.0 server on a Domino 7.0 server. See the topic System Requirements for complete information regarding servers supported by Sametime 7.0. Sametime 7.0 uses the directory, security, and replication features of the Domino 7.0 server. It is best if the Sametime 7.0 server is dedicated to supporting the real-time, interactive communication services of Sametime 7.0. For best performance, do not use the Sametime server for other high-demand Domino services such as mail storage and routing, application and database storage, or centralized directory and administration services. An iSeries or pSeries server can run multiple partitioned servers on the same Domino system. While it is possible to add Sametime 7.0 to an existing production Domino server, this configuration is not recommended. Instead, consider creating a new Domino server dedicated to running Sametime. The new Domino server can reside on the same system as your existing production server. Users must access the Sametime 7.0 server with a Web browser. IBM Lotus Notes client access to the Sametime 7.0 server home page (stcenter.nsf). All other Sametime 7.0 clients, including the Sametime 7.0 Connect client, can be downloaded by end users from the Sametime 7.0 server home page. To support the first Sametime server installed into your environment, the Domino server must be installed as a first server in a Domino domain. Step-by-step instructions for installing the Domino 7.0 server in this way are provided below. These steps describe a basic Domino server installation that can support Sametime 7.0.
29
For more detailed information about Domino server installations and Domino environments, see the Domino Installation Guide available from the documentation library of the Lotus Developers Domain web site at http://www.ibm.com/developerworks/lotus. If you are installing more than one Sametime 7.0 server, review the issues and procedures that are discussed in the Deploying multiple Sametime 7.0 servers chapter of the IBM Lotus Sametime 7.0 Administrators Guide before installing the additional Sametime 7.0 servers.
Before you install

Before you install the Domino server program files on a Windows platform, do the following: 1. Make sure that the required hardware and software components are in place and working. 2. Temporarily disable any screen saver and turn off any virus-detection software. 3. Make sure that all other applications are closed. Otherwise, you may corrupt any shared files, and the install program may not run properly. Note: If you are upgrading to Domino from a previous release, see the Domino Upgrade Guide available from the documentation library of the Lotus Developers Domain web site at http://www10.lotus.com/ldd/doc.
Installing Domino
To install Domino on a Windows platform, follow these steps. 1. Run the install program (SETUP.EXE), which is on the Domino server installation CD. 2. Read the Welcome screen, and click Next. Then read the License Agreement and click Yes. 3. Enter the administrators name and the company name. Do not elect to install Domino on partitioned servers. 4. Choose the program and data directory in which to copy the software, and then click Next. 5. Select Domino Enterprise Server as the server type. 6. Click Next to accept all components. 7. Specify the program folder or accept Lotus Applications as the program folder that will contain the software. 8. Click Finish to complete the install program. 9. Choose Start - Programs - Lotus Applications - Lotus Domino Server to start the Server Setup program.
Using the Domino Server Setup Program Locally

After installing the Domino server program files on a server, you run the Domino Server Setup program locally by starting the server. The Server Setup program asks a series of questions and guides you through the setup process. Online Help is available during the process.
Starting and Shutting Down the Domino Server

Start the Domino server so users can access shared databases and obtain other server services. Do not enter keystrokes or click the mouse while the Domino server is starting or shutting down. If the server program is running, do not use CTRL+S to stop scrolling the console, because no server services take place until you press a key to continue. Starting the server -- To start the Domino server from Windows, choose Start - Programs - Lotus Applications - Lotus Domino Server or start the service Lotus Domino Server (LotusDominoData) from the OS Control panel. Shutting down the server -- To shut down the Domino server, type exit or quit at the console. It may take several seconds for the server to shut down.
30
Next Step Set up the Domino server.
Installing the Domino Server on AIX or Solaris

If you are installing a new Domino 7.0 server for your Sametime 7.0 server, use these general directions. For complete instructions on installing a Domino server, see the Lotus Domino Administrator 7 help. To download or view the Lotus Domino Administrator 7 help, go to http://www.ibm.com/developerworks/lotus. Since you must add Sametime 7.0 to an existing Domino server, Domino software is included with the Sametime 7.0 package. If you have not separately purchased a Domino server license for this server, you are authorized to use the included copy of Domino on a single server, but only to run Sametime 7.0. The Domino installation programs for all versions of UNIX are simply scripts that ask for configuration information and then install the software in the appropriate directories. The instructions below are provided to remind you of the necessary steps to install Domino; the procedure assumes that you have a working knowledge of Domino administration. To install Domino: 1. Place the CD in the CD-ROM drive. 2. Become the root user by logging in as the root user or using the su command. Open Operations Navigator. 3. Mount the CD to make it available. You can mount the CD using the SMIT utility or the appropriate version of the following command:
mount -r -v -cdrfs /dev/cd0 /cdrom
4. Using the above example, change to the /cdrom directory and look for the ibmpow subdirectory (AIX) or the sunspa subdirectory (Solaris). Change to the appropriate directory. 5. Start the installation script using the following command:
./install
6. Follow the directions on each panel of the script, making sure to retain the information you provide for the location of the Domino executable directory and the Domino data directory. You will need this information when you install Sametime 7.0. After you have installed the Domino server, you must start and stop the Domino server at least once before installing the Sametime 7.0 server. This allows certain files to be created that Sametime 7.0 needs in order to install correctly.
Using the Domino Server Setup Program Locally

After installing the Domino server program files on a server, you run the Domino Server Setup program locally by starting the server. The Server Setup program asks a series of questions and guides you through the setup process. Online Help is available during the process.
Starting the Domino Server

To start the Domino server from AIX or Solaris, enter the path for the Domino program directory. For example, if you installed Domino in the /opt directory, enter:
/opt/ibm/lotus/bin/server
Shutting down the Domino Server

To shut down the Domino server, type exit or quit at the console. It may take several seconds for the server to shut down. Next Step
31
Set up the Domino server.
Adding a Domino Server to an Existing Domino Domain

If you are adding a server to an existing Domino domain for use as a Sametime server, you register the server before you can install Domino. When you do so, make sure to specify the following settings during registration: v Set the minimum password length to 0 so that Domino will not require a password on the Sametime 7.0 server. Sametime 7.0 cannot be added to a Domino server when the server ID file is password-protected. (Access to the Sametime 7.0 server will be controlled through Sametime 7.0 rather than Domino.) v Store the server ID file that is created during registration somewhere on your server where you will configure the Sametime 7.0 server. Record the path name; you will need to specify it when you configure the Sametime 7.0 server. v Use the same network name as the first Domino server in the Domino domain. For detailed information about registering an additional server, see the Lotus Administration documentation. The registration process creates a Server document in the Domino Directory.
Setting Up the Domino Server

The server setup program launches the first time you start the Domino server. During the setup program, you will need to provide the following information.
First Server
To set up a stand-alone server or the first server in a new Domino domain:
Field or option First or additional server? Server Name Organization Name Domino Domain Name Administrators Name Web Browsers (HTTP services) Internet Mail clients Directory Services (LDAP services) Internet Services - Customize Description Select Set up the first server or a new Domino domain. Enter the name of the Domino server where you will add Sametime 7.0. For example, specify STDOM1. Enter the name for the organization. This is usually the name of the company, such as IBM. Enter the name of the Domino domain. A domain is a collection of servers that share a Domino Directory. For example, LotusEast. Specify the Domino administrators name. This administrator will also be the Sametime 7.0 server administrator. Check this option. Sametime 7.0 requires that you use the Domino HTTP server. To reduce overhead, do not check. Sametime 7.0 does not require mail packages. Check this only if you will be using an LDAP directory. If you are using a Domino Directory, Sametime 7.0 does not require Directory Services. From the Internet Services screen, click Customize. Make sure the following Domino server tasks are not selected: v DOLS Domino Offline Services v DIIOP CORBA Services Note: The HTTP Server task should be checked. If it is not, check it.
32
Additional Server
If you are setting up an additional server in an existing Domino domain, select Set up an additional server when you begin the setup program. In addition to the setup options listed above, you also need to provide this information:
Field or option Get Domino Directory From Description Enter the name of the Domino server that has the Domino Directory that this server will use. Make sure to enter the hierarchical name of the server, for example, enter servername/company. Specify the path of the server ID file that was created when you registered the Sametime 7.0 server. For example, enter /LOTUS/DOMINO/stdom1.id. Leave blank. Note: If you specify a password for the server ID file, you will not be able to add Sametime 7.0 to this server. When you register the servers ID, set the password strength to 0 and do not specify a password.
Where is the server ID file? Optional Server ID password
Next Step Install and configure the Administrator and Notes clients.
Installing and Configuring the Notes Client and Domino Administrator Client
To administer the Domino server, you must install and configure at least one Windows PC as the administration workstation. Using the Domino software that shipped with Sametime 7.0, you must install and configure the Domino Administrator and Notes clients on the administration workstation. Note: Before you can install the Domino Administrator and Notes clients you must install and set up the Domino server. To install and configure the Domino Administrator and Notes clients: 1. Insert the Notes Client CD into the PC you plan to use as the administrators workstation. 2. Follow the instructions on each panel of the Notes installation wizard, selecting to install both the Domino Administrator and Notes clients. 3. Copy the certifier ID and administrator ID files from the Domino data directory of your Domino server to the Notes data directory of the Administrator workstation. You can use File Transfer Protocol (FTP) or another method, or you can let the initial communications between the server and administration workstation copy the files for you automatically. 4. If necessary, start the Domino Server. 5. Open Lotus Notes. 6. Follow the instructions in the setup wizard to configure the Notes Client. If you have moved the certifier and administrator ID files to the PC you have designated as your administration workstation, indicate the correct location when asked. If you have not copied the ID files, simply provide the user administrator name you specified during HTTP setup. You will be prompted for the password for this ID. The ID files will be copied and stored on your administration workstation for you automatically. Next Step When you have set up the Notes and Administrator clients, you are ready to begin preparing the Domino server for Sametime installation.
33
34
Chapter 8. Notices
This information was developed for products and services offered in the U.S.A. IBM may not offer the products, services, or features discussed in this document in other 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 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 grant 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 or send inquiries, in writing, to: IBM World Trade Asia Corporation Licensing 2-31 Roppongi 3-chome, Minato-ku Tokyo 106-0032, Japan The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION 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. 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 which has been exchanged, should contact: IBM Corporation Office 4360 One Rogers Street Cambridge, MA 02142 U.S.A. Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee.
35
The licensed program described in this information and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement, or 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 IBMs future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only. All IBM prices shown are IBMs suggested retail prices, are current and are subject to change without notice. Dealer prices may vary. This information is for planning purposes only. The information herein is subject to change before the products described become available. 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.
Trademarks
Domino, QuickPlace, AIX, iSeries, i5/OS, OS/400, z/OS, and zSeries Lotus, LotusScript, Notes, Notes Mail, Sametime, WebSphere,TeamRoom, and Word Pro are trademarks or registered trademarks of Lotus Development Corporation and/or IBM Corporation, in the United States, other countries, or both. UltraPort, iSeries, pSeries, and zSeries are trademarks and IBM, SecureWay, Thinkpad, and WebSphere are trademarks or registered trademarks of International Business Machines Corporation. Additional IBM copyright information can be found at: http://www.ibm.com/legal/copytrade.shtml. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. in the United States and other countries. Products bearing SPARC trademarks are based upon an architecture developed by Sun Microsystems, Inc. Java, the Java logo, Sun, and Solaris are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. Microsoft, Windows, Windows NT, ActiveX, MSN, Outlook, PowerPoint, and the Windows logo are registered 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 US and other countries.
36
Linux is a trademark of Linus Torvalds in the United States, other countries, or both. Other company, product, or service names may be trademarks or service marks of others.
Third Party Notices For the XSL and XML Parser and Processor
The Apache Software License, Version 1.1 Copyright (c) 1999-2000 The Apache Software Foundation. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. 3. The end-user documentation included with the redistribution, if any, must include the following acknowledgment: This product includes software developed by the Apache Software Foundation (http://www.apache.org/). Alternately, this acknowledgment may appear in the software itself, if and wherever such third-party acknowledgments normally appear. 4. The names Xerces and Apache Software Foundation must not be used to endorse or promote products derived from this software without prior written permission. For written permission, please contact apache@apache.org. 5. Products derived from this software may not be called Apache, nor may Apache appear in their name, without prior written permission of the Apache Software Foundation. THIS SOFTWARE IS PROVIDED ``AS IS AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE APACHE SOFTWARE FOUNDATION OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. This software consists of voluntary contributions made by many individuals on behalf of the Apache Software Foundation and was originally based on software copyright (c) 1999, International Business Machines, Inc., http://www.ibm.com. For more information on the Apache Software Foundation, please see http://www.apache.org/.
For DSIG base64

COPYRIGHT 1995 BY: MASSACHUSETTS INSTITUTE OF TECHNOLOGY (MIT), INRIA This W3C software is being provided by the copyright holders under the following license. By obtaining, using and/or copying this software, you agree that you have read, understood, and will comply with the following terms and conditions:
Chapter 8. Notices
37
Permission to use, copy, modify, and distribute this software and its documentation for any purpose and without fee or royalty is hereby granted, provided that the full text of this NOTICE appears on ALL copies of the software and documentation or portions thereof, including modifications, that you make. THIS SOFTWARE IS PROVIDED AS IS, AND COPYRIGHT HOLDERS MAKE NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED. BY WAY OF EXAMPLE, BUT NOT LIMITATION, COPYRIGHT HOLDERS MAKE NO REPRESENTATIONS OR WARRANTIES OF MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF THE SOFTWARE OR DOCUMENTATION WILL NOT INFRINGE ANY THIRD PARTY PATENTS, COPYRIGHTS, TRADEMARKS OR OTHER RIGHTS. COPYRIGHT HOLDERS WILL BEAR NO LIABILITY FOR ANY USE OF THIS SOFTWARE OR DOCUMENTATION. The name and trademarks of copyright holders may NOT be used in advertising or publicity pertaining to the software without specific, written prior permission. Title to copyright in this software and any associated documentation will at all times remain with copyright holders.
For STLport
License Agreement Boris Fomitchev grants Licensee a non-exclusive, non-transferable, royalty-free license to use STLport and its documentation without fee. By downloading, using, or copying STLport or any portion thereof, Licensee agrees to abide by the intellectual property laws and all other applicable laws of the United States of America, and to all of the terms and conditions of this Agreement. Licensee shall maintain the following copyright and permission notices on STLport sources and its documentation unchanged : Copyright 1999,2000 Boris Fomitchev This material is provided as is, with absolutely no warranty expressed or implied. Any use is at your own risk. Permission to use or copy this software for any purpose is hereby granted without fee, provided the above notices are retained on all copies. Permission to modify the code and to distribute modified code is granted, provided the above notices are retained, and a notice that the code was modified is included with the above copyright notice. The Licensee may distribute binaries compiled with STLport (whether original or modified) without any royalties or restrictions. The Licensee may distribute original or modified STLport sources, provided that: The conditions indicated in the above permission notice are met; The following copyright notices are retained when present, and conditions provided in accompanying permission notices are met : Copyright 1994 Hewlett-Packard Company Copyright 1996,97 Silicon Graphics Computer Systems, Inc. Copyright 1997 Moscow Center for SPARC Technology. Permission to use, copy, modify, distribute and sell this software and its documentation for any purpose is hereby granted without fee, provided that the above copyright notice appear in all copies and that both
38
that copyright notice and this permission notice appear in supporting documentation. Hewlett-Packard Company makes no representations about the suitability of this software for any purpose. It is provided as is without express or implied warranty. Permission to use, copy, modify, distribute and sell this software and its documentation for any purpose is hereby granted without fee, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation. Silicon Graphics makes no representations about the suitability of this software for any purpose. It is provided as is without express or implied warranty. Permission to use, copy, modify, distribute and sell this software and its documentation for any purpose is hereby granted without fee, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation. Moscow Center for SPARC Technology makes no representations about the suitability of this software for any purpose. It is provided as is without express or implied warranty. Copyright 2001 by STLport
For MD5 hash

Copyright (C) 1990, RSA Data Security, Inc. All rights reserved. License to copy and use this software is granted provided that it is identified as the RSA Data Security, Inc. MD5 Message-Digest Algorithm in all material mentioning or referencing this software or this function. License is also granted to make and use derivative works provided that such works are identified as derived from the RSA Data Security, Inc. MD5 Message-Digest Algorithm in all material mentioning or referencing the derived work. RSA Data Security, Inc. makes no representations concerning either the merchantability of this software or the suitability of this software for any particular purpose. It is provided as is without express or implied warranty of any kind. These notices must be retained in any copies of any part of this documentation and/or software.
For Log4J Logging

The Apache Software License, Version 1.1 at http://www.apache.org/LICENSE, 24 May 2002 The Apache Software License, Version 1.1 Copyright (c) 2000 The Apache Software Foundation. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. 3. The end-user documentation included with the redistribution, if any, must include the following acknowledgment: This product includes software developed by the Apache Software Foundation (http://www.apache.org/). Alternately, this acknowledgment may appear in the software itself, if and wherever such third-party acknowledgments normally appear. 4. The names Apache and Apache Software Foundation must not be used to endorse or promote products derived from this software without prior written permission. For written permission, please contact apache@apache.org.
Chapter 8. Notices
39
5. Products derived from this software may not be called Apache, nor may Apache appear in their name, without prior written permission of the Apache Software Foundation. THIS SOFTWARE IS PROVIDED ``AS IS AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE APACHE SOFTWARE FOUNDATION OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. This software consists of voluntary contributions made by many individuals on behalf of the Apache Software Foundation. For more information on the Apache Software Foundation, please see <http://www.apache.org/>. Portions of this software are based upon public domain software originally written at the National Center for Supercomputing Applications, University of Illinois, Urbana-Champaign.
40
Index A
AIX installing Sametime remotely 9 setting up to install Sametime 4 authentication setting up 11 Installing (continued) Notes and Domino Administrator clients 33 Sametime 7 Sametime installation (continued) on partitioned servers 9 overview 5, 7 procedure 7 remote 9 roadmap 1 troubleshooting 25 Sametime server starting and stopping 17 testing 16 uninstalling 18 upgrading 19 Server document configuring for Sametime installation 15 Session Initiation Protocol Connector installing 23 SIP see Session Initiation Protocol Connector 23 Solaris installing Sametime remotely 9 setting up to install Sametime 4 SSO authentication setting up 11 System requirements described 2
L
LDAP directory configuring 12 configuring the settings 13 Directory Assistance document 12 troubleshooting configuration 12
D
Directory determining the type 5 Directory Assistance document altering 12 Domino Administrator client installing 33 Domino Directory populating 14 Domino server adding to an existing domain 32 installation overview 29 installing on AIX or Solaris 31 installing on Windows 29 preparing for Sametime installation Domino Server document configuring 15
N
Notes client installing 33
P
3 Partitioned server installing Sametime on 9
S
Sametime Client Packager installing 21 Sametime Connect installing 23 Sametime Connect Client Packager installing 21 Sametime installation additional Sametime features 21
I
Installation roadmap 1 Installing Domino on AIX or Solaris Domino on Windows 29 31
T
Troubleshooting LDAP configuration 12 Sametime installation 25
41

Stinstall

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Stinstall

Uploaded by

Copyright:

Available Formats

Lotus Sametime

Chapter 4. Upgrading to Sametime 7.0

Chapter 2. Preparing the Domino Server for Sametime Installation . . . . . . . 3

Chapter 5. Installing other Sametime 7.0 features . . . . . . . . . . . . . 21

Chapter 3. Installing Sametime 7.0 . . . 7

Chapter 7. Installing and Setting Up Domino for Sametime . . . . . . . . 29

IBM Lotus Sametime 7.0 Installation Guide

Chapter 1. Sametime 7.0 Installation Overview

Sametime Installation Roadmap

IBM Lotus Sametime 7.0 Installation Guide

Chapter 2. Preparing the Domino Server for Sametime Installation

Preparing the Domino Server for Sametime

Domino Server Checklist

Setting the AIX or Solaris Environment

IBM Lotus Sametime 7.0 Installation Guide

Determine the Directory Type

Possible Scenarios for Sametime Installation

Chapter 2. Preparing the Domino Server for Sametime Installation

IBM Lotus Sametime 7.0 Installation Guide

Chapter 3. Installing Sametime 7.0

Sametime Server Installation Overview

Before You Begin

Run the Install CD

4. Start the installation process with this command:

5. Choose the install options.

IBM Lotus Sametime 7.0 Installation Guide

Remote AIX or Solaris Installation

AIX or Solaris Environment:

Installing Sametime 7.0 on Domino Partitioned Servers

Chapter 3. Installing Sametime 7.0

Sametime 7.0 Installation

IBM Lotus Sametime 7.0 Installation Guide

Sametime 7.0 Configuration

Configuring the Sametime Server to Access the LDAP Directory

Troubleshooting LDAP Configuration Information

Altering the Directory Assistance Document

IBM Lotus Sametime 7.0 Installation Guide

Configuring the LDAP Directory Settings

Chapter 3. Installing Sametime 7.0

Populating the Domino Directory

In a New Domino Domain

In an Existing Domino Domain

IBM Lotus Sametime 7.0 Installation Guide

Verifying the Domino Server Document Settings

Administer the server from a browser Internet authentication

Chapter 3. Installing Sametime 7.0

Basics tab Port

Protocol Net Address

80 (or 8088 if tunneling is being used) Enabled Yes Yes

Bind to Host name

Java servlet support

Testing the Sametime Server

Validate Creating a New Meeting

IBM Lotus Sametime 7.0 Installation Guide

Validate Screen Sharing

Starting and Stopping the Sametime 7.0 Server On Windows

Starting a Sametime Server on AIX or Solaris

Stopping a Sametime Server on AIX or Solaris

Uninstalling the Sametime Server

AIX and Solaris

IBM Lotus Sametime 7.0 Installation Guide

Chapter 4. Upgrading to Sametime 7.0