Publish wizard configuration parameters

You can change the behavior of the Publish wizard by modifying some configuration parameters in the WebSphere Commerce configuration file.

WCDE_installdir/workspace/WC/xml/config/wc-server.xml
WC_installdir/wc.ear/xml/config/wc-server.xml

Note: Your wc-server.xml file contains more parameters in the <DevTools> code block, but this topic only displays the configurable parameters.

<DevTools CommitCount="17000" 
      ConnectionPoolSize="50"
      IDResolverCustomizerFile="DB2JConnectionCustomizer"
      IDResolverMode="mixed" IDResolverPropFile="IdResolveKeys"
      LoaderCustomizerFile="MassLoadCustomizer" 
      LoaderMode="sqlimport"
      LoaderNoPrimary="error"
      MaxErrors="1"
      SampleSarPath="WCDE_installdir/starterstores"
      SarExtensions="sar;zip" 
      SarPath="WCDE_installdir/conf/sar"
      StoreParamsDescriptor="SAR-INF/store-refs.xml"
      StoreValidationDescriptor="SAR-INF/validate.xml"
      StoresPropertiesPath="WEB-INF/classes"
      StoresWebPath="workspace/Stores/WebContent"
      WebAppPath="/webapp/wcs/stores" 
      display="false" 
      instanceDir="WC_installdir/instances/instance_name">
</DevTools>

Commit Count

This number is used during publishing. The database gets committed after each commit count number of records gets loaded. If errors exist in the data, the database gets rolled back to the last commit point. Modify this number as needed. The commit count must be set to a number greater than the number of rows in the archive. You might also need to increase the DB2 log size after you increase the commit count.

ConnectionPoolSize

The JDBC connection pool size.

IDResolverCustomizerFile (mandatory)

Publish must also specify a customizer file to be used with the idresgen utility. The default customizer files are DB2ConnectionCustomizer.properties or OracleConnectionCustomizer.properties. The default value is ISERIES_RESWCSID_Customizer if you configured your instance to use the native JDBC driver, and TOOLBOX_RESWCSID_Customizer if you configured your instance to use the toolbox JDBC driver.

The OracleConnectionCustomizer.properties file is located in the following directory: WC_eardir/properties
The DB2ConnectionCustomizer.properties file is located in the following compressed file: WC_eardir/lib/loader/IdResGen.zip

For IBM i OS operating system The IDResolverCustomizerFile parameter is mandatory for IBM i systems.

Note: To specify your own customizer file, change the value of the following attribute in the DevTools section of the WebSphere Commerce configuration file to the name of your customizer file without the extension: IDResolverCustomizerFile="myidresgen_utilityCustomizerFile"

IDResolverMode

The idresgen utility mode is the method that is used in processing idresgen utility input. Specifically, whether to treat the data as if identifiers exist in the original data (update mode) or do not (load mode). Use mixed mode when some identifiers exist and others do not. Mixed mode is the recommended mode for Publish.

IDResolverPropFile

Name of the property file that is used by the idresgen utility to resolve and generate IDs for WebSphere Commerce data.

LoaderCustomizerFile (mandatory)

The Publish wizard and publishstore utility must also specify a customizer file to be used with the massload utility. If you do not specify a customizer file in the WebSphere Commerce configuration file, then the publish code uses the default customizer file: MassLoadCustomizer.

Note: To specify your own customizer file, change the value of the following attribute in the DevTools section of the WebSphere Commerce configuration file to the name of your customizer file without the extension:

LoaderCustomizerFile="
myLoaderCustomizerFile"

For IBM i OS operating system The LoaderCustomizerFile parameter is mandatory. The default value is ISeries_LODWCSDTA_Customizer if you are using the native JDBC driver.

LoaderMode

The massload utility can be run in six modes: SQL import, Native import, Load, and Ignore are discussed here. For more information about the methods in the load command, see Load command.

SQL import (default): Uses the Java Database Connectivity (JDBC) to insert and update data. This option provides the most flexible mode of operation but is also the slowest for importing large amounts of data into a few tables. It allows cell-level update. It is recommended that you use SQL import.
Native import: Uses the DB2 native import functions and allows cell-level update with medium speed and flexibility.; Uses the CPYFRMIMPF command.
Load: Uses the native facilities of the RDBMS (DB2 Load or SQLLoad) and is the fastest mode for loading large amounts of data into a few tables. If you are publishing to a staging server, you cannot use the Load method.; Uses the CPYFRMIMPF command and is the fastest mode for loading large amounts of data into a few tables. The Load mode inserts data only; it does not update data. If a record exists for the data you are loading, an error occurs.
Ignore: When you select ignore, the publish function does not load any data, and also does not call the product set publish, the contract and account imports, or the payment configuration.

LoaderNoPrimary

A parameter that is used by the Load command, when the primary key is missing for a record in the input file.

Error: Report the missing primary key and end.
Skip: Skip any record in the input file that does not have a primary key.
Insert: Attempts to process (insert or delete) the data.

MaxErrorsInSarXML

The maximum number of errors that the publishing process allows while the process loads the store data. If this number is exceeded, the publish stops and rolls back. The default value is 1.

SampleSarPath

The location of the starter store archives that display in the Publish wizard. The entries in the SARRegistry.xml file are relative to this directory. The value must be an absolute path.

SarExtensions

The acceptable extensions for a store archive file (SAR). For example, XXX.sar or XXX.zip.

SarPath

Store archives contained in this directory are automatically displayed in the Default view of the Publish wizard. This path provides an alternative to registering a store archive in the SARRegistry.xml. The default path is,

WC_installdir/instances/instance_name/sar
WC_userdir/instances/instance_name/sar
WCDE_installdir/conf/sar
Note: You need to create this directory structure. The conf/sar directories do not exist by default.

StoreParmsDescriptor

The path to the store-refs.xml file contained within the store archive. Every store archive must have this descriptor present in the specified location. This file contains parameters specific to a store archive that are used in store publish, such as the Store Directory and Store Identifier.

StoresDocRoot

The location on the WebSphere Commerce Server where the store's assets are stored. This value must be an absolute path.

StoresPropertiesPath

The location of the store's text assets (contained in a property resource bundle) relative to the StoresDocRoot.

StoresWebPath

The location of the store's web assets relative to the StoresDocRoot.

StoresXMLPath

The root of the Change flow notebook-related files.

WebAppPath

The WebAppPath forms part of the store's URL. For example, if you specify /webapp/wcs/stores, then the store URL is

http://host_name/webapp/wcs/stores/Mystore/index.jsp

display

Reserved for IBM use only.

instanceDir

The instance directory. For example, WC_installdir/instances/instance_name