IBM Connections 4.5 Integration - From Zero To Social Hero - 2.0 - with Domino LDAP

© 2009 IBM Corporation
IBM Collaboration Solutions
IBM Connections 4.5
Integration
”From Zero to Social Hero”
Frank Altenburg | SME for IBM Sametime
IBM Collaboration Solutions
mailto:frank.altenburg@de.ibm.com
Version 2.0, released May. 29. 2013
For Domino LDAP

2 © 2013 IBM CorporationSocial Business
Agenda
● Introduction
● Requirements for the IBM Connections 4.5 integration
● Architecture of a IBM Connections 4.5 integration deployment
● The steps to integrate an IBM Connections 4.5 Server with
other products

Introduction
This document
● Describes how to implement, in a very fast way, the connectivity to IBM Domino Social
Mail, IBM Sametime and IBM WebSphere Portal with an IBM Connections 4.5 Server.
● It is designed for a Proof of Concept, Proof of Technology or a small test pilot
deployment only.
● It does not contain information how to implement a high available infrastructure.
● You can start with this document just to "make your bosses happy". But to make the
system available for a larger number of users, it is recommended to invite IBM
Services to plan and implement a clustered IBM Connections infrastructure in your
organization that is fully supported.
● The Author has tested this scenario with the hardware specification and software
components described in this document.
● You can use the official IBM support channels for any issue you raise when you use
just this document to install your IBM Connections server. All instructions in this
document are based on the official documentation wiki.
● You need IBM Connections licenses to download the code from Passport Advantage
and to install and use this software.

Audience
This Installation Guide assumes that you have prior experience with products that support
enterprise web applications.
IBM® Connections has dependencies on a number of other products. This guide assumes that
you have a basic knowledge of those products, including how to:
● Install, configure, secure, and administer IBM WebSphere® Application Server.
● Install IBM Tivoli® Directory Server, Microsoft® Active Directory, Sun Java™ System
Directory Server, or IBM Lotus® Domino® LDAP directory, and then configure
WebSphere Application Server to use that LDAP directory with federated repositories.
● Create, manage, and drop IBM DB2®, Oracle, or Microsoft SQL Server databases.
● Install IBM HTTP Server, and then configure it to interact with IBM WebSphere
Application Server over HTTP and HTTPS.
● Install and configure Cognos Business Intelligence and Cognos Transformer

Agenda
● Introduction
● Requirements for the IBM Connections 4.5 integration
other products

Detailed system requirements for IBM Connections
You can find the official IBM Connections 4.5 System Requirements here:
Detailed system requirements for IBM Connections (#7012786)

IBM Connections 4.5 Server Prerequisites
For this pilot deployment you need
● to download the required installation files from Passport Advantage and Fix
Central
● A installed IBM Connections 4.5 Server
● A IBM Lotus Domino 8.5.3 FP3 Server for Domino Mail integration
● A IBM Sametime Proxy Server 8.5.2 IFR1 for the Sametime awareness and BIZ-
Card integration (optional)
● A IBM Sametime Advanced server version 8.5.2 IFR1 with the latest hotfix
● A IBM WebSphere Portal Server version 8.0.0 or 8.0.0.1 or CF5

OS and Network requirements
● Make sure that all servers you want to use can be resolved in DNS.
● If DNS is not available then list all full qualified server names and IP addresses from
all servers in the hosts file and publish this file to all servers.
● If your machines have multiple NIC and / or multiple IP addresses and / or multiple
hostnames and / or multiple aliases in DNS then this can cause issues that we
have not tested. We recommend to have machines with only one NIC and one IP
address, a full qualified host name in the OS network preferences and if required
one DNS Alias for example “connections.renovations.com” if the machine name
is cryptic and you don't want to use it as access point for your users.
● If you use Windows 2008 as Operating System, then you need to start all
installations and configurations in „Administrative mode“.

For the Domino Social Mail integration you need to download this file from Greenhouse:
ICM1.3_allplattform_install.zip
This download can be found here. Log in with your Greenhouse ID and password. If you dont
have a Greenhouse ID you can join Greenhouse for free.
https://greenhouse.lotus.com/plugins/plugincatalog.nsf/assetDetails.xsp?
action=editDocument&documentId=2118E657CE35A81F85257B2C0083B92D
For the IBM connections Portlets for WebSphere Portal:
IC45_Portlets_FP1_20130509.zip
This download can be found here. Log in with your Greenhouse ID and password. If you dont
have a Greenhouse ID you can join Greenhouse for free.
action=editDocument&documentId=B72C4E177060582285257B3A0053BB6F
Required files for a deployment on Windows

For the IBM connections Portlets for WebSphere Portal it is highly recommended that the
following Interim Fixes be deployed: PM85484, PM84403, LO74531, LO74499, LO74629.
You should download this files from Fix Central:
For the WebSphere Portal Server:
8.0.0.1-WP-IFPM85484.zip
8.0.0.1-WP-IFPM84403.zip
For the IBM Connections Server:
4.5.0.0-IC-Multi-LO74499.jar
LO74629.jar
An other important Hotfix for IBM Connections Content Manager is recommended. See this
Technote:
http://www-01.ibm.com/support/docview.wss?uid=swg21632856
Download this file from Fix Central:
5.2.0.0-P8CPE-IF001.zip
Required files for a deployment on Windows (cont...)

Required files for a deployment on Windows (cont.)
If you have downloaded all files into a single directory then this directory should look like
this screen shot:

Unpack the ICM file to the directory “C:Install” on your IBM Connections Server:

Unpack the Portlets file do the directory “C:Install” on your IBM WebSphere Portal
Server:

Agenda
● Introduction
● Requirements for a IBM Connections 4.5 integration
other products

IBM Connections 4.5 architecture for this document
Existing components New components to be installed
IBM DB2
Database
Server
IBM
Connections
Server
Cognos
BI Server
IBM HTTP
Server
IBM Lotus
Domino LDAP
Server
IBM Lotus
Domino Web
Access
Server
IBM
Sametime
Proxy Server
IBM
Sametime
Community
Server
IBM DB2
Database
Client
IBM Tivoli
Directory
Integrator
IBM
Connections
Content
Manager
IBM
Sametime
Advanced
Server
IBM
WebSphere
Portal
Server

Agenda
● Introduction
● Requirements for a IBM Connections 4.5 integration
other products

The steps to integrate an IBM Connections 4.5 Server with other products
● IBM Connections 4.5 on Mobile devices 18
● IBM Connections Desktop Plug-ins for Microsoft Windows 23
● IBM Connections 4.5 Plug-ins for IBM Lotus Notes 26
● Configure IBM Lotus Domino Social Mail integration 27
● An easy way to import some user photos 157
● Adding Sametime awareness through the IBM Sametime Proxy
Server 186
● Configure IBM Sametime Proxy to use the IBM Connections
business card in place of the Sametime business card 207
● Installing and configuring the IBM Connections Portlets for
WebSphere Portal 223
● Integrating IBM Sametime Advanced with IBM Connections 374

Connections 4.5 on Mobile devices
You can use the web browser on your mobile device to access the mobile version of IBM
Connections. The mobile version optimizes the applications for use from a mobile device.
It makes it easier for you to perform tasks with a minimal number of clicks.
Instead of using the web version from a mobile device, you can also install native
applications on the following devices:
Android devices
Apple iPhone
Apple iPad
Apple iPod Touch
BlackBerry OS6 devices
Search for the IBM Connections application from the Apple App Store, Android Market, or
BlackBerry App World.

How do I enable the mobile version?
Before you begin
Note: While it is possible to access IBM Connections by using the browser on your mobile
device, IBM recommends that you use the IBM Connections native app instead. The native
app is available for following mobile devices:
Android
Apple iOS
BlackBerry
Establish how mobile users will remotely and securely connect into your enterprise for IBM
Connections mobile access from a device.
If your enterprise requires the use of a VPN for mobile device remote access, Lotus Mobile
Connect is a recommended option.

If you use signer certificates that are not already trusted by the web browser, install the
SSL signer (trust) certificate on the mobile device. Standard certificate authorities, such as
VeriSign, for example, are trusted by most web browsers, so you would not need to
perform this step if you are using a certificate from a standard certificate authority. To
install the SSL signer certificate on the mobile device, complete the following step:
● Apple iOS:
Send an email to your users with the certificate provided as an attachment. Ask your
users to open the attachment from the device. When they do, the device recognizes
and installs the certificate.
● Devices that run on the Symbian operating system:
Refer to the documentation for the device to find out how to install certificates.
For example, to install a certificate on the Nokia S60 device, go to the Nokia website.
When you install IBM Connections, select the option to install Mobile.
Note: If you already installed IBM Connections, but did not select the Mobile application at
the time, you can rerun the installation wizard in Modify mode.

Instruct your users that they can access the mobile version of IBM Connections by
completing the following steps:
1) Log in to your intranet from the mobile device.
2) Go to the following web address:
http://hostname/mobile
in this example we can use
“http://connections.renovations.com/mobile”
where hostname is the same server host name from which users access IBM Connections
in a standard web browser.

