Home

 

Configure portlets to use Common Directory Services

Overview

Configure the IBM Lotus Connections portlets to use the Common Directory Services to enable lookup from Lotus Connections in the IBM WebSphere Portal environment.

Configure Common Directory Services for the Lotus Connections portlets

1. Stop WebSphere Portal Server.

2. On the server hosting Lotus Connections, edit...
   install_root/config/cells/{local.cell}/LotusConnections-Config/LotusConnections-config.xml

   ..locate the entry...

   :serviceReference serviceName="directory"

   ..and take note of the URLs for the profiles and communities integration settings.

   <sloc:serviceReference  
        communities.directory.service.extension.auth="DSX-Admin" 
        communities.directory.service.extension.auth.alias="connectionsAdmin" 
        communities.directory.service.extension.enabled="true"
        communities.directory.service.extension.href="http://server1.connections.example.com:9085/communities/dsx/"
        profiles.directory.service.extension.auth="None"
        profiles.directory.service.extension.auth.alias="connectionsAdmin"
        profiles.directory.service.extension.enabled="true"
        profiles.directory.service.extension.href="http://server1.connections.example.com:9088/profiles/dsx/"
        serviceName="directory"/>
   

3. On the IBM WebSphere Portal server, copy...
   • services.xml
   • services.xsd

   ..from the Connections Portlet deployment directory...

   PORTAL_HOME\wp_profile\installedApps\[cell]\PA_WPF.ear\snor.pf.portlets.war\WEB-INF\lcaccelerator\waltz ...

   ..to...

   PORTAL_HOME\wp_profile\config\cells\[cell]\

4. Edit services.xml and set:

   Option	Property from LotusConnections-config
   com.ibm.connections.directory.services.waltz.profiles.integration.service.url	profiles.directory.service.extension.href
   com.ibm.connections.directory.services.waltz.profiles.integration.service.auth	profiles.directory.service.extension.auth
   com.ibm.connections.directory.services.waltz.communities.integration.service.url	communities.directory.service.extension.href
   com.ibm.connections.directory.services.waltz.communities.integration.service.auth	communities.directory.service.extension.auth

5. Restart the Portal server after updatingservices.xml

   For example, here is a sample code block from services.xml after setting the parameters:

   <profileProvider class="com.ibm.connections.directory.services.provider.WaltzServiceProvider" >
       <!-- 
       *** Turn off the usage of LDAP group membership globally *** 
       <property name="com.ibm.connections.directory.services.ldap.group.membership.service.enabled">
           false
       </property>
       -->
   
       <!-- 
       *** WPI can only be used when Profiles services is available *** 
       -->
       <property name="com.ibm.connections.directory.services.waltz.profiles.integration.service.enabled">
           true
       </property>
   
       <property name="com.ibm.connections.directory.services.waltz.profiles.integration.service.url"> 
           http://HOSANNA.notesdev.ibm.com:9080/profiles/dsx/
       </property>
   
       <property name="com.ibm.connections.directory.services.waltz.profiles.integration.service.auth">
           SSO-Admin
       </property>
   

IBM Lotus Connections 2.5 Portlets for WebSphere Portal

---

+

Search Tips   |   Advanced Search