Use the Profiles database as the user directory 

Edit configuration property settings to enable IBM Connections directory service extensions.

Before starting

You only need to perform this task if you did not install the Profiles application initially and now want to install Profiles and set its database as the user directory for IBM Connections.

About this task

IBM Connections directory service extensions are protocols that propagate Profiles data between the applications. When the directory service extension is enabled, you can use the Profiles database to store user information instead of having to access the LDAP directory for each request. If you install the Profiles application, the Profiles database is set up to be the user directory for IBM Connections by default.

When you set the Profiles database to be the user directory, only authentication and group membership search requests are sent to LDAP; the Profiles directory handles all user profile search requests

Procedure

1. Start the wsadmin client from the following directory of the system on which you installed the deployment manager:
   
   app_server_root>\profiles\<dm_profile_root>\bin

   Note: You must start the client from this directory or subsequent commands that you try to run will not execute properly. See Starting the wsadmin client for more details.
   

2. Use the wsadmin client to access and check out the Lotus Connections configuration files.

   1. Enter the following command to access the IBM Connections configuration file: execfile("connectionsConfig.py")
      
      If prompted to specify a service to connect to, type 1 to pick the first node in the list. Most commands can run on any node. If the command writes or reads information to or from a file using a local file path, pick the node where the file is stored. This information is not used by the wsadmin client when you are making configuration changes.
      

   2. Check out the IBM Connections configuration files:
      
      LCConfigService.checkOutConfig("<working_directory>","<cell_name>")

      where:
      

      • <working_directory> is the temporary working directory to which the configuration XML and XSD files are copied and are stored while you make changes to them. Use forward slashes to separate directories in the file path, even if you are using the Microsoft Windows operating system.
        AIX and Linux only: The directory must grant write permissions or the command does not run successfully.
        

      • <cell_name> is the name of the WAS cell hosting the IBM Connections application. This argument is case-sensitive, so type it with care. To obtain the cell name:print AdminControl.getCell()
        

      For example:
      

      • AIX or Linux:LCConfigService.checkOutConfig("/opt/temp","foo01Cell01")

      • Microsoft Windows:LCConfigService.checkOutConfig("c:/temp","foo01Cell01")

3. Use the following command to enable the Profiles directory service extension:
   

   LCConfigService.updateConfig("profiles.directory.service.extension.enabled","true")

   
   

4. After making changes, check the configuration files back in and do so during the same wsadmin session in which you checked them out for the changes to take effect. See Apply common configuration property changes for information about how to save and apply your changes.
   

What to do next

Enable single sign-on between all the applications. For more information, see the Enable single sign-on between all applications topic.

Parent topic

Use the LDAP directory as the user directory

Related tasks

Starting the wsadmin client
Enable single sign-on between all applications
Synchronize user data between Profiles and the LDAP directory
Edit configuration files
Add applications to the SSL trust store
Forcing users to log in before they can access an application
Apply common configuration property changes
Configure portlets to use common directory services

   

 

});

+

Search Tips   |   Advanced Search