Enable custom tables for staging

 

+

Search Tips   |   Advanced Search

 


If you have customized your database schema by creating new tables and you want to stage these custom tables, do the following for each custom table you want to stage:

  1. Identify your customized table's scope:

    • site data

    • merchant data

    • mixed site and merchant data.

    • If your site is hosting several stores you may be using one common staging server. Sometimes you may want to propagate only site changes such as when you are adding a new tax or a new currency. Identifying each table's scope can help you in this task. You can decide at the record level if a table is site, merchant or mixed data depending on the records in that table. For example, if all records have to do with site changes, then the table is a site table. If some records have to do with store changes and some with site changes, it is a mixed table.

  2. In both the staging server and the production server, insert the customized table into the STGSITETAB, STGMERTAB, or STGMRSTTAB table, depending on the scope of the table:

    • For site tables, insert only into STGSITETAB.

    • For merchant tables, insert only into STGMERTAB.

    • For tables which contain both site and merchant data, insert into STGSITETAB, STGMERTAB, and STGMRSTTAB.

      If you inserting customized parent and child tables, ensure the TABNBR column value for the child tables are higher than the TABNBR column value for the parent tables. If your customized table is a parent table of a WebSphere Commerce table, ensure that the TABNBR column value for the customized table is lower than the TABNBR column value for the WebSphere Commerce table.

  3. On the staging server, create database triggers for the custom database table to record changes to the custom database table to the STAGLOG table.


 

Related Concepts


Staging server

 

Related tasks


Create triggers for custom tables

 

Related Reference


WebSphere Commerce staging-enabled tables