HCL Commerce configuration file (wc-server.xml)

Many aspects of the HCL Commerce runtime application are configured in an XML file. This XML file is located inside the HCL Commerce Java Platform, Enterprise Edition EAR.

The wc-server.xml file is located in the following directories:
  • WC_eardir/xml/config/
  • HCL Commerce Developerworkspace_dir\WC\xml\config\
Note: The wc-server.xml configuration file differs between HCL Commerce and HCL Commerce Developer installations. Windows uses semicolons as a separator between paths, whereas Linux uses colons.

Using an incorrect separator within your wc-server.xml configuration file will cause errors to be logged, and can also be observed as an error when attempting to login to Management Center for HCL Commerce as CWXFR0001E: A generic RuntimeException has occurred.

Modifying wc-server.xml

HCL Commerce Version 9.0 runs its Transaction server inside a Docker container. Containerized servers reset their contents to their preset state every time the server is restarted. This means that you cannot directly edit the wc-server.xml configuration file in a running container and expect the changes to be preserved when the container is restarted. You can modify the wc-server.xml configuration file using a couple of methods:
  1. Use Run Engine commands that modify specific features of the file in a running container, or set them to run on deployment. For available Run Engine commands, see Transaction server Run Engine commands.
  2. Build a new container image that includes changes to the file.
    1. Open for editing the copy of the wc-server.xml configuration file in your development environment, workspace_dir\WC\xml\config\wc-server.xml.
    2. Modify the file according to whatever instructions you are following. Once you have updated the file, save it in place, or check it into your code repository.
    3. Deploy the new file to the Transaction server using the HCL Commerce CI/CD pipeline. For more information about deployment, see Packaging customized code for deployment.
    4. Build the new Docker container. See Building packages.