WebSphere Commerce Version 7.0.0.6

Enabling interim fix JR47901

Interim fix JR47901 stages the INVCNFREL and INVCNF database tables for DOM inventory systems. After you complete this procedure, you can see the inventory count from the storefront.

Before you begin

Install the cumulative interim fix for Fix Pack 6, JR53048.fp.

Procedure

  1. Create staging triggers. Complete this step on the staging server only.
    • For DB2 or OS400: Connect to the WebSphere Commerce database, and then run the following SQL file:
      db2 -td# -vf WC_installdir\schema\db2\apar\wcs.create.stage.trigger.invcnf.sql >> createTriggers.log
    • For Oracle: Run the following SQL file:
      sqlplus -s %user%/%password%@%database% < WC_installdir\schema\oracle\apar\wcs.create.stage.trigger.invcnf.sql>> createTriggers.log  
      • %user%: The Oracle user name, for example wcs1
      • %password%: The Oracle user password, for example wcs1
      • %database%: The database name, for example ORCL
  2. Check the log files to ensure that the SQL commands executed successfully.
  3. Create the staging table record on both staging and production servers.
    • For DB2 or OS400: Connect to the WebSphere Commerce database, and then run the following SQL file:
      db2 -tvf WC_installdir\schema\db2\apar\wcs.insert.stgmertab.invcnf.sql >> insertStgmertab.log
          
    • For Oracle: Run the following SQL file:
      sqlplus -s %user%/%password%@%database% < WC_installdir\schema\oracle\apar\wcs.insert.stgmertab.invcnf.sql >> insertStgmertab.log
      • %user%: The Oracle user name, for example wcs1
      • %password%: The Oracle user password, for example wcs1
      • %database%: The database name, for example ORCL
  4. Check log files to ensure that the SQL commands executed successfully.