As of version 3.4 (released) (feature: FLA-11 - Getting issue details... STATUS  also available with 3.0.17), the mapping system has been enhanced to be able to send mapping requests to more than one systems via ODIL and manipulate multiple ODIL responses instead of one.

This is made possible with the usage of endpoint tags.

Use-case

The feature has been originally implemented to meet the 1 - 2 Lampelmeier scenario requirements.

One DASW Application should be able to send any Jobcard to two Target Systems, in order to the Service Order is created to both the DMS and the Service Order Planning Application of PlanIT.

At the same time the OAC Adapter should persistently store two JobCard ID Mappings and for the OD > PLanIT and the OD > Carlo respectively.

Overriding default behavior

As described in Neuro Integration Layer 2.0, the endpoint tags set with the OdilTargetEndpointTags setup key(s) are used when sending the request to ODIL by default.

To override the default behavior,

1. when Setting the Mapping Systems and Relations, provide an endpoint tag in Target Endpoint Tag text input.
2. on the methods you want to use the endpoint tag of the relation and not the default provided by the setup key(s), use the SyncContext attribute, with the Mapping ODILEntityAction as param

That way, then the OneDealer.Common.BusinessLayer.MappingSystem.ThinkRIT.Providers.IntegrationLayerSetupProvider.getTargetEndpointTags() is called, it will return the relation endpoint instead of the OdilTargetEndpointTags.

Related Links

• Changeset 62621: Merge latest SourceCore-FLA-11 to SourceCore - Repos (visualstudio.com)
• FLA-11 - Getting issue details... STATUS
• SyncContext