Installing plug-ins to use IBM Connections in other
applications
You can access your IBM Connections data from within other products by adding plug-ins
to those other products.
IBM Connections Desktop Plug-ins for Microsoft Windows
Use the plug-ins to share files and information between Microsoft™ Windows™
applications and IBM Connections.
IBM Connections Plug-in for Microsoft SharePoint
The IBM Connections Plug-in for Microsoft SharePoint brings IBM Connections
applications such as searching by tag, searching by profile, and viewing business cards,
into the SharePoint environment. Install the IBM Connections Widget for Microsoft
SharePoint so that Connections users can access documents from a SharePoint server.

IBM Connections Desktop Plug-ins for Microsoft
Windows
The IBM Connections Desktop Plug-ins Microsoft Windows supports:
● IBM Connections 4.5
● IBM Connections 4.0
● IBM Connections 3.0.1.1
● Microsoft Windows XP SP3 (32-bit)
● Windows Vista (32-bit)
● Windows 7 SP1 (32-bit, 64-bit)
● Microsoft Office 2007 Standard or higher (32-bit)2010 Standard or higher (32, 64-bit)
● Microsoft Outlook 2007 Standard or higher (32-bit), 2010 Standard or higher (32, 64-bit)

IBM Connections Desktop Plug-ins for Microsoft
Windows
The IBM Connections Desktop Plug-ins for Microsoft Windows provides the following
features from Microsoft Windows Explorer:
● Upload local files to IBM Connections from Windows Explorer or from your desktop
● Share uploaded files with people, communities, or folders in IBM Connections
● Work on files locally and publish them to IBM Connections
● View people's contact details and get in touch with them
● Pin, follow, or like IBM Connections files and folders
● View or contribute comments for a file
● Lock a file when you are editing it to prevent file conflicts
● View and restore files from IBM Connections Trash
● Share folders with IBM Connections Communities

Performing a user installation
Procedure
1) Download the plug-in from the IBM Connections catalog at the following web site:
https://greenhouse.lotus.com/catalog
2) Unzip the file.
3) Double-click “IBMConnectionsDesktop.exe” to launch the installation program.
4) Choose not to install the Microsoft Office or Microsoft Outlook plug-ins. In the Custom
Setup panel, click the icon next to Microsoft Office or Microsoft Outlook, and then click
“This feature will not be available” to not install those plug-ins. The Microsoft
Explorer plug in is always installed.
5) Click Finish to complete the installation.
6) If prompted, reboot your computer.

IBM Connections 4.5 Plug-ins for Notes
IBM has just released the latest IBM Connections 4.0 plug-ins for Notes. Unlike previous
releases, IBM has now combined all of the Notes plug-ins into a single install.
● NEW: attach a file to a status update
● NEW: like / unlike a status update
● NEW: Activity stream integration allows to monitor updates for all Connections services
● NEW: search by people and communities
● NEW Lock/unlock files
● Support for Linux desktops
You can download the new Plug-Ins from Greenhouse here:
action=editDocument&documentId=C1245802A721A20185257A9B005EFD52

Configure IBM Lotus Domino Mail integration in
IBM Connections 4.5
Installation overview
Review the software and hardware requirements for the systems that host IBM
Connections Mail. For more information, see IBM Connections Mail system requirements.
● Install and configure IBM Connections 4.5.
● Configure your IBM Lotus Domino Mail Server to use SSL with a self signed
certificate.
● Configure single sign-on between Connections and your mail servers. Import SSL
certificates. Then verify that your settings are correct. For more information, see
Preparing to install IBM Connections Mail.
● Restart all Connections servers.
● Download and install the required software. For more information, see Installing IBM
Connections Mail.
● Enable the mail and calendar icons, the discovery service, and the in-product help.
Optionally, change preferences. For more information, see Configuring IBM
Connections Mail.
● Restart all Connections servers.
The official IBM Connections Mail 1.3 documentation can be found here:
http://www-10.lotus.com/ldd/lcwiki.nsf/xpDocViewer.xsp?
lookupName=IBM+Connections+Mail+1.3+documentation#action=openDocument&content
=catcontent&ct=prodDoc

Configure your IBM Lotus Domino Mail Server to use SSL with a
self signed certificate.
If your IBM Lotus Domino Mail server is already configured to use a SSL certificate, then
you can skip this step.
In your IBM Lotus Notes Client login with an Admin ID and then click “File” - “Open” -
“Lotus Notes Application”. Or just use the “Ctrl-O” combination on your keyboard.

In the “Look in” field select your Mail Server. Then select the “Server Certificate Admin”
database and click the “Open” button.

Close the “About” page.

Click the last entry “Create Key Ring with Self-Signed Certificate”.

Fill the required fields:
“Key Ring Password” and “Password Verify”. The “Common Name” is the DNS Host
Name of your Mail server. The “Organization” the “State or Province” and “Country” fields
needs to be filled. Take note of the “Key Ring File name”. This file name is required later.

Confirm that you have entered all data correctly. Then click the “OK” button to continue.

Close the “Server Certificate Admin” database.

Open your Domino Directory to edit the Server document.

Close the “About” page if it opens.

In the navigator open “Configuration” - “Servers” and then click “All Server Documents”.

Double click your Mail server to open the server document.

In the server document click the “Ports” tab.

Now click the “Internet Ports...” tab.

To edit the server document click the “Edit Server” button.

In the “SSL key file name” field enter the name of your keyfile that you have created
before.

On the same page in the “Web” tab enable the “SSL port status”. Then click the “OK”
button.

In the “TCP/IP port status” field change the setting to “Redirect to SSL”. Then click the
“OK” button.

Click the “Save & Close” button.

To bring the last changes online just shut down the HTTP task. In your Server console
enter the command “tell http q”.

When the HTTP Server has shutdown enter the command “load http”.

The HTTP Server has started successfully.

To test the new settings open your browser and enter the URL to one of your mail files
like “http://chat.renovations.com/mail/sguru.nsf”.

The mail server automatically redirects you to a secure SSL connection and asks you to
confirm the self signed – untrusted – certificate. In Mozilla Firefox just click “I Understand
the Risks”.

