Configuring and running the toolkit deployment process

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.

High-level toolkit deployment process flow

The following diagram illustrates the high-level server deployment process flow:

High-level toolkit deployment process flow

  1. WebSphere Commerce Version 7.0.0.2Test the connection to the database to determine if any of the dataload steps are set to run.
  2. If set to run, back up the Derby database and the workspace.
  3. If set to run, perform common SQL dataload.
  4. If set to run, perform common XML dataload. This result is identical to running the idresgen tool, then running the massload tool.
  5. If set to run, perform common ACUG dataload. This result is identical to running the acugload tool.
  6. If set to run, perform common ACP dataload. This result is identical to running the acpload tool.
  7. If set to run, perform common ACP (NLS) dataload. This result is identical to running the acpnlsload tool.
  8. If set to run, perform target-specific SQL dataload.
  9. If set to run, perform target-specific XML dataload. This result is identical to running the idresgen tool, then running the massload tool.
  10. If set to run, perform target-specific ACUG dataload. This result is identical to running the acugload tool.
  11. If set to run, perform target-specific ACP dataload. This result is identical to running the acpload tool.
  12. If set to run, perform target-specific ACP (NLS) dataload. This result is identical to running the acpnlsload tool.
  13. For each connector project (module) set to include, copy to the workspace and import/refresh.
  14. For the dataload project (module) set to include, copy to the workspace and import/refresh.
  15. For the WebSphere Commerce EAR project (module), 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.
  16. For each EJB project (module) set to include, copy to the workspace, import/refresh, and deploy.
  17. For each Java utility project (module) set to include, copy to the workspace and import/refresh.
  18. For the static Web project (module), copy to the workspace and import/refresh.
  19. For each Web project (module) set to include, copy to the workspace and import/refresh.
  20. For each OpenLaszlo Web project (module) set to include, copy to the workspace, import/refresh and compile.
  21. Compile the workspace.
  22. Publish the Websphere Commerce application to the test server.
  23. WebSphere Commerce Version 7.0.0.3If set to run, clean the working directory.