This Help Center provides documentation on all aspects of the HCL Commerce+ Transaction Server product, from installation and deployment to operating and customization.
Topics in the Reference section contain all of the Commerce+ Transaction Server reference documentation.
Commerce+ Transaction Server provides many web services.
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.
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.
The following topics show how to migrate an existing HCL Commerce Version 9.1 environment to Commerce+ Transaction Server.
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.
The site administrator performs the tasks needed to support day to day operations of the Commerce+ Transaction Server site.
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.
These topics describe the security features of Commerce+ Transaction Server and how to configure these features.
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.
Topics in the Troubleshooting section highlight common issues that are encountered with Commerce+ Transaction Server, and how they can be addressed or mitigated.
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.
The Aurora starter store uses REST services throughout the checkout process. The actions for each page map to a REST service.
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.
The following Run Engine commands are available by default for you to configure the applications that are running inside the containers.
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.
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.
wcf:eMarketingSpotCache
In Commerce+ Transaction Server, payment processing uses the Payments subsystem.
AttributeDictionaryAttribute noun is used to model an attribute dictionary attribute. An attribute dictionary provides a central place to manage common attributes shared by products.
Catalog noun is used to model a catalog. A catalog can be a primary or a secondary catalog. A catalog represents the contexts under which the catalog groups or catalog entries are defined. When referring to any catalog entity including the Catalog, it is assumed that a store ID is present in the business context. When referring to a catalog entry, catalog group or a kit, the catalog ID is assumed to be present in a catalog context.
CatalogEntry noun is used to model a catalog entry. A catalog entry can be a product, an item, a package, kit or a bundle. The catalog ID, store ID and language are assumed to be set in the business contexts. The entitlement context is required for retrieving the offer prices. CatalogEntry noun is used by the Catalogs Tool at authoring time, and the store front at runtime.
The CatalogFilter noun defines types related to a catalog filter. A catalog filter contains the information to filter the categories and products within a catalog based on static inclusions or exclusions and dynamic conditions that are based the properties or attributes of products.
CatalogGroup noun is used to model a catalog group (or category). A catalog group represents a node in a catalog hierarchy or a tree. A node has a parent and can have zero or more child catalog groups or catalog entries. CatalogGroup noun is used by the Catalogs Tool at authoring time, and the store front at runtime. BOD Summary
The CatalogNavigationView noun was created to represent all of the information that is required to make use of faceted navigation (from a search engine) when a shopper is browsing catalog pages for a store model (Aurora) that is provided by default.
Commerce+ Transaction Server provides WSDL files to describe its Web services.
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.
The following URLs relate to the Messaging system.
The server subsystem consists of functions that are associated with URLs that are run by the scheduler.