Migrating customizations to next-generation Order Hub

When you move to next-generation Order Hub, you start with the new code base and then migrate any new applications or custom code to the new code base. Your custom code remains mostly the same.

Note: Next-generation Order Hub is built on Angular version 15. If you have customizations that are on earlier Angular versions, you need to migrate them to Angular version 15 before you migrate them to next-generation Order Hub.

Key differences for customization development

The following table outlines the key differences for customization development with next-generation Order Hub.

Table 1. Key differences with next-generation Order Hub customization
Order Hub Next-generation Order Hub
Order Hub runs at www.supply-chain.ibm.com Next-generation Order Hub runs in a local developer toolkit in https://localhost:7443/order-management
To set up the side navigation menu for new applications, you use the Customizations page. To set up the side navigation menu, you manually create the features.json file.
To enable module customizations for existing applications, you use Enable OOB module customization on the Customizations page. To enable module customizations, you use the Customize page.
To accept the certificate for the module, use bucgenerichost, for example, https://bucgenerichost:9300/ To accept the certificate for the module, use localhost, for example, https://localhost:9300/
To configure the customization folder and for authentication, use Display settings > Add ons > Customization Configuration Not applicable.

You need to do a separate build for each environment.

yarn build-<env>

You need to do only one build for all environments.

./build-customization.sh build-ui ui-modules
./build-customization.sh package-jar ui-modules

To deploy customizations in each environment, you use the command line interface.

yarn orderhub-cli publish-customization
 To deploy customizations in each environment, you use the extensions JAR file in Self Service.

The migration process

Migrating existing customizations to next-generation Order Hub is a multi-step process.

  • Download the new next-generation Order Hub code base
  • Prepare to migrate any new applications or customizations
  • Build the customizations
  • Test the customizations
  • Deploy the customizations

The process is slightly different for migrating custom applications and existing customizations.