IBM Connections 4.5 Integration From Zero to Social Hero

Transcription

1 For Domino LDAP IBM Collaboration Solutions IBM Connections 4.5 Integration From Zero to Social Hero Frank Altenburg SME for IBM Sametime IBM Collaboration Solutions Version 2.0, released May IBM Corporation

2 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 2

3 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. 3

4 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 4

5 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 5

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

7 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 FP3 Server for Domino Mail integration A IBM Sametime Proxy Server IFR1 for the Sametime awareness and BIZCard integration (optional) A IBM Sametime Advanced server version IFR1 with the latest hotfix A IBM WebSphere Portal Server version or or CF5 7

8 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. 8

9 Required files for a deployment on Windows 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. action=editdocument&documentid=2118e657ce35a81f85257b2c0083b92d For the IBM connections Portlets for WebSphere Portal: IC45_Portlets_FP1_ 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=b72c4e b3a0053bb6f 9

10 Required files for a deployment on Windows (cont...) For the IBM connections Portlets for WebSphere Portal it is highly recommended that the following Interim Fixes be deployed: PM85484, PM84403, LO74531, LO74499, LO You should download this files from Fix Central: For the WebSphere Portal Server: WP-IFPM85484.zip WP-IFPM84403.zip For the IBM Connections Server: IC-Multi-LO74499.jar LO74629.jar An other important Hotfix for IBM Connections Content Manager is recommended. See this Technote: Download this file from Fix Central: P8CPE-IF001.zip 10

11 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: 11

12 Required files for a deployment on Windows (cont.) Unpack the ICM file to the directory C:\Install on your IBM Connections Server: 12

13 Required files for a deployment on Windows (cont.) Unpack the Portlets file do the directory C:\Install on your IBM WebSphere Portal Server: 13

14 Agenda Introduction Requirements for a 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 14

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

16 Agenda Introduction Requirements for a 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 16

17 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

18 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. 18

19 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. 19

20 How do I enable the mobile version? 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 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. 20

21 How do I enable the mobile version? Instruct your users that they can access the mobile version of IBM Connections by completing the following steps: 1) 2) Log in to your intranet from the mobile device. Go to the following web address: in this example we can use where hostname is the same server host name from which users access IBM Connections in a standard web browser. 21

22 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. 22

23 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 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) 23

24 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 24

25 Performing a user installation Procedure 1) Download the plug-in from the IBM Connections catalog at the following web site: 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. 25

26 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=c a721a a9b005efd52 26

27 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: lookupname=ibm+connections+mail+1.3+documentation#action=opendocument&content =catcontent&ct=proddoc 27

28 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. 28

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

30 Close the About page. 30

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

32 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. 32

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

34 Close the Server Certificate Admin database. 34

35 Open your Domino Directory to edit the Server document. 35

36 Close the About page if it opens. 36

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

38 Double click your Mail server to open the server document. 38

39 In the server document click the Ports tab. 39

40 Now click the Internet Ports... tab. 40

41 To edit the server document click the Edit Server button. 41

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

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

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

45 Click the Save & Close button. 45

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

47 When the HTTP Server has shutdown enter the command load http. 47

48 The HTTP Server has started successfully. 48

49 To test the new settings open your browser and enter the URL to one of your mail files like 49

50 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. 50

51 Click the Add Exception... button. 51

52 To view the self signed certificate click the View... button. 52

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

54 Click the Get Certificate button and then the Confirm Security Exception button. 54

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

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

57 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 57

58 Log in with your wasadmin account and password. 58

59 In the navigator click Security - Global Security. 59

60 In the Authentication are click the LTPA link. 60

61 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. 61

62 Confirm that the keys where successfully exported to the file. 62

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

64 Now it is local on your PC. 64

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

66 In the Server document click the Internet Protocols... tab. 66

67 Now click the Domino Web Engine tab. 67

68 To change the settings click the Edit Server button. 68

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

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

71 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. 71

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

73 Now click on Keys... and then Import WebSphere LTPA Keys. 73

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

75 Enter the key file password and click the OK button. 75

76 Confirm that the import was successfully. Then click the OK button. 76

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

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

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

80 Reopen the server document now. 80

81 Click again the Internet Protocols... tab. 81

82 And again click the Domino Web Engine tab. 82

83 And once more click the Edit Server button. 83

