Page History

...

During the Dynamic Discovery, the Sending Processing Mode gets decorated. This means that some values are overwriten and others are left untouched. To correctly Sent or Forward a message, we need to know some required routing information (such as the PushConfiguration.Protocol.Url), but when using Dynamic Discovery, this information will be overwritten.

Anchor
Local Dynamic Discovery Profile (Default) Local Dynamic Discovery Profile (Default)

Local Dynamic Discovery Profile (Default)

The Local profile will use the locally stored SMP Configurations in the datastore to decorate the Sending Processing Mode. Following values will be overwritten; all other values are left untouched!

Anchor
Peppol Dynamic Discovery Profile Peppol Dynamic Discovery Profile

Peppol Dynamic Discovery Profile

...

<?xml version="1.0" encoding="utf-8"?>
<PMode
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  xmlns:xsd="http://www.w3.org/2001/XMLSchema"
  xmlns="eu:edelivery:as4:pmode">
  <Id>dynamic-discovery-send-pmode</Id>
  <DynamicDiscovery>
    <SmpProfile>Eu.EDelivery.AS4.Services.DynamicDiscovery.PeppolDynamicDiscoveryProfile, Eu.EDelivery.AS4, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null</SmpProfile>
    <Settings>
      <Setting key="SmlScheme">your-sml-scheme</Setting>
      <Setting key="SmpServerDomainName">your-sml-domain-name</Setting>
    </Settings>
  </DynamicDiscovery>
  ...
</PMode>

Anchor
Oasis Dynamic Discovery Profile Oasis Dynamic Discovery Profile

Oasis Dynamic Discovery Profile

Dynamic Discovery profile to retrieve a compliant eDelivery SMP profile based on the OASIS BDX Service Metadata Publishers (SMP) to extract information about the unknown receiver MSH. After a successful retrieval, the Sending Processing Mode can be extended with the endpoint address, service value/type, action, receiver party and the public encryption certificate of the receiving MSH.

...