Integrating with IBM Sterling Order Management System Software on-premises over phase 2

Configure the integration properties, JWT properties, and the public key to integrate Sterling Intelligent Promising with the on-premises offering of Sterling Order Management System Software over Sterling Inventory Visibility phase 2.

  1. Install the IBM® Sterling Order Management System Software. For more information, see Installing IBM Sterling Order Management System Software.
  2. Set up the integration between Sterling Order Management System Software and Sterling Inventory Visibility. For more information, see Setting up the Sterling Inventory Visibility integration.
  3. To enable JWT authentication, set the following property in the customer_overrides file.
    iv_integration.authentication.mode=JWT
  4. Configure the IBM Sterling Order Management System Software for Order Hub and JWT authentication. For more information, see Configuring Sterling Order Management System Software for Order Hub.
  5. Configure the JWT related properties in Sterling Order Management System Software. For more information, see JWT properties for Sterling Order Management System Software.
  6. Create your own public private key pair to authenticate the calls from Sterling Order Management System Software to Sterling Intelligent Promising. Then, configure the public key in the OMS Gateway. For more information, see Creating a JWT issuer secret by using a public key.

    The following snippet is an example of a customer_overrides.properties file after you set up the configuration in steps 2, 3, and 4.

    iv_integration.baseUrl=<SIP_BASE_URL>
iv_integration.tenantId=default
iv_integration.clientId=DEFAULT
iv_integration.secret=DEFAULT
yfs.iv.integration.icf=<initial context factory for queues>
yfs.iv.integration.demand.providerurl=<provider URL of the demand queue>
yfs.iv.integration.senddemandupdates.event.queue=<queue name for demand updates>
yfs.iv.integration.demand.qcf=<queue connection factory name for the demand queue>
yfs.iv.integration.supply.providerurl=<provider URL of the supply queue>
yfs.iv.integration.sendsupplyupdates.event.queue=<queue name for supply updates>
yfs.iv.integration.supply.qcf=<queue connection factory name for the supply queue>
iv_integration.authentication.mode=JWT
yfs.yfs.jwt.create.expiration=300
yfs.yfs.jwt.create.pk.alias=oms-default-jwt
yfs.yfs.jwt.create.issuer=oms
yfs.yfs.jwt.create.audience=oms
yfs.yfs.jwt.create.algorithm=RS512
  7. Start the integration server for syncing supplies and demands from Sterling Order Management System Software to Inventory Visibility by using phase 2 adapter. To start the integration servers, go to the <runtime>/bin directory and run the following commands:
    ./startIntegrationServer.sh IV_ADJUST_IS
./startIntegrationServer.sh IV_ADJUST_ID
Note:
  • While accessing the Order Hub,
    • Ensure to add the origin of the Order Hub as allowedOrigins in SIPEnvironment custom resource. For more information, see allowedOrigins in omsGateway parameter.
    • Ensure to accept the Operator CA certificate of the Sterling Intelligent Promising instance in the browser before accessing Order Hub.
  • While running the integration servers for Inventory Visibility, ensure that you add the certificate to the truststore of integration servers.
  • Before running the integration servers for supply and demand, ensure that you pass the JVM system startup properties in integration servers.
  • Before calling APIs ensure that you pass the JVM system startup properties in application server JVM.