WebSphere Commerce EnterpriseWebSphere Commerce DeveloperFeature Pack 7 or later

Running the server deployment process for server-side assets

Feature Pack 7 or later

With the deployment settings configured, you can run the server deployment process for deploying server-side assets on your WebSphere Commerce server.

Note: It is recommended to perform a system backup before you proceed with this lesson.

Procedure

  1. Start the WebSphere Commerce server.
  2. Open a command prompt and go to the following directory:
    • WCBD_deploy_server_common_dir
  3. Run the wcbd-ant command:
    wcbd-ant.bat -buildfile wcbd-deploy.xml -Dtarget.env=server
    

    Wait until the deployment process completes successfully.

  4. Optional: Update the shared library for your custom assets. By default, this library is Customer_shared_lib_instance_name.
    Note: This step is not mandatory and is included as an example for how to update the shared library configuration. If a JAR file that you are deploying exists within a file path that is not defined as a part of the shared library configuration, add the file path for your assets into the custom shared library configuration. If your assets are included within a path that configured for the shared library, you do not need to update your shared library configuration. Any new JAR files that you deploy within a configured path for the shared library can automatically be referenced by the shared library.
    To add the WebSphereCommerceServerExtensionsLogic.jar file in the classpath:
    1. Log on to the WebSphere Application Server Admin Console.
    2. Expand Environment. Click Shared libraries.
    3. In the list of shared libraries, click Customer_shared_lib_demo.
    4. In the Configuration tab for the shared library properties, enter a value for the Classpath filed.
      For example, ${WC_EAR_ROOT}\WebSphereCommerceServerExtensionsLogic.jar