Skip to main content
Version: 26.03

Operation View

Connector kit banner

General operation aspects​

As already mentioned in the adoption view, the connector divides into a control plane, which is typically an own service implementation and data planes, which could come in various forms. As mentioned, there is a Dataplane Signalling API which standardizes interactions between control and data plane. It is recommended to follow these instructions in order to provide a pluggable combination of control and data plane.

Catena-X: For Catena-X, the operation of a BPN-DID resolution service is required to provide the necessary mapping information between BPNLs and DIDs of participants.

Reference Implementation​

As all Eclipse Tractus-X products, the connector implementation comes with a helm chart that allows to easily deploy a setup in a kubernetes cluster. In fact, there are two different helm chart flavors, one supporting the deployment of a full-fledged setup with a control plane, a data plane and the required Postgres database, resp. Hashicorp vault. A second helm chart flavor allows to deploy the in-memory solution for testing purposes. The charts are published according to Eclipse Tractus-X rules defined in the TRGs.

The BPN-DID resolution service is packaged in the same manner and also is provided in an in-memory and a database flavor.

Configuration Parameters​

The connector requires a set of configuration parameters which are basically configured using the charts values file. Details are found in the Readme files of the helm charts.

Notice​

This work is licensed under the CC-BY-4.0.