This repository is part of the overarching Eclipse Tractus-X project.
BPDM is an acronym for business partner data management. This project serves two main purposes:
- Provide services for querying and sharing business partner information
- Establish an infrastructure for realising the Golden Record process which turns business partner information from sharing members to Golden Records, that is cleaned and enriched business partner data uniquely identified by a business partner number (BPN)
The following sections give an overview of this repository's structure.
Heart of this project is the source code for the BPDM applications. Together, those applications provide the infrastucture for the Golden Record process. The BPDM solution contains the following applications:
- Pool: The single source of truth for Golden Records and BPNs
- Gate: Holds business partner data from sharing members and allows them to share the data to the golden record process
- Orchestrator: Facilitates business partner data between Gate, Pool and external cleaning services
- Cleaning Service Dummy: A dummy implementation of a cleaning service, responsible for processing business partner data and turning it one step closer to a Golden Record
Subfolders for BPDM applications are easily recognizable by the bpdm prefix.
Please consult the INSTALL documentation file for in-depth installation instructions.
BPDM is an application environment designed to be interacted with over APIs. Therefore, please consult the api documentation for getting to know how to use BPDM.
For releasing new Docker images of the BPDM Pool and Gate we use GitHub Actions/Workflows, by convention found in the .github/workflows folder.
On pushing to the main branch or creating a new Git tag the applications are containerized and pushed to the repository's GitHub Container Registry.
The containerization of the applications is based on the Dockerfiles found in the root folders of the Pool and Gate modules.
Released images are tagged according to the main branch or Git tag name.
In addition to the release of the applications' Docker images, there is also a workflow to release a corresponding Helm chart on Git tag creation.
Helm charts are released via the helm/chart-releaser-action and are stored in the gh-pages branch of the
repository.
Furthermore, apart from the release workflows there also exists code scanning workflows for quality assurance:
- Before any release of Docker images GitHub executes unit and integration tests.
- Periodically, workflows execute a KICS and Trivy scan to ensure quality standards of the Docker images and Helm charts.
- For a more thorough security check the packaged applications are send to a VeraCode scan, which happens periodically and after a push to main
This README is just the gateway to more detailed documentation files that may be found in the docs folder
Below you can find information to the used Docker images in this application:
This work is licensed under the Apache-2.0.
- SPDX-License-Identifier: Apache-2.0
- SPDX-FileCopyrightText: 2023,2024 ZF Friedrichshafen AG
- SPDX-FileCopyrightText: 2023,2024 SAP SE
- SPDX-FileCopyrightText: 2023,2024 Bayerische Motoren Werke Aktiengesellschaft (BMW AG)
- SPDX-FileCopyrightText: 2023,2024 Mercedes Benz Group
- SPDX-FileCopyrightText: 2023,2024 Robert Bosch GmbH
- SPDX-FileCopyrightText: 2023,2024 Schaeffler AG
- SPDX-FileCopyrightText: 2023,2024 Contributors to the Eclipse Foundation
- Source URL: https://github.com/eclipse-tractusx/bpdm