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.
Reference
Topics in the Reference section contain all of the HCL Commerce reference documentation.
HCL Commerce database schema
The HCL Commerce database model was designed for data integrity and optimal performance. HCL Commerce provides several hundred tables that store HCL Commerce instance data. To maintain data integrity, and to ease maintenance referential integrity, constraints are widely used in the database model. Indexes are used carefully on tables to avoid over-indexing and to provide a good balance between data retrieval and data manipulation activities (insert and update). The business rules are implemented at the application level rather than by using database trigger. Triggers, however, are used to facilitate data staging and optimistic locking. A limited number of SQL-based database stored procedures are used for data intensive activities.
Database tables
I
INVSTVW
This is a view derived from the RECEIPT and ITEMFFMCTR tables which contains the existing quantity available for an item for a given store across all FulfillmentCenters.

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.
- Getting started
  HCL Commerce has different advantages for business users, administrators and developers. HCL Commerce targets each of these roles with a tailored set of offerings so that each of your users can get maximum benefit.
- Installing and deploying
  Learn how to install and deploy HCL Commerce development environments and HCL Commerce production environments.
- Migrating
  Before you migrate to HCL Commerce Version 9.1, review this information to help plan and execute your migration.
- Operating
  Topics in the Operating category highlight tasks that are typically performed by business users, customer support representatives, to complete their day-to-day tasks in the operation of the HCL Commerce site.
- Integrating
  Topics in the Integrating category highlight the tasks that are commonly performed for using HCL Commerce in combination with other products.
- 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.
- Customizing
  The topics in the Customizing section describe tasks performed by an application developer to customize HCL Commerce.
- Tutorials
  HCL Commerce provides many tutorials to help you customize and understand your HCL Commerce instance and stores.
- Samples
  Topics in the Samples category highlight the various samples that are provided with HCL Commerce.
- Compliance
  The following section describes how you can leverage HCL Commerce features and functionality to help your site be compliant with different privacy and security standards.
- Securing
  These topics describe the security features of HCL Commerce and how to configure these features.
- Performance
  Topics in the Performance section describe the means by which to plan, implement, test, and re-visit the optimization of HCL Commerce site performance.
- Troubleshooting
  Topics in the Troubleshooting section highlight common issues that are encountered with HCL Commerce, and how they can be addressed or mitigated.