84 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. 84

85 Click the Save & Close button to save the last changes. 85

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

87 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:\IBM\WebSphere\AppServer\profiles\Dmgr01\config\cells\connectionsCell01\wim\ config. Now open the file wimconfig.xml in an editor. (use Notepad or Wordpad or any other installed editor) 87

88 Now find the section <config:realmconfiguration and in here the line starting with <config:uniqueuseridmapping 88

89 Change the two parameters uniquename to externalname. Then save and close the file. 89

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

91 Select both nodes and click the Full Resynchronize button. 91

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

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

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

95 Click the CellDefaultTrustStore link. 95

96 Now click the Signer certificates link. 96

97 Click the Retrieve from port button. 97

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

99 Confirm the retrieved data and click the Apply button. 99

100 Save the changes by clicking the Save link. 100

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

102 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 wasadmin -password passw0rd cd..\..\dmgr01\bin stopserver dmgr -username wasadmin -password passw0rd 102

103 And now start all servers using this commands: startserver dmgr cd..\..\appsrv01\bin startserver nodeagent startserver connections_server Switch to the Cognos Box startserver nodeagent startserver cognos_server Switch to the Connections Box 103

104 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: 104

105 Log in with a user name and password. 105

106 You are now successfully logged in to IBM Connections. 106

107 In the URL line enter the URL to the mail file of the user who is logged in. In this example we use: 107

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

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

110 Click File and then Preferences. 110

111 Click the Add Repository... button. 111

112 Click the Browse button. 112

113 Navigate to the directory C:\Install\ICM and select the repository.config file. Then click the Open button. 113

114 Confirm that the path is correct. Then click the OK button. 114

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

116 Click the Install entry. 116

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

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

119 Correct the path and click the Next button to continue. 119

120 Click the Next button to continue. 120

121 Click the Install button to continue. 121

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

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

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

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

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

127 Click the Common application. 127

128 Click the Security role to user/group mapping link. 128

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

130 Select the All Authenticated in Application's Realm option. 130

131 Click the OK button to continue. 131

132 Click Save to save the last changes. 132

133 Enabling the discovery service for IBM Connections Mail In the folder in which you installed Connections Mail ( C:\IBM\Connections Mail ), locate the socialmail-discovery-config-template.xml and the socialmail-discoveryconfig.xsd file. Copy both files to the following folder: C:\IBM\WebSphere\AppServer\profiles\Dmgr01\config\cells\connectionsCell01\Lotu sconnections-config. 133

134 Rename the copied socialmail-discovery-config-template.xml file to socialmaildiscovery-config.xml. 134

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

136 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. 136

137 In the Integrated Solutions Console click System Administration - Nodes. 137

138 Select the 2 nodes and click the Full Resynchronize button. 138

139 Synchronization was successful. 139

140 Open your browser and enter the URL to your Connections Server 140

141 Log in with a valid user name and password. 141

142 Now enter the URL: Use the address of the user who logged in. 142

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

144 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. 144

145 Enabling help for IBM Connections Mail Open a CMD line window and navigate to the directory C:\IBM\WebSphere\AppServer\profiles\Dmgr01\bin. Then enter the command wsadmin -lang jython -username wasadmin -password passw0rd. 145

146 Now enter the command execfile( connectionsconfig.py ). 146

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

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

149 Select the Help application and click the Stop button. 149

150 The application Help is now stopped successfully. 150

151 In the File explorer navigate to the directory C:\IBM\WebSphere\AppServer\profiles\AppSrv01\temp\connectionsNode01\connecti ons_server. Here delete the Help subdirectory. 151

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

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

154 The Help application has started successfully. 154

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

156 The Help window now shows the Mail and Calendar help. 156

157 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. 157

158 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. 158

159 In the File explorer navigate to the directory c:\install\ibm_connections_install_windowsns\tdisol. Right click the file tdicol.zip and seleect Extract All

160 Enter the destination directory C:\IBM\TDISOL and click the Extract button. 160

161 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:\IBM\TDI\V7.1. Then enter the command ibmditk.bat -s C:\IBM\TDISOL\TDI. 161

162 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. 162

163 One of the batch files has a path to the TDI directory hard coded to C:\Program Files\IBM\TDI\V7.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:\IBM\TDISOL\TDI. Then enter the command C:\Program Files\Windows NT\Accesories\wordpad.exe tdienv.bat. 163

