search string side menu

BRIX On-Premises > BRIX On-Premises Enterprise > Administering BRIX Enterprise / Enable portable services

Enable portable services

For custom microservices in BRIX Enterprise, you can use the functionality of portable services. At the same time, it is possible to maintain state storage if you connect persistent storage. For example, when stopping or restarting a microservice with a database, the data in it will not be reset. Read more about services in Portable services.

The process of enabling portable services for the BRIX application consists of three steps:

  1. Prepare data storage systems.
  2. Make changes to the configuration file.
  3. Apply the parameters for BRIX Enterprise.

Step 1. Prepare data storage systems

The BRIX uses Longhorn as its storage system. For more details on configuring and installing this system, please refer to Install Longhorn.

Step 2. Make changes to the configuration file values-elma365.yaml

Начало внимание

The configuration file values-elma365.yaml is obtained and filled in during BRIX installation. Unthoughtful changes of parameters in this file may lead to the loss of BRIX application operability. Therefore, we recommend backing up the  file before making changes to it.

Конец внимание

Complete the values-elma365.yaml configuration file to configure the portable services:

  1. Make sure that the portable services are enabled, that is, the global.managedServices.enabled parameter is set to true.
  2. Specify the Longhorn storage system in the global.managedServices.defaultStorageClass parameter.
  3. In the global.managedServices.namespace specify the desired namespace where the portable services will be located.

global:
  ...
## enable portable services
  managedServices:
    enabled: true
## namespace for portable services
    namespace: elma365-applets
## storageclass for portable services
    defaultStorageClass: "longhorn"
...

Step 3. Apply portable service parameters for BRIX Enterprise

Update the BRIX application parameters using the values-elma365.yaml configuration file. The parameter update process takes 10–30 minutes, wait until it is completed.

When performing a parameter update, you need to:

  1. Determine the chart version with which the BRIX application was installed or updated.
  2. Use the same chart version to apply new parameters, to avoid side effects of the update on the application performance.

Update via the Internet

  1. Identify the version of the chart that was used to install the BRIX application:

helm show chart elma365/elma365

Command execution example:

enabling-portable-services

The version version line specifies the version of the chart with which the BRIX application was installed. This value should be specified for the --version flag by placing it instead of <elma365-chart-version>.

  1. Update the parameters specifying the installed version of the BRIX application and using the values-elma365.yaml configuration file:

helm upgrade --install elma365 elma365/elma365 -f values-elma365.yaml --version <elma365-chart-version> --timeout=30m --wait [-nnamespace]

Offline update without Internet access

Go to the catalog with the downloaded BRIX chart and run the command:

helm upgrade --install elma365 ./elma365 -f values-elma365.yaml --timeout=30m --wait[-nnamespace]

dump_db.html enable-tls-enterprise.html