Your Domino-based Lotus® Sametime® server running on IBM i (formerly known as i5/OS) does not work. What should you check first?
Note: This technote applies only to Domino-based Sametime servers which includes:
- Sametime Standard and Entry servers prior to release 8.5
- Sametime Community server and Sametime Entry servers for release 8.5 and later.
There are several common situations that are responsible for most problems with Domino-based Sametime servers running on IBM i. Most (but not all) are setup or configuration problems.
Unfortunately, it is difficult and time-consuming to retrace all of the steps you completed to configure a Sametime server, attempting to find the point where the problem arose. This document should help you efficiently determine whether one of these common situations is responsible for the problem you are having, and get you quickly on track to resolving it.
Note: It is easy to believe that if your previous release of Sametime was working correctly before you upgraded to a new release of Sametime, that your server cannot be suffering from a configuration problem. However, this is not the case. Sometimes an incorrect configuration will not have any apparent impact on an earlier release of Sametime but will cause a problem after upgrade.
This document contains information about identifying and resolving the following problems with Sametime installations on IBM i:
- System requirements not met or insufficient system resources
- Java installation is incomplete or out of date
- Important fix is not installed
- Not using Fully Qualified Host Name to access server
- Have not installed or configured optional components for slides or whiteboard area of meeting room
- Server document is incorrect
- Server host name configuration is incorrect
- Sametime server encountering TCP/IP Port conflicts
If you are unable to resolve the problem, using this document or other available technotes, contact Lotus Customer Support. There may be interim fixes available that will correct the problem.
1. System requirements not met or insufficient system resources
First you should verify that all system hardware and software requirements are met for running your release of Sametime.
See the technote "Sametime for IBM i: System Requirements" (#1092193).
If your system meets all of the stated requirements, but your Sametime server sometimes fails to start or takes a very long time to start, you may have insufficient resources available. Starting a Sametime server consumes more system resources than running a Sametime server once it has started. You may be encountering internal time-outs during server startup. The most common reasons are:
- Insufficient memory or fewer than 4 disk drives. (Even if the system has plenty of disk space, a small number of disk drives can cause severe I/O contention during start up, resulting in time-outs.)
- There may be too much non-Sametime activity on your system at the time you try to start the server.
You may be able to circumvent the problem temporarily by starting the server when the non-Sametime activity on the system is relatively low. It is also possible to increase the internal time-out values. However, the start up times will continue to be very long and occasional startup failures will likely still occur until you correct the system resource issues.
More detailed information about startup issues is available in the technote "Sametime on IBM i: common reasons for server not starting" (#1097835). This technote also describes how to increase the internal time-out values.
2. Java installation is incomplete or out of date
To determine whether your Java installation is complete, follow these steps:
- From any IBM i command line, run the DSPSFWRSC command.
- When the list of software products is displayed, page down until you find the IBM Developer Kit for Java, 5722JV1 (IBM i 5.4) or 5761JV1 (IBM i 6.1 or 7.1):
Required Java options
*BASE plus option 8 (J2SE 5.0 32bit)
*BASE plus option 7 (JDK 5.0)
If using Domino 7, option 6 (JDK 1.4) is also required.
7.5.x and 7.0
*BASE plus option 6 (JDK 1.4)
- Once the product and options are installed, make sure you have installed the recommended level of the Java Group PTF. The recommended level and the procedure for checking it depends on the level of your operating system. Even if you already have the latest Java Group PTF installed, you must reinstall it after you install a new option of 5722JV1 for the first time; this is necessary to apply the appropriate fixes for the new option. For the latest information, see the technote "Sametime for IBM i: What system fixes are required?"(#1089996).
3. Important fix is not installed
The technote"Sametime for IBM i: What system fixes are required?" (#1089996) describes important information about the fixes that you should have installed on your system. Review the technote and make sure you have all of the recommended fixes. The technote describes:
- Domino updates that affect Sametime
- Sametime updates
- PTFs required for various levels of the operating system (IBM i)
- Required Java Group PTF
- How to check level of PTF CUM package currently installed on the system
4. Not using Fully Qualified Host Name to access server
You are able to start the Sametime server and you are able to access the Sametime Welcome Page, but are unable to login.
Make sure you are specifying the server's fully qualified host name in the URL. For example, you must specify a URL similar to this: http://stserver.acme.com
5. Have not installed or configured optional components for slides or whiteboard area of meeting room
Note: this section applies only to Sametime releases prior to 8.5 and to classic Sametime 8.5 servers, that is, meetings running on the Domino-based Sametime server.
For IBM i, there are two meeting room functions that are available only if you install and configure certain optional components. If your Sametime server is functioning correctly except for a problem with the meeting room whiteboard or with files attached to meetings, you may not have installed one of these components.
- If meeting attachments (other than attachments prepared with the Sametime Print Capture Utility) are not displayed in the Slides section of the meeting, you probably have not configured Sametime Conversion Services. If you do not configure Sametime Conversion services, you must use the Sametime Print Capture Utility to prepare each attachment that you want to display on the whiteboard.
For Sametime 8.x and 7.5.1, there are two alternatives for running Sametime Conversion Services: either install the services on a separate Windows system (a remote conversion server), or run the function as an integrated part of your Sametime server (integrated conversion services). Both alternatives require some preparation whether you are installing Sametime for the first time or upgrading from a previous release. If you plan to make significant use of Sametime Conversion Services, a remote conversion server is preferred as it provides more faithful rendering of the slides for non-Windows Sametime servers and because the task is offloaded to a separate server, it does not affect the performance of other Sametime functions.
For detailed information, see the following (all of the referenced documentation is available from the Lotus Sametime documentation Web page:
- For Sametime meetings running on an 8.5.x Domino based Sametime server: "Configuring Meeting Services" in the Server Administration section of the Sametime 8.0.2 Information Center.
- For Sametime 8.0.x and 7.5.1: "Configuring Meeting Services" in the Server Administration section of the Sametime Information Center for your Sametime release.
- For Sametime 7.5: "Configuring Meeting Services" section of Lotus Sametime 7.5 Administrator's Guide (sthelpad.nsf or sthelpad.pdf)
- If you are unable to save the contents of the meeting room whiteboard, see the technote "Enabling capability to save contents of Sametime Whiteboard on IBM i" (#1089693).
If you do not enable save whiteboard, you should change the Sametime configuration so that the option does not appear to be available.
6. Server document is incorrect
Open the Server document for the Sametime server and check the following:
1. In the Basics tab, make sure that the Fully qualified Internet host name field contains the fully qualified host name for the Sametime server, as known by the DNS server.
2. Select Ports > Notes Network Ports, then ensure that:
- Port field contains TCPIP.
- TCP is specified as the protocol.
- Net Address Field contains the fully qualified host name of the Sametime server. For example: stdom1.acme.com. This MUST NOT be a numeric IP address.
3. Select Internet Protocols > HTTP, then ensure that:
- Basics: Host Name field contains the fully qualified host name of the Sametime server. This field may contain more than one name. If any of the names are incorrect or not needed, delete them. Make sure that the correct fully qualified host name is listed first in the field.
- Basics: Bind to host name field is set to Enabled.
- DSAPI: DSAPI filter file names field is blank.
The Server document entries described here are the ones that most often cause problems. Check the Installation portion of the Information Center or Installation Guide for your release for additional information.
If you change the server document, remember to stop the server and start it again in order for the changes to take effect. Also, if the Net Address Field was incorrect, it is likely that the Server host name configuration is incorrect also, so you should also complete the verification steps in the next section.
7. Server host name configuration is incorrect
Check to see if your Sametime server is configured to use the correct, fully qualified host name:
- From any IBM i command line, run the WRKDOMSVR command.
- Type option 12 (Work object links) next to the Sametime server and press Enter. This displays a list of the files and directories in the Sametime server data directory.
- Page down until you find sametime.ini. Type option 5 (Display) next to the sametime.ini file and press Enter.
- Inspect the VPS_HOST and STLINKS_HOST settings in the [Connectivity] section of the file. These should both contain the correct, fully qualified host name of your Sametime server. For example:
Note: If you see a short name or an IP address, the server host name configuration is wrong and you cannot fix the problem by simply updating the sametime.ini file. You must complete all of the steps below to ensure that your TCP/IP configuration defines the correct association between the IP address and the fully qualified host name for the Sametime server. Complete all of these steps (details follow):
- Determine whether TCP/IP is searching the IBM i host table or DNS first (and correct the DNS if necessary)
- Correct the IBM i host table
- Correct the Sametime server configuration
- Correct the Web SSO Configuration for LtpaToken
- Correct the Sametime client configuration
I. Determining whether TCP/IP is searching the IBM i host table or DNS first
To determine which portion of your TCP/IP configuration is incorrect, you need to determine whether TCP/IP is retrieving the host name from the IBM i host table or from the Domain Name Server (DNS).
1. From any IBM i command line, run the CFGTCP command.
2. Select option 12 to display the command prompt for CHGTCPDMN:
- *REMOTE: indicates that TCP/IP searches the DNS first for the host name. Work with your network administrator to correct the DNS so that the fully qualified host name of the Sametime server is the first name listed in the entry for the IP address associated with your Sametime server. The fully qualified name must be listed first, before any short names, in order for your Sametime server to function correctly. After correcting the DNS entry, skip to "Correcting the Sametime server configuration," later in this section.
- *LOCAL: indicates that TCP/IP searches the IBM i host table first for the host name. Proceed to "Correcting the IBM i host table."
II. Correcting the IBM i host table
- From any IBM i command line, run the CFGTCP command.
- Select option 10 to work with host table entries.
- Locate the IP address for your Sametime server and inspect the host names associated with the IP address.
- If more than one host name is listed for your Sametime server, the correct, fully qualified host name must be listed first, before any short names. Also, if you have more than one fully qualified host name associated with the same IP address, make sure that the fully qualified name for the Sametime server is listed first.
If you need to correct the host table:
- Type a 2 in the Opt column next to the Internet Address and press Enter to change the Host Table Entry.
- On the CHGTCPHTE command prompt, change the Host name values so that the fully qualified name is listed first and any alternative names are listed later.
- Run the command to update the host table.
III. Correcting the Sametime server configuration
If the IBM i host table or DNS was wrong at the time you configured the Sametime server, then the server configuration is wrong.
The steps required to correct the Sametime server configuration are described in the Sametime Information Center for your Sametime release. The title of the approproiate topic depends on your release of Sametime: either "Changing the host name of an IBM i Sametime Community Server" or "Changing the host name of an i5/OS Sametime Server."
The topic includes some additional steps that are only necessary when running HTTP tunneling with multiple IP addresses. If you have this situation and are running meetings on a Domino-based Sametime 8.5.x server, consult the Sametime 8.0.2 Information Center for information about correcting the Meeting services network settings.
IV. Correcting the Web SSO Configuration for LtpaToken
If your server host name configuration was wrong, it is likely that your Web SSO configuration is wrong also.
1. Use a Notes client to open the Domino directory (names.nsf) on your Sametime server.
2. From the left panel, select Server > Web Configurations.
3. Under * - All Servers -, find and open the Web SSO Configuration for LtpaToken document.
4. Look at the contents of the Token Domain field. If it contains only a period (.) as in the following example, or a full or partial IP address (such as, .5.131.122), the Web SSO Configuration is wrong and must be corrected.
5. To correct the configuration, update the Token Domain field with the full domain name for your Sametime server. In this example, spuds.rchland.ibm.com is the fully qualified name of the Sametime server so .rchland.ibm.com is the Token Domain name.
6. Save and close the Web SSO Configuration document.
V. Correcting the Sametime client configuration
Verify that client workstations are also configured to use the fully qualified host name of the Sametime server.
1. Open Sametime Connect for the desktop.
2. Select Options > Preferences, and then click on the Sametime Connectivity tab.
3. The Host field should contain the Sametime server's fully qualified host name, not the server's IP address.
8. Sametime server encountering TCP/IP Port conflicts
If your Sametime server is encountering TCP/IP port conflicts, it is usually caused by another HTTP server on your system (Domino or an IBM HTTP server) that is using port 80 on all of the configured IP addresses. In other words, the problem HTTP server is not bound to a specific IP address. It is attempting to use all of them, including the IP address that you assigned to your Sametime server.
Here is how to check if you have this problem:
- From any IBM i command line, run the NETSTAT command and then select option 3, Work with TCP/IP connection status.
- Press F14 to Display port numbers in the "Local Port" column, rather than port names.
- Page down until you find an entry for Local Port 80 where the State is "Listen." There may be more than one entry like this. Complete the remaining steps for each of them.
- Type option 5 next to the entry and press Enter, to display details for the entry.
- The Local host name field must contain a specific name and the Local internet address must contain a specific address as shown in this example:
These fields must not contain an asterisk (*). An asterisk indicates that this server is using all of the system IP addresses and is likely causing port conflicts with your Sametime server.
Make sure that you check all of the entries that indicate a server is listening on port 80. If any of them are listening on port 80 for all IP addresses, you must correct the configuration for those servers. The Sametime Information Center includes a section called "Preparing the TCP Environment on IBM i" or "Preparing the TCP/IP Configuration for i5/OS" which includes topics with instructions for updating the configuration of existing Domino servers and HTTP servers so that each one is bound to a specific IP address. This will typically resolve the port conflicts.
Note: If you have configured more than one Sametime server within the same Logical Partition (LPAR), the Sametime servers may be attempting to use the same Event Server or Token Server ports. For more information, see "Verifying each Sametime for IBM i server on system uses unique ports" (#1212892 ).