Click the “Add Exception...” button.

To view the self signed certificate click the “View...” button.

Yes it is your self signed SSL certificated issued to your mail server. Click the “Close”
button.

Click the “Get Certificate” button and then the “Confirm Security Exception” button.

Log in with the user ID and password of the mail file owner.

You have now successfully reached the IBM Lotus Domino Web Access of the user using a
secure SSL connection.

Configure single sign-on between IBM Connections and your IBM
Lotus Domino mail server.
First you need to access the IBM Connections Integrated Solutions Console. Open your
browser and enter the URL to your ISC. In this example we use
“http://connections.renovations.com:9060/admin”.

Log in with your wasadmin account and password.

In the navigator click “Security” - “Global Security”.

In the “Authentication” are click the “LTPA” link.

Enter a password twice and the path to where you want to store the exported LTPA
Token key file. Then click the “Export keys” button.

Confirm that the keys where successfully exported to the file.

Copy the LTPA Token file to your IBM Lotus Domino Client PC into a local directory.

Now it is local on your PC.

Go back to your Lotus Notes client and open again your Server document.

In the Server document click the “Internet Protocols...” tab.

Now click the “Domino Web Engine” tab.

To change the settings click the “Edit Server” button.

In the “HTTP Session” area change the field “Session Authentication” from “Disabled” to
“Multiple Server (SSO)”. Then click the “OK” button.

On the top of the Server Document click the “Create Web...” button and then the “SSO
Configuration” menu option.

In the “DNS Domain” field enter your DNS domain. Don't forget the prefix dot. Then click the
small icon near the “Domino Server Names”.

Select your Mail server and click the “Add” button. Then click the “OK” button.

Now click on “Keys...” and then “Import WebSphere LTPA Keys”.

Enter the path and file name to the local LTPA Token Key file. Then click the “OK” button.

Enter the key file password and click the “OK” button.

Confirm that the import was successfully. Then click the “OK” button.

In the “WebSphere Information” section change the field “Token Format” to “LtpaToken
and LtpaToken2 ...” Then click the “OK” button.

Now click the “Save & Close” button to save the last changes.

Back in the Domino server document click the “Save & Close” button to save the last
changes.

Reopen the server document now.

Click again the “Internet Protocols...” tab.

And again click the “Domino Web Engine” tab.

And once more click the “Edit Server” button.

It is required to save and reopen the Server document so you can see the newly created
“Web SSO Configuration”. Select the “LtpaToken” and click the “OK” button.

Click the “Save & Close” button to save the last changes.

Normally it is ok to just restart the HTTP server. But in this case it is recommended to restart
the full domino server.

The next step is required only if you use Domino LDAP. On your IBM Connections Server
open a file explorer and navigate to the directory
“C:IBMWebSphereAppServerprofilesDmgr01configcellsconnectionsCell01wim
config”. Now open the file “wimconfig.xml” in an editor. (use Notepad or Wordpad or any
other installed editor)

Now find the section “<config:realmConfiguration” and in here the line starting with
“<config:uniqueUserIdMapping”

Change the two parameters “uniqueName” to “externalName”. Then save and close the
file.

In your Integrated Solutions Console browser window navigate to “System
administration” - “Nodes”.

Select both nodes and click the “Full Resynchronize” button.

The “Full Resynchronize” action pushes the manually changed file from the Deployment
Manager to the nodes.

Import SSL certificates
Now click on “Security” - “SSL certificates and key management”.

In the “Related Items” section click the “Key stores and certificates” link.

Click the “CellDefaultTrustStore” link.

Now click the “Signer certificates” link.

Click the “Retrieve from port” button.

Enter the Host name of your Mail server, the Port “443” and an alias for the certificate.
Then click the “Retrieve signer information” button.

Confirm the retrieved data and click the “Apply” button.

Save the changes by clicking the “Save” link.

The certificate from the mail server is now succesfully added in WebSphere.

You need to restart all WebSphere
servers and tasks. If you use the
CMD-Line way enter this commands:
Switch to the Cognos Box
“stopserver cognos_server
-username wasadmin -password
passw0rd”
“stopserver nodeagent -username
wasadmin -password passw0rd”
Switch to the Connections Box
“stopserver connections_server
-username wasadmin -password
passw0rd”
“stopserver nodeagent -username
“cd ....Dmgr01bin”
“stopserver dmgr -username

And now start all servers using this
commands:
“startserver dmgr”
“cd ....AppSrv01bin”
“startserver nodeagent”
“startserver connections_server”
Switch to the Cognos Box
“startserver nodeagent”
“startserver cognos_server”
Switch to the Connections Box

Verify that SSO between IBM Connections and your IBM Lotus
Domino Mail server works
Open your browser and enter the URL to your connections server. In our example we
use: “https://connections.renovations.com/homepage”.

Log in with a user name and password.

You are now successfully logged in to IBM Connections.

In the URL line enter the URL to the mail file of the user who is logged in. In this example
we use: “https://chat.renovations.com/mail/sdaryn.nsf”.

If the system does not ask you again to authenticate, then the SSO configuration was
successful.

Installing IBM Connections Mail
To start the Installation Manager click on “Start” - “All Programs” - “IBM Installation
Manager” - “IBM Installation Manager”.

Click “File” and then “Preferences”.

Click the “Add Repository...” button.

Click the “Browse” button.

Navigate to the directory “C:InstallICM” and select the “repository.config” file. Then
click the “Open” button.

Confirm that the path is correct. Then click the “OK” button.

Un check all other repositories. Then click the “OK” button to continue.

Click the “Install” entry.

Check the 2 check boxes and click the “Next” button to continue.

Accept the terms in the license agreement and click the “Next” button to continue.

Correct the path and click the “Next” button to continue.

Click the “Next” button to continue.

Click the “Install” button to continue.

IBM Connections Mail is now installing. This task takes only 2-3 minutes.

The installation has finished successful. Click the “Finish” button to continue.

Close the IBM Installation Manager by clicking “File” and then “Exit”.

Log in to the WebSphere Integrated Solutions Console with your WebSphere
Administrator user ID and password.

Enabling or disabling access to IBM Connections Mail
In the Integrated Solutions Console click on “Applications” - “WebSphere enterprise
applications”.

Click the “Common” application.

Click the “Security role to user/group mapping” link.

Select the “mail-user” role and click the “Map Special Subjects” button.

Select the “All Authenticated in Application's Realm” option.

Click the “OK” button to continue.

Click “Save” to save the last changes.

Enabling the discovery service for IBM Connections Mail
In the folder in which you installed Connections Mail (“C:IBMConnections Mail”), locate
the “socialmail-discovery-config-template.xml” and the “socialmail-discovery-
config.xsd” file. Copy both files to the following folder:
“C:IBMWebSphereAppServerprofilesDmgr01configcellsconnectionsCell01Lotu
sConnections-config”.

Rename the copied “socialmail-discovery-config-template.xml” file to “socialmail-
discovery-config.xml”.

Open the file “socialmail-discovery.xml” in your editor. (you can use Notepad,
Wordpad or any other text editor)

In the socialmail-discovery-config.xml file, replace the example information with your
information. For each server configuration in your environment, you must have a
ServerConfig tag with a unique name attribute.
Example:
<ServerConfig name="domino-config">
<ConfigType>DOMINO</ConfigType>
<DirectoryServer>chat.renovations.com</DirectoryServer>
<DirectoryServerDomino>chat.renovations.com</DirectoryServer>
<DirectoryUser>LDAP Bind</DirectoryUser>
<DirectoryPW>Passw0rd</DirectoryPW>
<MailPattern type="renovations.com" />
</ServerConfig>
Then remove the unneeded examples. Now save and close the file.

