Configure the Connections repository for VMM

Configure the Connections repository for the Virtual Member manager (VMM) so that we can integrate communities with Portal security.

This task is done when the server is stopped. In a cluster, we can change the configuration files directly on the deployment manager and then synchronize the changes to all cluster nodes.

1. Configure VMM.

   • See Installation Options.

   • If we use Microsoft Active Directory (AD), IBM Domino Server, or Novell Directory Services, make sure defined the -DICpersonCorrelationAttributeSyntax attribute as described in the topic Installation Options.

   • If we do not use Tivoli Directory Server (TDS), then set the -DICldapTypeTDS flag to false.

   • Follow the pattern from Step 3 for running the ConfigEngine command for the operating system:

     AIX , Linux, or Solaris:

     ./ConfigEngine.sh <parameters>

     Windows:

     ConfigEngine.bat <parameters>

   • If we are installing in a clustered environment, perform this step on the primary node and then synchronize the nodes.

   Configure, following this pattern:

   ConfigEngine configure-SNPortletsVMM -DICpersonCorrelationAttribute=[personCorrelationAttribute]
   -DICpersonCorrelationAttributeType=[personCorrelationAttributeType] -DICcommunityRdnAttribute=[communityRdnAttribute] -DICmaxSearchResults=120 
   -DICldapTypeTDS=[ldapTypeTDS] -DICrunAsAdmin=false -DICpumaFilterClassname=com.ibm.connections.vmm.adapter.filter.VMMPrincipalFilter 
   -DICpumaFilterPosition=120 -DWasPassword=[was-admin-pwd] -DPortalAdminPwd=[portal-admin-pwd]
    -DPortalAdminPwd=[portal-admin-pwd]

   For example:

   ConfigEngine configure-SNPortletsVMM -DICpersonCorrelationAttribute=ibm-entryUuid -DICpersonCorrelationAttributeType=uniqueId 
   -DICcommunityRdnAttribute=cn -DICmaxSearchResults=120 -DICldapTypeTDS=true -DICrunAsAdmin=false 
   -DICpumaFilterClassname=com.ibm.connections.vmm.adapter.filter.VMMPrincipalFilter -DICpumaFilterPosition=120 
   -DWasPassword=[was-admin-pwd] -DPortalAdminPwd=[portal-admin-pwd]

2. Configure the VMM Repository.

   • See Installation Options.

   • Follow the pattern from Step 3 for running the ConfigEngine command for the operating system.

   • You must stop the WebSphere Portal Server before running the following command; otherwise, the command script fails.

   • If we are installing in a clustered environment, perform this step on the primary node and then synchronize the nodes.

   ConfigEngine wp-create-cur -DWasPassword=[was-admin-pwd] -Dfederated.cur.id=connections 
   -Dfederated.cur.adapterClassName=com.ibm.ws.wim.adapter.connections.ConnectionsAdapter 
   -Dfederated.cur.isExtIdUnique=true -Dfederated.cur.supportExternalName=false 
   -Dfederated.cur.supportPaging=false -Dfederated.cur.supportSorting=false 
   -Dfederated.cur.supportTransactions=false -Dfederated.cur.baseDN=o=connections

   If we are reinstalling the portlets after you remove them using the steps in Remove the Connections portlets, verify the VMM repository does not already exist.

   1. Log in to the WebSphere Administrative Server console.

   2. In the section Global securities > Federated repositories > Manage repositories look for a Connections repository. If one exists, delete it.

3. Update the Repository Group Repository Relationship

   • See Installation Options

   • Follow the pattern from Step 3 for running the ConfigEngine command for the operating system.

   • You must stop the WebSphere Portal Server before running the following command; otherwise, the command script fails.

   • If we are installing in a clustered environment, perform this step on the primary node and then synchronize the nodes.

   ConfigEngine wp-update-group-repository-relationship -DWasPassword=[was-admin-pwd] 
   -Drepository.id=[ldap-identifier] -Drepository.forgroups=connections

   Repeat for every LDAP repository configured in Federated Repositories for WAS.

4. Resynchronize the nodes.

• Troubleshooting the VMM configuration
  Verify that VMM is configured correctly and resolve issues if it is not.

Parent topic:
Integrate community membership with Portal security