Update stand-alone repositories
We can update the environment parameters we defined when created the stand-alone repository. You should run the task to update the custom repository if you any environment settings have changed such as the base DN or an administrator user ID and password. We can also run the update task to change any settings you specified when created the repository.For example, run the update task to change support for paging, sorting, and transactions.
To update a stand-alone repository:
- Edit wkplc.properties
- Set values under the VMM Standalone 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
- Save and close wkplc.properties.
- Run the following to update the stand-alone repository:
./ConfigEngine.sh wp-update-standalone-cur -DWasPassword=foo
- 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 stand-alone repositories