Building customizations in next-generation Order Hub

After you develop your customizations, build the UI extension JAR file for your customizations to make them ready for deployment in your environment.

Procedure

  1. Use the build-customization.sh script from the <order_hub_code_directory>/container-build path to build the UI extensions by using the following command.
    ./build-customization.sh build-ui
    You can also pass the module names as an argument in the build-customization.sh script to build UI extensions for specific modules. The module names are a comma-separated list of the UI modules that are customized and any new modules, such as buc-app-order,buc-app-inventory,my-new-module.
    For example,
    ./build-customization.sh build-ui buc-app-order,buc-app-inventory
    Note: If you get the error for permissions, run the following command to change the permission for the build script.
    chmod +x build-customization.sh
  2. Build a next-generation Order Hub customization extension JAR file by using the following command.
    ./build-customization.sh package-jar
    The extension JAR file is built in the following location.
    <order_hub_code_directory>/container-build/packagejar
    You can also pass the module names as an argument in the build-customization.sh script to build the extension JAR file for specific modules.
    For example,
    ./build-customization.sh package-jar buc-app-order,buc-app-inventory
    If you build the extension JAR file without building the UI extension, the modules for which UI extensions are not built are ignored when the extension JAR file is being built.

What to do next

Test your customizations. For more information, see Testing customizations in next-generation Order Hub.