Skip to main content link. Accesskey S
  • Help
  • IBM Logo
  • IBM Sametime wiki
  • All Wikis
  • All Forums
  • THIS WIKI IS READ-ONLY. Learn more...
  • Home
  • Product Documentation
  • Community Articles
  • Learning Center
  • IBM Redbooks
  • API Documentation
Search
Community Articles > Integration with other products > Video Chat widget for IBM Connections
  • Share Show Menu▼
  • Subscribe Show Menu▼

About the Original Author

Click to view profileIBM contributorMary Jrolf
Contribution Summary:
  • Articles authored: 3
  • Articles edited: 0
  • Comments Posted: 0

Recent articles by this author

Conference Manager Monitoring APIs

The administrator of the Sametime Media server can now extract the information of the Audio Video usage statistics so that customer administrators can write use their API consumers to monitor the Media server. This is now available in the form of REST and JMX APIs through the Sametime Conference ...

Using Call Data Records with Audio Video Conferencing

This article describes a step-by-step approach for fetching Call Data Records from the Sametime Video Manager and also provides details about the various reports generated for analysis.

Video Chat widget for IBM Connections

The Video Chat Widget The Video Chat widget provides audio video capability on an IBM Connections Community. Users of the Video Chat widget just click a button from the Connection community to start an audio video conference. If the conference has not been started by anyone, the Start Video ...
Community articleVideo Chat widget for IBM Connections
Added by IBM contributorMary Jrolf | Edited by IBM contributorMary Jrolf on November 15, 2013 | Version 22
expanded Abstract
collapsed Abstract
No abstract provided.
Tags: 9.0, Connections, widgets
The Video Chat Widget

How does the Video Chat Widget work?

Supported software versions

Supported softwareVersion
IBM Connections3.0.1 or later
IBM Sametime 8.5.2 IFR 1

Installation Prerequisites

The Login Properties field on the Connections Server needs to start with "mail" to match the Login Properties field on the Sametime server.

Enable communication between Sametime Meetings and Connections


The Sametime Meetings API requires authentication before releasing data, therefore, single sign-on must be enabled between Connections and the Sametime Meetings Server. Complete these procedures to enable single sign-on:

Note: LDAP should be configured correctly on the IBM Connections server and the Sametime Meeting Server.

Export LTPA tokens from the IBM® Sametime® Meeting Server.
After exporting the LTPA tokens, you can complete the procedure to import the LTPA token key file into IBM Connections.
  1. On the server hosting the Sametime Meeting Server, log in to the WebSphere Integrated Solutions Console as the WebSphere administrator.
  2. In the navigation tree, click Security > Global Security.
  3. In the Authentication section, click LTPA.
  4. On the Global Security - LTPA page, in the Cross-cell single sign-on section, complete these steps:
    1. Specify a password and confirm the password.
    2. In the fully qualified key file name field, specify a path and file name for storing the key file. For example, C:\ssoLtpa.key
      If you do not specify a path when saving the file, the default location is the Dmgr folder; for example on Windows:
      C:\Program Files(x86)\IBM\WebSphere\AppServer\profiles\...DMgr
  5. Click Export keys.

Import the LTPA token key file into Connections
Import the LTPA token key file into Connections from the Sametime Meetings Server by completing the following steps:
  1. Copy the token key file that you exported from the Sametime Meetings Server and store it on the computer where the Connections deployment manager is installed.
  2. On the server hosting the IBM Connections server, log in to the Integrated Solutions Console as a WebSphere® administrator.
  3. Click Security > Global Security.
  4. In the Authentication section, click LTPA.
  5. On the LTPA page, use the Cross-cell single sign-on section to provide the following information about the token key file:
    • Password: Type the password you provided when you exported this file from Sametime.
    • Confirm password: Type the password a second time to verify it.
    • Fully qualified key file name: Type the complete path and file name to the key file.
  6. Click Import keys to import the file.
  7. Click OK.

