Reference > Utilities


acugload utility

The acugload utility loads the XML files containing the user (access) group definitions into the appropriate databases.

Notes:

  1. The acugload utility only requires the input_filename parameter.

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

  3. If you create customized XML files, copy them into the WC_INSTALL/xml/policies/xml directory to have them loaded into the databases.

  4. There is a setting in the loading scripts that specifies the following parameter setting while resolving ID's and loading the data to the database: "-maxerror 100000". This means that if there up to 100000 foreign key violations while loading the data, they will be ignored, instead of aborting. This value can be increased or decreased as needed. For example, to stop after one such error, you would change the value to 1.

  5. To load the access groups and access control policies, run the following related utilities in this sequence:

    1. acugload (loads the user access group definitions)

    2. acpload (loads the main access control policy)

    3. acpnlsload (loads the display names and descriptions)

  6. If you create customized XML files, use the full path to the DTD in the file. The access control policies DTDs are located in the WC_INSTALL/xml/policies/dtd directory.

  7. 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.

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

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

      • WC_USER/instances/acugload.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 in which to load the policy.

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:

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 policy XML file that specifies what user (access) group definitions data to load into the database.

schema_name

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

schema_name is required for Oracle.


Example

From the WC_INSTALL/bin directory, run:


+

Search Tips   |   Advanced Search