Lotusphere IBM Collaboration Solutions Development Lab

Transcription

1 Lotusphere 2012 IBM Collaboration Solutions Development Lab Lab #6 Deliver Real-time Collaboration and Social Software by Integrating IBM WebSphere Portal with IBM Connections, IBM Sametime and inotes 1

2 Introduction: In this lab we have installed the following software: IBM WebSphere Portal IBM Connections IBM Sametime Lotus Domino All are installed and configured with Lotus Domino LDAP In this lab, you will learn how to: 1) integrate across the environment, Portal, Connections, Sametime and inotes Objective: In this lab, you will learn how to integrate the Lotus products. This lab is broken out into 13 Exercises. It's designed where you can pick and chose the exercise you want to focus on. If you are most interested in Blogs integration into Portal, complete exercise 5. If you want to know more about the new STProxy integration with Portal, go to exercise 12. Each exercise should take between min to complete and should give you a good idea of how to set it up back in your labs, and give you a quick overview of some of the features. Exercises 1 and 2 are detailed steps and hints and tricks for single sign on across the environment. In your test environment you would need to complete this before setting up integration. In our lab, however, you do not have to do these. SSO works, but I provided the steps for you to follow if you want to learn more about SSO. Exercise 3 is the 1 pre-req exercise in this lab. If you want to integrate portal with connections (detailed in exercise 4 9) then you need to complete the common steps exercise (3) prior to setting up and testing the portlets. Exercise 4, 5, 6, 7, 8 and 9 are the connections portlets. Complete step 3, then pick and chose the portlets you are most interested in. Exercise 10 details how to integrate the connections business card into portal, replacing the out of the box person card in portal with the rich content about users in Connections. Exercise 11 provides steps on integrating inotes with WebSphere Portal Exercise 12 details the new integration for Portal with STProxy. The new ajax based client for adding awareness and chat to your web based experience. Finally, exercise 13 explains how to integrate Connections with STProxy 2

3 Table of Contents Exercise 1: SSO Between Portal and Connections...4 Exercise 2: SSO between Portal and Domino...11 Exercise 3: Connections Portlets Common Steps...24 Exercise 4: Activities Portlet...32 Exercise 5: Blogs Portlet...38 Exercise 6: Bookmark portlet...43 Exercise 7: Profiles portlet...46 Exercise 8: Wikis Portlet...48 Exercise 9: Tags portlet...53 Exercise 10: Connections business card...58 Exercise 11: inotes portlet...62 Exercise 12: Portal STProxy integration...66 Exercise 13: Connections awareness and Chat with STProxy

