Configuring a connection from Order Hub running in a developer toolkit environment to Sterling Intelligent Promising

When you are running Order Hub in a developer toolkit environment, you can connect to the Sterling Intelligent Promising (SIP) cloud environment. Configuring a connection from Order Hub to SIP enables real-time access to inventory and fulfillment data, helping businesses to provide accurate delivery promises and to optimize order fulfillment. This integration helps to reduce stockouts, improve customer satisfaction, and streamline operations by using SIP’s intelligent decision-making capabilities.

About this task

These instructions are not applicable if you run Sterling Intelligent Promising in a developer toolkit environment.

Procedure

  1. Retrieve the jwtId value and OMS public key.
    1. Open the following file.
      om-appserver:/opt/ibm/wlp/usr/servers/defaultServer/dropins/smcfs.ear/lib/properties.jar/system_overrides.properties
    2. During the set up of the developer toolkit, the yfs.yfs.jwt.create.claims.jwtId.value JWT value is set up for you. The JWT value is what you need to send to IBM® Support in the next step. If this property is not defined in system_overrides.properties, set the value to be in the format of oms-<DTK_ID>.
      For example, if the DTK_ID in devtoolkit_docker/compose/docker/integration.properties is set to buc-12345, then add
      yfs.yfs.jwt.create.claims.jwtId.value=oms-buc-12345
      in the system_overrides.properties file.
    3. The value of the yfs.yfs.jwt.create.pk.alias property is used as the -alias value in the keytool command. If you do not define the property in the system_overrides.properties file, then the default oms-default-jwt key is used.
    4. Browse to the following directory:
      om-appserver:/var/oms/keystore
    5. Export the public key by running the following command:
      keytool -export -keystore key.jks -alias replace_jwt_pk_alias  | openssl x509 -inform der -pubkey -noout
      • The value for -alias (replace_jwt_pk_alias) is the value that you noted from the yfs.yfs.jwt.create.pk.alias property in step 1.c.
      • The password for key.jks is secret4ever.
      Note:

      If you want to replace the default key pair in the system_overrides.properties file, set the property yfs.yfs.jwt.create.pk.alias=<key alias>.

  2. Open a case with IBM Support and provide the jwtId value and the OMS public key. The IBM Support team adds the key to the Sterling Intelligent Promising tenant.
  3. Add the following properties to the system_overrides.properties file.
    • yfs.yfs.jwt.create.algorithm=RS256
    • yfs.yfs.jwt.create.claims=ivTenantId,envId,jwtId
    • yfs.yfs.jwt.create.claims.ivTenantId.value=<IV tenant ID>
    • yfs.yfs.jwt.create.claims.envId.value=<DTK ID>
    • yfs.yfs.jwt.create.pk.alias=<key alias>
    • yfs.yfs.jwt.create.claims.jwtId.value=oms-<DTK ID>

What to do next

After you configure a connection from Order Hub to SIP, you enable and validate the integration so that Order Hub can use the SIP services effectively. Some actions to take are as follows.
  • Validate the JWT authentication
  • Configure core SIP services such as promising, inventory, and optimization
  • Set up the Catalog service
  • Define carrier services and transit details
  • Create nodes and distribution groups
  • Test the integration