WebSphere Commerce configuration file

 

+

Search Tips   |   Advanced Search

The Configuration Manager should be used to modify most WebSphere Commerce configuration parameters. However, some parameters must be changed through the WebSphere Commerce configuration file.

There are two configuration files for each instance:

If you manually change the configuration file, also change the master configuration file. If you do not make the changes to the master configuration file, those changes will be lost if you use the WebSphere Commerce Configuration Manager, or other WebSphere Commerce utilities, to update your instance at a later time.

After manually changing the master configuration file, run...

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

...to update the runtime configuration with the master configuration file. This process ensures that all nodes running the WebSphere Commerce instance place an updated copy of the configuration file in the following location:

Ensure server1 is started successfully before modifying instance-specific properties in Configuration Manager.

The wc-server.xml file is also updated if you run the setdbtype command to configure the database type used with WebSphere Commerce. The file is updated with the newest database information. If you copying and moving files, you may need to rerun setdbtype to update the database information.

Related concepts

Configuration Manager

Related tasks

Opening the Configuration Manager
Propagating changes to the WebSphere Commerce configuration file