The Deployment Specification should define execution architecture of systems that represent the assignment (deployment) of software artifacts (i3-MARKET building blocks) to deployment targets (usually nodes).

Nodes represent either hardware devices or software execution environments. They could be connected through communication paths to create network systems of arbitrary complexity. Artifacts represent concrete elements in the physical architecture.

Once the deployment has been provided, a complementary specification would be necessary to define how to deploy software within the i3-MARKET ecosystem. In the context of i3-MARKET we will be referring to this specification as Management Operative specification.

The tool gives guidance on how are defined the solutions for deploying i3-MARKET software within the i3-MARKET instances as part of the deployment operative. The i3-MARKET operative considers four possible deployment scenarios categorized as manual or automated deployments and oriented towards i3-MARKET developers and/or Data Spaces and/or Data Marketplaces infrastructure administrators.

For the deployment and management operative, Ansible and Zabbix have been proposed as configuration, management, and monitoring tools respectively for the central environment. It is left to the stakeholders to decide which tools will be used and deployed for managing and monitoring the marketplaces instances.