Enable single sign-on between Sametime and Connections for the Meetings Rooms widget
Complete these steps to enable single sign-on between the IBM® Sametime® Meeting Server and IBM Connections so that users can enter meeting rooms without needing to authenticate again with the Sametime Meeting Server.
Perform this procedure on all WebSphere® Application Servers in the SSO domain to enable SSO among those servers. The Domain Name setting determines the cookie domain of the LtpaToken.
  1. Log on to the WebSphere Application Server, Integrated Solutions Console as an administrator.
  2. Click Security > Global Security.
  3. In the Authentication section, expand Web and SIP Security. Click Single sign-on (SSO).
  4. On the General Properties page, complete these steps:
    • Select Enabled to enable SSO between servers.
    • In the Domain Name field, enter the domain name for all SSO hosts. Add a leading dot before the domain name, for example, .ibm.com. You can also specify a UseDomainFromURL value, on which the application server sets the SSO domain name value to the domain of the host that is used in the Web address.
    • Select Interoperability mode to provide backward interoperability if you have a WebSphere Application Server version earlier than version 5.1 and a Lotus® Domino® version earlier than 7.0 in the SSO domain.
    • Select Web inbound security attribute propagation to enable this feature. Web inbound security attribution propagation might be required by some IBM products.
  5. Click OK.

For detailed instructions on enabling single sign-on, see this topic: Configuring single sign-on with an LTPA token on IBM WebSphere and IBM Domino platforms.

Installation
Install the widget

Install the SametimeVideo.xml file on the IBM Connections server in a web-accessible folder. For example:
.../IBM/WebSphere/AppServer/profiles/AppSrv01/installedApps//Communities.ear/comm.web.war/SametimeVideo.xml

Configure widget
  1. To display this widget on every community's home page, edit the widgets-config.xml file. This file is typically found in two places:
    .../IBM/WebSphere/AppServer/profiles/AppSrv01/config/cells//LotusConnections-config/widgets-config.xml
    ..../IBM/WebSphere/AppServer/profiles/Dmgr01/config/cells//LotusConnections-config/widgets-config.xml
  2. In each of these files, locate the resource tag with a type of community. Within that tag there is a widgets tag, and within that tag there is a definitions tag. To create a new Sametime Video widget definition, add a new widgetDef tag within the definitions section. The widget definition should look like this:
<widgetDef defId="Video" primaryWidget="false" modes="view" uniqueInstance="true" url="contextRoot/SametimeVideo.xml">
		<itemSet>
	<item name="sametimeMeetingServerUrl" value="http://stmeetings.company.com:9080/stmeetings" />
	<item name="ssl_sametimeMeetingServerUrl" value="https://stmeetings.company.com:9443/stmeetings" />
</itemSet>
	</widgetDef>
  1. Set the value of sametimeMeetingServerUrl to the appropriate fully qualified host name, port, and context-root of your Sametime Meeting server.
  2. Ensure that the URL specified in the main widgetDef matches where you installed the SametimeVideo.xml file.
    If you placed the SametimeVideo.xml file somewhere other than the suggested location above, modify this URL in your widget definition.

For example (Sametime Video widget added as second definition):

...
<resource type="community" aclServiceImpl="com.ibm.lconn.comm.acl.ACLSvcImpl" resourceValuesProvider="com.ibm.tango.internal.service.CommunitiesResourceValuesProvider" xpathMandatedWidgetForMainPage="/tns:config/tns:resource[@type='community']/tns:widgets/tns:layout/tns:page[@pageId = 'communityOverview']">
		<widgets xmlns:tns="http://www.ibm.com/widgets-config">
			<definitions>
				<widgetDef defId="Members" primaryWidget="false" modes="view fullpage" showInPalette="false" uniqueInstance="true" url="{webresourcesSvcRef}/web/lconn.comm/communityMembers/communityMembers.xml?version={version}">
					<itemSet>
						<item name="membersPerPage" value="18" />
						<item name="membersPerPageFullPage" value="16" />
					</itemSet>
				</widgetDef>
				
				<widgetDef defId="Video" primaryWidget="false" modes="view" uniqueInstance="true" url="{contextRoot}/SametimeVideo.xml">
					<itemSet>
						<item name="sametimeMeetingServerUrl" value="http://stmeetings.company.com:9080/stmeetings" />
					</itemSet>
				</widgetDef>
				
				<widgetDef defId="Blog" prerequisite="blogs" modes="view edit search" url="{blogsSvcRef}/static/{version}!{locale}/iwidgets/blog/blogsWidget.jsp" navBarLink="{blogsSvcRef}/{resourceId}" description="blogsDescription" uniqueInstance="true" helpLink="{helpSvcRef}/topic/com.ibm.lotus.connections.communities.help/community_blog_frame.html" iconUrl="{contextRoot}/nav/common/images/iconBlogs16.png">



In the same widgets-config.xml files, define where the new widget will display. From within the widgets tag, find the layout tag (should be after the close of the definitions tag). On the page with an id of communityOverview, create a new widgetInstance tag like the following:

<widgetInstance uiLocation="col3" defIdRef="Video"/>


The uiLocation setting and the order of the widgetInstance tags determines where the widget shows up on the page.

For example (Sametime Video widget in right-hand column, above "Members"):


<!-- mandated widgets -->
	<layout resourceSubType="default">
		<page pageId="communityOverview">
			<widgetInstance uiLocation="col3" defIdRef="Video"/>
			<widgetInstance uiLocation="col3" defIdRef="Members"/>
		</page>
		<page pageId="allCommunities">
			<widgetInstance uiLocation="col1" defIdRef="sand_recomComm"/>
		</page>
		<page pageId="myCommunities">
			<widgetInstance uiLocation="col1" defIdRef="sand_recomComm"/>
		</page>
	</layout>


3. Restart the Communities application.

4. Install the latest Sametime Meetings 8.5.2 IFR 1 fix from IBM Fix Central. At the time of this writing, that fix is RPOH-8U4KJM. Installation instructions can be found online here.

5. Adjust service provider properties

If you plan to use an audio/video service provider other than Sametime AV, modify the properties file so that video rooms are created with the appropriate attributes.
  1. On the Sametime Media server, where the Conference Focus Component is deployed, access this path: .../IBM/WebSphere/AppServer/profiles//sametime_tcspi
  2. Open the Service Provider specific properties file, for example, myAV.properties.
    Note the Service Provider ID (SERVICE_PROVIDER_ID).
  3. Open the ConferenceManager.properties file.
    Note the ServiceProvider name from the ConferenceServiceName property.
  4. On the Sametime Meeting Server, locate the serviceProvider.json file in the stmeetings.webclient.war folder of the Sametime Meeting Server.ear deployment.
    For example,
    .../IBM/WebSphere/AppServer/profiles//installedApps//SametimeMeetingServer.ear/
    stmeetings.webclient.war/serviceProvider.json
  5. Edit this file and set the following properties using the information from steps 2 and 3:
    1. id = SERVICE_PROVIDER_ID from step 2
    2. ConferenceServiceName = ConferenceServiceName from step 3
    3. label = ConferenceServiceName from step 3

Configuring the Ajax proxy

The Ajax proxy allows requests to be made across domains. Since the Sametime Meetings application resides on its own server, not on the Connections server, requests should be made through the Ajax proxy.

The WebSphere Application Server contains a modifiable proxy configuration file, proxy-config.tpl.


To modify the file, see this procedure: Configuring the Ajax proxy.

The proxy must allow the actions, cookies, and headers as shown.

