Secure > Authorization > Customize default access control policies
Load access control policy data
If you make policy changes by working directly with the XML files, load the changed XML files back into the databases.
It is important to maintain consistency between the XML files and the access control information in the databases for several reasons:
- When you create an instance of WebSphere Commerce, the policy and access group definitions are loaded from the XML files.
- To implement the same access control policies in a second instance of WebSphere Commerce, you can do so by copying the XML files to the appropriate directory before creating the second instance.
- The XML files offer a convenient way to directly view and edit the policies and their component parts, so keeping the files up-to-date is essential.
The loading process reads the XML files containing the access control policy information and access group definitions and loads them into the appropriate databases. The policy and access group information contained in the XML files is loaded at installation, however, reload the files if you make changes to them.
- Load access groups
To load user access group definitions, run the acugload script. This script loads the <UserGroup> element.
- Load access control policy definitions and other policy-related elements
To load access control policy definitions, run the acpload script. This script loads the following elements: <Action>, <ActionGroup>, <Attribute>, <ResourceCategory>, <ResourceGroup>, <Relation>, <RelationGroup>, <Policy>, <PolicyGroup>.
- Load policy display names and descriptions
To insert or update display names and descriptions for the various policy related elements, run the acpnlsload script. This script loads the following elements: <Action_nls>, <Attribute_nls>, <ActionGroup_nls>, <ResourceCategory_nls>, <ResourceGroup_nls>, <Relation_nls>, <Policy_nls>, <PolicyGroup_nls>