Home
Documentation
HCL Commerce is a high-availability, highly scalable and customizable e-commerce platform. Able to support hundreds of thousands of transactions per day, HCL Commerce allows you to do business with consumers (B2C) or directly with businesses (B2B). HCL Commerce uses cloud friendly technology to make deployment and operation both easy and efficient. It provides easy-to-use tools for business users to centrally manage a cross-channel strategy. Business users can create and manage precision marketing campaigns, promotions, catalog, and merchandising across all sales channels. Business users can also use AI enabled content management capabilities.
Administering
Topics in the Administering category highlight tasks that are typically performed by the Site Administrator, to support daily operations of the HCL Commerce site.
Staging environment
an HCL Commerce staging environment is a runtime environment where business and technical users can update and manage store data and preview changes. The changes can then be propagated to the production environment.
HCL Commerce staging-enabled tables
HCL Commerce staging-enabled tables are grouped according to whether they contain site-related data, merchant-related data, or both site and merchant-related data. Staging-enabled tables are also called staged tables.
Listing managed tables
Managed tables fall into three categories: site data tables; merchant data tables; mixed site and merchant data tables.

Listing managed tables

Managed tables fall into three categories: site data tables; merchant data tables; mixed site and merchant data tables.

To list the tables that are managed by the staging or authoring environment:

Procedure

Start a database command prompt session.
Connect to the staging or authoring database.
Issue one of the following SQL commands, depending on the category for which you want to see the list of managed tables:
Option Description
Site data select tabname from STGSITETAB
Merchant data select tabname from STGMERTAB
Mixed site and merchant data select tabname from STGMRSTTAB
Attention: Some of the managed tables that are returned by the SQL commands do not have staging triggers associated with them. Any changes that you make to these tables in the staging database are not captured in the STAGLOG table. When you run the stagingprop utility, changes in these non-staged tables are not propagated from the staging database to the production database.
To view a list of tables that contain staging triggers, issue the following SQL command:
- select trigname, tabname from syscat.triggers where trigname like 'STAG%'
  The list of tables with staging triggers can be found in the tabname column of the result set.
- select trigger_name, event_object_table from qsys2.systriggers where trigger_name like 'STAG%'
- select object_name from user_objects where object_type = 'TRIGGER' and object_name like '%STG_%;
  For Oracle staging triggers, it has this format:
  <X>STG_<tableName>
  where:
  
  X = I for insert, U for update, or D for delete
  
  tableName = the name of the table that owns the trigger.