Create federated repositories

Add custom repository to the default federated repositories. You must implement a custom registry adaptor so that WebSphere Portal can access the repository. After you implement custom registry adaptor, define several parameters for environment and run a task to add repository to the federated repositories.

You must create a custom user registry adaptor before you create repository. To create the user registry adaptor, implement the wim.Repository interface. Refer to the WAS Information Center for more information and instructions.

To create a federated repository, do the following:

1. Create a federated repository:

   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 Federated CUR Properties heading:
      federated.cur.id
      federated.cur.adapterClassName
      federated.cur.baseDN
      federated.cur.isExtIdUnique
      federated.cur.supportExternalName
      federated.cur.supportPaging
      federated.cur.supportSorting
      federated.cur.supportTransactions

   3. Save and close wkplc.properties.

   4. Run the following task from the WP_PROFILE/ConfigEngine:
      Windows: ConfigEngine.bat wp-create-cur -DWASPassword=foo

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

      i: ConfigEngine.sh wp-create-cur -DWASPassword=foo

   5. Restart the server1 and WebSphere_Portal servers.

2. Create custom properties for federated repository:

   1. Open wkplc.properties with any text editor from the following directory:
      Windows: WP_PROFILE/ConfigEngine/properties

      UNIX: WP_PROFILE/ConfigEngine/properties

      IBM i: WP_PROFILE/ConfigEngine/properties

   2. Specify values for the following parameters under the VMM Federated CUR Properties heading in wkplc.properties:
      cur.id
      cur.name
      cur.value

   3. Save and close wkplc.properties.

   4. Run the following task from the WP_PROFILE/ConfigEngine:
      Windows: ConfigEngine.bat wp-create-cur-custom-property -DWASPassword=foo

      UNIX: ./ConfigEngine.sh wp-create-cur-custom-property -DWASPassword=foo

      IBM i: ConfigEngine.sh wp-create-cur-custom-property -DWASPassword=foo

   5. 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 federated 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