Setting up the Sterling Intelligent Promising Inventory Visibility integration

A System Integrator can set up the integration between Sterling Order Management System Software and Sterling Intelligent Promising Inventory Visibility.

Before you begin

To enable the integration with Sterling Intelligent Promising Inventory Visibility, ensure that you have read and completed the integration prerequisites.

Procedure

To set up the integration with Sterling Intelligent Promising Inventory Visibility, complete the following steps:

  1. Configure the Sterling Intelligent Promising Inventory Visibility connectivity by setting the following properties in customer_overrides.properties:
    • iv_integration.tenantId
    • iv_integration.clientId
    • iv_integration.secret
    • iv_integration.baseUrl

    For more information, see iv_integration.properties.

  2. Define the integration queue to send messages to Sterling Intelligent Promising Inventory Visibility.
    Important: Before deploying the Sterling Order Management System Software application and integration servers, configure the queues in client-side JMS application such as IBM MQ or WebLogic.
    • Configure the following property in customer_overrides.properties as the initial context factory, which determines the JMS queue that is used. For example IBM MQ or WebLogic.
      yfs.iv.integration.icf=<initial context factory for queues>
      For example,
      • For weblogic: weblogic.jndi.WLInitialContextFactory
      • For IBM MQ: com.sun.jndi.fscontext.RefFSContextFactory
    • To connect to the JMS queue and send supply updates, configure the following properties in customer_overrides.properties.
      Property Description
      yfs.iv.integration.supply.providerurl The provider URL of the supply queue.
      yfs.iv.integration.sendsupplyupdates.event.queue The queue name for supply updates.
      yfs.iv.integration.supply.qcf The queue connection factory name for the supply queue.
    • To connect to the JMS queue and send demand updates, configure the following properties in customer_overrides.properties:
      Property Description
      yfs.iv.integration.demand.providerurl The provider URL of the demand queue.
      yfs.iv.integration.senddemandupdates.event.queue The queue name for demand updates.
      yfs.iv.integration.demand.qcf The queue connection factory name for the demand queue.
    Important: Create separate JMS queues for supply and demand updates. This means that the values defined for yfs.iv.integration.sendsupplyupdates.event.queue and yfs.iv.integration.senddemandupdates.event.queue properties must be different.
  3. Run the script provided in the installation to configure the appropriate rules and flags that Sterling Order Management System Software requires to enable the Sterling Intelligent Promising Inventory Visibility integration.
    Browse to the <runtime>/bin directory, and run the following command:
    ./sci_ant.sh -f configureIVIntegration.xml -DNewCustomerImplementation=true
  4. Ensure that the TLS version 1.2 is enabled.

    In the startup scripts, configure the following system JVM arguments for application servers, agents, and integration servers:

    • -Dhttps.protocols=TLSv1.2
    • Applicable only if IBM JRE is used. -Dcom.ibm.jsse2.overrideDefaultTLS=true

What to do next

To update supplies and demands, respectively from Sterling Order Management System Software to Sterling Intelligent Promising Inventory Visibility, you must start the integration servers.

To start the integration servers, browse to the <runtime>/bin directory and run the following commands:
  • ./startIntegrationServer.sh IV_ADJUST_IS
  • ./startIntegrationServer.sh IV_ADJUST_ID