Note: You must modify the url value according to your own configuration.


 <proxy:policy url="http://stkvmg17.cn.ibm.com:9080/*" acf="none">
        <proxy:actions>
            <proxy:method>GET</proxy:method>
            <proxy:method>HEAD</proxy:method>
            <proxy:method>POST</proxy:method>
            <proxy:method>PUT</proxy:method>
            <proxy:method>DELETE</proxy:method>
        </proxy:actions>
        <proxy:cookies>
            <proxy:cookie>LtpaToken</proxy:cookie>
            <proxy:cookie>LtpaToken2</proxy:cookie>
            <proxy:cookie>JSESSIONID</proxy:cookie>
        </proxy:cookies>
        <proxy:headers>
            <proxy:header>X-ST-CSRF-Token</proxy:header>
            <proxy:header>User-Agent</proxy:header>
            <proxy:header>Accept.*</proxy:header>
            <proxy:header>Content.*</proxy:header>
            <proxy:header>Authorization.*</proxy:header>
            <proxy:header>If-.*</proxy:header>
            <proxy:header>Pragma</proxy:header>
            <proxy:header>Cache-Control</proxy:header>
            <proxy:header>X-Update-Nonce</proxy:header>
            <proxy:header>WWW-Authenticate.*</proxy:header>
            <proxy:header>Access.*</proxy:header>
        </proxy:headers>
    </proxy:policy>


