Skip to main content

Deploying a Data Contract

note

This section is part of a series that uses the sample data contract introduced in the Data Contracts Overview page as a reference

If you followed the Creating a Data Contract tutorial you now have a system — including a data contract and its guardian — ready to be deployed.

You can proceed by creating a new release and triggering the deployment operation. Refer to the User Manual for additional help on deploying a system.

Data Contracts Provisioning​

A first indicator that everything went according to the plans is a (successfully executed) "Data Contracts provisioning" task in the resulting provisioning plan.

This task performs essential operations, including:

  • detecting any data contracts and guardians within the system descriptor
  • notifying the Computational Governance Platform (CGP) about these new resources: this ensures that the CGP is ready to collect and validate the monitoring results sent by guardians overseeing the data contracts
  • providing a policy reference in the CGP to each guardian tech adapter, enabling them to send monitoring results

Once deployment is complete, your data contract and guardian should be fully operational.

Witboost Marketplace​

The provisioning operation has published the data contract in the Witboost Marketplace, so you should now be able to locate it in the Marketplace's Data Contracts Graph. It displays:

  • all the data contracts exposed within your organization, along with their details
  • alerts for any violated data contracts
  • systems that are exposing and consuming data contracts

To monitor the status of a data contract, you can open its details in the graph, or go directly to the data contract page in the Marketplace, where a status widget will also be available.

note

In our sample data contract, the Compliant Topic is the only consumable subcomponent, so it will be the only one visible in the Marketplace. When a consumer system declares to read from this subcomponent, it effectively subscribes to the Data Contract defined at the parent component level. As a result, the Data Contracts Graph will show a link between the consumer system and the parent Data Contract — not directly with the subcomponent.

In scenarios where a consumable subcomponent is also defined as a data contract, the link will instead point directly to that subcomponent.