Home

 

Enable Lotus Connections directory service extensions

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

Lotus Connections directory service extensions are protocols that propagate Communities and Profiles data between the features. When these service extensions are enabled, you can use the Communities and Profiles databases to store user information instead of having to access the LDAP for each request.

To edit configuration files, use wsadmin. See Start the wsadmin client for details.

Complete the following steps to enable Lotus Connections service extensions:

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

   1. Access the Lotus Connections configuration file:

      • Stand-alone deployment: execfile("connectionsConfig.py")

      • Network deployment: execfile("WAS_HOME/profiles/Dmgr01/config/bin_lc_admin/connectionsConfig.py")If you are prompted to specify which server to connect to, type 1.

        This information is not used by wsadmin when you are making configuration changes.

   2. Check out the Lotus 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.

      • cell_name is the name of the WebSphere Application Server cell hosting the Lotus Connections feature. This argument is required even in stand-alone deployments. This argument is also case-sensitive, so type it with care. If you do not know the cell name, do one of the following to determine it:

        • Stand-alone deployment: From the file system...

          WAS_HOME\profiles\profile_name\config\cells\
          

      • Network deployment: From wsadmin...

        print AdminControl.getCell()
        

      For example:

      • AIX/Linux:

        LCConfigService.checkOutConfig("/opt/temp","foo01Cell01")
        

   3. Microsoft Windows:

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

2. Enable the Communities service extension:

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

   To specify the Web address from which to access the service, use this command:

   LCConfigService.updateConfig("communities.directory.service.extension.href","<web_address>")
   

   Specify the Web address using the syntax: <communities_server>/dsx where <communities_server> is the Web address from which the Communities feature is available. If the feature is set up to secure data traffic, be sure that the value of this property is specified as a secure HTTP (HTTPS) Web address.

3. Enable the Profiles service extension:

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

   To specify the Web address from which to access the service, use this command:

   LCConfigService.updateConfig("profiles.directory.service.extension.href","<web_address>")
   

   Specify the Web address using the syntax: <profiles_server>/dsx where <profiles_server> is the Web address from which the Profiles feature is available. If the feature is set up to secure data traffic, be sure that the value of this property is specified as a secure HTTP (HTTPS) Web address. If you want plan to configure Lotus Connections to hide e-mail addresses, use the following command to change the type of authentication that is used:

   LCConfigService.updateConfig("profiles.directory.service.extension.auth",
    "DSX-Admin")
   

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 Applying common configuration property changes for information about how to save and apply your changes.

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

Administer all Lotus Connections features

 

Related tasks

Enable single sign-on between all features

Synchronize user data between Profiles and the LDAP directory

Edit configuration files

Add features to the SSL trust store

Forcing users to log in before they can access a feature

---

+

Search Tips   |   Advanced Search