Create stand-alone repositories

Add 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 environment and run a task to create the stand-alone repository.

If you plan to use a single repository other than an LDAP directory, 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.

To create a stand-alone repository, do the following:

  1. Open wkplc.properties with any text editor from the following directory:

      Windows™: WP_PROFILE/ConfigEngine/properties

      UNIX™: WP_PROFILE/ConfigEngine/properties

      IBMi: WP_PROFILE/ConfigEngine/properties

  2. Specify values for the following parameters under the VMM Stand-alone CUR configuration heading:

      standalone.cur.id
      standalone.cur.baseDN
      standalone.cur.realm
      standalone.cur.delimiter
      standalone.cur.adapterClassName
      standalone.cur.WasAdapterClassName
      standalone.cur.primaryAdminId
      standalone.cur.primaryAdminPassword
      standalone.cur.primaryPortalAdminId
      standalone.cur.primaryPortalAdminPassword
      standalone.cur.primaryPortalAdminGroup
      standalone.cur.personAccountParent
      standalone.cur.groupParent
      standalone.cur.personAccountRdnProperties
      standalone.cur.groupRdnProperties
      standalone.cur.isExtIdUnique
      standalone.cur.supportExternalName
      standalone.cur.supportPaging
      standalone.cur.supportSorting
      standalone.cur.supportTransactions

  3. Save and close wkplc.properties.

  4. Run the following task from the WP_PROFILE/ConfigEngine to validate LDAP server settings:

      Windows: ConfigEngine.bat validate-standalone-ldap -DWASPassword=foo

      UNIX: ./ConfigEngine.sh validate-standalone-ldap -DWASPassword=foo

      IBM i: ConfigEngine.sh validate-standalone-ldap -DWASPassword=foo

  5. Run the following task from the WP_PROFILE/ConfigEngine to set the stand-alone repository:

      Windows: ConfigEngine.bat wp-modify-cur-security -DWASPassword=foo

      UNIX: ./ConfigEngine.sh wp-modify-cur-security -DWASPassword=foo

      i: ConfigEngine.sh wp-modify-cur-security -DWASPassword=foo

  6. Restart the server1 and WebSphere_Portal servers.

If you created clustered environment then performed the steps in this task, now run the update-jcr-admin task on the secondary node. See Enable LDAP security after cluster creation for instructions.


Parent

Set stand-alone repositories

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

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

WAS 7.0 Information Center, VMM API

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

 


+

Search Tips   |   Advanced Search