Home
Documentation
This Help Center provides documentation on all aspects of the HCL Commerce+ Transaction Server product, from installation and deployment to operating and customization.
Reference
Topics in the Reference section contain all of the Commerce+ Transaction Server reference documentation.
Commerce+ Transaction Server database schema
The Commerce+ Transaction Server database model was designed for data integrity and optimal performance. Commerce+ Transaction Server provides several hundred tables that store Commerce+ Transaction Server 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.
Data models
Any given database data model displays the relationship among database tables in the schema.
System
The system data models show the relationship of database tables used for Commerce+ Transaction Server system functions.

Documentation
This Help Center provides documentation on all aspects of the HCL Commerce+ Transaction Server product, from installation and deployment to operating and customization.
- Overview
  Welcome to the HCL Commerce+ Transaction Server overview. Explore these feature overviews to learn how Commerce+ Transaction Server operates. Refer to the related links listed at the end of each topic to access expanded product documentation.
- Deploying
  This section provides details on deploying HCL Commerce+ Transaction Server. It explains how to download the Docker images and Git bundles that comprise the product, how to create a minimal environment, and how to plan for a full deployment. It details supported software versions, patches, and configurations to ensure the platform performs well.
- Migrating
  The following topics show how to migrate an existing HCL Commerce Version 9.1 environment to Commerce+ Transaction Server.
- Operating
  The topics in this section focus on tasks that are performed by business users, marketers, and customer support representatives to connect with partners and attract and satisfy customers.
- Administering
  The site administrator performs the tasks needed to support day to day operations of the Commerce+ Transaction Server site.
- Extending
  Using Commerce+ Transaction Server's xC programming model, you can use HCL-provided extension points to extend existing Commerce logic. You can implement these extensions with the xC Customization toolkit provided by HCL. Commerce+ also provides Packaged Business Capability integrations that extend the product's reach and functionality.
- Securing
  These topics describe the security features of Commerce+ Transaction Server 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 Commerce+ Transaction Server site performance.
- Troubleshooting
  Topics in the Troubleshooting section highlight common issues that are encountered with Commerce+ Transaction Server, and how they can be addressed or mitigated.
- Reference
  Topics in the Reference section contain all of the Commerce+ Transaction Server reference documentation.
  - REST API
    The REST API reference describes the available endpoints for customizing the system. Essential information such as the resource path, descriptions of each operation, and samples of the request and response payloads is provided.
  - Mapping of REST services to storefront checkout actions
    The Aurora starter store uses REST services throughout the checkout process. The actions for each page map to a REST service.
  - REST service annotations
    Commerce+ Transaction Server REST services and Search REST services are annotated so you view and test the APIs with Swagger, an interactive REST service interface. The REST Discovery API generates a list of REST resources and APIs by parsing annotations on a resource handler. By documenting your custom REST resource handlers with the same annotation standards as Commerce+ Transaction Server REST services, your custom REST services can be viewed and tested with Swagger.
  - Run Engine commands
    The following Run Engine commands are available by default for you to configure the applications that are running inside the containers.
  - Commerce+ Transaction Server database schema
    The Commerce+ Transaction Server database model was designed for data integrity and optimal performance. Commerce+ Transaction Server provides several hundred tables that store Commerce+ Transaction Server 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.
    - 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.
      - Legend for data models
        Database tables within the HCL Commerce database schema are organized into functional groups, called data models.
      - Marketplace
        The marketplace data model shows the relationship between database tables related to the Marketplace Management system.
      - Catalog
        The catalog data model shows the relationship between database tables related to the Catalog subsystem.
      - Marketing
        The marketing data model shows the relationship between database tables related to the Marketing subsystem.
      - Promotions
        The promotions data models show the relationship between database tables that are related to the promotions.
      - Member
        The member data model shows the relationship between database tables related to the Member subsystem.
      - Order Management
        The order management data model shows the relationship between database tables related to the Order Management subsystem.
      - Payment
        The payment data models show the database tables that are related to the payments subsystem.
      - Store
        The store data models show the relationship between database tables that are related to stores.
      - System
        The system data models show the relationship of database tables used for Commerce+ Transaction Server system functions.
        Command
        The command data model shows the relationship between database tables that contain information about the system commands.
        Scheduler
        The Scheduler data model shows the relationship between database tables that contain information about the scheduler.
        Language
        The language data model shows that a store entity can specify alternative languages, in pairs.
        Messaging
        The Messaging data model shows the relationship between database tables that contain information about messaging.
        Messaging extension
        The messaging extension data model shows the relationship between database tables that contain information about messaging extensions.
        Mobile device
        The Mobile device data model shows the relationship between database tables that contain information about mobile (pervasive) device options within the system.
        Staging environment
        The staging environment data model shows the database tables that contain information about the staging environment. These tables have no direct relationship with each other.
        System
        The system data model shows the relationship between database tables that contain information about systems.
        User traffic
        The user traffic data model shows the relationship between database tables that contain information about user traffic.
        Views and temporary tables
        The views and temporary tables data model shows information about views and temporary tables.
        Session management
        The session management data model shows the relationship between database tables that contain information about session management.
      - Trading
        The trading data models show the relationship of database tables in the Trading subsystem.
      - Content Management
        The Content Management shows the relationship between database tables that contain information about content management.
      - Content management system integration
        The content management system integration data model shows the relationship between database tables used by the solution.
      - Content versioning
        The content versioning data model shows the relationship between database tables that contain information about the content versioning.
      - Folder data model
        The folder data model shows the relationship between the database tables that include information about folder and folder items.
      - Wish list
        The Wish list data model (previously the Gift Center data model) shows the relationship between database tables that contain information about the storefront user wish list.
      - Commerce+ Transaction Server search engine optimization
        The Commerce+ Transaction Server search engine optimization (SEO) shows the relationship between database tables that contain information about Commerce+ Transaction Server search engine optimization (SEO).
      - Commerce+ Transaction Server search data model
        The Commerce+ Transaction Server search data model shows the relationship between database tables that are related to Commerce+ Transaction Server search.
    - Database tables
  - Tag: eMarketingSpotCache
    You can include the wcf:eMarketingSpotCache tag within an e-Marketing Spot JSP fragment to indicate that the JSP fragment is to be dynamically cached. This tag dynamically sets dependency IDs for e-Marketing Spot cache entries.
  - Payments subsystem
    In Commerce+ Transaction Server, payment processing uses the Payments subsystem.
  - Commerce+ Transaction Server web services
    Commerce+ Transaction Server provides many web services.
  - Utilities
    In Commerce+ Transaction Server 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.
  - 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.

System data models

The system data models show the relationship of database tables used for Commerce+ Transaction Server system functions.