WebSphere Commerce Build and Deployment tool change log

• Changes in fix pack 7
• Changes in fix pack 3
• Changes in fix pack 2
• Changes in fix pack 1

Changes in fix pack 7

• If the store WAR for your WebSphere Commerce instance is separated into a store EAR, you can now deploy assets into the store EAR. Refer to Deploying new and changed store assets into a separated store EAR for more details.

Changes in fix pack 3

• Added the ability to perform delta deployment, that is, deploying only the changes between two builds. Refer to the Configuring and running the server delta deployment process and Configuring and running the toolkit delta deployment process topics for detail.
• Added support for loading data using the WebSphere Commerce Data Load utility. Refer to the Advanced server deployment features and Advanced toolkit deployment features topics for detail.
• Added support for loading procedural SQL files (that is, SQL files with statements that use a non-default statement delimiter), based on an identifier in the file name, in the deployment processes. Refer to the Advanced server deployment features and Advanced toolkit deployment features topics for detail.
• Added the ability to extract source code by incremental update instead of a full extraction. Refer to the Advanced build features topic for detail.
• Added a mechanism to include and/or exclude EAR assets from the packaging steps of the build process. Refer to the Advanced build features topic for detail.
• Added the ability to clean the working directory at the end of the build and deployment processes with the new clean.working.dir target.
• Added support for building connector modules that are based on J2EE Connector Architecture (JCA) Version 1.5, which requires a specific packaging scheme. Refer to Chapter 17 of the specification document for detail.
• Added support for several debugging options for EJBDeploy in the build process. Refer to the Advanced build features topic for detail.
• Added the ability to continue on error when loading XML, ACP and ACUG data in the deployment processes.
• Changed the default value of the dos2unix.includes and dos2unix.excludes properties in the build settings to use a safer file inclusion strategy for dos2unix conversion. By default, it now converts only shell scripts and shell script template files.
• Fixed the issue where Java compilation fails on classes that depend on customized, out-of-the-box WebSphere Commerce Java EE modules that are checked into the repository due to incorrect classpath precedence.
• Fixed the issue where loading data from an ordered list of XML files fails in the deployment processes due to an incorrect helper target being called.
• Fixed the issue where wsadmin fails during server deployment with an invalid JVM maximum heap size value, if fix pack 2 is installed but the configured deployment properties file is not synchronized with the updated template.
• Changed how the compilation and EJBDeploy classpath in the build process is constructed to remove duplicate entries between the WebSphere Commerce or WebSphere Commerce Developer installation directory and the WC project in the extracted source directory. This is to mitigate the command-line string limitation on the Windows platform, but is not meant as a solution.
• Replaced all usages of the custom stringLengthCompare condition from the Build and Deployment tool with the standard Ant length condition.
• Added the Build configuration references, Server deployment configuration references, and Toolkit deployment configuration references topics and improved description of configuration properties.

Changes in fix pack 2

• Added IBM i support to the Build and Deployment tool.
• Added support for Data Load utility customization build and deployment. Refer to the Setting up the Data Load utility customization deployment Ant script topic for detail.
• Provided the ability to invoke the build process using a different properties file identified by build type. Refer to the Advanced build features topic for detail.
• Added support for centralized server deployment by invoking the server deployment process as part of the build process. Refer to the Advanced build features topic for detail.
• Added support for server deployment with a WebSphere Commerce Developer installation.
• Added a mechanism to include and/or exclude files in a Web module from the packaging steps of the build process. This feature is useful for excluding static assets from large Web modules such as Stores from deployment if they are not changed frequently. Refer to the Advanced build features topic for detail.
• Improved external compilation classpath management by introducing the new ext.compile.class.path property in the build settings. A full classpath can be specified using this property instead of the old method of copying the libraries to the ${unit.test.lib.dir} directory.
• Added support for setting EJB references during application update in the server deployment process. A binding option file, in CSV file format, can be specified by the new binding.option.file property in the server deployment settings. Refer to the Advanced server deployment features topic for detail.
• Added the ability to specify a maximum heap size for wsadmin in the server deployment process with the new was.jvm.max.memory property in the server deployment settings.
• Added more up-front checking of build and deployment settings as well as database and application server connection checks.
• Replaced the verbose performance logging for target start and end times in the build and deployment processes with a custom Ant logger. This reduces the amount of logs output by the echo.start.time and echo.end.time targets, regardless of whether the build and deployment processes are run in verbose or debug mode. Refer to the Advanced build features, Advanced server deployment features, and Advanced toolkit deployment features topics for detail.
• Added the was.install.root environment variable to the setenv files to resolve a wsadmin invocation error that occurs when an augmented WebSphere Application Server profile is used.
• Reduced the size of the classpath used by the EJB deployment step in the build process by excluding optional WebSphere Application Server libraries. This is to mitigate the command-line string limitation on the Windows platform, but is not meant as a solution.
• Removed module mappings to the Deployment Manager (DMgr) when deploying Java EE modules to the WebSphere Commerce application in the server deployment process, so that it does not cause mapping conflicts on a DMgr that manages multiple WebSphere Commerce instances.
• Set the includeAntRuntime attribute to false for all occurrences of the task in the build process to avoid contamination of the compilation classpath by the Ant runtime classpath.

Changes in fix pack 1

• Automated the configuration of the SOAP request timeout value in the soap.client.props file in the WebSphere Application Server profile during the server deployment process. This is a replacement of the manual step in the server deployment system prerequisites.
• Reduced the size of the classpath used by the EJB deployment step in the build process by excluding the NL-related WebSphere Application Server libraries if they exist. This is to mitigate the command-line string limitation on the Windows platform, but is not meant as a solution.
• Added support for setting virtual hosts for new Web modules during application update in the server deployment process. Refer to the Advanced server deployment features topic for detail.
• Refactored the wsadmin feature that runs a full application update for the partial application update into an option that can be turned on and off in the server deployment process.
• Relaxed the exclusion rules for files in the WEB-INF directory of Web modules that are deployed as part of the partial application update in the server deployment process. Only metadata files sensitive to overwriting are excluded with this change.
• Added verbose performance logging for target start and end times in the build and deployment processes with the new echo.start.time and echo.end.time targets.
• Fixed the issue where the massload utility fails to execute in the deployment processes on an input file that contains spaces in its absolute path.
• Fixed the issue where the wsadmin step in the server deployment use '/' as the path separator.
• Fixed the issue where application update fails in the server deployment process because a Web services EJB module is deployed before its dependent router module.
• Fixed the issue where the open.laszlo.web.module.list property in the toolkit deployment setting is not used to copy the OpenLaszlo Web projects into the workspace. This issue forced the user to specify the project(s) in the web.module.list property.
• Fixed various issues with the FTP and SCP/SFTP static Web server assets deployment and WebSphere Commerce configuration file synchronization script templates.
• Fixed the issue where the workspace backup step fails in the toolkit deployment process because there are files locked by the headless build process that cannot be copied.
• Deleted obsolete documentation and scripts from the Build and Deployment tool.