Update federated repositories
You can update the environment parameters you defined when you created the federated repository. You should run the task to update custom repository if you any environment settings have changed such as the base DN. You can also run the update task if you want to change any settings you specified when you created the repository. For example, run the update task if you want to change support for paging, sorting, and transactions.
To update a federated repository, do the following:
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.
- 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
- 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
- Save and close wkplc.properties.
- Run the following task from the WP_PROFILE/ConfigEngine:
Windows: ConfigEngine.bat wp-update-federated-cur -DWASPassword=foo
UNIX: ./ConfigEngine.sh wp-update-federated-cur -DWASPassword=foo
IBM i: ConfigEngine.sh wp-update-federated-cur -DWASPassword=foo
- Restart the server1 and WebSphere_Portal servers.
Parent
Set federated repositories