Semarchy xDI
This integration extracts deliveries from Semarchy xDI and creates Semarchy xDG assets representing these data flows.
Semarchy xDI harvesting is automatically performed from a Runtime component when a delivery is published to this runtime.
You must configure the Runtime for this automated harvesting.
Configure the runtime
To configure harvesting for a given Runtime, add the metadataHarvester element to the engineParameters.xml configuration file of the Runtime.
<metadataHarvester>
<!-- Optional folder to persist the harvesting files -->
<parameter name="outputFolder"
value="harvesting"/>
<!-- Base URL for the Semarchy xDG api -->
<parameter name="apiEndpoint"
value="https:<your-tenant-name>.semarchy.net/api/xdg/v1" />
<!-- Semarchy xDG harvester request path -->
<parameter name="harvestingPath" value="/harvesting/xdi-runtime" />
<!-- Semarchy xDG personal access token token -->
<parameter name="authorizationToken"
value="<your-personal-access-token>"/>
<!-- Optional URN of the initiative assets are associated with. -->
<parameter name="defaultInitiativeUrn"
value="<initiative-urn>"/>
</metadataHarvester>The following table lists the parameters you can use in this configuration.
| Parameter | Description | ||
|---|---|---|---|
|
Optional Folder into which each harvesting session is dumped as a file named |
||
|
URL of the Semarchy xDG site. |
||
|
Personal access token used to authenticate to Semarchy xDG. It is required when
|
||
|
Optional URN of the initiative the harvested assets are associated with. |
| All parameters support the external value resolver syntax available in Semarchy xDI. |
Run the harvesting
After configuring the Runtime, any delivery published to this Runtime is automatically synchronized to Semarchy xDG.
| This integration is always stateful with no extra configuration. It keeps track of previous harvesting sessions, updating existing assets with changes performed in Semarchy xDI. |