Advanced toolkit deployment features
The WebSphere Commerce Build and Deployment tool provides many advanced toolkit deployment features to support more complex configurations. Ensure that you review this page to find and implement features that may improve your toolkit deployment process.
Loading procedural SQL files
Many database management systems
support procedural extensions for SQL. Statements written in procedural SQL often require a
different delimiter than the default one for regular SQL statements. The deployment process supports
loading procedural SQL files with a procedural statement delimiter based on a keyword identifier in
the file name. By default, if the base name if a SQL file contains the keyword identifier
procedural
, it will be loaded with the procedural statement delimiter
@
. These can be configured as required by changing the
procedural.sql.file.name.id
and procedural.sql.delimiter
properties in
WCBD_deploy_toolkit_dir/deploy-target-env.properties
respectively.
Loading data using the Data Load utility
The Data Load utility
provides an efficient data load solution based on business objects. The deployment process supports
loading data using the Data Load utility, which is useful for loading test data and administrative
data such as member data. Similar to how other data files are organized in the repository, data and
configuration files used by the Data Load utility are put into the dataload
subdirectory of the DataLoad
project, which is further organized into the common
and target-specific subdirectories. The build process will then include these files into the
deployment packages. Unless configured otherwise, all files with the name
wc-dataload.xml are included for loading. Additional parameters for the Data
Load utility command can be included by setting the dataload.params
property in
WCBD_deploy_server_dir/deploy-target-env.properties.
Refer to the Server deployment configuration
properties topic for more information on the properties specific to the Data Load
utility.
It is recommended that you follow the Data Load best practices as you develop and
organize Data Load data and configuration files. To promote reuse of properties defined in the
deployment configuration properties file, especially those of the database, consider using variable
substitutions by referencing variables in the configuration files and passing the variable values
with the dataload.params
property mentioned above.
Additional logging and tracing
Ant provides both a verbose
and a debug option to provide additional tracing that may be useful for problem determination. To
enable verbose mode, provide either the -v
or -verbose
option when
calling the wcbd-rad-ant.bat
command to run the toolkit deployment process.
Likewise, to enable debug mode, provide either the -d
or -debug
option when calling the wcbd-rad-ant.bat
command to run the toolkit deployment
process.
Note that Ant does not capture the verbose nor debug output in the log file normally
generated by the toolkit deployment process. The additional output will only be displayed in the
console, so the standard output and error streams should be redirected to a separate log file when
running the toolkit deployment process with these logging and tracing options. This can be done by
appending the following options when calling the wcbd-rad-ant.bat
command to run
the toolkit deployment process, where log-file is the log file to which the
console output is
written:
> log-file 2>&1