Skip to main content
Configure Your Dataspace Services
Updated over a week ago

A dataspace in Tractus-X is a secure and collaborative ecosystem designed to facilitate seamless, trusted, and sovereign data exchange among participants in the automotive industry, fostering innovation and transparency. Our product, Dataspace OS, supports multiple dataspaces. This guide will walk you through configuring your Dataspace and the necessary services.

Pre-Requisite

  • You have successfully onboarded to the Portal with an Admin user role.

  • You have access to your Dataspace OS account.

  • If you need any assistance in getting access to your account, please reach out to us here >> support@cofinity-x.com

Instructions

Step 1: Actions in the Portal

  • Log in to the Portal and navigate to App Marketplace.

  • Search for Dataspace OS and subscribe to our app offering.

  • Once your subscription is activated, you will receive a confirmation email. Upon activation, Technical users are created which will allow you to properly configure your Dataspace OS services.

  • Return to the Portal and go to Technical User Management. You will find two new Technical Users:

    • One with the ‘DIM’ Role (not needed for this configuration).

    • Another Technical User with all necessary roles.

  • Note down the Client ID and Client Secret of the second technical user for use in later steps.

Step 2: Actions in Dataspace OS

  • Log in to Dataspace OS and go to the ‘Dataspaces’ tab.

  • Click ‘Add Dataspace’ and fill in the following fields:

    • Name: Choose a unique name for your Dataspace.

    • Type: This will be preselected.

    • Version: Select the latest version.

    • BPN: BPNLxxxxx

  • Once the Dataspace is configured, you can begin adding services.

Step 3: Adding your Services

The main services to add are:

  • Membership

  • Semantic Hub

  • EDC_Discovery

  • Connector_Registration

  • Navigate to your Dataspace and click on the ‘Add Service’ button.

  • Select the Service Type you want to configure and provide a name. For example:

  • Use the previously noted Client ID and Secret from the Portal for authorization.

Note: The Token URL, Client ID, and Client Secret will remain the same across all services created within the same environment.

Service URLs

  • Semantic Hub Service:
    PROD: https://semantic-hub.svc.cofinity-x.com/semantics
    Pre-Prod: https://semantic-hub.beta.cofinity-x.com/semantics

  • EDC Discovery Service:
    PROD: https://portal-backend.svc.cofinity-x.com/api/administration
    Pre-Prod: https://portal-backend.beta.cofinity-x.com/api/administration

  • Connector Registration Service:
    PROD: https://portal-backend.svc.cofinity-x.com/api/administration
    Pre-Prod: https://portal-backend.beta.cofinity-x.com/api/administration

Did this answer your question?