This blog promotes knowledge sharing through experience and collaboration. For more product information, visit our WebSphere Commerce CSE page. For easier navigation, utilize the Categories to find posts that match your interest.
Deploying Out-Of-The-Box Code Can Corrupt Your Installation
Including out-of-the-box code in your deployment can lead to numerous system issues and instability. To maintain a stable environment, limit deployments to include only the customization you have made, and only use the provided Fix Pack and Interim Fix (iFix) installation utilities for out-of-the-box (OOTB) maintenance.
When developing customizations, both OOTB and custom JARs might be checked in the source repository by developers. This can cause issues because OOTB JARs are designed to be maintained by Commerce maintenance: Fix Packs, Feature Packs and iFixes.
Consider the following scenario:
To avoid code inconsistencies, only check in and deploy the customized files. None of the OOTB JARs should be checked into the source repository or deployed.
If the out-of-the-box jars are deployed, you will likely see server start-up issues, or functional issues, for example, when Toolkit specific files replace their runtime version.
When you are working on your Commerce Developer environment (Toolkit), we include OOTB modules and JARs (e.g. OrganizationAdministration, LOBTools, etc) in the WCProject you are working in. They exist only to allow you to test your customization with your test server. When you finish with your customization, you only need to check in the files that you have created/updated, into your source repository.
For example: this means you should check in only the customized files within:
and not check in any of the OOTB folders or files:
Follow these guidelines and I assure you, you will prevent a lot of issues down the road.