4 Exercise 1: SSO Between Portal and Connections 1. Configure SSO across the environment. Many of the portlet we will use allow you to specify a name/password in the configuration and SSO is not a requirement, but typically setting up SSO is the preferred method of authentication between the different servers. In this lab we will configure SSO between Portal, Connections, Quickr and inotes. No matter the integration you decide to configure, make sure to set up SSO first. 1.1 Configure SSO between Portal and Connections You can configure the portlets where users enter their name and password to authenticate with the Connections server, but usually the experience is better if you configure Single Sign On, so we will walk through the steps of that now, and give you a few tips of things to watch for. We will export the sso key file from Portal and import it into Connections. 1.2 Export Key file from Portal Access the Portal was admin console ( - sign in as the admin (localadmin : password) Choose Security > Global Security Open Web and SIP security > Single sign-on (SSO) 4

5 4. Set the Domain name to the domain you will use to access portal and connections (ibm.com in our env) If you need both an LtpaToken and LtpaToken2 cookie generated, select Interoperability Mode. For the Connections and Sametime portlets, LtpaToken2 will work well, but you will need LtpaToken for the Quickr Domino portlets, so we will go ahead and select it now as well: Click OK and Save the changes Now, back on the Global Security, click LTPA 7. Click Key Set Groups 5

6 8. Make sure Automatically Generate Keys is set to false (In WAS 6.1 it will be set to true by default, in 7.0, it will be set to false by default 9. Click on LTPA 6

7 10. Here you can update the token timeout (we ll leave at the default of 120 minutes. Enter a password, (I used password) and a file location where to save the file (c:\portalltpa.txt ) and click Export keys. VERY IMPORTANT: NEVER click Generate keys. If you do, you would need to restart portal, then come back and click Export keys. 11. You should see the following message 12. Logout of the Integrated Solutions Console The key is now exported, for the domain name update, you would need to restart Portal for it to take effect. That is not necessary during this lab. Now we need to import the key file into Connections and test SSO. 1.3 Import the key file into IBM Connections 13. Access the Connections was admin console ( - sign in as the admin (localadmin : password) 7

8 14. Choose Security > Global Security 15. Open Web and SIP security > Single sign-on (SSO) 16. Set the Domain name to the domain you will use to access portal and connections (ibm.com in our env) If you need both an LtpaToken and LtpaToken2 cookie generated, select Interoperability Mode. For the Connections and Sametime portlets, LtpaToken2 will work well, but you will need LtpaToken for the Quickr Domino portlets, so we will go ahead and select it now as well: 17. Click OK and Save the changes 18. Now, back on the Global Security, click LTPA 19. Click Key Set Groups 8

9 20. Make sure Automatically Generate Keys is set to false (In WAS 6.1 it will be set to true by default, in 7.0, it will be set to false by default 21. Click on LTPA 22. Here you can update the token timeout to the same timeout we have set in Portal (120 minutes) Enter the password used when exporting the key from from Portal, (I used password) and the file location where you copied the file from the portal server onto the Connections server (c:\portalltpa.txt) and click Import keys. 23. And Save the new keys 9

10 24. Logout of the Integrated Solutions Console At this point you would need to restart Connections for the change to take effect, but that is not necessary during this lab. 1.4 Test Single Sign On between Portal and Connections 25. Open a browser to WebSphere Portal ( 26. Sign in as cprice : password 27. Once signed in, change the url to IBM Connections ( 28. You should be signed in as Charlie 29. Single Sign on is working between Portal and Connections. Summary: In this lab, you learned the basic steps to configure SSO between Portal and Connections 10

11 Exercise 2: SSO between Portal and Domino 2 Configure SSO across the environment. Many of the portlet we will use allow you to specify a name/password in the configuration and SSO is not a requirement, but typically setting up SSO is the preferred method of authentication between the different servers. In this lab we will configure SSO between Portal, Connections, Quickr and inotes. No matter the integration you decide to configure, make sure to set up SSO first. 2.1 Configure SSO between Portal and STProxy, ST Community and inotes We will export the sso key file from Portal and import it into Domino. 2.2 Export Key file from Portal Access the Portal was admin console ( - sign in as the admin (localadmin : password) Choose Security > Global Security Open Web and SIP security > Single sign-on (SSO) 11

12 4. Set the Domain name to the domain you will use to access portal and connections (ibm.com in our env) If you need both an LtpaToken and LtpaToken2 cookie generated, select Interoperability Mode. For the Connections and Sametime portlets, LtpaToken2 will work well, but you will need LtpaToken for the Quickr Domino portlets, so we will go ahead and select it now as well: Click OK and Save the changes Now, back on the Global Security, click LTPA 7. Click Key Set Groups 12

13 8. Make sure Automatically Generate Keys is set to false (In WAS 6.1 it will be set to true by default, in 7.0, it will be set to false by default 9. Click on LTPA 13

14 10. Here you can update the token timeout (we ll leave at the default of 120 minutes. Enter a password, (I used password) and a file location where to save the file (c:\portalltpa.txt ) and click Export keys. VERY IMPORTANT: NEVER click Generate keys. If you do, you would need to restart portal, then come back and click Export keys. 11. You should see the following message 12. Logout of the Integrated Solutions Console The key is now exported, for the domain name update, you would need to restart Portal for it to take effect. That is not necessary during this lab. Now we need to import the key file into Domino and test SSO. 2.3 Import the SSO token into Domino You will take the same token exported, then imported into Connections and import it into Domino for SSO to work to inotes, Sametime Community and STProxy. 14

15 13. Open the Notes Client 14. Click on File Open Lotus Notes Application 15. Under Look in: select the domino server (stcomm/ibm) select ibm s Directory and click Open 16. The sametime install creates an LtpaToken document created by the server id file. We need to remove this document and recreate a new one with the admin id so you can update and change the settings in the document. 15

16 17. Open Configuration - Web - Web Configurations and delete the Web SSO Configuration for LtpaToken document 18. Now we will recreate the document and import the token from Portal -- Open Configuration Servers All Server Documents 16

17 19. Click Web Create Web SSO Configuration 20. Leave Configuration Name: LtpaToken Organization should be blank DNS Domain is the domain of the url you use to access Domino, Portal and Connections (ibm.com) make sure to add the inotes and ST community server to the list of Domino Server names (stcomm/ibm) Update the Expiration (minutes): to the value used in Portal (120) 17

18 21. Click on Keys -- Import WebSphere LTPA Keys 22. type in the location of the exported key file from Portal (C:\portalltpa.txt) and click OK 23. Enter the password and click OK 24. You should see the following message 25. Under WebSphere Information select the button to change the Token Format: 18

19 26. Select LtpaToken and LtpaToken2 to use both tokens, the same as generated by WebSphere, and click OK 27. Save and close the document Now the key file has been imported into domino, you need to tell the inotes and ST community server to use this document for creating and decrypting LtpaTokens passed in from the browser. 28. Back in Configuration Servers All Server Documents, double click on the Domino server document (stcomm/ibm) 29. Go to Internet Protocols -- Domino Web Engine, Click Edit 19

20 30. Set Session authentication: Multiple Servers (SSO) Web SSO Configuration: LtpaToken 31. Save and Close the server document 32. Restart the http task for the change to take effect by entering the following commands on the domino console. 20

21 tell http quit load http 21

22 2.1 Test Single Sign On between Portal and ST Community 33. Open a browser to WebSphere Portal ( 34. Sign in as cprice : password 35. Once signed in, change the url to st community server ( 22

23 36. You should see your name at the top left corner 2.2 Test Single Sign On between Portal and STProxy 37. Open a browser to WebSphere Portal ( 38. Sign in as cprice : password 39. Once signed in, change the url to stproxy web client url ( 40. You should see youself logged into the stproxy web client 2.3 Test Single Sign On between Portal and inotes 41. Open a browser to WebSphere Portal ( 42. Sign in as cprice : password Once signed in, change the url to your mail file: ( You should see your mail file Summary: In this lab, you learned the basic steps to configure SSO between Portal and Domino 23

24 Exercise 3: Connections Portlets Common Steps 3 Common steps for all Connections Portlets 3.1 Install and add the Portlets to a page The portlets are available at the following url (on Greenhouse): action=editdocument&documentid=d5a8480b41c18f e300006b78 You will simply install the snor.pf.portlets.war file in the Web Module page in Portal Administration. We have already completed these steps for you to save time. Next you add the portlets to a page. Again, we have already created an added the portlets to 6 pages on our lab: They are set up under Applications > IBM Connections> Activities/Blogs/Bookmarks/Tag Cloud/Profiles/Wikis pages. All you have to do is configure the portlets to work with your Lotus Connections Installation (don t worry that is plenty for this lab time) 3.2 Add Connections SSL certificates into Portal trust store. The Connections portlets must communicate to Connections over SSL. Therefore, you need to add the public key used to encrypt html in Connections into the trust store used by WebSphere Portal. 3.3 Access and Import SSL key files into Portal Access the Portal was admin console ( - sign in as the admin (localadmin : password) Choose Security > SSL certificate and key management. 24

25 Choose Key stores and certificates under Related Items on the right hand side. Select NodeDefaultTrustStore. Choose Signer certificates, and click Retrieve from port. 25

26 6. Enter host: connections.ibm.com port: 443 Alias: lc ssl keys (this can be any value you want) and click Retrieve signer information 7. Click OK 26

27 8. Then click Save 9. At this point you would need to restart the Portal server for the certificates to be picked up, but that won t be necessary for our lab 10. Go ahead logout and close out of the WAS admin console. Now we have configured portal to connect to the Connections server over SSL. 3.4 Configuring portlets to use common directory services 11. Open C:\IBM\WPSWAS\wp_profile\installedApps\integrate\PA_WPF.ear\snor.pf.portlets.war\WEB- INF\lcaccelerator\waltz in windows explorer 12. Copy the 4 files (directory.services.xml, directory.services.xsd, sonata.services.xml and sonata.services.xsd) to C:\IBM\WPSWAS\wp_profile\config\cells\integrate (NOTE: overwrite the existing files) 13. Open directory.services.xml in notepad from C:\IBM\WPSWAS\wp_profile\config\cells\integrate 14. Update the following line: <property name="com.ibm.connections.directory.services.waltz.profiles.integration.service.url"> rofiles.ibm.com/profiles/</property> to <property name="com.ibm.connections.directory.services.waltz.profiles.integration.service.url"> onnections.ibm.com:9080/profiles/dsx/</property> 27

28 15. and update this line: <property name="com.ibm.connections.directory.services.waltz.communities.integration.service.url">htt ps://communities.ibm.com/communities/</property> to <property name="com.ibm.connections.directory.services.waltz.communities.integration.service.url">htt p://connections.ibm.com:9080/communities/dsx/</property> 16. and update this line: <property name="com.ibm.connections.directory.services.waltz.profiles.integration.service.auth">dsx- Admin</property> to <property name="com.ibm.connections.directory.services.waltz.profiles.integration.service.auth">none </property> 17. Save and close the file 18. Open the file to make sure no mistakes were made in IE, it s a bit easier to read the xml like this 19. At this point you would need to restart the Portal server for the config files to be read, but that is not necessary in our lab. 28

29 3.5 Configuring the Portal AJAX proxy to support authentication 20. New for 3.0.1: The Connections Portlets now use the Portal AJAX Proxy as the mechanism for forwarding security headers and cookies with each REST service call to authenticate the request with the Connections server. You can configure the AJAX Proxy to forward LTPA token as well as the appropriate headers for an environment behind a TAM or SiteMinder security proxy. The following instructions outline the steps to enable the default setting to forward the LTPA. 21. Open the following file from the directory where the Portal server is installed C:\IBM\WPSWAS\wp_profile\config\cells\integrate\applications\AJAX Proxy Configuration.ear\deployments\AJAX Proxy Configuration\wp.proxy.config.war\WEB-INF\proxyconfig.xml 22. Add a new policy to the proxy-config.xml file by adding the following lines. Note: We have already created a working proxy-config.xml called proxy-config.xml.working with the updated settings. Simply rename the proxy-config.xml to proxy-config.xml.old and proxy-config.xml.working to proxy-config.xml Where: CONNECTIONS_SERVER_BASE_URL is the base url for your connections server. For example: SOCKET_TIMEOUT_VALUE is the maximum wait time for open requests. We recommend setting this to MAX_PER_HOST is the maximum number of connections per host. We recommend setting this to

30 MAX_TOTAL_CONNECTIONS is the maximum number of connections allowed. We recommend setting this to Open up a DOS command line by going to Start>Run> and typing CMD. 24. Navigate to the Config Engine directory: C:\IBM\WPSWAS\wp_profile\ConfigEngine 25. Run the ConfigEngine task to set the new proxy configuration: (this has already been done for you in this lab) C:\IBM\WPSWAS\wp_profile\ConfigEngine> ConfigEngine.bat checkin-wp-proxy-config -DProxyConfigFileName= C:\IBM\WPSWAS\wp_profile\config\cells\integrate\applications\AJAX Proxy Configuration.ear\deployments\AJAX Proxy Configuration\wp.proxy.config.war\WEB-INF\proxyconfig.xml -DWasUserId=localadmin -DWasPassword=password 30

31 26. Restart the Portal Server. (This has already been done for you and no restart is needed) At this point the portlet wide settings are complete, and we can begin to configure the individual portlets. If there are specific ones you want to see, I would recommend skipping to those sections. Summary: In this lab, you learned the common steps necessary for integration between Portal and Connections used by all portlets. 31

32 Exercise 4: Activities Portlet 4 Configure the Activities portlet Let s walk through the 5 steps for the Activities portlet 4.1 Configure the Service URL Open a browser to Portal ( and sign in as the portal administrator localadmin : password Go to where we have the Activities portlet deployed (Applications Connections Activities) 3. In the Activities portlet title bar click, click the down arrow button and chose Configure 4. Set the: Service URL to Profile URL to Communities URL to and click OK 32

33 NOTE: This must be an SSL url to connections. 5. Now go ahead and logout as the localadmin user and login using one of our user accounts: cprice : password 6. Go to Applications -- Connections -- Activities At this point you should see the Activities portlets working. 4.2 Using the Activities Portlets Just like in the native IBM Connections UI, in the Activities portlet, you can add a to do, an entry, or a section to an existing Activity. You can create new Activites from here, as well as edit existing Activities. In this lab we will do three things in the Activities portlet: Create a new Activity Create a new Activity entry and a to do s Check off the to do s we have completed 33

34 Create a new Activity 1. Click on Start an Activity 2. Fill in the Title, Activity Goal, Tags, and the Due date for that Activity click Save. Under Members search for Greg and click the + to add him to the activity. 3. You have now created a new Activity that also resides on the Connections server. 34

35 Create a new Activity entry and a to do Let s now create a new Activity entry. Click on New Entry and create a Lab Environment Details entry. Fill out the Title, Content, and Tags sections and click Save 6. You can now see our new entry in the Activities Portlet Lets now create a to do entry. Click Add a to do item and provide the To Do, Assigned To, Due Date, Description, Tag and click Save 35

36 9. Create two to do s: Import the SSL certificates into Portal Download and Install the portlets That to do is now part of this activity: 36

37 Mark off our completed To Do s. 12. Click on the Activity we created earlier, Integrate Portal with Connections, Mail and Quickr 13. Check off the two to do s which we have already completed, that you entered earlier 14. Now you should be a bit more familiar with the functionality of the Activities portlet. Summary: In this lab, you learned the basic steps to configure and use the activities portlet. 37

38 Exercise 5: Blogs Portlet 5 Configure the Blogs Portlet Configuring the blogs Portlet takes just a few steps: Configure the Service URL End users add their name / password (with SSO configured this is not needed) 5.1 Configure the Service URL Open a browser to Portal ( and sign in as the portal administrator localadmin : password Go to where we have the Blogs Portlet deployed (Applications Connections Blogs) In the Blogs Portlet title bar click, click the down arrow button and chose Configure 4. Set the: Service URL: Profiles URL: Homepage Handle: home and click OK 38

39 NOTE: This must be an SSL url to connections NOTE: the homepage handle is the homepage we set on blogs as part of the post install configuration when installing and setting up Connections. This can be anything you want, it just needs to match the configuration on blogs. Now go ahead and logout as the localadmin user and login using one of our user accounts: cprice : password Go to Applications - Connections - Blogs At this point you should see the Blogs Portlet working 39

40 5.2 Using the Blogs Portlet In the blogs portlet you get a summary of the latest blog entries, you can look at specific blogs, and enter entries into an existing blog. In this lab we will enter an entry into a blog I created earlier. 5.3 Adding a new entry to an existing blog: Click on the My Blogs Drop Down Click on the Blog we created earlier (Practically Integrated) 10. Click on New Entry 40

41 11. Provide the title, tag and blog entry. Click Save. 41

42 12. Your entry is added to the blog Now you should be a bit more familiar with the Blogs Summary: In this lab, you learned the basic steps to configure and use the blogs portlet. 42

43 Exercise 6: Bookmark portlet 6 Configure the Bookmark Portlet Just as with the Activities and Blogs portlet, there are a few steps to configure the Bookmarks Portlet Configure the Service URL End users add their name / password (with SSO configured this is not needed) 6.1 Configure the Service URL Open a browser to Portal ( and sign in as the portal administrator localadmin : password Go to where we have the Bookmarks Portlet deployed (Applications Collaboration Connections Bookmarks) In the Bookmarks Summary portlet title bar click, click the down arrow button and chose Configure 4. Set the: Service URL to Profiles URL to and click OK 43

44 5. NOTE: This must be an SSL url to connections Now go ahead and logout as the localadmin user and login using one of our user accounts: cprice : password Go to Applications - Connections - Bookmarks At this point you should see the Bookmarks Portlet working 44

45 6.2 Using the Bookmarks Portlet Creating a bookmark from Portal Go to the Bookmark Portlet Click on My Bookmarks Click on Create Bookmark and provide the Title, Description, Link and Tags for your bookmark and click Save. (you can use any url you want) Click Save, and the bookmark is saved to the server as a public bookmark. Summary: In this lab, you learned the basic steps to do xyz. 45

46 Exercise 7: Profiles portlet 7 Configure the Profiles Portlet Open a browser to Portal ( and sign in as the portal administrator localadmin : password Go to where we have the Profiles Portlet deployed (Applications Collaboration IBM Connections Profiles) In the Profiles portlet title bar click, click the down arrow button and chose Configure 4. Set the: Profiles URL to and click OK NOTE: This must be an SSL url to connections Now go ahead and logout as the localadmin user and login using one of our user accounts: cprice : password Go to Applications - Connections - Profiles 46

47 You should now see the Profiles Portlet now working Summary: In this lab, you learned the basic steps to configure and use the profiles portlet. 47

48 Exercise 8: Wikis Portlet 8 Configure the Wikis Portlet Open a browser to Portal ( and sign in as the portal administrator localadmin : password Go to where we have the Wikis Portlet deployed (Applications Connections Wikis) In the My Wikis portlet title bar click, click the down arrow button and chose Configure 4. Set the: Profiles URL to Wikis URL to: 48

49 And click OK NOTE: This must be an SSL url to connections Now go ahead and logout as the localadmin user and login using one of our user accounts: cprice : password Go to Applications - Connections - Wikis You should now see the portlet working: 49

50 8.1 Using the Wikis Portlet Creating a wiki entry from Portal 8. Go to the Wikis portlet, click on the wiki I created earlier 9. This will take you to the welcome page, you can click drop down next to Welcome to see more pages in the wiki: 10. Let's create a new page in the wiki 50

51 11. Click Page Actions - Create Peer 12. Fill out the title and description 51

52 13. Click Save and you will be taken to the new page created in your wiki: Summary: In this lab, you learned the basic steps to configure and use the wikis portlet. 52

53 Exercise 9: Tags portlet 9 Configure Tags and Wiring Now that we have configured all of our Portlets, let s configure the Tags Portlet wiring with the some of the portlets. As an overview, there are two modes of operation with regards to the interaction between the tag cloud and the other Connections portlets: one-way and two-way communication mode. In one-way communication mode, the tag cloud portlet sends a wire to the other Connections portlets to update their view according to a selected tag (this is what we will be setting up in this lab) In two-way communication mode, the other Connections portlets can also send a wire to the tag cloud portlet to update its view as well according to the view being displayed Open a browser to Portal ( and sign in as the portal administrator localadmin : passw0rd Go to where we have the Tag Cloud Portlet is deployed (Applications Connections Tag Cloud) Click on the configure drop down on the portlet and set the following URL s (as seen in the screenshot) 53

54 6. Note: This must be an SSL url to Connections 7. At this point the portlet would show tags from the connections server for a user in connections. Now we need to wire the tags portlet with the other connections portlets on the page. Follow these steps to add wires so the portlets can exchange data. 8. Go to Administration>Manage Pages>Content Root>Applications>Connections 54

55 9. Click on Edit Page Layout (pencil icon) for the Tag Cloud page: 10. Click on the Wires tab: 11. Go to Edit Page Layout and setup the wiring with the following settings: Source Portlet tags Target Page Tags Cloud Target Portlet Profiles Receiving selected Tag Wire type - public 12. Click the + and you are now done with setting up the wiring between tags and profiles portlets., repeat step 11 for bookmarks and blogs 13. Click Done once complete 14. Now, you might be asking what does the wiring do? 55

56 15. Now go ahead and logout as the localadmin user and login using one of our user accounts: cprice : password 16. Go to the Tags Page 1. Click on the tag connections as an example you will notice if will bring up any profile, blog or bookmark that has been tagged connections. In this case its Charlie Greg s and Karen's profile, along with a bookmark. As you can see, no blogs currently are tagged connections. 56

57 Summary: In this lab, you learned the basic steps for configuring the Tags portlet and wiring it to other connections portlets on the same page. 57

58 Exercise 10: Connections business card 10 Configure Connections Business Card integration 10.1 Ensure that ibm-primary is mapped to the mail attribute open C:\IBM\WPSWAS\wp_profile\ConfigEngine\properties\wkplc.properties Search for federated.ldap.attributes.mapping.ldapname and set it to federated.ldap.attributes.mapping.ldapname=mail Just below this, set federated.ldap.attributes.mapping.portalname=ibm-primary Save and close the file Open a command prompt change dir to C:\IBM\WPSWAS\wp_profile\ConfigEngine Run ConfigEngine.bat wp-update-federated-ldap-attribute-config 8. This should build successfully: 58

59 10.2 Create the business card url provider 9. Access the Portal was admin console ( - sign in as the admin (localadmin : password) 10. Choose Resources URL URL providers 11. Select Default URL Provider at the Node level 12. Under Additional Properties, select URLs 13. Click New 59

60 14. Enter. Name: CONNECTIONS_PEOPLE_CARD JNDI name: CONNECTIONS_PEOPLE_CARD Specification: Category: CATEGORY_CONNECTIONS_PEOPLE_CARD 15. Click Ok and Save the changes 16. Log out of the Integrated Solutions Console 17. At this point you would need to restart the Portal server and delete all temp internet files on the client for the change to take effect, but that will not be necessary in our lab. 18. Open a browser, and sign into portal as our test user (charlie : password) 19. Go to the bookmarks portlet 60

61 20. Hover over a name and click Click here to view business card Summary: In this lab, you learned the basic steps to configure the connections business card in Portal. 61

62 Exercise 11: inotes portlet 11 Configure Portal Integration with inotes mail Out of the box we have the DWA portlet, which you can configure to auto-detect your mail file and display specific components that you want your end users to see in portal. This method uses ldap calls to the domino ldap to determine the users mailserver and mail file. This approach involves updating a properties file on portal (csenvironment.properties) and setting the internet hostname in the server document on the domino ldap directory. These options require you to restart the portal server and ldap service, which takes longer than I want to spend on this topic. If you want to use this approach, let me know and I can walk you through the steps on the test system. Another option to autodetect the mail file is to use the redirect database. In the next section we will cover the redirect database Configuring the inotes portlet to use the inotes redirect database Open a browser to Portal ( and sign in as the portal administrator localadmin : password Go to Administration Portlets 62

63 3. Search for domino, and click the Configure icon next to Domino Web Access portlet 4. Click on the Edit Value icon for the DWARedirectDB parameter 5. and set it to (the full url to the redirect database) and click OK 6. Back in Manage portlets click OK Now configure the portlet to use the redirect database parameter instead of the default of autodetect using ldap searches. 63

64 7. As the admin, click on Applications Messaging Mail 8. Click on the Display Menu link at the top right of the inotes portlet, and select Edit Shared Settings 9. Set height to 600, and select Let the DWA Redirector find my mail database then click Save 10. You will see the login screen because the portal admin in our lab does not have a mail file: 11. Log out of portal, and log back in as a test user: cprice : password 64

65 12. click on Applications Messaging Mail 13. You should now see Charlie s mail file: Summary: In this lab, you learned the basic steps to configure the inotes portlet with the redirect database. 65

66 Exercise 12: Portal STProxy integration 12 Configure Portal Awareness and Chat with STProxy 12.1How it works When configuring Awareness and Chat with an STProxy server, you need the following 3 servers: Portal IBM HTTP Server (optional) STProxy ST Community server or higher In our lab we also configure an IBM HTTP server in front of Portal. Once everything is configured, the flow of traffic from the browser to Portal and STProxy will all go through a single URL. The reason for this to prevent cross side scripting errors not allowed by the browser when running the javascript and ajax calls. The POST and CONNECT calls made by the STProxy api to log the user in and get status updates are not allowed by the browser to go to a different url than the one you are currently accessing. In our case this URL is the HTTP server in front of the Portal server, so later in the lab we will configure the IBM HTTP Server to proxy requests for STProxy. If you do not have an HTTP server you can configure the AJAXProxy server in Portal to proxy these requests. The main thing is whatever you use to access Portal (IHS, Edge caching proxy, Tivoli Access Manager, Portal direct, etc.) must be configured to proxy the requests to the STProxy server as well, as shown in the diagram below: 66

67 IBM HTTP Server WebSphere Portal Sametime Proxy Server Sametime Community Server LDAP Directory You can also allow the browser direct access to the STProxy server (as shown in the dotted line above) but it s not necessary for the portlet to work. 67

68 12.2Install STProxy hotfix for portal integration There are a number of steps you need to take before integrating Portal and STProxy 1. Portal must be on version STProxy must be on version an STProxy hotfix must be applied to the system. This hotfix is a new ear that you need to update in WebSphere Application Server, and new jar files that are copied into the STProxy deployed app. For this lab we have done this and synced it with the node, so we will skip these steps. Details of this can be found here: To save time, each of these steps has been completed in the lab, you can move the install and config piece of the STProxy integration: 12.3Install the Sametime Proxy Server upgrade Now that we have the correct versions, hotfixes and fixed the portal theme, we are ready to install the new upgraded functionality of using STProxy for awareness and chat. First you need to download the IBM Lotus Sametime Proxy Server upgrade for WebSphere Portal 7, which you can find here: action=editdocument&documentid=250f9656bec11b2d And run a few ConfigEngine batch files to install the new portlet into your portal server. I have downloaded the update zip file from the portlet catalog, and unzipped it to c:\stproxy. Now let s run the commands to install the portlet. NOTE: The 2 commands we will run are saved for you, so you can copy and paste them into the command prompt 1. open a command prompt and change directory to C:\IBMWPS\WebSphere\wp_profile\ConfigEngine 68

69 2. run the following command (you can copy this command out of the stproxycommands.txt file on the desktop) ConfigEngine.bat -install -installpackage C:/stproxy/SametimeProxyServerUpgrade.zip -offeringroot./config/work -installpath C:/IBMWPS/WebSphere/PortalServer -expandbinaries true 3. Once this completes, run the next command in stproxycommands.txt ConfigEngine.bat deploy-apps -DconfigExtensionList=-applySametimeProxyServerUpgrade 4. These commands update the portal theme to work with stproxy and install the new Sametime Web 2.0 contacts portlet. We will look at this once all the configuration is complete 12.4Configure SSO between Portal and Sametime. For awareness and chat to work in Portal, you must configure SSO between Portal and the Community 69

70 server. It s not necessary to configure SSO on the WAS based STProxy server, as that server does not actually authenticate the user, instead it will forward the credentials passed in to the community server to authenticate and login the user. This can take 15 minutes todo, so there is another part of the lab where you can do this part if you want, in this lab you can skip it. 12.5Fix theme to show business card in portlet in Windows exploerer go to the following folder: C:/IBMWPS/WebSphere/PortalServer/theme/wp.mashup.cc.theme/installedApps/wp.mashup.cc.t heme.ear/pagebuilder2.war/themes/html/pagebuilder2 Double click on config.jsp to open it in wordpad (to quickly make the changes below, simply delete config.jsp and rename config.jsp.working to config.jsp Search for var stproxyconfig under plugins remove the following 2 lines: lnmpaddcontact : false lnmpaddsubgroup : false Once done, the lines will look like the following: var stproxyconfig = { server: "${sametimeproxyurl}", isconnectclient: false, disablexdomain: true, isportalajaxproxy: ${isportalajaxproxy}, plugins: { lnmpchat : false, lnmpcall : false, lnmpmeetinginvite : false, lnmpsendannouncement : false, lnmpbizcard : false, lnmpaddtocontacts : false, lnmpaddtocontacts : false, } } 70

71 12.6Configure WAS setting (cc.sametime.proxy.url) for browser to communicate with STProxy server 9. Open a browser to the WAS admin console for Portal: ( and login (localadmin : password) 10. Click Resources -> Resource Environment -> Resource Environment Providers. 11. In the list, locate the WP CommonComponentConfigService and open this entry by clicking it. (it will be on the 2 nd page) 12. Click Custom properties. 71

72 13. Click New and enter the following settings: Name: cc.sametime.proxy.url Value: /stproxy NOTE: the value can be anything you want, it just needs to start with a slash. The value used here is used as the context root when configuring the IHS server to proxy requests for STProxy. 14. Click OK 15. Click Save 16. log out of the Integrated Solution Console Normally you would need to restart Portal for the change to take effect, but that is not necessary in our lab. 12.7Configure Portal HTTP server to communicate with STProxy server Now that the Portal server is configured with the proxy rule for communication with STProxy, we need to configure the HTTP Server to communicate with the STProxy server. NOTE: If you want to skip these steps, you can simply delete httpd.conf and rename httpd.conf.working to httpd.conf in C:\IBMWPS\HTTPServer\conf, then restart the HTTP server service. 17. Open C:\IBMWPS\HTTPServer\conf\httpd.conf 72

73 18. Search for proxy and uncomment the following 2 lines: LoadModule proxy_module modules/mod_proxy.so LoadModule proxy_http_module modules/mod_proxy_http.so 19. At the bottom of the file, just above: LoadModule was_ap22_module "C:\IBMWPS\HTTPServer\Plugins\bin\mod_was_ap22_http.dll" WebSpherePluginConfig "C:\IBMWPS\WebSphere\wp_profile\config\cells\wpsst\nodes\wpsst\servers\webserver1\plugi n-cfg.xml" Add the following lines: (NOTE: you can copy and paste these lines out of stproxycommands.txt on the desktop <IfModule mod_proxy.c> ProxyPass /stproxy connectiontimeout=2 ProxyPassReverse /stproxy ProxyPassReverseCookieDomain ibm.com ProxyPassReverseCookiePath / /stproxy </IfModule> 20. Notice the ProxyPass /stproxy and ProxyPassReverseCookiePath / /stproxy If you used something else for the context root in the cc.sametime.proxy.url WAS variable, you would enter that here. 21. Save and close the file 22. Restart IBM HTTP Server for the change to take effect a. Open the services link b. Scroll down to IBM HTTP Server 7.0, right click and chose Restart 73

74 c. Once the Server is restarted it is ready to proxy the requests to the STProxy server 12.8Change JSESSIONID cookie name in STProxy server This is the most missed step in configuring Portal with STProxy, so after today if any of you guys call into support and haven t completed this step... I m going to be very upset. Because we use the same url to access STProxy as we do to Portal, we need to configure a different session id on the STProxy server, so the jsessionid cookies don t get overwritten by each server. 23. Open a browser to the WAS admin console for STProxy ( and login as the administrator (localadmin : password) 24. Expand Servers in the navigation pane, and then select Server Types -> WebSphere application servers. 25. Click on STProxyServer 26. Expand Web Container Settings under Container Settings, and then select Web container. 74

75 27. Click Session management. 28. Click on Enable cookies. 75

76 29. Change the Cookie name field to STJSESSIONID. 30. Click OK, click Save, and then logout of the Integrated Solutions Console. At this step, you would need to restart the STProxy server for the change to take effect, but it s not necessary in our lab. 12.9Test the new portlet. That s it, now we are ready to test the new portlet 31. Open a browser to portal ( and login as our test user (cprice : password) 32. Go to Applications STProxy 76

77 33. The updated contact list should appear 34. Let s add a user to the buddy list 35. Under Type to find name, enter Greg, and click Search directory for Greg 36. Hover over Charlie Price and click Click for Person Card 77

78 37. Select More Actions and Add to Contacts 38. On the new window that appears click Add 78

79 39. You should see the user added to the portlet 40. Now, let s start a chat window just so you can see some of the new features of chat in STProxy 41. Double click on the green icon next to Greg s name 79

80 42. Notice you have a few rich text options, not as many as the full connect client, but much more than what was available in stlinks Summary: In this lab, you learned the basic steps to configure portal chat and awareness with STProxy. 80

81 Exercise 13: Connections awareness and Chat with STProxy 13 Configure Connections Awareness and Chat with STProxy 13.1How it works When configuring Awareness and Chat with an STProxy server, you need the following 3 servers: Connections IBM HTTP Server STProxy ST Community server or higher STProxy hotfix WHOS-8MAJ6R In our lab we also configure an IBM HTTP server in front of Connections. Once everything is configured, the flow of traffic from the browser to Connections and STProxy will all go through a single URL. The reason for this to prevent cross side scripting errors not allowed by the browser when running the javascript and ajax calls. The POST and CONNECT calls made by the STProxy api to log the user in and get status updates are not allowed by the browser to go to a different url than the one you are currently accessing. In our case this URL is the HTTP server in front of the Connections server, so later in the lab we will configure the IBM HTTP Server to proxy requests for STProxy. If you do not have an HTTP server you can configure the AJAXProxy server in Connections to proxy these requests. The main thing is whatever you use to access Connections (IHS, Edge caching proxy, Tivoli Access Manager, Connections direct, etc.) must be configured to proxy the requests to the STProxy server as well, as shown in the diagram below: 81

82 IBM HTTP Server WebSphere Portal Sametime Proxy Server Sametime Community Server LDAP Directory You can also allow the browser direct access to the STProxy server (as shown in the dotted line above) but it s not necessary for the portlet to work. 82

83 13.2Install STProxy hotfix for Connections integration There are a number of steps you need to take before integrating Connections and STProxy 1. Connections must be on version STProxy must be on version an STProxy hotfix (WHOS-8MAJ6R) must be applied to the system. This hotfix is a new ear that you need to update in WebSphere Application Server, and new jar files that are copied into the STProxy deployed app. For this lab we have done this and synced it with the node, so we will skip these steps. To save time, each of these steps has been completed in the lab, you can move the install and config piece of the STProxy integration: 13.3Configure SSO between Connections and Sametime. For awareness and chat to work in Connections, you must configure SSO between Connections and the Community server. It s not necessary to configure SSO on the WAS based STProxy server, as that server does not actually authenticate the user, instead it will forward the credentials passed in to the community server to authenticate and login the user. This can take 15 minutes todo, so there is another part of the lab where you can do this part if you want, in this lab you can skip it. 13.4Configure Connections HTTP server to communicate with STProxy server Now that the Connections server is configured with the proxy rule for communication with STProxy, we need to configure the HTTP Server to communicate with the STProxy server. NOTE: If you want to skip these steps, you can simply delete httpd.conf and rename httpd.conf.working to httpd.conf in C:\IBMWPS\HTTPServer\conf, then restart the HTTP server service Open C:\IBM\HTTPServer\conf\httpd.conf Search for proxy and uncomment the following 2 lines: LoadModule proxy_module modules/mod_proxy.so LoadModule proxy_http_module modules/mod_proxy_http.so 83

84 3. At the bottom of the file, just above: LoadModule was_ap22_module "C:\IBMWPS\HTTPServer\Plugins\bin\mod_was_ap22_http.dll" WebSpherePluginConfig "C:\IBMWPS\WebSphere\wp_profile\config\cells\wpsst\nodes\wpsst\servers\webserver1\plugi n-cfg.xml" Add the following lines: (NOTE: you can copy and paste these lines out of IC_stproxycommands.txt on the desktop <IfModule mod_proxy.c> ProxyPass /stwebclient ProxyPass /stwebapi ProxyPass /stbaseapihttp://stproxy.ibm.com:9083/stbaseapi ProxyPassReverse /stwebclient ProxyPassReverse /stwebapi ProxyPassReverse /stbaseapi ProxyPassReverseCookieDomain ibm.com ProxyPassReverseCookiePath / / </IfModule> Save and close the file Restart IBM HTTP Server for the change to take effect a. Open the services link b. Scroll down to IBM HTTP Server 7.0, right click and chose Restart c. Once the Server is restarted it is ready to proxy the requests to the STProxy server 84

85 13.5Update Connections config file to enable STProxy Open a command prompt to the Connections DMGR directory (c:\ibmlc\websphere\appserver\profiles\dmgr01\bin) Run the following command: wsadmin -lang jython -user localadmin -password password -port At the wsadmin prompt run the following commands: execfile("connectionsconfig.py") LCConfigService.checkOutUIextensionsConfig("c:/temp","vm64Cell01") 9. Leave the wsadmin prompt and window open 85

86 10. Open uiextensions-config.xml file from the temp directory in notepad, scroll down near the bottom of the file and look for the following lines: NOTE: instead of editing the file manually, you can simply delete c:\temp\uiextensionsconfig.xml and rename c:\temp\uiextensions-config.xml_working to uiextensions-config.xml <extension name="global.pagerendering" jscallback="lconn.profiles.sametime.sametimeproxyinit" enabled="false"/> <extension name="lc.imawareness" jscallback="lconn.profiles.sametime.sametimeproxyaddlivename" invokedelay="2000" enabled="false" id="stproxy"> <params> <param name="isconnectclient" value="true" /> <param name="lconnproxysvcurl" value="admin_replace"/> <param name="lconnproxysvcurlssl" value="admin_replace"/> </params> </extension> update this section by setting enabled="true" and setting the lconnproxysvcurl to the hostname of the HTTP Server used to access Connectoins: <extension name="global.pagerendering" jscallback="lconn.profiles.sametime.sametimeproxyinit" enabled="true"/> <extension name="lc.imawareness" jscallback="lconn.profiles.sametime.sametimeproxyaddlivename" invokedelay="2000" enabled="true" id="stproxy"> <params> <param name="isconnectclient" value="true" /> <param name="lconnproxysvcurl" value=" <param name="lconnproxysvcurlssl" value=" </params> </extension> 11. Save and close uiextensions-config.xml 86

87 12. Back in the wsadmin command window, enter the following command: LCConfigService.checkInUIextensionsConfig("c:/temp","vm64Cell01") 13. Type exit to exit out of the wsadmin console At this step, you would need to restart the Connections server for the change to take effect, but it s not necessary in our lab. 13.6Test awareness and chat. That s it, now we are ready to test awareness 14. Open a browser to Connections ( and login as our test user (cprice : password) 15. At the bottom right corner of the browser, you should see where you are logged into sametime 16. If you search the directory for Charlie 87

88 17. Hover over the name, and click to show the business card 18. You will also see that you can see the users status in the business card, and have the ability to chat from here as well: Summary: In this lab, you learned the basic steps to chat and awareness in Connections using STProxy. 88