In the Integrated Solutions Console click “System Administration” - “Nodes”.

Select the 2 nodes and click the “Full Resynchronize” button.

Synchronization was successful.

Open your browser and enter the URL to your Connections Server
“https://connections.renovations.com/homepage”.

Log in with a valid user name and password.

Now enter the URL:
“https://connections.renovations.com/connections/resources/discovery/DiscoverySe
rvlet?email=samantha.daryn@renovations.com”. Use the email address of the user
who logged in.

The discovery service should display the domino mail server name, the mail file and the path.

In the menu line you can now see the icons for Mail and Calendar.
If you don't see the icons, then clean the browser cache and log in again.

Enabling help for IBM Connections Mail
Open a CMD line window and navigate to the directory
“C:IBMWebSphereAppServerprofilesDmgr01bin”. Then enter the command
“wsadmin -lang jython -username wasadmin -password passw0rd”.

Now enter the command “execfile(“connectionsConfig.py”)”.

To enable help for all applications enter the command:
“LCConfigHelp.setHelp("c:/temp","activities","blogs","bookmarks","communities",
"files","forums","homepage","profiles",“wikis“,“icmail“)”.

Switch back to your Integrated Solutions Console and click “Applications” -
“Application Types” - “WebSphere enterprise applications”.

Select the “Help” application and click the “Stop” button.

The application Help is now stopped successfully.

In the File explorer navigate to the directory
“C:IBMWebSphereAppServerprofilesAppSrv01tempconnectionsNode01connecti
ons_server”. Here delete the “Help” subdirectory.

Confirm that you really want to delete this directory with the “Yes” button.

Switch back to the Integrated Solutions Console. Select the “Help” application and click the
“Start” button.

The Help application has started successfully.

In your Connections Browser window click the Help Button ( the one with the questionmark
? )

The Help window now shows the “Mail and Calendar” help.

An easy way to import some user photos into the
profiles
About this task
Adding users photos make IBM Connections more user friendly and will help increase
acceptance of this Pilot.
Be aware that all people using this system must agree to show their photos to others.
The following task demonstrates an easy way to import a small number of user photos (no
more than 50) into profiles for a IBM Connection Pilot. However, if you have more people
and want an automated process for maintaining photos it is recommended to invite IBM
Services to develop a solution that will fit your environment.

Setting up your development environment
About this task
When you install IBM Connections, a set of Tivoli Directory Integrator (TDI) components are
installed on your system. These components are used by the population wizard and other
TDI tasks, such as the synchronization tasks, to populate and update the IBM Connections
user directory. They are stored in a compressed file referred to as the TDI solution directory
(tdisol.zip or tdisol.tar).
The solution directory includes a set of connectors, which are standard TDI components
that you can use to build your own TDI assembly lines when the assembly lines in the
solution directory do not suit your needs. Your custom assembly lines can:
● Use an available plug point, such as an alternate source for profiles data or custom
delete processing
● Create a stand-alone program to interact with the profiles, photos, pronunciation, or
code sections of profiles through the available connectors.
This section describes how to set up a development environment in which you can write
your own assembly lines using the Profiles TDI connectors provided in the IBM Connections
installation package.

In the File explorer navigate to the directory
“c:InstallIBM_Connections_Install_WindowsnsTDISOL”. Right click the file
“tdicol.zip” and seleect “Extract All...”.

Enter the destination directory “C:IBMTDISOL” and click the “Extract” button.

Next step is to configure the TDI development environment. Open a CMD Line window with
Administrator rights and navigate to your TDI directory with the command “cd
C:IBMTDIV7.1”. Then enter the command “ibmditk.bat -s C:IBMTDISOLTDI”.

In the Workspace Launcher window just accept the default workspace path and click the
“OK” button. Ignore the popup message and close the Workspace Launcher. It already has
created the required “workspace” directory.

One of the batch files has a path to the TDI directory hard coded to “C:Program
FilesIBMTDIV7.1”. If you have installed your environment to another drive or to another
path then you need to change this hard coded path in the file “tdienv.bat”. To edit
“tdienv.bat” it is best to use the wordpad or any other Editor, but not Notepad. Open a CMD
line window and navigate to your Development Directory with the command “cd
C:IBMTDISOLTDI”. Then enter the command “C:Program FilesWindows
NTAccesorieswordpad.exe tdienv.bat”.

Find the “SET TDIPATH” line and change the path to “C:IBMTDIV7.1”

Save and close the file.

The next step is to modify the properties file. Open your File Explorer and navigate to the
“C:IBMTDISOLTDI” directory and open the file “profiles_tdi.properties”.

Edit these fields with the right data:

source_ldap_url=ldap://chat.renovations.com:389
source_ldap_user_login=LDAP Bind
{protect}-source_ldap_user_password=Passw0rd
[...]
dbrepos_jdbc_url=jdbc:db2://connections.renovations.com:50000/peopledb
dbrepos_jdbc_driver=com.ibm.db2.jcc.DB2Driver
dbrepos_username=LCUSER
{protect}-dbrepos_password=passw0rd
[...]

The TDI development environment is now ready to use.
An easy way to import user photos is to:
● Add one photo in the standard way using the IBM Connections User interface
● Use the TDI script to export this photo into the development environment
● Add other photos into the development environment using the existing one as an
example
● Use the TDI script to import all photos to the IBM Connections Profiles database

Log In to IBM Connections with a valid user account.

Click “Profiles” and then “My Profile”.

Click the “Edit My Profile” button.

Click the “Photo” tab.

Click the “Choose a file” button.

Navigate to the directory where you have the photos and select the right photo file.
Then click the “Open” button.

Correct the display size and click the “Save and Close” button.

The user photo is now in the profile.

Go back to your CMD line window and be sure to be in the “C:IBMTDISOLTDI”
directory. Enter the command “dump_photos_to_files.bat”. Be sure to get the “success
records is 1” message.

Navigate to the directory where the dump script has saved the photo file
“C:IBMTDISOLTDIdump_photos” and copy your Photo files into this directory.

In the “C:IBMTDISOLTDI” directory open the file “collect_photos.in” for editing.

Mark the 3 existing lines and copy them – five copies in this example. One copy for
each user you want to add a photo.

In this example there are now 6 records for user photos. Next is to modify these
records with the right photo filenames and users short names.

After editing it can look like this example. Save and close the file.

Go back to your CMD line window and enter the command
“load_photos_from_files.bat”. Be sure to see the message “success records is 6”.

In the IBM Connections user interface navigate to “Profiles” - “My Network”. Now you can
see the photos in the “Do You Know” frame.

Adding Sametime awareness through the
Sametime Proxy Server
Before you begin
Note: This is an optional configuration.
You must have the following software enabled to be able to add presence awareness to
IBM Connections:
● Domino® Server 8.5 or later
Refer to Installing and setting up Domino servers.
● IBM Sametime 8.5.2 Interim Feature Release 1 or later, with the Sametime System
Console, Sametime Community Server, and Sametime Proxy Server components.
Refer to the appropriate installation documentation for your Sametime product:
● Sametime Standard 8.5.2 Interim Feature Release 1
● Sametime Advanced 8.5.2 Interim Feature Release 1
Attention: See the IBM Connections system requirements for details on interim fixes
required for enabling Sametime awareness.
Complete the following procedures before attempting to enable awareness.
● Enable single sign-on between the Domino environment and the IBM Connections
server. See the following wiki article for details: http://www-
10.lotus.com/ldd/lcwiki.nsf/dx/setting-up-single-sign-on-in-domino-environments

