Home
User Guide
The information contained in this section applies to IBM WebSphere Commerce Version 7.0.0.9 and Feautre Pack 8. The documentation also applies to all subsequent releases and modifications until otherwise indicated in new editions.
Administering
Overview of administering a WebSphere Commerce site
In WebSphere Commerce the person who performs administrative tasks is called a Site Administrator. The Site Administrator installs, configures, and maintains WebSphere Commerce and the associated software and hardware. The administrator responds to system warnings, alerts, and errors, and diagnoses and resolves system problems. Typically, this person controls access and authorization (creating and assigning members to the appropriate role), manages the Web site, monitors performance, and manages load balancing tasks. The Site Administrator might be responsible for establishing and maintaining several server configurations for different stages of development such as testing, staging, and production. The Site Administrator also handles critical system backups and resolves performance problems.
Configuration Manager
To configure a WebSphere Commerce or a WebSphere Commerce Payments instance, use the Configuration Manager. The Configuration Manager interface shows mandatory fields and provides help.
Updating the WebSphere Commerce configuration file
Many aspects of the WebSphere Commerce runtime application are configured in an XML file. This XML file is inside the WebSphere Commerce Java Platform, Enterprise Edition EAR.
Updating WebSphere Commerce runtime configuration
Many aspects of the WebSphere Commerce application are configured in an XML file. This XML file is inside the WebSphere Commerce JEE EAR.
Propagating changes to the WebSphere Commerce configuration file
If you manually change WebSphere Commerce instance properties, you must propagate these changes to ensure your WebSphere Commerce instance runs correctly

Propagating changes to the WebSphere Commerce configuration file

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

About this task

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.

For IBM i OS operating system Solaris Linux AIX Windows If you manually change the WebSphere Commerce configuration file, you must propagate your changes to the WebSphere Commerce Server EAR file.

Procedure

Ensure that the WebSphere Application Server hosting your administrative console is running. In a standalone (WebSphere Application Server) environment, this is server1. In a managed (WebSphere Application Server Network Deployment) environment, this is your deployment manager server.
Issue the following command:
- WC_installdir/bin/config_ant.sh -DinstanceName=instance_name UpdateEAR
- WC_installdir\bin\config_ant.bat -DinstanceName=instance_name UpdateEAR
Wait for the message BUILD SUCCESSFUL. This process can take some time to complete.
Stop and start WebSphere Commerce.