164 Find the SET TDIPATH line and change the path to C:\IBM\TDI\V

165 Save and close the file. 165

166 The next step is to modify the properties file. Open your File Explorer and navigate to the C:\IBM\TDISOL\TDI directory and open the file profiles_tdi.properties. 166

167 Edit these fields with the right data: 167

168 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 [...] 168

169 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 169

170 Log In to IBM Connections with a valid user account. 170

171 Click Profiles and then My Profile. 171

172 Click the Edit My Profile button. 172

173 Click the Photo tab. 173

174 Click the Choose a file button. 174

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

176 Correct the display size and click the Save and Close button. 176

177 The user photo is now in the profile. 177

178 Go back to your CMD line window and be sure to be in the C:\IBM\TDISOL\TDI directory. Enter the command dump_photos_to_files.bat. Be sure to get the success records is 1 message. 178

179 Navigate to the directory where the dump script has saved the photo file C:\IBM\TDISOL\TDI\dump_photos and copy your Photo files into this directory. 179

180 In the C:\IBM\TDISOL\TDI directory open the file collect_photos.in for editing. 180

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

182 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. 182

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

184 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

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

186 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 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 Interim Feature Release 1 Sametime Advanced 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: 186

187 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: Note: After downloading the toolkit, the documentation can be found in the sdk/client/connectwebapi/doc/connectwebapidevguide.pdf directory. 187

188 Start the wsadmin client in a Administrator CMD-Line with the command: cd \IBM\WebSphere\AppServer\profiles\Dmgr01\bin wsadmin -lang jython -username wasadmin -password passw0rd 188

189 To access your configuration file enter the command: execfile( connectionsconfig.py ) 189

190 Check out the configuration file with the command: LCConfigService.checkOutConfig( c:\install, connectionscell01 ) 190

191 Open the file C:\Install\LotusConnections-config.xml with a text editor. 191

192 Then find the string sametimeproxy and configure your Proxy Server URL and ssl URL's. 192

193 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. 193

194 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. 194

195 Stop and restart all of the IBM Connections application servers. 195

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

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

198 Click the CellDefaultTrustStore link. 198

199 Now click the Signer certificates link. 199

200 Click the Retrieve from port button. 200

201 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. 201

202 Confirm the retrieved data and click the Apply button. 202

203 Save the changes by clicking the Save link. 203

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

205 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. 205

206 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. 206

207 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 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 expose enabled which needs to be set to true for the following integration points to work. 207

208 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. 208

209 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. 209

210 Complete this field with a URL in the following format: For example, in the example environment the URL: =sametime.guru@renovations.com when typed into a browser displays the photo associated with the account that has that address. 210

211 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> 211

212 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. 212

