Create federated repositories
Add your custom repository to the default federated repositories. We implement a custom registry adapter so that WebSphere Portal can access the repository. After implementing the custom registry adapter, define several parameters for the environment and run a task to add the repository to the federated repositories.
Create a custom user registry adapter before creating the repository. To create the user registry adapter, implement the wim.Repository interface. Refer to the WAS documentation for information and instructions.
- Perform the following steps to create a federated repository:
- Open wkplc.properties with any text editor from the following directory:
- Set values 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
- Save and close wkplc.properties.
- Run...
cd WP_PROFILE/ConfigEngine
./ConfigEngine.sh wp-create-cur -DWasPassword=foo
- Restart the WebSphere_Portal server.
- Perform the following steps to create custom properties for the federated repository:
- Open wkplc.properties with any text editor from the following directory:
WP_PROFILE/ConfigEngine/properties
- Set values under the VMM Federated CUR Properties heading in wkplc.properties:
- cur.id
- cur.name
- cur.value
- Save and close wkplc.properties.
cd WP_PROFILE/ConfigEngine
./ConfigEngine.sh wp-create-cur-custom-property -DWasPassword=foo
- Restart the WebSphere_Portal server.
Parent Set federated repositoriesRelated tasks:
Related information:
Websphere Application Server Information center: Sample custom adapters for federated repositories examples
Repository SPI
Virtual member manager API
Set up a custom user repository with Virtual Member Manager for IBM WebSphere Application Server and IBM WebSphere Portal