WebSphere Commerce Build tool prerequisites

  1. How do we extract the source code from the SCM (for example, CVS, Subversion, or ClearCase)?

  2. How many server environments (prod, stage, etc...) are used by the project?

  3. Do the environments have different configuration settings (database, wc-server.xml, etc...)?

  4. For each server environment, is the EAR deployed in a single-server environment or a clustered environment?

  5. If a remote web server hosts static web contents, how do we deploy the web assets (ftp, scp, ...)

  6. IBM recommends that a server is dedicated to performing builds.

  7. Match the WebSphere Application Server fix pack and interim fixes on the production environment, with the WebSphere Application Server of the development environment.

  8. 2 GB of extra disk space for the WebSphere Commerce Build tool, temporary files, and build packages generated by the build process.

  9. Apache Ant 1.7.1 or later installed on each server.

  10. The client software of the SCM used must be installed and available in command line (with the PATH environment set for the SCM client).

  11. If we 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

  1. Download Ant-Contrib and extract it to a temporary directory.

  2. Copy ant-contrib/ant-contrib-version.jar from the temporary directory to WCB_installdir/lib.

Java Activation Framework (JAF) 1.1.1 Optional. Email notification.

  1. Download JAF and extract it to a temporary directory.

  2. Copy jaf-version/activation.jar from the temporary directory to WCB_installdir/lib.

JavaMail 1.4.1 Optional. Email notification

  1. Download JavaMail and extract it to a temporary directory.

  2. Copy javamail-version/mail.jar from the temporary directory to WCB_installdir/lib.

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 we want support for other protocols, investigate alternative solutions. For more information, see Apache Subversion Ant Library.

Optional. Source extraction from Subversion and SSLv3 enabled.

  1. Download SvnAnt and extract it to a local directory (referred to as SvnAnt_installdir for the rest of the page).

  2. When setting up the source extraction Ant script for Subversion, set the svn.ant.lib.dir property to SvnAnt_installdir/lib WCB_installdir/extract-svn.properties.

Third-libraries are included in the packages created by the build process, so they are not required to be downloaded and set up directly on the deployment systems. If build and deployment processes are failing due to Ant task and type loading issues related to third-party library dependencies, see Troubleshooting: Ant tasks and types fail to load or run due to missing classes


See also


Related concepts
Location and file structure of the WebSphere Commerce Build tool


Related tasks
Configure and build packages
Customize the WebSphere Commerce Build tool