Configuring the DOM integration feature

The DOM integration feature is configured and the store is updated to use an external system for inventory and order processing.

Procedure

  1. Start the following servers:
  2. Open the WebSphere Commerce Administration Console.
  3. On the Site/Store Selection page, select Site.
  4. Select Configuration > Transports.
  5. Select WebServices over HTTP.
  6. Click Change Status.
  7. Select Configuration > Message Types.
  8. Create the following two new message type configurations:
    Property Value
    Message type Message for external inventory system
    Transport WebServices over HTTP
    Device format Webservices
    URL http://hostname:9080/ExtOMSSimMediationModuleWeb/sca/InventoryServices
    Property Value
    Message type Message for external order system
    Transport WebServices over HTTP
    Device format Webservices
    URL http://localhost:9080/ExtOMSSimMediationModuleWeb/sca/OrderServices
  9. Close the Administration Console.
  10. Connect to the database:
    • Use a database client to connect to the WebSphere Commerce database.
    • WebSphere Commerce DeveloperOn a WebSphere Commerce Developer machine, navigate to the following URL: http://localhost/webapp/wcs/admin/servlet/db.jsp
  11. Execute the following SQL statement to use an external system for inventory and order processing:
    UPDATE STORE SET INVENTORYSYSTEM=-5 WHERE STORE_ID IN (SELECT STOREENT_ID FROM STOREENT WHERE IDENTIFIER='Store_Identifier' );

    Where Store_Identifier is the value of your store identifier. For example, 'AuroraESite' for your consumer direct store.

  12. Insert records into the INVCNF and INVCNFRE tables to setup inventory configurations that apply to items and locations.
    For example, the following sample configuration applies to all items and all locations. The sample configuration enables the database cache, fetches inventory availability from the DOM system when the cached quantity is below 5, decrements cached inventory availability after orders are submitted, and updates it when the information is retrieved from the DOM system:
    
    INSERT INTO INVCNF (INVCNF_ID, IDENTIFIER, DESCRIPTION, PRECEDENCE, FLAGS, THRESHOLDQUANTITY, CHEXPABOVETHRES, 
    CHEXPBELOWTHRES, CACHEPRIORITY, FALLBACKINVSTAT, FALLBACKAVAILTIME, FALLBACKINVOFFSET, QUANTITYMEASURE) 
    values (1, 'Sample', 'Sample Configuration', 0, 30, 5, null, 0, 0, 'UAVL', null, null, 'C62'); 
    
    INSERT INTO INVCNFREL (INVCNFREL_ID,INVCNF_ID,CATENTRY_ID,STORE_ID,STLOC_ID) 
    VALUES (1, 1, null, null, null);
    
    For more information, see Inventory availability caching, and INVCNF.
  13. Enable the side by side integration.
    1. Go to the following directory:
      • Windows WC_eardir/xml/config/com.ibm.commerce.order-fep
      • WebSphere Commerce Developer Workspace_dir\xml\config\com.ibm.commerce.order-fep
    2. Open the wc-admin-component.xml file for editing.
    3. Locate the following code:
      <_config:configgrouping name="SideBySideIntegration">
      <_config:property name="enable" value="N"/>
    4. Set the value of the enable property to be "Y".
    5. Save and close your file.
  14. Download the following files to a temporary directory:
    • wc-component-client.xml (this compressed file contains the wc-component-client.xml file that is updated for inventory).
    • wc-component-client.xml (this compressed file contains the wc-component-client.xml file that is updated for order).
  15. Use the WebSphere Application Server standard deployment method to deploy the downloaded wc-component-client.xml files:
    1. For inventory:
      • WC_eardir/xml/config/com.ibm.commerce.inventory.external/wc-component-client.xml
      • WebSphere Commerce Developer workspace_dir/wc/xml/config/com.ibm.commerce.inventory.external/wc-component-client.xml
    2. For order:
      • WC_eardir/xml/config/com.ibm.commerce.order.external/wc-component-client.xml
      • WebSphere Commerce Developer workspace_dir/wc/xml/config/com.ibm.commerce.order.external/wc-component-client.xml
  16. Restart your WebSphere Commerce Server: