This Help Center provides documentation on all aspects of the HCL Commerce+ Transaction Server product, from installation and deployment to operating and customization.
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.
Kubernetes is the default tool for deploying a live HCL Commerce+ Transaction Server production site. HCL provides all the required applications as Docker images for you to use in a configuration of your choice. Also included are Kubernetes Helm Charts.
This section describes how to prepare to install a full Commerce+ Transaction Server environment using Kubernetes. It focuses on deploying to a default data environment. You can base your production environment on this setup.
Prepare a Postgres, IBM Db2, or Oracle database to use as the Commerce+ Transaction Server database.
Use Oracle Database to serve as your database.
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.
The following table provides a list of generally available (GA) software levels, fixes, and settings for the latest HCL Commerce+ Transaction Server release.
Best practice for installing HCL Commerce+ Transaction Server is to start with a preconfigured 'minimal environment.' To install Commerce+ Transaction Server, first, set up and test the minimal environment, then plan for your production environment using your own organization's IT and business experts.
Deploying Commerce+ Transaction Server on Kubernetes and operating it securely in a production environment requires comprehensive and careful planning, and security hardening considerations. To make it easier to deploy for non-production and testing environments, and to learn about how Commerce+ Transaction Server consumes data from Vault, Helm charts are provided alongside Commerce+ Transaction Server for deployment to a Kubernetes cluster. Once Vault is deployed and set up, you can deploy Commerce+ Transaction Server with different deployment topologies based on your site requirements.
There are multiple software, environment, and deployment configuration prerequisites to deploy Commerce+ Transaction Server on Kubernetes. Commerce+ Transaction Server provides a large degree of flexibility, and each available option should be considered for viability in your resulting production deployment.
The hcl-commerce-vault-helmchart Helm Chart deploys Vault for use as a remote configuration center, storing Commerce+ Transaction Server environment data, and acting as the certification agent to issue certificates to each Commerce+ Transaction Server application server based on their unique service names. The Vault must be deployed before deploying the Commerce+ Transaction Server application. Once Vault are deployed, it can be used to deploy and control multiple Commerce+ Transaction Server environments. After Vault is started, it can run scripts to load Commerce+ Transaction Server environment configuration data as specified in values.yaml, and can also configure a Public Key Infrastructure (PKI) back-end to issue certificates, if enabled via the vault.vaultLoadData configuration.
vault.vaultLoadData
Vault is used to store configuration data, and it can contain the secrets for Commerce+ Transaction Server security. Vault is ideal for this implementation path because it can also act as a Certification Authority (CA) to issue SSL certificates.
This guide will help you set up PostgreSQL in Commerce+ Transaction Server as a standalone database for testing purposes. In a minimal deployment the database is installed for you using the installation Helm charts. For minimal installations, this guide covers steps such as installation, database preparation, and schema loading.
Use the following instructions to install and configure Oracle Database for use with HCL Commerce+ Transaction Server.
You need to prepare Oracle Database for use with HCL Commerce+ Transaction Server by creating a table space and user.
You need to use a script to load the Commerce+ Transaction Server database schema.
The spiuser password is used for API communication between the different servers in your Commerce+ Transaction Server setup (e.g., Store server, Search server, Transaction server). This password needs to be set the same way on all servers to ensure they can communicate properly. It must be the same on the Store, Search, and Customization servers, and also in the database for the Transaction server.
Before you set up your production environment, ensure that you understand the Commerce+ Transaction Server application structure and that you are familiar with basic steps for setting up the environment.
Commerce+ Transaction Server supports several deployment configurations. The default configuration mode the provided Helm Chart uses is Vault configuration mode.
HCL Commerce+ Transaction Server includes an xC service that you can use to create custom plugins .
The following topics contain information that you can use in planning and implementing custom production and development environments.
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.
Topics in the Reference section contain all of the Commerce+ Transaction Server reference documentation.