+

Search Tips   |   Advanced Search

Configure federated repositories


Add the 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 the custom registry adaptor, define several parameters for the environment and run a task to add the repository to the federated repositories.

Create a custom user registry adaptor before created the 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:

  1. To create a federated repository:

    1. Edit wkplc.properties

    2. Set values under the VMM Federated CUR Properties heading:

    3. Save and close wkplc.properties.

    4. Run the following

        ./ConfigEngine.sh wp-create-cur -DWasPassword=foo

    5. Restart the WebSphere_Portal server.

  2. To create custom properties for the federated repository:

    1. Edit wkplc.properties

        WP_PROFILE/ConfigEngine/properties

    2. Set values under the VMM Federated CUR Properties heading in wkplc.properties:

    3. Save and close wkplc.properties.

    4. Run the following

        ./ConfigEngine.sh wp-create-cur-custom-property -DWasPassword=foo

    5. Restart the WebSphere_Portal server.

If 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 federated 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