- Reference
  Topics in the Reference section contain all of the HCL Commerce reference documentation.
  - HCL Commerce API reference
    HCL Commerce exposes two main programming APIs. The first and newest API is a REST interface, and most new classes are exposed here. The legacy Java API also contains new classes not suitable for REST, and can be browsed in Javadoc format.
  - Cross-reference of data beans and tables
    Data beans are grouped into several component groups.
  - Cross-reference of commands, tasks, and tables
    URL commands, controller commands, task commands, view commands and tables are related to each other.
  - Cross reference: Commands to beans to database tables
    Use this information when you are customizing a command and you want to know which tables are affected. You should also use this topic if you are modifying a table and want to know which commands and beans are affected.
  - Run Engine commands
    The following Run Engine commands are available by default for you to configure the applications that are running inside the containers.
  - Entering Docker containers
    To enter a Docker container you can complete the following steps.
  - Docker container start up logic for HCL Commerce Version 9.1
    When you deploy a container from an HCL provided image, an Entrypoint.sh helper script determines the configurations to use while starting up the container. Review the following information to learn about what the helper script does, and how you can customize the configurations.
  - HCL Commerce database schema
    The HCL Commerce database model was designed for data integrity and optimal performance. HCL Commerce provides several hundred tables that store HCL Commerce instance data. To maintain data integrity, and to ease maintenance referential integrity, constraints are widely used in the database model. Indexes are used carefully on tables to avoid over-indexing and to provide a good balance between data retrieval and data manipulation activities (insert and update). The business rules are implemented at the application level rather than by using database trigger. Triggers, however, are used to facilitate data staging and optimistic locking. A limited number of SQL-based database stored procedures are used for data intensive activities.
    - Column data type considerations
      Several column data types are available for you to use when you are creating new database table or columns.
    - Schema changes from Version 8 to Version 9
      Database tables and columns within the HCL Commerce Version 9 database schema can differ from the tables and columns in the database schema for HCL Commerce Version 8.
    - Deprecated tables and columns
      If a database table or column is marked as deprecated, then the table or column is outdated by newer constructs. Deprecated sections are supported for reasons of compatibility with an earlier version only. These tables or columns are obsolete or can become obsolete in future versions of HCL Commerce.
    - Data models
      Any given database data model displays the relationship among database tables in the schema.
    - Database tables
      - A
      - B
      - C
      - D
      - E
      - F
      - G
      - H
      - I
        ICCNCPTLNK
        This table is deprecated and is provided for backward compatibility only.
        ICCONSTRNT
        This table is deprecated and is provided for backward compatibility only.
        ICCONSTVAL
        This table is deprecated and is provided for backward compatibility only.
        ICDATAREG
        This table is deprecated and is provided for backward compatibility only.
        ICDEWIDREG
        This table is deprecated and is provided for backward compatibility only.
        ICEXPLDESC
        This table is deprecated and is provided for backward compatibility only.
        ICEXPLFEAT
        This table is deprecated and is provided for backward compatibility only.
        ICFEATPROP
        This table is deprecated and is provided for backward compatibility only.
        ICKNOWDESC
        This table is deprecated and is provided for backward compatibility only.
        ICKNOWLEDG
        This table is deprecated and is provided for backward compatibility only.
        ICMERDESC
        This table is deprecated and is provided for backward compatibility only.
        ICMERTREE
        This table is deprecated and is provided for backward compatibility only.
        ICMETAFEAT
        This table is deprecated and is provided for backward compatibility only.
        ICMETAPHOR
        This table is deprecated and is provided for backward compatibility only.
        ICMETAPROP
        This table is deprecated and is provided for backward compatibility only.
        ICMETAREG
        This table is deprecated and is provided for backward compatibility only.
        ICMREGDESC
        This table is deprecated and is provided for backward compatibility only.
        ICROOTCAT
        This table is deprecated and is provided for backward compatibility only.
        ICTPRICES
        This table is deprecated and is provided for backward compatibility only.
        IITEM
        Each row of this table represents an IItem in an IItemList.
        IITEMLIST
        Each row in this table represents an InterestItemList.
        INIRULEVAL
        This table is deprecated and is provided for backward compatibility only.
        INITIATIVE
        This table is deprecated and is provided for backward compatibility only.
        INSRULE
        Each row in this table represents an installment rule.
        INSRULECATENT
        The relationship between an installment rule and a catalog entry.
        INSRULECATGRP
        Each row in this table represents a relationship between an installment rule and a catalog group.
        INSRULECOND
        Each row represents the installment qualified condition of an installment rule.
        INSRULEINSOPT
        Each row represents an installment payment option of an installment rule.
        INSRULEPAYMTHD
        Each row represents a qualified payment type in an installment rule.
        INTVSCHED
        This table is deprecated and is provided for backward compatibility only.
        INVADJCODE
        Each row of this table defines an InventoryAdjustmentCode for a Store, or the Stores in a StoreGroup. Each code represents a reason for an InventoryAdjustment, such as broken, lost, or found.
        INVADJDESC
        Each row of this table contains language-dependent information about an InventoryAdjustmentCode.
        INVADJUST
        This table records adjustments made to inventory.
        INVAVL
        Each row represents an inventory availability record cached by the Commerce database.
        INVCNF
        Each row represents an DOM inventory cache configuration.
        INVCNFREL
        Each row represents the relationship of an item and/or location with an inventory configuration.
        INVENTORY
        The inventory table. Each row of this table contains a quantity amount representing the inventory for a particular CatalogEntry. The CatalogEntry is available to be shipped from a FulfillmentCenter on behalf of a Store. This table cannot be used in conjunction with Available To Promise (ATP) inventory allocation. It is used only when ATP inventory is not enabled (refer to the INVENTORYSYSTEM column of the STORE table). And it is used by the default implementations of the non-ATP inventory task commands: ResolveFullmentCenterCmd, CheckInventoryCmd, UpdateInventoryCmd, and ReverseUpdateInventoryCmd.
        INVITMVW
        This is a view derived from the RECEIPT and ITEMFFMCTR tables which contains the existing quantity available for an item across all Stores and FulfillmentCenters.
        INVOICE
        This table stores the invoice XML generated for the order release. An order release is represented by a row in the ORDRELEASE table.
        INVRESERVE
        Each row contains information about existing inventory that has been reserved for such purposes as auctions. This reserved inventory is not available for customer orders until the reservation is reversed.
        INVRSRVDSC
        Each row contains language-specific descriptions for the types of inventory reservations that the user has defined.
        INVRSRVTYP
        Each row contains user-defined reservation types that can be used when reserving inventory.
        INVSTFFMVW
        This is a view derived from the RECEIPT and ITEMFFMCTR tables which contains the existing quantity available for an item at a Store and FulfillmentCenter.
        INVSTVW
        This is a view derived from the RECEIPT and ITEMFFMCTR tables which contains the existing quantity available for an item for a given store across all FulfillmentCenters.
        ISEDITATT
        This table holds the attributes of the transport in the form of name-value pairs. The attributes of this table refer to interaction-level (message) attributes of a transport. This table holds attribute information at the profile level.
        ITEMFFMCTR
        Each rows contains information about reserved quantities, amount on backorder, and amount allocated to backorders for items owned by a store at a fulfillment center.
        ITEMSPC
        Information about specified items. A specified item is a product with values for all its attributes. A specified item could correspond to a 2L bottle of milk, with 2% fat content. A specified item is the customer view of what the merchant sells.
        ITEMTYPE
        Each row of this table represents a type of BaseItem.
        ITEMVERSN
        Each row of this table represents an ItemVersion for a BaseItem. An ItemVersion expires when its expiration date is in the past. Each BaseItem must only have a single ItemVersion defined.
      - J
      - K
      - L
      - M
      - N
      - O
      - P
      - Q
      - R
      - S
      - T
      - U
      - V
      - W
      - X
      - Y
      - Z
  - Payments subsystem
    In HCL Commerce, payment processing uses the Payments subsystem.
  - Dynamic caching
    In general, caching improves response time and reduces system load. Caching techniques are used to improve the performance of World Wide Web Internet applications. Most techniques cache static content (content that rarely changes) such as graphic and text files. However, many websites serve dynamic content, containing personalized information or data that changes more frequently. Caching dynamic content requires more sophisticated caching techniques, such as those provided by the WebSphere Application Server dynamic cache, a built-in service for caching and serving dynamic content.
  - HCL Commerce store pages properties
  - Cache-entry elements
    The root element of the cachespec.xml file, <cache>, contains <cache-entry> elements. The WebSphere dynamic cache service parses the cachespec.xml file during start-up, and extracts a set of configuration parameters from each <cache-entry> element.
  - Data Load utility configuration file schema
    The Data Load utility contains several configuration files. You can use the configuration file schema to understand and customize the data load configuration files.
  - HCL Commerce web services
    HCL Commerce provides many web services.
  - Utilities
    In HCL Commerce utilities are scripts that perform operations such as loading access control policies, loading store data, and cleaning the database of obsolete objects. In runtime environments, run utilities from the Utility server Docker container. In the development environment, run utilities from the bin directory.
  - Shopping flow URLs
    HCL Commerce shopping flow URLs are organized by subsystem.
  - Messaging system URLs
    The following URLs relate to the Messaging system.
  - Scheduler URLs
    The server subsystem consists of functions that are associated with URLs that are run by the scheduler.
  - jQuery Enhancements API
    The Aurora starter store in HCL Commerce is completely written in jQuery, which is one of the most commonly used JavaScript libraries used in dynamic websites. The jQuery AJAX and events API provides an easy to use framework that meets most AJAX requirements for storefront development.
  - HCL Commerce foundation tag library
    The HCL Commerce foundation JSTL tag library is a collection of custom tags that are provided to you to support the authoring of HCL Commerce JSP files. HCL Commerce stores use the JavaServer Pages Standard Tag Library (JSTL) to perform logic, instead of Java code. At the same time, business logic is moved into data beans. The combination of these steps allows for less Java code in a JSP page.

INVSTVW

This is a view derived from the RECEIPT and ITEMFFMCTR tables which contains the existing quantity available for an item for a given store across all FulfillmentCenters.

Column Descriptions:

Name	Type	Description
STORE_ID	INTEGER NOT NULL	The Store that owns the inventory.
ITEMSPC_ID	BIGINT NOT NULL	The inventory item identifier.
QTYAVAILABLE	INTEGER	Existing quantity available for this item derived from RECEIPT.QTYONHAND - RECEIPT.QTYINPROCESS - (ITEMFFMCTR.QTYRESERVED + ITEMFFMCTR.QTYALLOCBACKORDER).
QUANTITYMEASURE	CHAR (16) NOT NULL	The unit of measure for the item.