About this task
When you enable presence awareness using the Sametime Proxy server, a person's
online status is indicated by a set of icons and an associated status message that is
available from the person's profile and business card. Presence awareness tells you
whether the person is available to chat, busy in a meeting, or away from their computer. In
addition to seeing a person's availability, you can carry on a chat with that person even
when no Sametime client is installed.
SSL support: If you have configured the product to send traffic over SSL, presence
awareness can be retrieved over SSL. For more information about enabling SSL for
Sametime, refer to the documentation provided with the Sametime SDK, which is available
from the following web site:
http://www.ibm.com/developerworks/lotus/downloads/toolkits.html
Note: After downloading the toolkit, the documentation can be found in the
sdk/client/connectWebApi/doc/ConnectWebApiDevguide.pdf directory.

Start the wsadmin client in a Administrator CMD-Line with the command:
“cd IBMWebSphereAppServerprofilesDmgr01bin”
“wsadmin -lang jython -username wasadmin -password passw0rd”

To access your configuration file enter the command: “execfile(“connectionsConfig.py”)”

Check out the configuration file with the command:
“LCConfigService.checkOutConfig(“c:Install”,”connectionsCell01”)”

Open the file “C:InstallLotusConnections-config.xml” with a text editor.

Then find the string “sametimeProxy” and configure your Proxy Server URL and ssl URL's.

The flag “enabled” is to enable online awareness in the browser access to connections.
The flag “isConnectClient” is only required if you have installed Sametime Connect Clients.
Then the Client listens on a specific port in the network interface and the browser can
request the sametime information using the Connect Client connection to the Sametime
Community server.

Save and close the LotusConnections-config.xml file. Then check in the file with the
command: “LCConfigService.checkInConfig(“c:Install”,”connectionsCell01”)”
Then enter the command “synchAllNodes()”
To exit the wsadmin client just enter the command “exit”.

Stop and restart all of the IBM Connections application servers.

Import SSL certificate from the Sametime Proxy Server
Now click on “Security” - “SSL certificates and key management”.

Click the “CellDefaultTrustStore” link.

Now click the “Signer certificates” link.

Click the “Retrieve from port” button.

Enter the Host name of your Sametime Proxy Server, the Port (we use “9443” in this
example) and an alias for the certificate. Then click the “Retrieve signer information”
button.

Confirm the retrieved data and click the “Apply” button.

Save the changes by clicking the “Save” link.

The certificate from the Sametime Proxy server is now successfully added in WebSphere.

You should restart your Connections Server now and then clean the Browser cache
before you try the Sametime Awareness in Connections.
Stop the 3 “WebSphere Application Server ...” services and then restart them.

Confirm that this procedure worked by accessing one of the IBM Connections applications,
and then opening a person's business card. It may take a few seconds for the person's
presence information to display the first time. If you can start a chat with the person, then
enabling awareness through the proxy server was successfully completed.

Configure your Sametime Proxy Server to use
Connections as the business card server
Overview
There are two potential areas of integration where Connections features can be surfaced
within Sametime:
● Photos stored in Connections profiles can appear in Sametime web client instant
message headers and Sametime business card.
● Connections business card can be used in place of Sametime business card.
Note that both of these require that email addresses are enabled on the Connections
server. This is the default setting in a Connections deployment but to verify whether this has
been disabled check LotusConnections-config.xml. There is a setting in this file called
exposeEmail enabled which needs to be set to true for the following integration points to
work.

Displaying Connections profile photos in Sametime
web client instant messages
The following steps are required in order to display the photos stored in Connections
profiles within the Sametime web client. Note that this configuration does not affect the
Sametime Connect client.
● Add a photoURL to the LDAP person records.
● Configure the photoURL in the Sametime Community server.

Add a photoURL to the LDAP person records
The example environment uses the Domino directory as the LDAP. By default, person
records contain a field named photoURL which is displayed in the Miscellaneous tab of
the person record.

Complete this field with a URL in the following format:
http://Connections_hostname/profiles/photo.do?email=user_email_address
For example, in the example environment the URL:
“http://connections.renovations.com/profiles/photo.do?
email=sametime.guru@renovations.com” when typed into a browser displays the photo
associated with the account that has that email address.

Configure the photoURL in the Sametime
Community server
The contents of the Sametime business card is controlled by the “userInfoConfig.xml” file
that is stored in the Domino program directory of the Sametime Community server.
Open this file in your editor.
In the first lines add the parameter to not use the configuration from stconfig.nsf and
Sametime System Console. It is required to use the configuration defined here in this
configuration file only that it works.
<UserInformation>
<ReadStConfigUpdates value=”false”/>
<Resources>

Append the following line to the Details section:
<Details>
<Detail Id="MailAddress" FieldName="mail" Type="text/plain"/>
<Detail Id="Name" FieldName="cn" Type="text/plain"/>
<Detail Id="Title" FieldName="title" Type="text/plain"/>
<Detail Id="Location" FieldName="postalAddress" Type="text/plain"/>
<Detail Id="Telephone" FieldName="telephoneNumber" Type="text/plain"/>
<Detail Id="Company" FieldName="ou" Type="text/plain" />
<Detail Id="Photo" FieldName="jpegPhoto" Type="image/jpeg" />
<Detail Id="PhotoURL" FieldName="PhotoURL" Type="text/plain"/>
</Details>
Add PhotoURL as a parameter in both lines in the ParamSets section
<ParamsSets>
<Set SetId="0"
params="MailAddress,Name,Title,Location,Telephone,Photo,PhotoURL,Company"/>
<Set SetId="1"
params="MailAddress,Name,Title,Location,Telephone,Photo,PhotoURL,Company"/>
</ParamsSets>
Save and close the UserInfoConfig.xml file.
Then restart the Sametime Community Server.

To verify the configuration:
1)Login to the Sametime web client (either using the Sametime 8.5.2 Proxy server or the
Sametime 8.5.1.1 Proxy server) using the credentials of one of the LDAP users.
2)Using a separate browser, login to the Sametime web client as a different LDAP user.
3)From one of the browsers add the other user to the contact list (if not already added).
4)Hover over the user's name and the Sametime business card should be displayed with the
Connections profile photo.
5)Start a chat with the user and the user's photo should appear in the header of the instant
message.

Configure to use the Connections business card in place of
the Sametime business card
Open your browser and enter the URL to your Sametime System Console:
“http://sametime.renovations.com:8700/admin”
Log in to the Sametime System Console with administrator privileges.

Click “Sametime System Console” -> “Sametime Servers” -> “Sametime Proxy
Servers”.

Click the Sametime Proxy Server's link to open its Configuration page.

Under "General Properties" navigate to the "Business card server" section.

Click Connections Server and enter the server's address.
The address for a Connections Profile server typically looks like this:
“https://connections.renovations.com/profiles”

Click “OK”, and then click “Apply”.

Open your browser and login to the Sametime Proxy Server. Hover over a contact and see
the business card changes after some seconds and shows the connections profile data.

If you click the icon left of the photo you get the connections menu. To see the profile of the
contact just click the “Profile” link.

A new Browser window opens and shows the Connections Profile of the contact.

