QuickPlace for iSeries: Enabling Integration With Sametime

• You must install QuickPlace and Sametime on two separate Domino servers.
• The QuickPlace and Sametime servers must reside in the same DNS domain.
• Both servers must be enabled for Single Sign-on (SSO)
• Both servers must be configured to connect to the same LDAP user directory.
• If you plan to install both of the servers on the same iSeries server, review the latest information in the document "Sametime for iSeries: Can Sametime 3.x and QuickPlace Be Installed on the Same System? [#  1091353 ]" to be certain you are using compatible releases of Domino, Sametime and QuickPlace.
• Integration has been tested with the following combinations of products:
  • QuickPlace 3.0.1 and Sametime 3.1, each running on Domino 5.0.12 servers
  • QuickPlace 3.0 and Sametime 3.0a, each running on Domino 5.0.10 servers
  • Team Workplace 6.5.1 and Lotus Instant Messaging and Web Conferencing 6.5.1, each running on Domino 6.5.1 servers
  • Team Workplace 6.5.1 and Sametime 3.1
  
  Note: If you use a Domino directory as your LDAP server, you should carefully consider which Domino server to use. Here are some issues to keep in mind:
  
  • It is important to remember that when your Sametime and QuickPlace servers are configured to use an LDAP server, the LDAP server must be active in order for the Sametime servers to run and for external users to authenticate or be added to places on the QuickPlace server.
  • If you run LDAP on your QuickPlace server, then the QuickPlace server must always be active when you start Sametime. If you plan to use Sametime independently of QuickPlace and must be able to stop your QuickPlace server without affecting the Sametime server, do not run LDAP on the QuickPlace server.
  • If you run LDAP on your Sametime server, then the Sametime server must be active in order for external users on the QuickPlace server to authenticate or be added to places. Also, whenever you start the QuickPlace server in this situation, there is a short delay before the Sametime integration features become available to QuickPlace users.
  • Consider configuring a separate Domino server (a server which is not your QuickPlace or Sametime server) for running LDAP. With this environment, you can start and stop the QuickPlace and Sametime servers independently of each other. Also, if you decide to create additional QuickPlace or Sametime servers, they can all access the same Domino LDAP server without creating additional server interdependencies.

Domino directory: If you are currently using a Domino directory, you can modify your Domino server configuration so that you can access the same directory using the LDAP server protocol. For information about enabling the LDAP service on a Domino server, see "Domino Administration Help." Ensure the fully qualified host name for the server, for example, server.acme.com, is specified in the Ports/Notes Network Ports/Net Address for TCP/IP and in the Basics/Fully qualified Internet host name field.


iSeries Directory Server: For more information, see the iSeries Information Center web site at http://www.ibm.com/eserver/iseries/infocenter. After selecting your location, language, and OS/400 release, select the following from the left-hand navigation bar:

For V5R3 or V5R2, select "e-business and Web serving", then "Security and Directory Services"

For V5R1, select "Security", then "IBM SecureWay: iSeries and the Internet"

For Sametime, follow the instructions in "Installing and Managing Lotus Instant Messaging and Web Conferencing (Sametime) 6.5.1 for iSeries" or "Installing and Managing Sametime 3.x for iSeries" which is available on the Sametime product CD-ROM.

• If you are using QuickPlace 3.x (which requires Domino R5), it is recommended that you use a Domino R5 server for your Sametime server in order to avoid potential server replication issues. Also, you should install or upgrade to Sametime 3.0a or Sametime 3.1.
• If you are configuring a new Sametime server, specify *LDAP as the directory type and specify the fully qualified name of the LDAP server you have selected.
• If you use an existing Sametime server that is currently using a Domino directory, follow the instructions in Technote #1181284, "How to change your Sametime server from Domino to LDAP after installation."
• It is preferable to use a separate server for Domino LDAP, but if you decide to put your LDAP server on the same Domino server where you have already configured Sametime, you must delete the LDAP document that Sametime created in the Directory Assistance database. The Directory Assistance database is usually named DA.NSF. If you cannot find the database, check the Basics tab of the server document to determine the name of the database on your server.

For QuickPlace, follow the instructions in "Installing and Managing Team Workplace 6.5.1 for iSeries" or "Installing and Managing QuickPlace 3.0 for iSeries" to install and setup your server.

• When prompted for the administrator username and password, ensure you specify a name that is not in the LDAP user directory, for example, qpadmin.
• Configure the QuickPlace server to use the same external user directory (LDAP) as the Sametime server. For information about connecting to an LDAP user directory, see the Team Workplace Administrator's Guide (6.5.1) or the QuickPlace Administrator's Guide (releases prior to 6.5.1).

