Publish wizard configuration parameters

Use the following parameters to change the behavior of the Publish wizard. These parameters are found in the WebSphere Commerce configuration file, instance_name.xml, in the following directory:

<DevTools CommitCount="17000"
        ConnectionPoolSize="50"
        IDResolverCustomizerFile="DB2ConnectionCustomizer"
        IDResolverMode="mixed"
        IDResolverPropFile="IdResolveKeys"
        LoaderCustomizerFile="MassLoadCustomizer"
        LoaderMode="sqlimport"
        LoaderNoPrimary="error"
        MaxErrors="1"
        SampleSarPath="WC_installdir/samplestores"
        SarExtensions="sar;zip"
        SarPath="WC_installdir/instances/instance_name/sar"
        StoreFrontFile="devtools/storefront/StoreFront.xml"
        StoreParamsDescriptor="SAR-INF/store-refs.xml"
        StoresDataPath="$StoresDocRoot$/$StoresWebPath$/WEB-INF/stores"
        StoresDocRoot="WAS_installdir/installedApps/hostname/WCServer_enterprise_archive"
        StoresPropertiesPath="Stores.war/WEB-INF/classes"
        StoresWebPath="Stores.war"
        StoresXMLPath="WAS_installdir/installedApps/hostname/WCServer_enterprise_archive/Stores.war/WEB-INF/xml/tools/stores"
        TempPath="dWC_installdir/instances/instance_name/temp/tools/devtools"
        ToolsStoresPropertiesPath="WAS_installdir/installedApps/hostname/WCServer_enterprise_archive/properties/tools/stores"
        ToolsStoresXMLPath="WAS_installdir/installedApps/hostname/WCServer_enterprise_archive/Stores.war/WEB-INF/xml/tools/stores"
        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 there are errors in the data, the database gets rolled back to the last commit point. Modify this number depending on the amount of data you are loading - the commit count must be set to a number greater than the number of rows in the archive. You may also need to increase the DB2 log size after increasing the commit count.
ConnectionPoolSize
The JDBC connection pool size.
IDResolverCustomizerFile (mandatory)
Allows you to specify a customizer file for use with ID Resolver. The default value is either DBConnectionCustomizer or OracleConnectionCustomizer.
i5/OSiSeriesThe IDResolverCustomizerFile parameter is mandatory. The default value is ISERIES_RESWCSID_Customizer if you have configured your instance to use the Native JDBC driver, and TOOLBOX_RESWCSID_Customizer if you have configured your instance to use the Toolbox JDBC driver.
IDResolverMode
The ID Resolver mode is the method used in processing ID Resolver 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 used by IdResGen command to resolve and generate IDs for WebSphere Commerce data.
LoaderCustomizerFile (mandatory)
Allows you to specify a customizer file for use with the Loader package. The default customizer file is MassLoadCustomizer.
i5/OSiSeriesThe LoaderCustomizerFile parameter is mandatory. The default value is ISeries_LODWCSDTA_Customizer if you are using the Native JDBC driver.
LoaderMode
There are six modes for the Loader: only 3 modes SQL import, Native import and load are discussed here. For more information on these methods and cadelete and delete, see the topic Load command in the WebSphere Commerce Development online help.
SQL import: This mode uses Java Database Connectivity (JDBC) to insert and update data, providing the most flexible mode of operation but also the slowest for importing large amounts of data into a small number of tables. It allows cell-level update. It is recommended that you use SQL import.
Native import:
AIXLinuxSun Solaris Operating EnvironmentWindows This mode uses DB2 native import functions and allows cell-level
update with medium speed and flexibility.

i5/OSiSeriesThis mode uses the CPYFRMIMPF command.

Load:
AIXLinuxSun Solaris Operating EnvironmentWindows This mode uses the native facilities of the RDBMS (DB2 Load or SQLLoad) and is the fastest mode for loading large amounts of data into a small number of tables. If you are publishing to a staging server, you cannot use the Load method.

i5/OSiSeriesThis mode uses the CPYFRMIMPF command and is the fastest mode for loading large amounts of data into a small number of tables. The Load mode only inserts data; it does not update data. If a record already 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 used by the Load command, when the primary key is missing for a record in the input file. There are three options: error, skip, and insert.
Error: report the missing primary key and terminate.
Skip: skip any record in the input file that does not have a primary key.
Insert: Attempts to process (insert or delete) the data.
MaxErrors
This is the maximum number of errors that the publishing process will allow while loading the store data. If this number is exceeded, the publish will stop and rollback. 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. This is 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 will automatically be displayed in the Default view of the Publish wizard. This provides an alternative to registering a store archive in the SARRegistry.xml. The default path is:
StoreFrontFile
This file contains data for the Change pages page in the WebSphere Commerce Accelerator as well as the image size specifications for the Uploading Banner and Logo pages in the WebSphere Commerce Accelerator.
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.
StoresDataPath
The default location for the store's data assets. This parameter not currently used.
StoresDocRoot
The location on the WebSphere Commerce Server where the store's assets are stored. This is 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 store tooling related files.
ToolStorePropertiesPath
The location of the text assets for the Change flow tooling in WebSphere Commerce Accelerator.
ToolsStoresXMLPath
The location of the XML assets for the Change flow tooling in WebSphere Commerce Accelerator.
WebAppPath
The WebAppPath forms part of the store's URL. For example, if the store URL is
http://host_name/webapp/wcs/stores/Mystore/index.jsp

then /webapp/wcs/stores is the WebAppPath.

display
For internal use only.
instanceDir
The instance directory. For example, WC_installdir/instances/instance_name

Feedback