Reference > Utilities

acpextract utility

The acpextract utility extracts the access control policy and access group information in the database and generates files that capture the information in XML format. It uses an input filter XML file to specify the data to extract from the database.

Notes:

1. The acpextract utility only requires the input_filename parameter.

2. The test server should be stopped before running the utility.

3. To run the utility, login using the non-root WebSphere Commerce user ID.

   The user ID must have the following permissions:

   • Read/write/execute authority to the directories, subdirectories, and files of WC_INSTALL/xml/policies and WC_INSTALL/logs.

   • Read/execute authority to the WC_INSTALL/bin directory and its files.

     If the user does not have the required authority, grant this authority using the chmod command.

   You must login with a profile which has the following permissions:

   • Read/write/execute authority to files under WC_INSTALL/xml/policies, WC_USER /instances and WC_USER/instances/ instance/logs.

   • Read/execute authority to the WC_INSTALL/bin directory and its files.

     For example, define the profile with USRCLS *SECOFR.

4. Check for errors in the log files. Note that errors might not appear on the command line.

   1. Check the acpextract.log and messages.txt files...

      • WC_INSTALL/logs

   2. • WC_USER/instances/acpextract.log

      • WC_USER/instances/ instance/logs/messages.txt

   3. Any error files generated in WC_INSTALL/xml/policies/xml directory.

Parameter values

database

Required: Name of the database from which to extract the policy and access group information.

For DB2 UDB databases, the Type 2 database name is deprecated, where the database names do not contain a prefix.

That is, the DB2 Type 4 JDBC driver is used instead, where the Type 4 database name is prefixed with the database server and port. For example, db_server:db_port/db_name.

See the DB2 Information Center for more information:

• How JDBC applications connect to a data source

• How JDBC applications connect to a data source

database_user

Required: Name of the database user who can connect to the database.

database_user_password

Required: The associated password for the database user.

input_filename

Required: The input filter XML file that specifies what data to extract from the database.

ACPoliciesfilter.xml

This file is used to extract all access group and policy data.

ACUserGroupsFilter.xml

This file is used to extract all access group data.

OrganizationPoliciesFilter.xml

This file is used to extract all access group and policy data for a particular organization. Before using this file, you should edit this file to specify the required organization ID. The policy data owned by this organization ID will be extracted.

schema_name

Optional: The name of target database schema. This name is normally the same as database_user.

This parameter is required if there are multiple schemas in the database into which you are loading data.

Example

From the WC_INSTALL/bin, run:

• ./acpextract.sh mall dbuser dbusrpwd ACPoliciesfilter.xml

• acpextract.cmd mall dbuser dbusrpwd ACPoliciesfilter.xml

• ./acpextract.sh localhost:50000/mall dbuser dbusrpwd ACPoliciesfilter.xml

• acpextract ACPoliciesfilter.xml

The following files are created:

ExtractedACPolicies.xml

This file contains data extracted by the Extract command for the given filter criteria.

ExtractedACPolicies.dtd

The DTD for the ExtractedACPolicies.xml file.

AccessControlUserGroups.xml

The file containing the access group definitions.

AccessControlPolicies.xml

The file containing the language-independent access control policy information.

AccessControlPolicies_ locale.xml

The language-dependent access control policies file that contains the display names and descriptions.

+

Search Tips   |   Advanced Search