Configure portlets to use common directory services
Configuring the IBM Connections portlets to use common directory services enables directory lookup from IBM Connections in the IBM WebSphere Portal environment.
- Review: Use the Profiles database as the user directory.
- Stop WebSphere Portal Server.
For a clustered deployment, stop all Portal servers.
- On the server hosting IBM Connections, open the LotusConnections-config.xml file for editing. This file is located in...
{install.root}/config/cells/{local.cell}/LotusConnections-Config
- Make sure the Profiles database is set up to be the user directory for IBM Connections by looking for the following setting:
- Locate the <serviceReference> elements with the serviceName="communities" and serviceName="profiles" attributes and take note of the values of the <interService> and <hrefPathPrefix> elements.
<sloc:serviceReference serviceName="profiles" <sloc:hrefPathPrefix>/profiles</sloc:hrefPathPrefix> <sloc:interService href="https://enterprise.example.com:9080"/> </sloc:serviceReference> <sloc:serviceReference serviceName="communities" <sloc:hrefPathPrefix>/communities</sloc:hrefPathPrefix> <sloc:interService href="https://enterprise.example.com:9081"/> </sloc:serviceReference>- Do the following to copy the configuration files:
- For a single server: On the IBM WebSphere Portal server, copy the following files:
- directory.services.xml
- directory.services.xsd
- sonata.services.xml
- sonata.services.xsd
- From the Connections Portlet deployment directory,
$WP_PROFILE/installedApps/cell/PA_WPF.ear/snor.pf.portlets.war/WEB-INF/lcaccelerator/waltz
...to...
$WP_PROFILE/config/cells/cell/
- For a clustered deployment: On the primary IBM WebSphere Portal server, copy directory.services.xml and directory.services.xsd from the Connections Portlet deployment directory,
$WP_PROFILE/installedApps/cell/PA_WPF.ear/snor.pf.portlets.war/WEB-INF/lcaccelerator/waltz
...to the DMGR directory
DMGR_profile/config/cells/cell/
- Edit directory.services.xml to remove the comment characters from the following section:
<property name="com.ibm.connections.directory.services.waltz.communities.integration.service.auth">DSX-Admin</property>
<!-- *** This setting will 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">https://profiles.ibm.com/profiles/</property>
<property name="com.ibm.connections.directory.services.waltz.profiles.integration.service.auth">DSX-Admin</property>
<property name="com.ibm.connections.directory.services.waltz.profiles.integration.service.auth.alias">connectionsAdmin</property>
-->
<!-- *** WCI can only be used when Waltz is running on SSO enabled environment ***
<property name="com.ibm.connections.directory.services.waltz.communities.integration.service.enabled">true</property>
<property name="com.ibm.connections.directory.services.waltz.communities.integration.service.url">https://communities.ibm.com/communities/</property>
<property name="com.ibm.connections.directory.services.waltz.communities.integration.service.auth">DSX-Admin</property>
<property name="com.ibm.connections.directory.services.waltz.communities.integration.service.auth.alias">connectionsAdmin</property>
-->
<!-- *** User these custom id settings below with VMM/Waltz provider only, when you like to set up different id attribute type per object class ***
<property name="com.ibm.connections.directory.services.waltz.custom.user.id.attribute.type">customUserID</property>
<property name="com.ibm.connections.directory.services.waltz.custom.group.id.attribute.type">customGroupID</property>
-->
- Edit directory.services.xml and set:
Option
Property from LotusConnections-config com.ibm.connections.directory.services.waltz.profiles.integration.service.url
[interService href] + [hrefPathPrefix] + /dsx/ com.ibm.connections.directory.services.waltz.profiles.integration.service.enabled
true com.ibm.connections.directory.services.waltz.profiles.integration.service.auth
None com.ibm.connections.directory.services.waltz.profiles.integration.service.auth.alias
profiles_directory_service_extension_auth_alias com.ibm.connections.directory.services.waltz.communities.integration.service.url
[interService href] + [hrefPathPrefix] + /dsx/ com.ibm.connections.directory.services.waltz.communities.integration.service.auth
DSX-Admin com.ibm.connections.directory.services.waltz.communities.integration.service.enabled
true com.ibm.connections.directory.services.waltz.communities.integration.service.auth.alias
ccommunities_directory_service_extension_auth_alias
For example, here is a sample code block from directory.services.xml after setting the parameters:
<config version="3.0" id="directory.services" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="directory.services.xsd"> <profileProvider class="com.ibm.connections.directory.services.provider.WaltzServiceProvider/dsx1/"> <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">https://profiles.ibm.com/profiles/dsx/</property> <property name="com.ibm.connections.directory.services.waltz.profiles.integration.service.auth">None</property> <property name="com.ibm.connections.directory.services.waltz.profiles.integration.service.auth.alias">connectionsAdmin</property> <property name="com.ibm.connections.directory.services.waltz.communities.integration.service.enabled">true</property> <property name="com.ibm.connections.directory.services.waltz.communities.integration.service.url">https://communities.ibm.com/communities/dsx/</property> <property name="com.ibm.connections.directory.services.waltz.communities.integration.service.auth">DSX-Admin</property> <property name="com.ibm.connections.directory.services.waltz.communities.integration.service.auth.alias">connectionsAdmin</property> <profileProvider/> </config>
- (Clustered deployment only) Login to DMGR admin console and navigate to the System Administration - Nodes. Select both WebSphere Portal nodes and click Full Resynchronize.
- Restart the Portal server after updating directory.services.xml or restart all of the servers for a clustered deployment.
Parent topic
IBM Connections Portlets for WebSphere Portal
Related tasks
Use the Profiles database as the user directory