Installing the IBM Connections Portlets for WebSphere Portal
Installing this package makes the following portlets available to your portal users:
● Activities – Collaboration tool for collecting, organizing, sharing, and reusing work
related to a project goal.
● Activity Stream – Integration portlet that lets you monitor and interact with people and
content that you are following.
● Blogs – Online journals you can use to deliver timely information with a personal touch.
● Bookmarks – Social bookmarking tool that you can use to save, organize, and share
Internet and intranet bookmarks.
● Tags – Meaningful keywords you can use to find associated content.
● Profiles – Directory of colleagues you can use to build a network and locate expertise.
● Wikis – Repository for sharing and collaborating on pages of interest to your group.
● Forums – View and contribute to discussion topics.
● Community Overview – View basic community information like the description, tags,
and community owners. Perform basic community actions from the portlet.
● Blogs Summary – Choose a view to see a snapshot of recent, latest, or featured blog
activity
● Profiles Summary – View a summary of information about your colleagues.
● Forums Summary – View a list of forums that you can access.
● Bookmarks Summary – View a list of bookmarks you can access.

You can also deploy community pages, which are portal pages associated with
communities from IBM Connections communities. Portlets on community pages are
automatically scoped to the community membership and display content from the
community in the portlets. For example, if your community contains a forum, adding the
forum portlet to a community page lets portal users view and interact with the forum
content from a Portal application.
The installation of the IBM Connections Portlets for WebSphere Portal requires the Portal
server to be on the latest Portal release.
It has to be WPS 8.0.0.1 CF5.
Then it contains the latest fixes required to run successfully the Connections Portlets and
the Biz Card integration.
Download from Fix Central these files and install them to your WebSphere Portal server:
8.0.0-WP-Server-FP001.zip
8.0.0.1-WP-WCM-Combined-CFPM84211-Server-CF05.zip

Implementing IBM Connections fixes required for the IBM Connections
Portlets for WebSphere Portal
Download these fixes from the IBM Fix Central page:
4.5.0.0-IC-Multi-LO74499.jar
LO74629.jar
Copy these 2 files to the IBM Connections Server into the directory “C:InstallFixes”:

Open a CMD line window and navigate to the WebSphere Binaries directory with the
command “cd IBMWebSphereAppServerbin”. Then run the command
“SetupCmdLine.bat”.

Now navigate to the Connections UpdateInstaller directory with the command “cd
IBMConnectionsUpdateInstaller”. Then run the command “UpdateWizard.bat”.

Change the Directory Path to “C:InstallFixes”. Then click the “Next” button to continue.

Select the second option “I have backed up all changes to IBM Connections....”.
Then click the “OK” button to continue.

Enter your WebSphere Administrators user name and password. Then click the “Next”
button to continue.

Click the “Install” button to start the installation.

The fixes are now installing this can take approximately 10 to 15 minutes.

The installation was successful. Click the “Finish” button to close the UpdateWizard.

Importing a certificate to support SSL
About this task
In order for WebSphere Portal to communicate with IBM Connections over Secure Sockets
Layer (SSL), the WebSphere Portal Server must trust the signer of the SSL certificate for
IBM Connections. This might be set up by default in your WebSphere infrastructure if you
use SSL certificates that are issued by a commonly recognized authority. If you use self-
signed certificates, the default certificate or a signer that is not recognized by your
WebSphere Portal Server, you must import the SSL certificate from IBM Connections to
your WebSphere Portal Server.

Log in to your WebSphere Portal Integrated Solutions Console with your WebSphere
administrator user name and password.

Click “Security” - “SSL certificate and key management”.

Now click the “NodeDefaultTrustStore”.

In the “Additional Properties” section click the “Signer certificates” link.

Click the button “Retrieve from port”.

Enter the DNS host name of your connections server in the “Host” field. The SSL Port in the
“Port” field. An alias in the “Alias” field. Then click the button “Retrieve signer information”.

To save the last changes click the “Save” link.

Updating the portlet theme
About this task
By design, the default themes for Portal 7.0.0.2 and Portal 8.0 do not load Dojo in view
mode. This helps to render the theme faster. Because the Connections portlets depend on
different capabilities, you must use a profile that includes the Dojo capabilities. For the
portal default theme, the PAA installer is automatically assigning the "Full" profile.
However, that profile includes more capabilities than the portlets need. In order to create a
highly optimized setup, the rest of this article describes which dependencies the portlets
have and how you can add them to your custom theme profile.
If you do not add these modules to your theme profile used for the pages that contain the
IBM Connections portlets, you can still deploy and configure the Connections portlets on a
Portal 7 server, but some features will not work as expected. You can not deploy and
configure the Connections portlets on a Portal 8 server. An error warns you that the
modules are missing.

To change the Theme you need a FTP client that supports the WebDAV protocol. We use
“AnyClient” from JSCAPE in this example. You can download the client from this URL:
“http://www.jscape.com/downloads/anyclient”. Then install the client to your computer.

Start the WebDAV client.

Click “File” - “Site Manager”.

Click the “New” button to create a connection to your Portal Server.

Enter a name for the connection – we use “Portal”. In the Host field enter the url:
“http://portal.renovations.com:10039/wps/mycontenthandler/dav/themelist”.
Enter the WebSphere Portal Server Administrator user name and password. As Protocol
select “WebDAV”. Enter a local directory and then click the “Save” button.

Select the “Portal” Site and click the “Connect” button.

In the right window click the “ibm.portal.80Theme”.

Click the “profiles” subdirectory.

Select the file “profile_deferred.json” and click the green “copy” button.

Open your file explorer and locate the local directory that you have selected earlier. Open
the file “profile_deferred.json” with your favorite editor.

Add this 2 lines in the “moduleIDs” section:
“wp_liveobject_framework”,
“dijit_form_17”,
Then save the file and close the editor.

Now select the file “profile_deferred.json” in the left window and click the green “copy”
button.

Click the “Yes” button to overwrite the file in the Portal server.

Close the AnyClient.

Restart your WebSphere Portal server.

Configuring authentication for the portlets
IBM Connections uses single sign-on (SSO) to secure the transfer of user ID and
password information that is used to authenticate with the system. With SSO, users can
switch to different applications without needing to authenticate again. SSO is automatically
enabled when IBM Connections is installed on a single WebSphere Application Server
profile or when different profiles are federated into the same cell.
Configuring basic authentication allows the manual entry of user credentials in the
personalize mode of the portlets. Basic authentication for the portlets can only be
supported if single sign-on is not already enabled between WebSphere Portal and IBM
Connections. If single sign-on is enabled (through LTPA, Kerberos or another mechanism),
it takes precedence. If single sign-on is enabled, the basic authentication credentials that
are entered in the personalize mode of the portlets are ignored.
Configuring single sign-on for users is recommended over using basic authentication for
user interactions. If you use basic authentication for the portlets, every user must type in
their personal credentials manually in the personalize mode of the portlets or shared
credentials can be supplied from the Credential Vault. Basic authentication can be
especially useful for trials of the portlets before you have a chance to configure some form
of single sign-on, but is not recommended for production use.

Enabling single sign-on for the portlets for a stand-alone LDAP
server
About this task
This task describes the steps that are required to enable SSO between IBM Connections
and WebSphere Portal when they are on different WebSphere Application Server cells.
Applications that are deployed on servers within the same WebSphere Application Server
cell are enabled by default for SSO.
Set the realm name in the LTPA token to that of the LDAP server before you export the
LTPA token. For example, if you connect to an LDAP server at ldapserver.example.com
over port 389, then you must set the realm name to ldapserver.example.com:389. If you
must change the realm name, see the topic Changing the realm name.
To allow SSO between IBM Connections and WebSphere Portal, complete the following
steps:

We have already exported the LTPA Token key from the Connections server and importet it
to the Domino and Community Server. We can use his token and import it to the Portal
server.

Copy the LTPA Token file to a directory on your Portal server.

Login to the Integrated Solutions Console of your Portal server and click “Security” -
“Global security”.

