Configuring property files

You can deploy the ASI and AC pods with preconfigured tuning parameters on a Certified Container setup.

Configuring system_overrides.properties

You can configure the database pool properties using system_overrides.properties, which is present in ibm-b2bi-prod/properties. The values of the configured database pool properties are applicable for all ASI, AC and API pods, present in the cluster.

Important: Property folder ibm-b2bi-prod/properties is now renamed to ibm-b2bi-prod/config. You must copy existing customized property files from the folder ibm-b2bi-prod/properties to the folder ibm-b2bi-prod/config.

By default, the database pool properties are commented in the system_overrides.properties file. You must uncomment and replace {DB} with the applicable DB vendor.

For example:
#jdbcService.{DB}Pool_NoTrans.buffersize=500
If the vendor is db2, you can replace {DB} with db2 and uncomment the above line as:
jdbcService.db2Pool_NoTrans.buffersize=500
Note: If you modify any file present under the ibm-b2bi-prod helm chart properties directory and want to propagate the changes on a running setup, you must run the following command, for the changes to take effect.
helm upgrade <release-name> --timeout 3600s --recreate-pods

Configuring server-overrides.xml

A new server-overrides.xml is introduced to override or add new configurations to the Liberty from API pods that are present in the cluster. server-overrides.xml is in the folder ibm-b2bi-prod/config.

Refer to the below configuration example that can be added in the server-overrides.xml:

<server>
    <feature>mpOpenTracing-1.0</feature>
</server>

Configuring jvm.options

A new jvm.options is introduced to override or add any additional jvm configuration to the Liberty from API pods that are present in the cluster. jvm.options is in the folder ibm-b2bi-prod/config.

Refer to the below configuration example that can be added in the jvm.options:
-Xmx1221m
Note: Following jvm specific configuration options for liberty (API) from the values.yaml will be deprecated in the future releases:
  • .Values.setupCfg.libertyJvmOptions
  • .Values.api.env.jvmOptions

Upgrading

Refer to the below instructions when you upgrade Sterling B2B Integrator:

  • When you want to upgrade from previous versions of Sterling B2B Integrator to the current version, you must not copy the system_overrides.properties file of the previous installation directly. Instead, you must update the required values into the system_overrides.properties files packaged in the Helm chart before starting Helm install or upgrade.

  • With every new release of B2B Helm charts, you should copy the server-overrides.xml from the previous Helm chart's ibm-b2bi-prod/config folder to the new Helm chart's ibm-b2bi-prod/config folder. In case of IIM to Container deployment migration, you should move the existing customized server.xml configuration to server-overrides.xml from the folder ibm-b2bi-prod/config. If there is any overlap with configuration, you can verify messages.log to see which values are used by liberty at run-time from the server-overrides.xml.

  • With every new release of B2B Helm charts, you should copy the jvm.options from the previous Helm chart's ibm-b2bi-prod/config to the new Helm chart's ibm-b2bi-prod/config folder. In case of IIM to Container deployment migration, you should move the existing customized jvm.options configuration to jvm.options from the folder ibm-b2bi-prod/config.