Deploying customized assets

When you deploy customized assets for WebSphere Commerce, consider the two stages: packaging and deploying.

Stage 1: Packaging

The first stage is twofold: compiling and then packaging:

  • Compiling involves taking source from your source code management system, and building or compiling it into the binaries that are required by the target server environment. For example, you can take your .java files and compile them into .class files.
  • Packaging involves taking the output of the build process and creating deployment packages for your target environment. For Java EE assets, the format of your packaging will vary depending on the type of objects: a single file, a partial application, or an entire module.

Stage 2: Deployment

In this stage, the deployment packages are actually deployed to the target server environment. This process makes the assets created in the build process ready to be executed in the target environment. Each target environment will have a set of tools that are used to deploy of the packages.