Migrating from Sterling Intelligent Promising Inventory Visibility integration phase 1 to phase 2

To start using Sterling Intelligent Promising Inventory Visibility as your inventory management system for Sterling Order Management System Software, ensure that you migrate to Sterling Intelligent Promising Inventory Visibility.

To successfully complete the migration, System Integrators must review best practices and deprecated Sterling Order Management System Software APIs and events.

Before you begin

Complete the following prerequisites:
  • Disable the reference implementation of IVReadCachedAvailabilityUEImpl or IVReadCachedAvailabilityUEImpl_v1 for OMPGetInventoryFromCacheUE, if implemented. This UE implementation is used to fetch inventory availability from Sterling Intelligent Promising Inventory Visibility. With phase 2 integration, inventory availability is fetched out-of-the-box, and therefore, you need not implement this UE.
  • Run the InventorySnapshot agent to sync demands and supplies from Sterling Global Inventory Visibility to Sterling Intelligent Promising Inventory Visibility.
    Note:
    • Traditionally, demands and supplies are sent to Sterling Intelligent Promising Inventory Visibility by using DEMAND_CHANGE and SUPPLY_CHANGE_LIST events. However, if you have customized phase 1 to send demands and supplies to Sterling Intelligent Promising Inventory Visibility through a user exit, ensure to disable this customization. If this customization is active in phase 2, duplicate demands and supplies might be sent to Sterling Intelligent Promising Inventory Visibility.
    • In phase 2, for the demands and supplies of untagged items, the tag number is set to blank.

Procedure

  1. Run the Inventory Snapshot agent to synchronize demands and supplies from Sterling Order Management System Software into Sterling Intelligent Promising Inventory Visibility.
  2. Shut down all the application servers, agents, and integration servers.
    Note: Ensure that you permanently shut down and disable the following agents and integration servers:
    • Inventory Snapshot agent
    • <Enterprise>_IVD integration servers
    • <Enterprise>_IVS integration servers
    Note: If you are using the SIV integration adapter functionality, disable the <Enterprise>_ID and <Enterprise>_IS integration servers.
  3. Enable Sterling Intelligent Promising Inventory Visibility phase 2 integration by completing the following steps:
    1. Configure the following properties in customer_overrides.properties to establish the connection to Sterling Intelligent Promising Inventory Visibility:
      • iv_integraion.tenantId = <tenant id obtained from Sterling Intelligent Promising Inventory Visibility>

        For example, iv_integration.tenantId=a6868ay3

      • iv_integration.clientId=<client id obtained from Sterling Intelligent Promising Inventory Visibility>

        For example, iv_integration.clientId=k12dyFucZK3tZFDtuNStXQcWKAI7u5r1

      • iv_integration.secret=<client secret obtained fromSterling Intelligent Promising Inventory Visibility>

        For example, iv_integration.secret=sampleW5IsFmEINaOwGHy231eM

      • iv_integration.baseUrl=<base URL obtained from Sterling Intelligent Promising Inventory Visibility>

        For example, iv_integration.baseUrl=https://api.watsoncommerce.ibm.com/inventory

    2. Verify that the following integration queues are correctly configured to send messages to Sterling Intelligent Promising Inventory Visibility.
      • yfs.iv.integration.demand.providerurl=<provider URL for 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 for 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>
      • yfs.iv.integration.icf=<initial context factory for queues>
    3. Set up the Sterling Intelligent Promising Inventory Visibility integration by completing the following steps:
      1. Browse to the <runtime>/bin directory and run any one of the following commands:
        • For UNIX, run
          ./sci_ant.sh -f configureIVIntegration.xml -DNewCustomerImplementation=false
        • For Windows, run
          sci_ant.cmd -f configureIVIntegration.xml -DNewCustomerImplementation=false
  4. Rebuild the application EAR.
  5. Enable the TLS version 1.2 in the startup scripts by configuring the following JVM argument for application servers, agents, and integration servers.
    -Dhttps.protocols=TLSv1.2
    If you are using IBM JRE, configure -Dcom.ibm.jsse2.overrideDefaultTLS=true
  6. Start the demand and supply integration servers by running the following commands:
    • For UNIX, run
      • ./startIntegrationServer.sh IV_ADJUST_IS
      • ./startIntegrationServer.sh IV_ADJUST_ID
    • For Windows, run
      • startIntegrationServer.cmd IV_ADJUST_IS
      • startIntegrationServer.cmd IV_ADJUST_ID
  7. Restart all the application servers, agents, and integration servers.

What to do next

Complete the post migration activities.
After sufficient time (at least in the order of days) is elapsed and on completing all testing and validation, complete the following steps:
  1. Configure the value of iv_integration.migration.complete=true in the customer_overrides.properties file to indicate that the migration to phase 2 is completed.
  2. Run the Inventory Purge agent to cleanup inventory records from the Sterling Order Management System Software database.