In the “Authentication” section click the “LTPA” link.

Enter the password of the LTPA Token Key file and the path and file name. Then click the
“Import keys” button.

Click the “Save” link to save the last changes.

In the “Authentication” section click “Web and SIP security” then “Single sign-on (SSO)”.

Enter the Domain name and check the flag “Interoperability mode”. Enter “LtpaToken” in
the LTPA V1 cookie name and “LtpaToken2” in the LTPA V2 cookie name. Uncheck the
flag “Set security cookies to HTTPOnly...”. Then click the “OK” buton.

Click the “Save” link to save the last changes.

Open your browser and enter the URL to your Connections server
“https://connections.renovations.com/homepage”.

Log in with a Connections user

Now change the URL to your Portal server “https://portal.renovatons.com/wps/myportal”.

You should be already logged in to the Portal server.

Installing the IBM Connections Portlets for WebSphere Portal
Before you begin
Using the portlets, you can access only those IBM Connections offerings that you already
installed and configured. Note the following restrictions and prerequisites before you install:
● You must uninstall any previous versions of the portlets before you install. Upgrading
from previous versions is not supported. Before you run the PAA Solution installer,
manually clear configuration settings from the previous installations. For example,
remove any existing settings for the DynaCache, REP, search jars, or VMM
configuration.
● To enable LTPA single sign-on between an IBM Connections feature and a
WebSphere Application Server configured for stand-alone LDAP, complete the steps in
the section Configuring authentication. to enable single-sign on before you start the
installation.
● When Single Sign-On is enabled between Portal and Connections, the Portal
administrator who installs and configures the IBM Connections portlets must be a valid
Connections user. For example, the user you assign to manage the Virtual Member
manager, as set using the -DICdsxAdminId parameter from Step 5, can be made a
Portal administrator by following the steps in the article How to assign a new portal
administration group aside from wpsadmins in the IBM WebSphere Portal wiki. You
can also create a Connections profile for the default Portal administrator in the IBM
Connections profiles database by following the steps in the topic Adding LDAP data to
the Profiles database.
● Anonymous Portal users can access the IBM Connections portlets and are treated as
anonymous Connections users. However, authenticated Portal users must also be
valid Connections users or they will get an error when they try to access a Connections
portlet.

In your File explorer navigate to the directory
“C:IBMWebSpherewp_profileConfigEngineproperties”.
Then open the file “wkplc.properties” with your editor.

Confirm the two administrative passwords for the WebSphere Administrator and the
WebSphere Portal Administrator are set. Check the fields “WasPassword=passw0rd” and
“PortalAdminPwd=passw0rd”.

Find the path to where you have unpacked the Portlets with the file “SNPortlets.paa”.

Open a CMD line window and navigate to the ConfigEngine directory with the command
“cd IBMWebSpherewp_profileConfigEngine”. Then enter the command
“ConfigEngine.bat install-paa
-DPAALocation=C:/Install/IC45_Portlets_FP1_20130509/SNPortlets.paa”. Be sure to
enter the path with forward slashes and not with back slashes as you normally do it in
Windows.

Wait until the command has completed successfully.

Now enter the command: “ConfigEngine.bat deploy-paa -DappName=SNPortlets
-DwasPassword=passw0rd -DportalAdminPwd=passw0rd -DmaxTimeToWait=30
-DmaxAppTimeToWait=5”

The last command to enter is: “ConfigEngine configure-SNPortlets -DICversion=4.5
-DICblogsHomepageHandle=homepage -DICemailSetting=email-exposed
-DICtagSearchType=mysearch -DICdsxAdminId=wasadmin
-DICdsxAdminPwd=passw0rd
-DICbaseURLunsecured=http://connections.renovations.com
-DICbaseURL=https://connections.renovations.com”

Start your browser and access the Portal site with the URL
“https://portal.renovations.com/wps/portal”.

Click the “Log In” link.

Log in with a LDAP user name and password.

Click the “IBM Connections” link in the menu.

The first step was successful. The next step is to configure some post install tasks.

Configuring the Connections business card
Enable the IBM® Connections Business Card so that your users can access Connections
data such as a person's profile information.

In the CMD line window navigate to the ConfigEngine directory with the command “cd
IBMWebSpherewp_profileConfigEngine”. Then run the command “ConfigEngine
configure-ConnectionsBizCard
-DICbaseURLunsecured=http://connections.renovations.com
-DICbaseURL=https://connections.renovations.com -DURLProviderName="Default
URL Provider"”.

Confirm that the command was running successfully.

Start your browser and access the Portal site with the URL
“https://portal.renovations.com/wps/portal”.

Click the “IBM Connections” link in the menu.

Hover with the mouse over a name. The yellow box appears with the text “Click here or
press control-enter to view the business card”. Click into the message.

The IBM Connections Business Card of the user appears.

Integrate Connections Communities into your Portal site
Integrate Connections Communities into your Portal site to enhance your portal's social
collaboration capabilities.
You integrate Communities by associating a set of portal pages with a community. These
types of portal pages are called Community Pages. By associating a set of portal pages
with a community in Connections, all of the Connections portlets on those pages
automatically render their content within the context of that community. One or more
communities can be integrated into your portal site. You can associate different sets of
pages in your portal site with the appropriate community. The community can be public,
moderated, or private.
Note: Before you add portlets to a community page, make sure that the corresponding
widget exists in the community. For example, before you add a Blogs portlet to a
community page, make sure that the IBM Connections community contains a blog. If not,
add the Blogs widget to the IBM® Connections community using the browser interface.

Restriction: Ideation blogs are not supported for community pages. If your IBM
Connections community contains an Ideation blog widget, it does not display if the Blogs
portlet is deployed on a community page.
Some of the ways the portlets on a Portal community page interact with an IBM
Connections community include:
● Clicking a profile user name or photo in a Profiles summary portlet displays profile
detail in the target portlet.
● Clicking a View all link in a Profiles summary portlet displays a list of community
members in the target portlet. This link works only if there is a Profiles detail portlet on
the page.
● Clicking the View all link in a Blogs summary portlet displays all entries in a
community blog in the Blogs detail portlet on a community page.
● Clicking the entry in a Blogs summary portlet displays the detail of that entry in the
Blogs detail portlet on a community page.
● When a user hovers over an entry in a Blogs summary portlet, a pop-up displays, with
a link that allows a user to read the entry.
● Clicking Read for an entry in the Blogs summary portlet shows the selected entry
details in the Blogs detail portlet.

Mapping a community page to a community
In this example we create a new page called “Community” in the “IBM Connections” part
and map several applications of the community into this new page. You can use every
existing page and map the community applications there.
Start your browser and access your Portal server. Then click the “Log In” link.

Log in with your WebSphere Portal administrator user name and password.

In the top line click the “Administration” link.

Click the “Manage Pages” link in the “Portal User Interface” section.

Click the “Content Root” link.

Click the “Home” link

Click the “IBM Connections” link.

Click the “New Page” button to create a new page.

Fill the Title field with “Communities” and the Unique Name field with
“ibm.conn.community”. Then click the “OK” button.

Now click the “Home” link in the top of the screen.

And now click the new “Communities” link.

Next is to map the community to the page. Click the “Edit Mode” link in the top of the
screen.

In the “Overview” tab hover with the mouse over “Community: none”. Then the line gets
light blue and an “Edit” link appears. Click this “Edit” link.

Click the “Select a community” button.

In this example only one community appears. So we can select only this community. If
you already have several communities in your Connections Server you can select one of
them or search for one using the “Find Community” feature. Then click the “Select”
button.

