Configuring and building packages
The HCL Commerce Build tool is highly configurable, to suit your current server environment, repository structure, and target environments.
Four predefined applications can be built:
- Customization server
- Search server
- Store server
- Transaction server
Applications and Data can share a build machine, if the configuration property files and output files for each application or Data are distinguished by a naming convention
The following diagram shows the high-level build process flow:

- If set to run, extract source code with the user-provided Ant script.
- Consolidates all Java source code from the source, compiles, and creates a global JAR file that
is used to compile each module individually. This is to help resolve classpath circular dependencies
during the compilation phase using
javac
. - For each connector module set to build, compile and create an expanded resource archive (RAR).
- For each Enterprise JavaBean (EJB) module set to build, compile, deploy, and create an EJB Java Archive (JAR) file.
- For each Java utility module set to build, compile and create a JAR file.
- For each web module set to build, compile and create an expanded web archive (WAR).
- If set to run, create a server deployment package by consolidating assets from source, archived modules, and the HCL Commerce Build tool.
- If set to run, clean the working directory.