Jive Connects for IBM Sametime

Transcription

1 Jive Connects for IBM Sametime

2 TOC 2 Contents Jive Connects for IBM Sametime...3 System Requirements...3 Setting Up Sametime...3 Configuring Sametime Integration...4 Setting Up Sametime Integration... 4 Disabling Sametime Integration...5 FAQ: Sametime Integration... 5 System Properties for Sametime Integration...6 Using Sametime... 7 How do I start a Sametime chat from the community?...8 How do I turn off the chat bar?... 8 Documentation PDFs... 8

3 Jive Connects for IBM Sametime 3 Jive Connects for IBM Sametime Jive Software has brought instant messaging integration between Jive and IBM Sametime. Jive Connects for IBM Sametime lets community users see each other's presence status and initiate chats via the community user interface. This module uses the pre-installed Lotus Sametime Connect client. You can easily see any user's chat presence from several locations such as the user profile, user profile hover, and the Jive chat bar. The chat bar makes it even easier to find the people you want to chat with by showing which users shown on the current page are online. It also shows which of your community connections (such as people you're following) are online. You can start a chat with one click. System Requirements To integrate IBM Sametime with your community, you'll need the following: The Jive Connects for IBM Sametime plugin. Jive version 5.0 and later. The following OS/browser/chat client combinations: Operating System Browsers Chat Client Windows XP Windows Vista Windows 7 Mac OS X Please see the Jive system requirements. Note: Users using Chrome browser will need to have Google Gears installed in order to use the chat bar. Users who want to use integrated chat will need to have a compatible Sametime client. Note that this does not include all clients that support Sametime, including some multi-protocol clients. Supported clients include: A standalone Sametime client version or later. A Sametime client embedded in Notes with Interim Feature Release 1 (IFR1) or later. You can access the Notes IFR1 at IBM at rs=475&uid=swg After installing Notes IFR1, you will be instructed to install the latest Notes Cumulative Client Hotfix. Cumulative Client Hotfix 1 (CCH1) is available from IBM at docview.wss?rs=475&uid=swg A Sametime client embedded in Notes 8.5 or later. Linux Not supported. Not supported. Setting Up Sametime To get set up with Jive Connects for IBM Sametime, you'll need to: 1. Install the Jive Connects for IBM Sametime plugin. See the Jive documentation for information on installing plugins. 2. Apply a deployment license that enables you to use the feature by opening to System > Management > License Information in the Admin Console. For more about managing licenses, see "Managing the Deployment License" in the core documentation. 3. Restart the application. 4. Configure the application to integrate with Sametime by passing identifying information to users' Sametime client when they begin a chat. For more information, see Configuring Sametime Integration

4 Jive Connects for IBM Sametime 4 Once the community is configured, users can begin chats by clicking the menus available in the user interface. For user help on the feature, see How do I start a Sametime chat from the community? Configuring Sametime Integration You can integrate your IBM Sametime instant messaging platform with Jive. When you do, Sametime users in your community will be able to begin chats with their community connections, as well as with people associated with activities listed on community pages. You configure Sametime integration by using the admin console. (Everyone participating in chat must be a Sametime user.) Note: This content assumes that you've installed the Sametime integration plugin. Note: For more information on how Sametime users experience chat integration, see How do I start a Sametime chat from the community? Users need to be logged into a Sametime client or above to chat with others. Jive does not connect directly with your Sametime server. Instead, it communicates with a user's Sametime client to get presence information and begin chats. For example, when someone starts a chat with a second Sametime user, the application contacts the Sametime client, identifying the second user by passing an identifying value to the Sametime client, which in turn communicates with the server to begin the chat. To support this, you must configure the application to know how to locate the value through which to identify the user to the Sametime client. Setting Up Sametime Integration You configure Sametime integration in the admin console. Use the steps below. Fastpath: Admin Console: System > Settings > Connects for IBM Sametime Note that if the application uses LDAP, installing the plugin and restarting the system will prompt the application to synchronize its database with the LDAP data store. For more information, see Synchronizing with User Authentication Systems in the Jive documentation. 1. Install the Jive Connects for IBM Sametime plugin. For more on installing plugins, see the Jive documentation. 2. In the admin console, on the Jive Connects for IBM Sametime page, specify the user field or attribute that holds the value that uniquely identifies a user to the Sametime server. How you do this differs depending on whether or not your community is connected to the same LDAP data store as the Sametime server (note that what's on the Admin Console page differs depending on whether an LDAP connection exists): Specify the field using one of the following options: If the community is connected to the same LDAP server as Sametime, you need only enter the name of the LiveName LDAP attribute: Under Configuration, in the LiveName LDAP Attribute box, enter the name of the LDAP attribute that the application should use for discovering presence and starting chat with other users. A value here is required. By default, the mail attribute is used. Keep in mind that the attribute name you enter here is not validated against the LDAP data store itself. In other words, be sure that the attribute exists in LDAP. If the community isn't connected to the LDAP server, you'll need to choose a user profile field that contains a value identifying the user to Sametime. If none your existing profile fields will work, you can create a new field for the purpose. For example, you could create a "Sametime User Name" or "LiveName ID" field in which user's could enter the value that would work. Under LiveName Profile Field, select the user profile field that corresponds to the Sametime LiveName field. If the profile field you need isn't visible, you can click the link in the description text to create a new profile field for the purpose.

5 Jive Connects for IBM Sametime 5 3. Click Save. Note: Regardless of whether the community is connected to the LDAP server, you can force the use of a particular application user profile field by specifying that field using a system property. For more information, read about the jive.chat.presence.force.livename.field.selection system property in System Properties for Sametime Integration. Configuring the Maximum Number of Connections You can set the maximum number of connections that will be displayed from the chat bar. By default, the chat bar will list up to 200 of a user's community connections. You can set this to another value by using the jive.chat.presence.max.connections.analyzed system property. When a user's number of connections exceeds the maximum number, they'll see a link through which they can view more connections in the list. You might want to set the number to a lower value, for example, to help improve performance if your people in the community tend to have a large number of connections. For more on system properties, see Fine-Tuning with System Properties in the Jive documentation and System Properties for Sametime Integration. Disabling Sametime Integration If you already have the Jive Connects for IBM Sametime plugin installed, but you want to disable the functionality, you can do so in the admin console. In the admin console, on the Jive Connects for IBM Sametime page, click the Disable Integration button. FAQ: Sametime Integration Why can't I see presence for any of the users? Only users with LiveNames which are recognized by Sametime will have presence displayed in the community. If the community is integrated with LDAP, make sure that the LDAP field specified to be the source of user LiveNames contains valid Sametime LiveNames. If a profile field is explicitly chosen to source the LiveName field -- which could be the case if the community is not integrated with LDAP or if explicit LiveName field selection is forced -- the profile field must contain a valid Sametime Livename for each user. The LiveName must match exactly with whats in Sametime. Note that the value is case sensitive. What happens if I click on "start chat" and nothing happens? This could mean that the Sametime chat client running on the user's system is not available to the browser. The user should try restarting the client; make sure that the port (59449) is open to browser access; make sure they're using a supported version of the Sametime client. (See the System Requirements for more information.) Is there an expected performance decrease on the Sametime server that should be planned for? The Sametime chat clients are going to be asking the Sametime server more often for presence, so you can expect more stress on the Sametime server. However, Sametime clients basically cache presence information and subscribe to updates (rather than request it from the Sametime server each time it's asked). Can you use other Jive chat integrations with the Sametime integration? No; only one presence integration may be used at a time. You must uninstall any existing Jive chat integrations and reset the Jive server prior to installing the Sametime integration plugin. What happens to users who don't have the client installed? Those users won't see presence information anywhere in the system (including in the profile popup, user profile, or chat bar). For a user without the chat client, the community looks just as it would without the integration installed. What browsers support this? The System Requirements describe support for browsers and chat clients.

6 Jive Connects for IBM Sametime 6 Does this module honor profile privacy? Yes it does; there is a privacy option for presence specifically which is in effect; username visibility is also respected. Can I enable this for specific users? No. It's on or off globally. If a user doesn't have a value set for the Sametime client in LDAP, do they see the chat bar / chat options? They do. They can still see other people's presence status (those with a Sametime LDAP ID, called LiveName). However, those other people will not be able to see the presence of the person with no LiveName (they show up as Unknown). For more on configuring the feature, see Configuring Sametime Integration. The community is integrated with LDAP, but I do not want to use LDAP to source my users' LiveNames. What are my options? You may set the system property property jive.chat.presence.force.livename.selection to true, giving administrators the ability to explicitly choose a profile field from which to source the users' LiveNames. You may create new custom profile fields for sourcing that data, which may be populated not using the LDAP sync. For more on system properties, see System Properties. The Google Chrome browser is asking me whether or not my site should be allowed to use Google Gears. What is this and should I allow it? The chat bar uses local browser caching in the case of Google Chrome, so you should allow the site to use Google Gears. You must allow the site to use Google Gears if you wish to use the chat bar. I can't see the chat bar in the Chrome browser. Help! Make sure that the Chrome is allowing your site to use Google Gears. Why do some of my SBS connections never seem to appear on the chat? This will happen if a user has more than the default 200 connections. By default, the system will only analyze users' first 200 connections for being online; the 201st user and onwards will not be inspected for being online, and therefore may not show up on the chat bar even though they are online. The threshold is configurable; please see System Properties. System Properties for Sametime Integration System properties provide a way to do additional configuration. To make changes to system properties, in the admin console go to System > Management > System Properties. Keep in mind that both property names and values are case-sensitive. Note: You should make changes to system settings only under the guidance of Jive's support or professional services teams. The following is a list of system properties that can be used to fine tune configuration. Property jive.chat.presence.max.connections.analyzed Description The maximum number of a person's community connections for whom the browser will request presence information. These connections are displayed in the chat bar's Connections tab; if the number is reached, a More link is provided. The user can click the More link to view a more complete list of their connections. Default is 200. If people in your community have a large number of connections (such as people they're following), you might find that the browser's checks for their connections' presence can slow performance. If you

7 Jive Connects for IBM Sametime 7 Property Description suspect that this is the case, consider setting this property to a lower number. Lower this value if users are likely to have fewer than 200 community connections; increase this value if they are likely to have more than 200. Note that the higher this value is, the more CPUintensive it will be for the user's local CPU. jive.chat.presence.force.livename.field.selectiontrue to force the admin to explicitly choose a profile field to represent the LiveName attribute. If LDAP is enabled, the precreated LiveName profile field will be available and pre-selected. Default is false. In an LDAP configuration where the value is not true, the plugin assumes you will be using an LDAP user attribute and provides a field on the Connects for IBM SameTime configuration page to enter which LDAP attribute to use. This property effectively forces an LDAP-configured instance to behave like a non-ldap configured instance with respect to presence. It forces you to choose a profile field for the mapping between community users and Sametime users. jive.chat.presence.max.page.scrapes jive.chat.presence.refresh.interval.ms jive.chat.presence.poll.rate.ms jive.chat.presence.is.on.demand jive.chat.presence.monitor.notification.delay The number of users obtained via page scrapes to be analyzed for presence. Defaults to 300. Set this to a lower value if it appears that users' local CPUs are too busy processing the browser requests to the local chat client. The interval, in milliseconds, for refreshing the data in the chat bar. By default, this property is not set, so the presence information in the chat bar is not refreshed after the page loads for the user (unless they refresh the page). With a large number of users, or users who have a large number of community connections, refreshing the chat bar can be performanceintensive. But if you want to enable refreshes that feel more "live" for users, set this to a value higher than zero. The interval, in milliseconds, between refreshes of the presence indicator on the profile popup and the profile page. Default is (1 minute). true to force the chat bar to only show presence information when the user clicks it. Default is false. Set this to true if Sametime users' local CPUs are overburdened by presence checks to the chat client. The interval, in millseconds, between error notifications if the presence provider is not available to the application. Default is (4 hours). Change this parameter if reminders should be more or less frequent. Set to -1 to disable reminders. Using Sametime

8 Jive Connects for IBM Sametime 8 How do I start a Sametime chat from the community? If you're a Sametime chat user, you can easily start a chat with other Sametime users who are your community connections and people who are listed on community pages that list content and activity in the community. Note: You must be logged in to your Sametime chat client. Also, people must be logged in to the community as well as to chat in order to appear in your chat bar. Starting chat from the chat bar In the lower-right corner of a community page, notice that you can view lists of people who are Connections and people on This page. To start a chat from the chat bar: 1. Choose whether you want to chat with one of your connections or with someone whose name appears on the page. To chat with a connection, click Connections. To chat with someone whose name appears on the page you're viewing, click This page. 2. Click the name of the person you want to chat with. Your Sametime client will open and begin a chat with the person you selected. Starting chat from a user's profile In a user's profile, click the Chat button. Your Sametime client will open and begin a chat with the person you selected. Starting chat by hovering a user's name Hover your mouse over a user's name or avatar, then click Chat. Your Sametime client will open and begin a chat with the person you selected. How do I turn off the chat bar? If you're a Sametime chat user, you'll be able to start chats with other people in the community by clicking their name in the chat bar displayed in the lower right of your screen. When you don't want to see the chat bar, you can turn it off in your preferences. To turn off the chat bar: 1. To the top right, next to your name, select Preferences from the drop-down menu to get to your Preferences page. 2. On the IM Preferences tab, click the Show the chat bar check box, then click Save. Documentation PDFs Download PDF versions of documentation included in help. Document Jive Connects for IBM Sametime Description Jive Software has brought instant messaging integration between Jive and IBM Sametime. Jive Connects for IBM Sametime lets community users see each other's presence status and initiate chats via the community user interface. This module uses the pre-installed Lotus Sametime Connect client.