After you create the deployment package, you can deploy it to your development
environment using additional Ant scripts provided as part of the WebSphere Commerce Build and Deployment tool .
Figure 1 . High-level toolkit deployment process flow
Test the connection to the database to determine if any of the dataload steps are set to
run.
If set to run, back up the Derby database and the workspace.
If set to run, perform common SQL dataload.
If set to run, perform common XML dataload. This result is identical to running the
idresgen
tool, then running the massload
tool.
If set to run, perform common ACUG dataload. This result is identical to running the
acugload
tool.
If set to run, perform common ACP dataload. This result is identical to running the
acpload
tool.
If set to run, perform common ACP (NLS) dataload. This result is identical to running the
acpnlsload
tool.
If set to run, perform target-specific SQL dataload.
If set to run, perform target-specific XML dataload. This result is identical to running the
idresgen
tool, then running the massload
tool.
If set to run, perform target-specific ACUG dataload. This result is identical to running the
acugload
tool.
If set to run, perform target-specific ACP dataload. This result is identical to running the
acpload
tool.
If set to run, perform target-specific ACP (NLS) dataload. This result is identical to running
the acpnlsload
tool.
For each connector project (module) set to include, copy to the workspace and
import/refresh.
For the dataload project (module) set to include, copy to the workspace and import/refresh.
For the WebSphere Commerce EAR and WebSphere Commerce search EAR projects (modules),
copy assets to the workspace and import/refresh. EAR properties and XML files will be copied to the
properties and xml directories in the WebSphere Commerce Developer installation directory.
For each EJB project (module) set to include, copy to the workspace, import/refresh, and
deploy.
For each Java utility project (module) set to include, copy to the workspace and
import/refresh.
For the static Web project (module), copy to the workspace and import/refresh.
For each Web project (module) set to include, copy to the workspace and import/refresh.
Compile the workspace.
Publish the WebSphere Commerce application to the test server.
If set to run, clean the working directory.