Installing Sterling B2B Integrator using Certified Container

You can use a Certified Container to install and deploy Sterling B2B Integrator.

A Certified Container is a package manager for Kubernetes that contains Helm charts and allows developers and operators to easily package, configure, and deploy applications and services onto Kubernetes clusters.


The following are the prerequisites for a successful use of the Certified Container:
  1. Installing a Kubernetes cluster and configuring a local copy of kubectl
  2. Applying security configurations to your installation
  3. Installing and configuring Helm
    Note: For more information, see Installing Helm.


A Certified Container provides the basic features of a package manager to help with the installation and maintenance of software. Using Helm, you can:
  • Install software
  • Automatically install software dependencies
  • Upgrade software
  • Configure software deployments
  • Fetch software packages from repositories
It uses these important concepts:
  • chart - a bundle of information necessary to create an instance of a Kubernetes application.
  • config - contains configuration information that can be merged into a packaged chart to create a releasable object.
  • release - a running instance of a chart, combined with a specific config.
It uses the following:
  • A packaging format called charts.
  • A command line tool Helm, which provides the user interface.

Helm Charts

A Chart is a collection of files that consist of a few YAML configuration files and templates rendered into Kubernetes manifest files. They are created as files laid out in a particular directory tree, which you can package into versioned archives that the system deploys.

A Chart is organized as a collection of files inside a directory. The directory name is the name of the Chart.

For more information on the Chart structure, see Helm Charts.

Helm Commands

You can use the following sequence of commands to install Sterling B2B Integrator.

1. helm package <path/to/helm/Charts/b2bi folder>
2. helm install <path for the *.tgz file created from above command>
The Database setup runs as a preinstalled job during an Helm install or an upgrade. To ensure the Helm install or upgrade command does not timeout, add the following option to the Helm install command. The timeout value (in seconds) is the approximate time the stem takes to set up the database on the environment.

helm install <release name> --values=<path to custom values yaml> <path to charts directory>

Here is a list of basic Helm commands.

1. $ helm init -      To begin working with Helm. Installs Tiller to your running Kubernetes cluster and sets up 
                      the required local configuration.
2. $ helm create -    Creates a new Chart with the given name.
3. $ helm delete -    Deletes the release from Kubernetes.
4. $ helm package -   Packages a Chart directory into a Chart.
4. $ helm install -   Installs a Chart.
5. $ helm upgrade -   Upgrades to a new release.
6. $ helm rollback -  Rolls back a release to a previous version.

For more information on other commands and options, see Helm Commands.