Propagating changes to the WebSphere Commerce configuration file

 

+

Search Tips   |   Advanced Search

 

If you manually change WebSphere Commerce instance properties you must propagate these changes to ensure your WebSphere Commerce instance runs correctly

Changes made to the WebSphere Commerce configuration file in WebSphere Commerce Developer do not need to be propagated to the WebSphere Commerce 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.

AIX|Linux|Solaris|I5/OS|Windows:

If you have manually changed parameters by changing the WebSphere Commerce configuration file, propagate your changes to the WebSphere Commerce server EAR file.

1. Ensure that the WAS hosting your Administrative console is running. In a standalone (WAS) environment, this is server1. In a managed (WAS ND) environment, this is your deployment manager server.

2. Issue the following command:

   • AIX|Linux|Solaris|I5/OS

     WC_installdir/bin/config_ant.sh -DinstanceName=instance UpdateEAR

   • Windows

     WC_installdir/bin/config_ant.bat -DinstanceName=instance UpdateEAR

   Wait for the message BUILD SUCCESSFUL. This may take some time to complete.

3. Stop and start WebSphere Commerce.

Configuration Manager
WebSphere Commerce configuration file
Opening the Configuration Manager
ANT target: UpdateEAR