Administer > Stage server > Staging server utilities


Enable custom tables for staging

If you have customized the database schema by creating new tables, to stage these custom tables...

  1. Identify the scope of the customized table:

    If the site is hosting several stores you might be using one common staging server. Sometimes you might want to propagate only site changes such as when you are adding a new tax or a new currency. Identifying the scope of each customized table 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 the 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:

    If you are 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 the 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.


What to do next


Related concepts

Stage server


Related tasks

Create triggers for custom tables

Related reference

WebSphere Commerce staging-enabled tables


+

Search Tips   |   Advanced Search