a. Open the server document and set Internet Protocols/Domino Web Engine/Session Authentication to Multi-Server, then save the server document.

b. On the QuickPlace server, add the following settings to the NOTES.INI file:

NoWebFileSystemACLs=1
h_ScopeUrlInQP=1

c. On the QuickPlace server, create DOMCFG.NSF using the DOMCFG5.NTF template.

d. In DOMCFG.NSF, create a new Login Mapping document, setting the fields as follows:

Target Database = QUICKPLACE/RESOURCES.NSF
Target Form = QuickPlaceLoginForm

a. Open a browser session and connect to the QuickPlace server by specifying the fully qualified server name (for example, http://qpserver.enterprise.com/quickplace) and sign in.

b. Create a test Place and add several members from the user directory to confirm correct operation.

c. From the same browser session, connect to the Sametime server (for example, http://stserver.enterprise.com/stcenter.nsf) and verify that you are still signed in. (Go to the Attend Meeting page and check who is signed in.)

d. If you can authenticate a single time and remain logged in between the two products, SSO is working correctly. If not, then you have a problem with SSO which must be corrected before proceeding to the next step. For more information, see "Multi-server session-based name-and-password authentication for Web users (single sign-on)" in the Lotus Domino 6.5.1 Administrator Help or "Enabling Single Sign-on for Domino and WebSphere servers" in Chapter 4 of the Domino 5.0.12 Release Notes.

a. Open the Sametime web administration tool in a web browser.
b. Select Configuration-Connectivity and choose the "Servers in this Community" tab.
c. Enter values for a dummy server and click Add. For example:

Destination Server: dummy/server
Destination Server IP address: 1.1.1.1

a. Create a new directory. For example, you can enter the following command:

mkdir '/STMtg'

b. Use the CHGOWN command to change the owner of the new directory to QNOTES. For example, enter the following command:

CHGOWN OBJ('/STMtg') NEWOWN(QNOTES)

c. Copy the following files from the /qibm/proddata/lotus/sametime directory into the new directory:

STMtgManagement.jar
STCore.jar
ibmjsse.jar

d. Use the CHGOWN command to change the owner of the files in the previous step to QNOTES. For example, enter the following command:

CHGOWN OBJ('/STMtg/*') NEWOWN(QNOTES)

a. Add the following lines to the NOTES.INI file:

ST1=/STMtg/stmtgmanagement.jar
ST2=/STMtg/stcore.jar
ST3=/STMtg/ibmjsse.jar

Note: STMtg is the name of the new directory from the previous step.

b. Append ST1, ST2, and ST3 settings to JavaUserClassesExt setting in the NOTES.INI file. For example:

JavaUserClassesExt=LQPJava1,LQPJava2,LQPJava3,LQPJava4,LQPJava5,ST1,ST2,ST3

a. Look in the QuickPlace server's data directory for a file called QPCONFIG.XML.
If QPCONFIG.XML does not exist, make a copy of qpconfig_sample.xml and name it QPCONFIG.XML.

b. Open the QPCONFIG.XML file for editing.

c. Make sure that a <sametime> XML section is defined in the file, and that it is not commented out.

If this section does not exist in your file, copy the section from the qpconfig_sample.xml file.

If the section is preceded by a line that reads "START OF SAMPLE" and is followed by a line that reads "END OF SAMPLE", remove these lines to enable the XML section.

d. Modify the <credentials> element and add the name and password of the user you created in Step 1. For example:

<sametime local_users="false" ldap=="true">
<meetings invite_servers="false">
<tools>
<audio enabled="true"/>
<video enabled="true"/>
</tools>
<credentials>
<dn>cn=John Doe/o=Enterprise </dn>
<password>password</password>
</credentials>
</meetings>
</sametime>

Notes:
• The <local_users> attribute must be "false." Local users using Sametime is an unsupported configuration.
• The <invite_servers> attribute is not available on Team Workplace releases prior to 6.5.1. Change the value to "true" if you have multiple Sametime servers in the Community and you want meetings to be available on all of the servers.

9. Click Sign In in the left corner of the screen.

10. Enter the user name and password of a QuickPlace server administrator.

11. In the table of contents, click Server Settings, Other Options, Edit Options.

12. Under Sametime Servers, enter the fully qualified URL of the Sametime Meeting Server. For example:
http://stserver.enterprise.com

13. Click Next.

14. Do the following to verify that places allow members to schedule online meetings.

a. Sign in to the place as a Manager.
b. Click Customize, Basics, Change Basics.
c. Scroll down to the bottom of the Change Basics page.Under the Real-time collaboration heading,make sure "Members can schedule online meetings" is checked..
d. Click Done.