Home
Deploying
IBM® Sametime® consists of a variety of servers and clients, and can be deployed to suit many different environments. The deployment instructions are organized by feature set, beginning with the minimum components that are necessary to support instant messaging, and then expanding the deployment to include features such as audio and video support, and conferencing.
Integrating Sametime® with other products
Expand the range of features in your IBM® Sametime® deployment by integrating with other products.
Integrating Sametime® with Connections
Integrate IBM® Sametime® servers such as the Sametime Advanced Server and the Sametime Meeting Server with IBM Connections.
Configuring the Sametime® Meeting Server for Connections Files integration
You can configure the IBM® Sametime® Meeting Server to enable web and mobile meeting participants to share files stored in the My Files directory on an IBM Connections server. To configure integration, you must have a Connections server version 4.5IFR CR2 installed, and a Sametime Meeting Server version 9.0 or later. You also need the Files Content Management Interoperability Services (CMIS) API installed on the Connections server.
Configuring login properties for Files integration
The Connections Files server and the Sametime® Meeting Server need to use the same set of login properties.

Configuring login properties for Files integration

The Connections Files server and the Sametime® Meeting Server need to use the same set of login properties.

About this task

Set the login properties in the WebSphere® Integration Solutions console. Note that the Meeting Server requires that the mail attribute appear first in the list of login properties.

Procedure

Log in to the WebSphere Integrated System Console as the WebSphere administrator on the physical Sametime Meeting Server.
Click Security > Global security.
In the "User account repository" section, for "Available realm definitions," select Federated repositories, and then click Configure.
In the list of repositories in the realm, click the name of the repository in the Repository Identifier column.
In the "Security" section, for the field Federated repository properties for login, enter the set of login properties that are used on the Connections Files server. Make sure to enter the mail attribute as the first entry in this field.