Administer > Overview of administering a WebSphere Commerce site > Configuration Manager
Propagate changes to the WebSphere Commerce configuration file
Overview
If you manually change WCS instance properties propagate these changes to ensure the WCS instance runs correctly
Changes made to the configuration file in WebSphere Commerce Developer do not need to be propagated to the EAR file. The development environment does not have the concept of an instance, therefore there is a single instance of the configuration file, wc-server.xml. In a production environment, each instance has its own configuration file which must be deployed with the WebSphere Commerce enterprise application.
If you have manually changed parameters by changing the configuration file, propagate the changes to the WebSphere Commerce Server EAR file.
Procedure
- Verify the WAS server hosting the Administrative console is running.
In a standalone (WAS) environment, this is server1. In a managed (WAS ND) environment, this is the dmgr server.
- Update the instance EAR file...
WC_INSTALL/bin/config_ant.sh -DinstanceName=instance UpdateEAR
Wait for the message BUILD SUCCESSFUL. This may take some time to complete.
- Stop and start WebSphere Commerce.