Configuring a Resource Environment Provider for IBM Connections portletsAdded by IBM | Edited by IBM on December 14, 2012 | Version 4 (Show original)
|You must add IBM® Connections server URLs to the WebSphere® Resource Environment provider before you can add an IBM Connections repository to the Virtual Member Manager.
Before you begin
Copy the com.ibm.ws.wim.adapter.connections.filter.jar file to the \\Portalserver\shared\app
Ensure you have followed the previous steps in Deploying libraries for the IBM Connections portlets
before performing this configuration or your server may fail to start after setting these parameters.
About this task
Add any allowed IBM
Connections server URLs. For example, if the server allows http and https URLs, you must add both.
- Log into the WebSphere Application Server Integrated Solutions Console.
- Navigate to Resources -> Resource Environment -> Resource Environment Providers.
- Select Server or Cluster as the scope, depending on whether you are deploying on a single server or on a cluster.
- If the WP ConnectionsIntegrationService already exists, click on it. If not, click New, specify WP ConnectionsIntegrationService, and click Apply.
- Click Custom Properties.
- Click New and configure the following attributes:
Name, description, and type of environment variables
|personCorrelationAttribute (formerly personRdnAttribute)||Specify the corresponding person relative distinguished name attribute. For example, ibm-primaryEmail.||java.lang.String|
|personCorrelationAttributeType||Assign a value of mail or uniqueId to specify whether the correlation attribute represents an email address or unique identifier. ||java.lang.String|
|communityRdnAttribute||Specify the corresponding communitiy relative distinguished name attribute. For example, cn.||java.lang.String|
|maxSearchResults||A maximum of results the connections repository will return on a single query. For example, 120.||java.lang.String|
|J2CAuthAlias||The auth alias name as noted in Step Authentication Alias Configuration. For example, cell/dsxAdmin||java.lang.String|
|ldapTypeTDS||Specify True if you are using TDS as your LDAP, or specify False if you are using a different LDAP, for example, Microsoft ADS or Novell DS||java.lang.String|
|mailProperties (No longer needed. Maintained for backward compatibility.)||Specify all possible mail properties. For example, mail,ibm-primaryEmail||java.lang.String|
- Optionally alter the default cache settings and add these to the configuration of the environment variable you configured in the topic Configuring the resource environment provider as part of the installation process. If a user is added to a community through the IBM Connections user interface, the user may need to wait for caches to time out before seeing private community pages or other effects of joining the community in WebSphere Portal.
Connections uses three different caches:
- Communities: caches communities from IBM Connections based on the unique ID
- Members: caches members of a community from IBM Connections based on the unique ID
- Entities: caches repository entities (either group or person) based on their unique ID
The possible configuration options are:
|communitiesCache.size ||java.lang.String ||1024|
|communitiesCache.lifetime ||java.lang.String ||600|
|membersCache.size ||java.lang.String ||1024|
|membersCache.lifetime ||java.lang.String ||600|
|entitiesCache.size ||java.lang.String ||1024|
|entitiesCache.lifetime ||java.lang.String ||86400 |
All lifetime values are specified in seconds. The cache size indicates number of elements.
- Save the new settings.
What to do next
Stop the server so that you can deploy the libraries and make changes to the XML configuration files.
Parent topic: Integrating community membership with Portal security