IBM BPM, V8.0.1, All platforms > Administer the IT infrastructure > Administer Process Portal
Configure Sametime Connect integration
IBM Lotus Sametime Connect provides instant messaging support to allow your end users to collaborate in real time on their work. To integrate Sametime Connect functionality with Process Portal, you must perform additional configuration steps in both environments.
Before you begin this task, the Process Portal must have been installed and started.
The following WebSphere Application Server requirements apply to your IBM BPM and Sametime Connect environments:
- The two environments must share a common user registry, and it must be available as a base entry in your IBM BPM federated repositories.
- To support the use of short names and email addresses for system login, the federated repository entry must contain login properties of either uid, mail, or uid;mail
- The two environments must share the same federated repositories realm name.
- The two environments must share an LtpaToken for single sign-on (SSO) functionality. This requires that common domain names and interoperability mode are enabled globally.
- You must import Lightweight Third Party Authentication (LTPA) keys from one environment to the other.
- If you use SSL communication, it must be enabled on all the servers in the configuration including the Process Center server, Process Server, and Sametime Connect server. Normal SSL configuration is required, including certificate exchange across all servers.
Procedure
- Configure IBM BPM and Sametime Connect to share the same user registry and the same federated repositories realm name. For information about this task, see "Managing the realm in a federated repository configuration".
- Configure IBM BPM and Sametime Connect to share an LtpaToken for SSO functionality, which would include common domain names and interoperability mode to be enabled in the Global security panel and the Global security > Single sign-on (SSO) panel in the administrative console. For information about this task, see "Implementing single sign-on to minimize web user authentications".
- Import LTPA keys from one environment to the other.
For example, you must either import the Sametime Connect LTPA keys into IBM BPM or import the IBM BPM LTPA keys into Sametime Connect. For information about this task, see "Importing Lightweight Third Party Authentication keys", and "Preparing servers running on WebSphere Application Server for single sign-on".
- Configure the Sametime Proxy Server so that the domain
that is specified in the SSO settings is in the allowed list of domains. All subsequent access to Process Portal and Sametime Connect must be done through a host name that ends in this domain name.
- Log in to the Sametime System Console as the Sametime administrator.
- Click Sametime Servers > Sametime Proxy Servers.
- From the Proxy Servers list, select the name of a Sametime Proxy Server to open its Configuration page.
- In the Domain list of Sametime Proxy Server section, enter the same domain name that you used in the WebSphere Application Server SSO settings, for example, ibm.com.
- Click OK and restart all the WebSphere Application Server-based Sametime servers
Results
Process Portal is now configured for Sametime Connect. When you use Process Portal, you see the standard Sametime Connect icons and team member information integrated within the expert and participant information.
What to do next
In Process Designer, enable the process applications that you want to expose in Process Portal for Sametime Connect integration.
Related concepts:
Instant messaging: Frequently asked questions
Related tasks:
Enabling Sametime Integration in Process Portal
Related information:
Manage the realm in a federated repository configurationImplementing single sign-on to minimize web user authenticationsImporting Lightweight Third Party Authentication keysPreparing servers running on WebSphere Application Server for single sign-onSecure communications using SSLRetrieve from port