acpnlsload utility

The acpnlsload utility loads the XML files containing the display names and descriptions, into the appropriate databases.

Diagram of the acpnlsload utility. See the list entitled Parameter values for the applicaple syntax.

Notes:
  1. Apache Derby The acpnlsload utility only requires the input_filename parameter.
  2. Apache Derby The test server should be stopped before running the utility.
  3. If you create customized XML files, you need to copy them into the WC_installdir/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, if you want to stop after one such error, you would change the value to 1.
  5. To load the access groups and access control policies, you need to 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. For IBM i OS operating system If you create customized XML files, you must use the full path to the DTD in your file. The access control policies DTDs are located in the WC_installdir/xml/policies/dtd directory.
  7. To run the utility:

    SolarisLinuxAIX To run the utility, you must login using the non-root WebSphere Commerce user ID.

    • Read/write/execute authority to the directories, subdirectories, and files of WC_installdir/xml/policies and WC_installdir/logs.
    • Read/execute authority to the WC_installdir/bin directory and its files.

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

    For IBM i OS operating systemYou must login with a profile which has the following permissions:
    • Read/write/execute authority to files under WC_installdir/xml/policies,/WC_userdir /instances and WC_userdir/instances/ instance_name/logs.
    • Read/execute authority to the WC_installdir/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. SolarisLinuxAIXWindows Check the acpnlsload.log and messages.txt files in the following directory:
      • WC_installdir/logs
    2. For IBM i OS operating system
      • WC_userdir /instances/acpnlsload.log
      • WC_userdir /instances/ instance_name/logs/messages.txt
    3. Any error files generated in WC_installdir/xml/policies/xml directory.

Parameter values

database
Required: Name of the database in which to load the policy.
DB2Note: For DB2 UDB databases, the DB2 Type 4 JDBC driver is used, where the Type 4 database name is prefixed with the database server and port. For example, db_server:db_port/db_name.
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 NLS policy XML file that specifies what display names and descriptions data to load into the database.
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, for example if the database is workspace enabled.

OracleImportant: schema_name is required for Oracle.

Example

From the WC_installdir/bin directory, run:

  • SolarisLinuxAIXWindows./acpnlsload.sh mall dbuser dbusrpwd defaultaccesscontrolpolicies_en_US.xml
  • Windows acpnlsload.cmd mall dbuser dbusrpwd defaultaccesscontrolpolicies_en_US.xml
  • DB2./acpnlsload localhost:50000/mall dbuser dbusrpwd defaultAccessControlPolicies_en_US.xml
  • Apache Derbyacpnlsload defaultaccesscontrolpolicies_en_US.xml