expanded Attachments (0)
collapsed Attachments (0)
expanded Versions (65)
collapsed Versions (65)
Version Comparison     
VersionDateChanged by              Summary of changes
65Jan 2, 2014, 11:13:28 AMMary Jrolf  IBM contributor
64Jan 2, 2014, 10:28:53 AMMary Jrolf  IBM contributor
63Jan 2, 2014, 10:28:37 AMMary Jrolf  IBM contributor
62Jan 2, 2014, 10:28:22 AMMary Jrolf  IBM contributor
61Jan 2, 2014, 10:26:05 AMMary Jrolf  IBM contributor
60Jan 2, 2014, 10:17:28 AMMary Jrolf  IBM contributor
59Jan 2, 2014, 9:59:50 AMMary Jrolf  IBM contributor
58Jan 2, 2014, 9:47:03 AMMary Jrolf  IBM contributor
57Jan 2, 2014, 9:46:01 AMMary Jrolf  IBM contributor
56Jan 2, 2014, 9:45:13 AMMary Jrolf  IBM contributor
55Dec 6, 2013, 1:37:37 PMMary Jrolf  IBM contributor
54Nov 26, 2013, 10:40:56 AMMary Jrolf  IBM contributor
52Nov 26, 2013, 10:39:30 AMMary Jrolf  IBM contributor
51Nov 26, 2013, 10:39:27 AMMary Jrolf  IBM contributor
50Nov 26, 2013, 10:36:38 AMMary Jrolf  IBM contributor
49Nov 26, 2013, 10:36:10 AMMary Jrolf  IBM contributor
48Nov 18, 2013, 4:37:29 PMMary Jrolf  IBM contributor
47Nov 18, 2013, 4:35:55 PMMary Jrolf  IBM contributor
46Nov 18, 2013, 4:34:04 PMMary Jrolf  IBM contributor
45Nov 18, 2013, 4:33:23 PMMary Jrolf  IBM contributor
44Nov 18, 2013, 4:30:12 PMMary Jrolf  IBM contributor
43Nov 18, 2013, 4:27:03 PMMary Jrolf  IBM contributor
42Nov 18, 2013, 4:25:42 PMMary Jrolf  IBM contributor
41Nov 18, 2013, 4:24:56 PMMary Jrolf  IBM contributor
40Nov 18, 2013, 4:02:26 PMMary Jrolf  IBM contributor
39Nov 18, 2013, 4:02:12 PMMary Jrolf  IBM contributor
38Nov 18, 2013, 3:56:15 PMMary Jrolf  IBM contributor
37Nov 18, 2013, 3:52:33 PMMary Jrolf  IBM contributor
36Nov 18, 2013, 3:47:19 PMMary Jrolf  IBM contributor
35Nov 18, 2013, 3:46:32 PMMary Jrolf  IBM contributor
34Nov 18, 2013, 3:45:24 PMMary Jrolf  IBM contributor
33Nov 18, 2013, 3:43:03 PMMary Jrolf  IBM contributor
32Nov 18, 2013, 3:42:50 PMMary Jrolf  IBM contributor
31Nov 18, 2013, 3:32:09 PMMary Jrolf  IBM contributor
30Nov 18, 2013, 3:31:59 PMMary Jrolf  IBM contributor
29Nov 18, 2013, 3:25:23 PMMary Jrolf  IBM contributor
28Nov 18, 2013, 2:50:09 PMMary Jrolf  IBM contributor
27Nov 18, 2013, 2:32:40 PMMary Jrolf  IBM contributor
26Nov 18, 2013, 2:20:03 PMMary Jrolf  IBM contributor
25Nov 18, 2013, 2:13:52 PMMary Jrolf  IBM contributor
24Nov 18, 2013, 2:12:00 PMMary Jrolf  IBM contributor
23Nov 18, 2013, 2:03:43 PMMary Jrolf  IBM contributor
This version (22)Nov 15, 2013, 3:54:36 PMMary Jrolf  IBM contributor
21Nov 15, 2013, 3:41:27 PMMary Jrolf  IBM contributor
20Nov 15, 2013, 3:38:40 PMMary Jrolf  IBM contributor
19Nov 15, 2013, 3:36:24 PMMary Jrolf  IBM contributor
18Nov 15, 2013, 3:34:02 PMMary Jrolf  IBM contributor
17Nov 15, 2013, 3:31:20 PMMary Jrolf  IBM contributor
16Nov 15, 2013, 3:29:34 PMCraig Lordan  IBM contributor
15Nov 15, 2013, 3:27:57 PMCraig Lordan  IBM contributor
14Nov 15, 2013, 3:19:19 PMMary Jrolf  IBM contributor
13Nov 15, 2013, 3:16:47 PMMary Jrolf  IBM contributor
12Nov 15, 2013, 3:15:46 PMMary Jrolf  IBM contributor
11Nov 15, 2013, 3:15:44 PMMary Jrolf  IBM contributor
10Nov 15, 2013, 2:44:50 PMMary Jrolf  IBM contributor
9Nov 15, 2013, 2:39:58 PMMary Jrolf  IBM contributor
8Nov 15, 2013, 2:39:09 PMMary Jrolf  IBM contributor
7Nov 15, 2013, 2:34:16 PMMary Jrolf  IBM contributor
6Nov 15, 2013, 2:29:32 PMMary Jrolf  IBM contributor
5Nov 14, 2013, 2:02:02 PMMary Jrolf  IBM contributor
5Nov 14, 2013, 2:27:55 PMMary Jrolf  IBM contributor
4Nov 14, 2013, 1:58:42 PMMary Jrolf  IBM contributor
3Nov 14, 2013, 1:53:26 PMMary Jrolf  IBM contributor
2Nov 14, 2013, 1:51:45 PMMary Jrolf  IBM contributor
1Nov 14, 2013, 12:59:17 PMMary Jrolf  IBM contributor
Copy and paste this wiki markup to link to this article from another article in this wiki.
Go ElsewhereStay ConnectedHelpAbout
  • IBM Collaboration Solutions wikis
  • IBM developerWorks
  • IBM Software support
  • Twitter LinkIBMSocialBizUX on Twitter
  • FacebookIBMSocialBizUX on Facebook
  • ForumsLotus product forums
  • BlogsIBM Social Business UX blog
  • Community LinkThe Social Lounge
  • Wiki Help
  • Forgot user name/password
  • About the wiki
  • About IBM
  • Privacy
  • Accessibility
  • IBM Terms of use
  • Wiki terms of use