Package customized code for deployment

The WebSphere Commerce Build tool is used to build customizations into input packages. These packages can be used to build new container images and deploy to the runtime environments. If a CI/CD pipeline is implemented, you do not need to concern yourself with deployment. The WebSphere Commerce Build Tool can build customization assets for the four server environments that are found in WebSphere Commerce Version 9:

Note: To customize the Web server, see Customizing the Web server Docker container. Templates and samples of configuration and property files are provided for each type of application. We can easily start building these out-of-box applications, but more advanced and specialized build processes are also achievable by customizing the build ANT scripts themselves.

Each application is built into an isolated package. The configuration, input, and output files are separate for each application. While it is building one application, the tool cannot access or reference the assets of another application. However, only one WebSphere Commerce Build Tool environment is needed to build all the applications. We can cleanly separate the files and assets of different applications by keeping them in different directories, or by using different file name conventions.

The WebSphere Commerce Build Tool has the following features:

We can run the WebSphere Commerce Build Tool from within the WebSphere Commerce development environment, or the WebSphere Commerce Utility server Docker container.