HCL Commerce Build tool prerequisites
Before you begin, you must ensure that all prerequisites for the HCL Commerce Build tool are met. In addition, you must learn about the current build, development, and deployment processes that are used in your project. Learning about the current processes helps in planning the adoption of the HCL Commerce Build tool.
Knowledge prerequisites
You are expected to have knowledge in the following to be able to set up and run the HCL Commerce Build tool:
- The software configuration management (SCM) that is used by the customization project
- Remote file transfer protocols such as FTP, SCP, and SFTP
- Is your customization project using an SCM? If so, which one? How do you extract the source code from the SCM?
- How many server environments are used by your customization project? For example, production, staging, or testing. If you use more than one environment, do the environments have different configuration settings? For example, different data in the database, or different settings in the wc-server.xml file.
- For each server environment, is your HCL Commerce Enterprise Application (EAR) deployed in a single-server environment or a clustered environment?
- For each server environment, if you have a remote web server that hosts static web contents for the customization project, how do you deploy the web assets? Can you use remote file transfer methods such as FTP or SCP?
You also need access to the servers in your HCL Commerce topology. You must access these servers for information that is required to set up the build process. If you do not have access to these servers, ensure that an administrator can provide you with this information.
Knowledge resources
Build system prerequisites
It is highly recommended that a server is dedicated to performing builds. In addition, the following requirements must also be met:
- Match the WebSphere Application Server fix pack and interim fixes on your production environment, with the WebSphere Application Server of your development environment.
- 2 GB of extra disk space for the HCL Commerce Build tool, temporary files, and build packages that are generated by the build process.
- Apache Ant 1.7.1 or later installed. To install, download the binary distribution and extract it to a local directory.
- The client software of the SCM used (for example, CVS, Subversion, or ClearCase) must be
installed and available in command line (with the
PATH
environment set for the SCM client). - If you are using the email notification functions, access to an SMTP server is required.
Third-party library dependencies
Software | Importance | Setup instructions |
---|---|---|
Ant-Contrib Ant-Contrib 1.0b3 | Required |
|
Java Activation Framework (JAF) 1.1.1 | Optional: Complete the setup instructions if the mail Ant task is used (for
email notification) |
|
JavaMail 1.4.1 | Optional: Complete the setup instructions if the mail Ant task is used (for
email notification) |
|
SvnAnt 1.2.1 Note: By default, SvnAnt 1.2.1 supports the SSLv3 protocol
only, therefore does not work if WebSphere Application Server has SSLv3 disabled. If you want
support for other protocols, you need to investigate alternative solutions. |
Optional: Complete the setup instructions if the svn Ant task is used (for
source extraction from Subversion) and SSLv3 is enabled. |
|