+

Search Tips   |   Advanced Search

Configure stand-alone repositories


Add the custom stand-alone user registry and repository. You must implement the UserRegistry interface to connect to VMM and then implement a custom registry adaptor so that WebSphere Portal can access the repository. After you implement the required interfaces, define several parameters for the environment and run a task to create the stand-alone repository.

To use a single repository other than an LDAP directory, you must implement the UserRegistry interface to create a custom stand-alone user registry. You must also create a custom user registry adaptor by implementing the wim.Repository interface. Refer to the WAS Information Center for more information and instructions.


Create a stand-alone repository

  1. Edit wkplc.properties

  2. Set values under the VMM Standalone CUR configuration heading:

  3. Save and close wkplc.properties.

  4. Validate the LDAP server settings:

      ./ConfigEngine.sh validate-standalone-ldap -DWasPassword=foo

  5. Set the standalone repository:

      ./ConfigEngine.sh wp-modify-cur-security -DWasPassword=foo

  6. Restart the WebSphere_Portal server.

If you created the clustered environment, including the additional nodes, and then completed the steps in this task, run update-jcr-admin on the secondary nodes.


Parent: Set stand-alone repositories
Related:

WAS 8.0 Information Center, Sample custom adapters for federated repositories examples

WAS 8.0 Information Center, Repository SPI (System programming interfaces for virtual member manager adapters)

WAS 8.0 Information Center, VMM API

Set up a custom user repository with Virtual Member Manager for IBM WAS and IBM WebSphere Portal