The community is now selected. Click the “OK” button to continue.

You can now see your selected community in the Page Properties. Click the “Save” link to
save the changes.

Now click the “Content” tab.

You can now add your Communities applications to the page. To find more applications use
the “Next” link.

To add a portlet just click the “plus” icon or drag and drop it from the Content area to your
page. Then you can place it on your page where you want. Left or right before or after an
existing application.

Add the next application or drag and drop it.

In this example we have added the applications “Community Overview”, “Activities”
and “Blogs” on the left side, and “Bookmarks”, “Forums” and “Wikis” on the right side.

Save the changes and switch back to the “View Mode”.

The Portal Admin does not have rights to access Connections. So the applications cant
show any content from the Connections Community. Log out using the “Log Out” link

Now click the “Communities” link.

Configuring search integration
IBM® Connections search integration in IBM WebSphere Portal allows users to perform
search queries and view query results for IBM Connections content within the context of
their portal environment.
This integration point is enabled by configuring the portal search center component to
include IBM Connections content as part of the related search results. You also must
configure a component to allow the navigation from the portal search center to the portlets
so that users can view the Connections-related search results.

Understanding the search architecture
Portal currently provides the following two search frameworks. The one you use depends on
whether you value performance or ease of maintenance.
Search Service
Search Service is a live search and uses REST (along with other technologies) to
search on a target information source and fetch the matching results.
Connections/Portal integration uses the "Remote Content Server Search Service Type"
(referred to as RCSS type), using the ATOM/REST APIs exposed by Connections. This
approach would tag relevance score of connections content, in isolation, to the portal
relevance score. It is a federated approach in which the search is federated between
Portal and Connections instances.
Search Collections
Search Collections use a seedlist framework to crawl and index all of the Connections
data locally on a Portal server. The advantage of this approach is that it removes extra
network traffic to the Connections server during the search process, making
information retrieval fast. One disadvantage is that the crawler must run frequently to
synchronize local content with all the latest content on the Connections server. It can
do a better relevance ranking of search results, as search results (including Portal and
Connections) are served by the Portal engine only.

Deploying search integration prerequisites
Open a CMD-line window and navigate to your ConfigEngine directory with the command
“cd IBMWebSpherewp_profileConfigEngine”. Then enter the command
“ConfigEngine.exe configure-SNPortletsSearch -DICversion=4.5”.

Confirm that the command run successfully.

Configuring search collection
In this example we are configuring the search using Search Collections. Be aware this
method can only be used if the Portal Server is not clustered. If your Portal Server is
clustered you have to use the RCSS method. More information about this configuration
method can be found in the documentation.
Before you begin
Important: Ensure that these IBM Connections seedlists are available with basic
authentication. Depending on your security configuration, basic authentication might be
the default or can be accomplished with an additional virtual host in your HTTP server, by
addressing a WebSphere node directly, or by altering Tivoli® Access Manager or
SiteMinder configuration to open a basic authentication protected endpoint.
About this task
To configure a search collection, you specify one content source for each Connections
seed list. Each Connections service (for example, Profiles, Communities, or Blogs)
exposes its own seed list so there is one content source per Connections service.

Open your browser and navigate to your Portal server. There click the “Log In” link.

Log in with your Portal administrator user name and password.

In the top line click the “Administration” link.

Under “Search Administration” click “Manage Search”.

Click the “Search Collections” entry.

Click the “New Collection” button.

In the Location field enter the path to your collection. Normally this should be under
“C:IBMWebSpherewp_profilePortalServercollections”. Add a subdirectory for the
collection you are creating. Here the Activities Collection. This directory is created
automatically. Enter the name of the collection in the “Name of Collection” field.

Next is to create the Content Source settings. Click the new created Collection. Here the
“Activities Collection”.

Click the “New Content Source” button.

In the “Content source type” selection box select “Seedlist provider”.

Enter your Content source name and the URL. In this example we use
“Connections_Content_Source_Activities” and the URL
“https://connections.renovations.com:443/activities/seedlist/myserver” for the
Activities. Be sure to use the IHS port and add the port even if you use standard ports like
80 or 443.

On the right side click the “Security” tab.

Enter the Connections server administrator user name and password. Then click the small
“Create” icon.

Now click the “Create” button.

The Connections
Content Source
for Activities is
now configured
successfully.

Now you should create the Collections for the other Connections Applications: Blogs
Bookmarks Communities Files Forums Profiles Wikis. Go back by clicking the link
“Collections from all Services”.

It is the same procedure as described starting on page 359 here in the documentation.

Collection Name Location Content Source Name URL
Activities Collection C:IBMWebSpherewp_profilePor
talServercollectionsActivities
Connections_Content_Source_Ac
tivities
https://connections.renovations.co
m:443/activities/seedlist/myserver
Communities Collection C:IBMWebSpherewp_profilePor
talServercollectionsCommunities
Connections_Content_Source_Co
mmunities
m:443/communities/seedlist/myse
rve
Blogs Collection C:IBMWebSpherewp_profilePor
talServercollectionsBlogs
Connections_Content_Source_Bl
ogs
m:443/blogs/seedlist/myserve
Bookmarks Collection C:IBMWebSpherewp_profilePor
talServercollectionsBookmarks
Connections_Content_Source_Bo
okmarks
m:443/dogear/seedlist/myserve
Files Collection C:IBMWebSpherewp_profilePor
talServercollectionsFiles
Connections_Content_Source_Fil
es
m:443/files/seedlist/myserve
Forums Collection C:IBMWebSpherewp_profilePor
talServercollectionsForums
Connections_Content_Source_Fo
rums
m:443/forums/seedlist/myserve
Profiles Collection C:IBMWebSpherewp_profilePor
talServercollectionsProfiles
Connections_Content_Source_Pr
ofiles
m:443/profiles/seedlist/myserve
Wikis Collection C:IBMWebSpherewp_profilePor
talServercollectionsWikis
Connections_Content_Source_Wi
kis
m:443/wikis/seedlist/myserve

You have now created up to 8 collections and configured their content source.

Go back by clicking the “Manage Search” link.

Setting the Search Scope
Define search scopes for the content from IBM® Connections that is returned from a
search in IBM WebSphere® Portal applications.
About this task
After the service or collection is defined, you can optionally define search scopes to make
available to users. A search scope defines different levels of granularity at which the
search is executed from the Portal user interface.

Click the “Search Scopes” link.

Click the “New Scope” button.

Enter a name for
the new scope and
then click the
“Select Locations”
button.

Check the first check box near “Locations”. All boxes get checked automatic. Then click
the “OK” button.

Now click the “OK” button to save the new created Search Scope.

The new search scope is created. To test the search, log out first.

And re log in.

Log in with a directory user name and password.

Now click the “Search Center”
link in the top row. Then click
the “Search Center” link.
Enter a search string and click
the search icon or wait just
some seconds.

IBM Connections 4.5 Integration - From Zero To Social Hero - 2.0 - with Domino LDAP

IBM Connections 4.5 Integration - From Zero To Social Hero - 2.0 - with Domino LDAP

Recommended

Recommended

More Related Content

What's hot

What's hot (16)

Viewers also liked

Viewers also liked (20)

Similar to IBM Connections 4.5 Integration - From Zero To Social Hero - 2.0 - with Domino LDAP

Similar to IBM Connections 4.5 Integration - From Zero To Social Hero - 2.0 - with Domino LDAP (20)

More from Frank Altenburg

More from Frank Altenburg (6)

Recently uploaded

Recently uploaded (20)

IBM Connections 4.5 Integration - From Zero To Social Hero - 2.0 - with Domino LDAP