213 To verify the configuration: 1)Login to the Sametime web client (either using the Sametime Proxy server or the Sametime 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. 213

214 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: Log in to the Sametime System Console with administrator privileges. 214

215 Click Sametime System Console -> Sametime Servers -> Sametime Proxy Servers. 215

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

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

218 Click Connections Server and enter the server's address. The address for a Connections Profile server typically looks like this: 218

219 Click OK, and then click Apply. 219

220 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. 220

221 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. 221

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

223 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. 223

224 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 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: WP-Server-FP001.zip WP-WCM-Combined-CFPM84211-Server-CF05.zip 224

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

226 Open a CMD line window and navigate to the WebSphere Binaries directory with the command cd \IBM\WebSphere\AppServer\bin. Then run the command SetupCmdLine.bat. 226

227 Now navigate to the Connections UpdateInstaller directory with the command cd \IBM\Connections\UpdateInstaller. Then run the command UpdateWizard.bat. 227

228 Click the Next button to continue. 228

229 Change the Directory Path to C:\Install\Fixes. Then click the Next button to continue. 229

230 Click the Next button to continue. 230

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

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

233 Click the OK button to continue. 233

234 Click the Install button to start the installation. 234

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

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

237 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 selfsigned 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. 237

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

239 Click Security - SSL certificate and key management. 239

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

241 Now click the NodeDefaultTrustStore. 241

242 In the Additional Properties section click the Signer certificates link. 242

243 Click the button Retrieve from port. 243

244 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. 244

245 Click the OK button to continue. 245

246 To save the last changes click the Save link. 246

247 Updating the portlet theme About this task By design, the default themes for Portal 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. 247

248 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: Then install the client to your computer. 248

249 Start the WebDAV client. 249

250 Click File - Site Manager. 250

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

252 Enter a name for the connection we use Portal. In the Host field enter the url: Enter the WebSphere Portal Server Administrator user name and password. As Protocol select WebDAV. Enter a local directory and then click the Save button. 252

253 Click the OK button to continue. 253

254 Select the Portal Site and click the Connect button. 254

255 In the right window click the ibm.portal.80theme. 255

256 Click the profiles subdirectory. 256

257 Select the file profile_deferred.json and click the green copy button. 257

258 Click the OK button to continue. 258

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

260 Add this 2 lines in the moduleids section: wp_liveobject_framework, dijit_form_17, Then save the file and close the editor. 260

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

262 Click the Yes button to overwrite the file in the Portal server. Click the OK button to continue. 262

263 Close the AnyClient. 263

264 Restart your WebSphere Portal server. 264

265 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. 265

266 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: 266

267 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. 267

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

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

270 In the Authentication section click the LTPA link. 270

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

272 Click the Save link to save the last changes. 272

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

274 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. 274

275 Click the Save link to save the last changes. 275

276 Restart your WebSphere Portal server. 276

277 Open your browser and enter the URL to your Connections server 277

278 Log in with a Connections user 278

279 Now change the URL to your Portal server 279

280 You should be already logged in to the Portal server. 280

281 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. 281

282 In your File explorer navigate to the directory C:\IBM\WebSphere\wp_profile\ConfigEngine\properties. Then open the file wkplc.properties with your editor. 282

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

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

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

286 Wait until the command has completed successfully. 286

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

288 Wait until the command has completed successfully. 288

289 The last command to enter is: ConfigEngine configure-snportlets -DICversion=4.5 -DICblogsHomepageHandle=homepage -DIC Setting= -exposed -DICtagSearchType=mysearch -DICdsxAdminId=wasadmin -DICdsxAdminPwd=passw0rd -DICbaseURLunsecured= -DICbaseURL= 289

290 Wait until the command has completed successfully. 290

291 Restart your WebSphere Portal server. 291

292 Start your browser and access the Portal site with the URL 292

293 Click the Log In link. 293

294 Log in with a LDAP user name and password. 294

295 Click the IBM Connections link in the menu. 295

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

297 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. 297

298 In the CMD line window navigate to the ConfigEngine directory with the command cd \IBM\WebSphere\wp_profile\ConfigEngine. Then run the command ConfigEngine configure-connectionsbizcard -DICbaseURLunsecured= -DICbaseURL= -DURLProviderName="Default URL Provider". 298

299 Confirm that the command was running successfully. 299

300 Restart your WebSphere Portal server. 300

301 Start your browser and access the Portal site with the URL 301

302 Click the Log In link. 302

303 Log in with a LDAP user name and password. 303

304 Click the IBM Connections link in the menu. 304

305 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. 305

306 The IBM Connections Business Card of the user appears. 306

307 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. 307

308 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. 308

309 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. 309

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

311 In the top line click the Administration link. 311

312 Click the Manage Pages link in the Portal User Interface section. 312

313 Click the Content Root link. 313

314 Click the Home link 314

315 Click the IBM Connections link. 315

316 Click the New Page button to create a new page. 316

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

318 Now click the Home link in the top of the screen. 318

319 Click the IBM Connections link. 319

320 And now click the new Communities link. 320

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

322 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. 322

323 Click the Select a community button. 323

324 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. 324

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

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

327 Now click the Content tab. 327

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

329 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. 329

330 Add the next application or drag and drop it. 330

331 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. 331

332 Save the changes and switch back to the View Mode. 332

333 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 333

334 Click the Log In link. 334

335 Log in with a LDAP user name and password. 335

336 Click the IBM Connections link. 336

337 Now click the Communities link. 337

338 338

339 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. 339

340 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. 340

341 Deploying search integration prerequisites Open a CMD-line window and navigate to your ConfigEngine directory with the command cd \IBM\WebSphere\wp_profile\ConfigEngine. Then enter the command ConfigEngine.exe configure-snportletssearch -DICversion=

342 Confirm that the command run successfully. 342