- Production guidance on deploying Commerce+ Transaction Server
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.
- Prerequisites for deploying Commerce+ Transaction Server on a Kubernetes cluster
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.
- Preparing your Commerce+ Transaction Server environment
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.
- Planning your Commerce+ Transaction Server environment
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.
- Deploying HCL Commerce+ Transaction Server with Helm on Kubernetes
Commerce+ Transaction Server supports several deployment configurations. The default configuration mode the provided Helm Chart uses is Vault configuration mode.