Install > Installing maintenance > WebSphere Commerce > Installing WebSphere Commerce fix packs
Update the WebSphere Commerce Build and Deployment tool after installing a WebSphere Commerce fix pack
WebSphere Commerce fix packs provide fixes and improvements for the Build and Deployment tool, which are highly recommended. Due to the customizable nature of the Build and Deployment tool, additional steps are required after fix pack installation to incorporate the fixes into the configuration files and customization.
Before you begin
- Verify the customization to the Build and Deployment tool adheres to the rule of non-customizable files, that any files with the prefix wcbd- should not be modified for serviceability reasons. If you require customization, follow the proper process to create new files and customize as required. Otherwise a fix pack installation may overwrite the customization.
- Back up all files that were created during the setup and customization processes of the Build and Deployment tool. These files generally reside in the WCBD_INSTALL on the build system and in the software configuration management (SCM) system. The files may include:
Process Files Build
- setenv and/or setenv.bat
- build.properties, build.private.properties
- The source extraction Ant script and properties files, if used
- All other files that are created for customization
Server deployment
- setenv and/or setenv.bat
- deploy-target.env.properties and deploy-target.env.properties
- The static Web server assets deployment Ant script and properties files, if used
- The WebSphere Commerce configuration file synchronization Ant script and properties files, if used
- All other files that are created for customization
Toolkit deployment
- setenv.bat
- deploy-target.env.properties and deploy-target.env.properties
- All other files that are created for customization
Procedure
- This fix pack updates many files. See the Files Changed link on the WebSphere Commerce fix pack page. to identify the files for the Build and Deployment tool that have been updated by the fix pack installation.
- For each updated file identified from the previous step:
- Determine the configuration and customization files in WCBD_INSTALL and in the SCM that derived from it.
- For each derived file identified:
- Execute a file comparison with the original, updated file to identify the changes, and then port the changes over to the derived file. Caution must be exercised to ensure that you do not overwrite any values, particularily in configuration files and templates, that may have been changed for the environment. IBM recommends that you use a file comparison tool to minimize the effort and risk.
- If the file is a configuration properties file/template, open the file with a text editor and search for new properties that may have been introduced by the fix pack with the following string:
SINCE: V7 FP Such properties may provide additional functionality that you may help in the build and deployment processes. Review the description of the property and set them as appropriate, then save the file.
- Verify the updated files are committed in the SCM for subsequent runs of the build and deployment processes.
- Test the build and deployment processes with the updated Build and Deployment tool scripts to ensure that they can be completed successfully and work as expected.
Related concepts
Overview: WebSphere Commerce Build and Deployment tool
Customize the Build and Deployment tool
Related tasks
Install WebSphere Commerce fix packs interactively
Install WebSphere Commerce fix packs silently
Migrate the database from DB2 V9.5 Fix Pack 4 to DB2 V9.7 Fix Pack 1