Composite mode

Companion for integration offers the possibility to process the same XML file once with multiple outputs with the Composite extensions.

To configure the Composite extension, an asset of type C4I-CompositeConfigType is required.

This asset will contain a .properties file indicating how to configure each extension.

The mandatory properties for each extension are described under this section.

The extensions are configured with the prefix extensions.[#extension].

Each extension needs at least the following property : configAssetId to indicate the ID of the asset containing the mappings.

# Extension 1
extensions.[0].pluginId=...
extensions.[0].configAssetId=C4I-Config1
...
# Extension 2
extensions.[1].pluginId=...
extensions.[1].configAssetId=C4I-Config2
...

Where pluginId can be one of: fr.cantor.c4i.SQLDelivery, fr.cantor.c4i.MongoDBDelivery, fr.cantor.c4i.ActiveMQDelivery, fr.cantor.c4i.FileDelivery, fr.cantor.c4i.RESTDelivery, fr.cantor.c4i.KafkaDelivery, fr.cantor.c4i.ElasticSearchDelivery, fr.cantor.c4i.AWSDelivery or fr.cantor.c4i.PubSubDelivery. Multiple extensions of the same pluginId can be configured in a single properties file.

Multiple extensions can use the same mappings asset.

A maximum of 8 plugins can be configured in a single properties file.

The passwords to connect to the target databases are never stored in the properties file but rely on the standard password feature for configuring STEP plugins.

Variables

Additional properties defined in the .properties file can be accessed directly in the YAML configuration file.

For exemple, using the following .properties file :

# Extensions configuration 
...

# Custom variables
classificationId=TestClassification

And the following YAML file :

Product[ClassificationReference/@ClassificationID=$classificationId]:
  product[id]:
    - ./@ID: id

Will filter out products that are not linked to the chosen classification.