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.
The Activity noun is used to model a marketing activity. Marketing activities allow you to define the marketing messages to deliver to customers when a given activity is triggered. BOD Summary
The Campaign noun is used to model a marketing campaign. Campaigns serve to organize your marketing efforts. Campaigns contain any number of marketing activities, which are classified as either Web activities, or e-mail activities. BOD Summary
The CampaignElementTemplate noun is used to model a campaign element template. Campaign element templates are the template definitions of elements within a marketing campaign. BOD Summary
The MarketingContent noun is used to model marketing content. Marketing content refers to any creative material created for your site. Marketing content can have multiple language descriptions, and can optionally be associated with an attachment. BOD Summary
The MarketingEmailTemplate noun is used to model a marketing e-mail template. A marketing e-mail template defines the subject and content of the e-mail. The templates are capable of providing robust, dynamic, and personalized e-mail messages.
The MarketingSpot noun is used to model an e-Marketing Spot. An e-Marketing Spot reserves space on your store pages in which personalized marketing content displays. This noun is used in an authoring environment to provide the list of e-Marketing Spots when creating marketing activities, and to manage creating, updating and deleting e-Marketing Spots. In the storefront, the MarketingSpotData noun is used to provide the data to display to customers in an e-Marketing Spot. BOD Summary
The MarketingSpotData noun is used to model e-Marketing Spot data. This is the data to display to a customer in an e-Marketing Spot. The e-Marketing Spot data contains the catalog entries, catalog groups, and marketing content to display in the storefront. The corresponding campaign, activity, and experiment test element information are returned with each data element. This noun is used in the storefront to provide the data to display to customers in an e-Marketing Spot. In an authoring environment, the MarketingSpot noun is used to list and manage e-Marketing Spots when creating marketing activities.
The MarketingTrigger noun is used to model a marketing trigger. Marketing triggers are used to communicate with the marketing runtime that particular events have occurred (customer interaction points that start or continue a marketing activity), or that the marketing runtime should perform a specific action.
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.