Glossary - European Commission | Choose your … · Web viewJava EE 7 Java EE provides an API and runtime environment for developing and running enterprise software, including network

EUROPEAN COMMISSIONDIRECTORATE-GENERALINFORMATICS

DIGIT.B.4Information Systems for Corporate financial, procurement & Policy solutions

European Commission

eDeliveryPMode Configuration

Date: 18/02/2016

Version: 0.04

Author: Kenneth Irvine

Reviewed by: Adrien FERIAL, Marcio SAMPAIO, Benoit DEBROUX, Pedro TAVARES

To be approved by: Joao RODRIGUES FRADE

Public:

Reference Number:

Document Print Date: 08 May 2023 Page 1 of 21

eDeliveryPMode ConfigurationVersion 0.04Published 18/02/2016Document History

Version Date Changes Modified Sections0.04 18/02/2016 Fourth Draft Takes on board input from

Pim van der Eijk.

0.03 04/02/2016 Third Draft Revised following review.Section on AS4 deployment governance removed.

0.02 26/01/2016 Second Draft Revised following review.

0.01 15/01/2016 First Draft n/a


eDeliveryPMode ConfigurationVersion 0.04Published 18/02/2016Contents

European Commission..............................................................................................................1Glossary....................................................................................................................................41 Introduction........................................................................................................................71.1 Purpose of this document..................................................................................................71.2 PMode overview...............................................................................................................71.3 Intended Readership.........................................................................................................72 PMode Parameters............................................................................................................82.1 Overview and description of each parameter.......................................................................82.2 Bare Minimum Attributes of the PModes..........................................................................13

2.2.1 Explanation of the structure of the PMode...............................................132.2.1.1 Process.....................................................................................................13

2.2.2 Example of customisation according to use cases.................................132.2.2.1 How to add a new partner linked to an existing Access Point............13

2.2.2.2 How to add a new Access Point.............................................................133 Information Sources.........................................................................................................13


eDeliveryPMode ConfigurationVersion 0.04Published 18/02/2016

Glossary

Term Description

Access Point An AS4 Gateway is referred to as an Access Point.

aka also known as

API Application programming interfaceSet of routines, protocols, and tools for building software applications.

AS2 Applicability Statement 2

AS4 Applicability Statement 4

B2B Business to Business

BRIS Business Registers Interconnection System

CEF Connecting Europe Facility

CEF AO CEF Architect Office

DB Database

DNS Domain Name System

Domibus ebMS3 Access Point based on the AS4 profile.

DSI Digital Service Infrastructure

ebCore ebXML Core

ebMS ebXML Messaging Service Specification

ebXML Electronic Business XMLProject to use XML to standardise the secure exchange of business data.

Eclipse A platform for developing software applications.Can be downloaded at http://www.eclipse.org/

e-CODEX e-Justice domain enabling citizens and businesses to have cross-border access of legal means in Europe.

EDI Electronic Data Interchange

eIDAS Electronic Identification and Trust Services

ESB Enterprise Service Bus

e-SENS Electronic Simple European Networked ServicesLarge-scale pilot project with the aim of consolidating, improving, and extending technical solutions based around the building block DSIs to foster digital interaction with


http://www.eclipse.org/

https://en.wikipedia.org/wiki/API


Term Description

public administrations across the EU.EU European Union

HTTP Hypertext Transfer Protocol

HTTPS aka HTTP over SSLHypertext Transfer Protocol Secure

J2EE Previous name for Java EE 7.

Java EE 7 Java EE provides an API and runtime environment for developing and running enterprise software, including network and web services, and other large-scale, multi-tiered, scalable, reliable, and secure network applications.

JBoss J2EE applications server for developing and deploying enterprise Java applications, Web applications and services, and portals.

MEP Message Exchange PatternThis is an AS4 term.

MPC Message Partition Channel.Different MPCs can exist, each defined as a Container.An MPC allows the flow of messages from a Sending MSH to a Receiving MSH to be partitioned into several flows, each of which is controlled separately.An MPC also allows flows from several Sending MSHs to be merged into a single unique flow that will be treated as such by a Receiving MSH.

MSH Message Service Handler

OASIS Advancing open standards for the information societyNon-profit, international consortium creating interoperable industry specifications based on public standards.

OMB

PAO Project and Architecture Office

PConf Processing Mode configurationA text file with extension .pconf is used by an Eclipse plug-in to generate the PMode XML file.

PEPPOL Pan-European Public Procurement Online

PKI Public Key Infrastructure

PMode Processing Mode

PoC Point of ContactName of contact person.

SML Service Metadata Locator

SMO Stakeholder Management Office

SMP Service Metadata Publisher


https://en.wikipedia.org/wiki/Web_service

https://en.wikipedia.org/wiki/Network_service

https://en.wikipedia.org/wiki/Enterprise_software

https://en.wikipedia.org/wiki/API


Term Description

SMTP Simple Mail Transfer Protocol

SOAP Simple Object Access Protocol

SSL Secure Sockets Layer

TC Technical Committee

TO Technical Office

URL Uniform Resource Locator

XML eXtensible Markup Language



1 INTRODUCTION

A processing mode – or PMode – is a collection of parameters that determine how user messages are exchanged between a pair of Access Points with respect to quality of service, transmission mode, and error handling. A PMode maps the recipient Access Point from the partyId, which represents the backend offices associated to this Access Point.

1.1 Purpose of this document

This document analyses the PMode configuration possibilities. It identifies the relevant eDelivery configuration options, and lists the reasons and implications for each option.This allows usage profiles to be intelligently created and provides implementation guidelines for the use of PMode. The term profile can be likened to concepts such as scenario, business process or business collaboration.These general guidelines give further advantages such as increased consistency, easier interoperability and simplified deployment are to be expected.Note however that precise guidelines cannot be given for some configuration parameters as they are domain-dependent. These general guidelines can nevertheless be a useful guidance for project implementers in the domain.

1.2 PMode overview

What is the role of the PMode in an AS4 exchange? A PMode describes how messages are exchanged between two AS4 partners. A PMode is defined in an XML file1 which contains the identifiers of each Access Point. In a PMode file an Access Point is identified as a party.A party is defined as an initiator party if it can send a message to another party.A party is defined as a responder party if it can respond to a message it has received from an initiator party.A party can be defined as both an initiator party and a responder party.Adding, modifying or deleting a participant implies modifying the corresponding PMode files.

1.3 Intended Readership

Business Owner OMB

Project Managers

Architects

Analysts

Developers

Testers

End users

1 In a Production or Acceptance environment the Domibus plugin for Eclipse generates a PMode XML file for each instance. This XML file is updated every time a participant is added, modified or deleted.A copy of the XML file can be edited for testing purposes.


2 PMODE PARAMETERS

2.1 AS4 Business Metadata

PMode uses the eb:Messaging header container which provides rich message metadata. This metadata – including business-related metadata – is used for routing, monitoring and validation, and can be configured for specific exchanges.2.1.1 ServiceAS4 defines a default service at PMode level.The ebMS3 standard defines the PMode[].BusinessInfo.Service element as: “This required element occurs once. It is a string identifying the service that acts on the message and it is specified by the designer of the service.”The header is a non-empty-string of XML schema type and its value is a PMode parameter, meaning that communication partners are expected to define specific values for specific process modes. i.e. to define specific values for various types of messages.The Service element can have a type attribute in order to categorise services.Some established very large scale deployments of ebMS use the Service header for routing messages to dedicated, service-specific endpoints, where the routing can be carried out by SOAP-aware XML firewalls or similar hardware appliances, and in this way reduce the burden on more traditional ebMS endpoints.Service information is also relevant to monitoring and reporting.Organisations may have different business applications responsible for handling different services. They may also use ESB or another middleware platform to route messages from their AS4 endpoint to the relevant internal service.One business process is unrelated to and has no side-effects on other business processes that may also involve choreographed message exchanges.Note that – as a PMode parameter – both sender and receiver need to agree on values. It isn't possible for the sender to invoke a service on a partner that offers a generic document handling service (or vice versa). So the decision for a class of exchanges needs to be made jointly by the parties involved.2.1.2 ActionAS4 defines a default ACTION at PMode level.The ebMS3 standard defines PMode[].BusinessInfo.Action element as: “This required element occurs once. It is a string identifying the service that acts on the message and it is specified by the designer of the service.”The action can be used to select a schema against which to validate a received payload.Action information is also relevant to monitoring and reporting.2.1.3 RoleThe Role element is mandatory with From and To party identifier elements.The ebMS3 standard defines PMode[].BusinessInfo.Role element as:: “The required eb:Role element occurs once, and identifies – for the sending Party – the authorised role of the From element, or –for the receiving Party – the authorised role of the To element.The value of the Role element is a non-empty string, with a default value of:http://docs.oasis-open.org/ebxml-msg/ebms/v3.0/ns/core/200704/defaultRoleRole information is also relevant to monitoring and reporting.


http://docs.oasis-open.org/ebxml-msg/ebms/v3.0/ns/core/200704/defaultRole

2.2 Overview and description of each parameter

Among others, the AS4 message headers Service, Action and Role are covered in the table below. Service, Action and Role are mandatory header elements in AS4, so a value has to be selected for them and agreed between sender and receiver.Per project the assigned Business Analyst will establish for the required business process configuration values for the various PMode parameters:

Parameter Explanation on useMPCs Container which defines the different Message Partition

Channels. A Message Partition Channel is …MPC A Message Partition Channel allows the

partition into several flows of the flow of messages from a Sending MSH to a Receiving MSH, each of which is controlled separately. An MPC also allows merging flows from several Sending MSHs into a unique flow that will be treated as a single flow by a Receiving MSH.

qualifiedNameenableddefaultretention_downloaded Retention interval for messages already

delivered to the backend.retention_undownloaded Retention interval for messages not yet

delivered to the backend.businessProcessConfigurations Container which defines the different Business Process

Configurations. A Business Process Configuration is …businessProcessConfiguration

businessProcesses Container which defines the different Business Processes. A Business Process is …

businessProcessroles Container which defines the different Roles. A Role is

…role:

The value of the role element is a non-empty string, with a default value of http://docs.oasis-open.org/ebxml-msg/ebms/v3.0/ns/core/200704/defaultRole

Other possible values are subject to partner agreement.

The required role element occurs once, and identifies the authorised role as follows:

When the role is present as a child of the From element:

o It can be seen as the fromAuthorizedRole of the Party sending the message.

o This is the Initiator role, which can be seen as being the Buyer in the transaction.

When the role is present as a child of the To element:

o It can be seen as the toAuthorizedRole of the Party receiving the message.

o This is the Responder role, which can be seen as being the Seller in the transaction.

processes Container which defines the different Processes. A Process is …

process In Process everything is plugged together.parties Container which defines the different Parties, which

can be both Initiator Parties and Responder Parties. A


Parameter Explanation on useParty is …

partypartyId The ebCore Party ID type can simply be used

as an identifier format and therefore as a convention for values to be used in configuration and – as such – does not require any specific solution building block.

partyIdTypes Container which defines the different Party Identification Types. A Party Identification Type is …

partyIdType Message Unit bundling happens when the Messaging element contains multiple child elements or Units (either User Message Units or Signal Message Units).

endpoint The endpoint is a party attribute that contains the link to the MSH.The value of this parameter represents the address (endpoint URL) of the Receiver MSH (or Receiver Party) to which Messages under this PMode leg are to be sent. Note that a URL generally determines the transport protocol (e.g. if the endpoint is an email address, then the transport protocol must be SMTP; if the address scheme is "http", then the transport protocol must be HTTP).

allowChunking Chunking is a memory management strategy to aggregate related memory-allocation requests.

legConfigurations Container which defines the different Leg Configurations. A Leg Configuration is …

legConfiguration: service action reliability security receptionAwareness payloadProfile errorHandling compressPayloads

legs Container which defines the different Legs. A Leg is …leg Because messages in the same MEP may be subject to

different requirements - e.g. the reliability, security and error reporting of a response may not be the same as for a request – the PMode will be divided into legs. Each user message label in an ebMS MEP is associated with a PMode leg. Each PMode leg has a full set of parameters for the six categories above (except for General Parameters), even though in many cases parameters will have the same value across the MEP legs. Signal messages that implement transport channel bindings (such as PullRequest) are also controlled by the same categories of parameters, except for BusinessInfo group.

AS4 Container which defines the different means of exchange of Business-to-business documents using AS4 Web services.

receptionAwareness: These parameters are stored in a composite


IRVINE Kenneth (DIGIT-EXT), 03/02/16,

?

Parameter Explanation on use retryTimeout: timeout in seconds

e.g. 1 retryCount: total number of retries

e.g. 6 strategy: frequency of retries

The only strategy value currently available is CONSTANT.

duplicateDetection: check for duplicates in order to prevent receiving the same message twice.The only duplicateDetection value currently available is TRUE.

string.

reliability: nonRepudiation: prevents a recipient from

denying receipt of a message.Value of TRUE => non-repudiation of receiptValue of FALSE => reception awareness only

replyPattern:Value of Response => send a receipt on the HTTP response or back-channel.Value of Callback => send a receipt on a separate connection.

securities Container which defines the different Securities. A Security is …

securitypolicy The parameter in the PConf file defines the

name of a WS-SecurityPolicy file.Here we can specify whether or not we're using the encryption. The typical default setting will be to use encryption.A project should not fail to use encryption without good and declared reason.

signatureMethod This parameter is not supported by WS-SecurityPolicy and therefore it is defined separately.

agreements Container which defines the different Agreements. An Agreement is …

agreement: a URL This OPTIONAL element occurs zero times or once. The AgreementRef element is a string that identifies the entity or artifact governing the exchange of messages between the parties.

actions Container which defines the different Actions. An Action is a Use Case.e.g. retrieve company

push companyupdate companysearch for company…

action This REQUIRED element occurs once. The element is a string identifying an operation or an activity within a Service that may support several of these

services Container which defines the different Services. A Service represents the Business.



Describe the impact of configuration on Security.

Parameter Explanation on usee.g. BRIS is a service.

serviceserviceTypes Type This REQUIRED element occurs once. It is a

string identifying the service that acts on the message and it is specified by the designer of the service.

MEPs Container which defines the different Message Exchange Patterns. A Message Exchange Pattern is …

MEP [@Legs] An ebMS MEP defines a typical choreography of ebMS User Messages which are all related through the use of the referencing feature (RefToMessageId). Each message of an MEP instance refers to a previous message of the same instance, unless it is the first one to occur. Messages are associated with a label (e.g. request, reply) that precisely identifies their direction between the parties involved and their role in the choreography.

bindings Container which defines the different Bindings. A Binding is …

binding The previous definition of ebMS MEP is quite abstract and ignores any binding consideration to the transport protocol. This is intentional, so that application level MEPs can be mapped to ebMS MEPs independently from the transport protocol to be used.

initiatorRole: defaultRole The message producer carries out the initiator role.

responderRole: defaultRole The message producer carries out the responder role.

properties Container which defines the different Properties. A Property is …

propertypropertySet Container which defines the different Property Sets. A

Property Set is …propertySetpropertyRef

payloadProfiles Container which defines the different Payload Profiles. A Payload Profile is …

payloadProfilemaxSize Maximum size allowed for a message.attachmentpayloads Container which defines the different Payloads. A

Payload is …payload This parameter allows specifying some

constraint or profile on the payload. It specifies a list of payload parts.A payload part is a data structure that consists of five properties:

1. name (or Content-ID) that is the part identifier, and can be used as an index in the notation PayloadProfile;

2. MIME data type (text/xml, application/pdf, etc.);

3. name of the applicable XML Schema file if


Parameter Explanation on usethe MIME data type is text/xml;

4. maximum size in kilobytes;5. Boolean string indicating whether the part is

expected or optional, within the User message.

The message payload(s) must match this profile.

errorHandlings Container which defines the different means of Handling Errors.

errorHandlingerrorAsResponse This Boolean parameter indicates (if TRUE) that errors

generated from receiving a message in error are sent over the back-channel of the underlying protocol associated with the message in error. If FALSE, such errors are not sent over the back-channel.

processErrorNotifyProducer This Boolean parameter indicates (if TRUE) that the Producer (application/party) of a User Message matching this PMode should be notified when an error occurs in the Sending MSH, during processing of the User Message to be sent.

processErrorNotifyConsumer This Boolean parameter indicates (if TRUE) that the Consumer (application/party) of a User Message matching this PMode should be notified when an error occurs in the Receiving MSH, during processing of the received User message.

deliveryFailureNotifyProducer When sending a message with this reliability requirement (Submit invocation), one of the two following outcomes will occur: - The Receiving MSH successfully delivers (Deliver invocation) the message to the Consumer.- The Sending MSH notifies (Notify invocation) the Producer of a delivery failure.

2.3 Approaches for PMode profiles

Values for Service, Action and Role can be defined using multiple approaches.Three approaches are presented:

1. Service-Oriented approach2. Document-Based approach3. Approach based on using default values.

This approach can be validated against a sample application from a particular domain.

2.3.1 Service Oriented ApproachIn a service-oriented approach, the exchange involves the invocation of actions on services. In a B2B setting, there is typically a peer-to-peer communication among actors participating in specific roles. Parties can take turn to initiate some actions and respond to others.An action is typically best named using a combination of a verb and a direct-object noun that relate to some resource in the real world on which the action is to take place.In this approach, the PMode Service parameter is set to the business service, and the PMode Action parameter is set to the action associated with the exchange.The Service is the name of the business process the service implements: e.g. OrderingThe Action is the name of an actions: e.g. SubmitOrder, AcceptOrder, RejectOrder



Business?


Business?

The Role is the role of an actor: Buyer, SellerThis approach reflects the distinction between positive and negative responses. For a pair of parties P1 and P2 – where P1 is the Buyer and P2 is the seller – three PModes need to be defined. As such, this approach can be an issue for domains that have not modelled their interactions on a service-oriented approach, in which case the PMode designer has to specify which actions are associated with an exchange.The service-oriented approach has been successfully carried out in several AS4 case studies.2.3.2 Document Oriented ApproachIn a document-oriented approach, the exchange involves the business document (rather than the business action).This approach could be used for domains that have modelled their exchanges on a document-oriented style, or which have an existing EDI communication that they want to migrate with minimal changes.In this approach, the PMode Action parameter is set to the document type associated with the exchange: e.g. Order, OrderResponseNote that this approach does not reflect the difference between positive and negative responses.

Furthermore, the approach does not fit the purpose and semantics of the AS4 Action header element. However, if a community wants to adopt this approach, there are no practical barriers, as for any AS4 product the values are un-interpreted strings.2.3.3 Default ApproachAS4 defines default values for Service, Action and Role. In this approach, for any exchange between a P1 and P2, only one PMode needs to be defined. Effectively, the AS4 metadata feature is disabled and none of its benefits (ability to support routing, monitoring, validation ...) apply.

2.3.4 Explanation of the structure of the PMode

2.3.4.1 Process

2.3.5 Example of customisation according to use cases

2.3.5.1 How to add a new partner linked to an existing Access Point

2.3.5.2 How to add a new Access Point


3 PMODE EXAMPLE

3.1 Domibus Configuration

<?xml version="1.0" encoding="UTF-8"?><db:configuration xmlns:db="http://domibus.eu/configuration"

xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"xsi:schemaLocation="http://domibus.eu/configuration

file:/C:/development/git-repos/domibus/Domibus-MSH/domibus-configuration.xsd" party="blue_gw">

<mpcs><mpc name="defaultMpc"

qualifiedName="http://docs.oasis-open.org/ebxml-msg/ebms/v3.0/ns/core/200704/defaultMPC"

enabled="true" default="true" retention_downloaded="0" retention_undownloaded="60"/>

</mpcs><businessProcesses>

<roles><role name="defaultInitiatorRole"

value="http://docs.oasis-open.org/ebxml-msg/ebms/v3.0/ns/core/200704/initiator"/><role name="defaultResponderRole"

value="http://docs.oasis-open.org/ebxml-msg/ebms/v3.0/ns/core/200704/responder"/>

</roles><parties>

<partyIdTypes><partyIdType name="partyTypeEmpty" value=""/>

</partyIdTypes><party name="ibmgw"

endpoint="http://5.153.46.53:29001/AS4" allowChunking="false"

><identifier partyId="urn:oasis:names:tc:ebcore:partyid-

type:unregistered:IBMgw" partyIdType="partyTypeEmpty"/></party><party name="domibus_de"

endpoint="http://test.edelivery.it.nrw.de/domibus-msh" allowChunking="false"


type:unregistered:domibus-de" partyIdType="partyTypeEmpty"/></party><party name="flame"

endpoint="http://fmstest.flame.co.za:8080/AS4" allowChunking="false"


type:unregistered:flame" partyIdType="partyTypeEmpty"/></party>


<party name="holodeck" endpoint="http://msh.holodeck-b2b.org:8080/msh" allowChunking="false"


type:unregistered:holodeck-b2b" partyIdType="partyTypeEmpty"/></party><party name="axway"

endpoint="http://208.67.130.9/exchange/axwayas4" allowChunking="false"


type:unregistered:axway" partyIdType="partyTypeEmpty"/></party><party name="cefgw"

endpoint="https://secure.gateway.eu/as4" allowChunking="false"


type:unregistered:CEF" partyIdType="partyTypeEmpty"/></party><party name="blue_gw_two"

endpoint="http://d02di13390fff44dit.net1.cec.eu.int:7001/domibus/services/msh" allowChunking="false"


type:unregistered:domibus-blue_two" partyIdType="partyTypeEmpty"/></party><party name="red_gw"

endpoint="http://d02di1339044dit.net1.cec.eu.int:7001/domibus/services/msh" allowChunking="false"


type:unregistered:domibus-red" partyIdType="partyTypeEmpty"/></party><party name="blue_gw"

endpoint="http://D02DI1339058DIT.net1.cec.eu.int:8080/domibus/services/msh" allowChunking="false"


type:unregistered:domibus-blue" partyIdType="partyTypeEmpty"/></party>

</parties><meps>

<mep name="oneway" value="http://docs.oasis-open.org/ebxml-msg/ebms/v3.0/ns/core/200704/oneWay"/>

<mep name="twoway" value="http://docs.oasis-open.org/ebxml-msg/ebms/v3.0/ns/core/200704/twoWay"/>

<binding name="push" value="http://docs.oasis-open.org/ebxml-msg/ebms/v3.0/ns/core/200704/push"/>

<binding name="pushAndPush" value="http://docs.oasis-open.org/ebxml-msg/ebms/v3.0/ns/core/200704/push-and-push"/>


</meps><properties>

<property name="originalSenderProperty" key="originalSender" datatype="string" required="true"/>

<property name="finalRecipientProperty" key="finalRecipient" datatype="string" required="true"/>

<propertySet name="ecodexPropertySet"><propertyRef property="finalRecipientProperty"/><propertyRef property="originalSenderProperty"/>

</propertySet></properties><payloadProfiles></payloadProfiles><securities>

<security name="signOnly"policy="signOnly.xml"signatureMethod="RSA_SHA256" />

<security name="noSigNoEnc"policy="doNothingPolicy.xml"signatureMethod="RSA_SHA256" />

<security name="signAndEncrypt"policy="signEncrypt.xml"signatureMethod="RSA_SHA256" />

</securities><errorHandlings>

<errorHandling name="demoErrorHandling" errorAsResponse="true" businessErrorNotifyProducer="false"businessErrorNotifyConsumer="false" deliveryFailureNotifyProducer="false"/>

</errorHandlings><agreements>

<agreement name="agreementEmpty" value="" type=""/></agreements><services>

<service name="testService1" value="bdx:noprocess" type="tc1"/><service name="testService2" value="bdx:noprocess" type="tc2"/><service name="testService3" value="bdx:noprocess" type="tc3"/><service name="noSecService" value="InternalTesting" />

</services><actions>

<action name="tc1Action" value="TC1Leg1"/><action name="tc2Action" value="TC2Leg1"/><action name="tc3ActionLeg1" value="TC3Leg1"/><action name="tc3ActionLeg2" value="TC3Leg2"/><action name="noSecAction" value="NoSecurity"/>

</actions><as4>

<receptionAwareness name="receptionAwareness" retry="5;4;CONSTANT" duplicateDetection="true"/>


<reliability name="AS4Reliability" nonRepudiation="true" replyPattern="response"/>

<reliability name="noReliability" nonRepudiation="false" replyPattern="response"/>

</as4><legConfigurations>

<legConfiguration name="pushTestcase1tc1Action" service="testService1" action="tc1Action" defaultMpc="defaultMpc" reliability="AS4Reliability" security="signOnly" receptionAwareness="receptionAwareness" propertySet="ecodexPropertySet"errorHandling="demoErrorHandling"compressPayloads="false"></legConfiguration>

<legConfiguration name="pushTestcase2tc2Action" service="testService2" action="tc2Action" defaultMpc="defaultMpc" reliability="AS4Reliability" security="signAndEncrypt" receptionAwareness="receptionAwareness" propertySet="ecodexPropertySet"errorHandling="demoErrorHandling"compressPayloads="false"></legConfiguration>

<legConfiguration name="pushTestcase3Leg1tc3ActionLeg1" service="testService3" action="tc3ActionLeg1" defaultMpc="defaultMpc" reliability="AS4Reliability" security="signAndEncrypt" receptionAwareness="receptionAwareness" propertySet="ecodexPropertySet"errorHandling="demoErrorHandling"compressPayloads="false"></legConfiguration>

<legConfiguration name="pushTestcase3Leg2tc3ActionLeg2" service="testService3" action="tc3ActionLeg2" defaultMpc="defaultMpc" reliability="AS4Reliability" security="signAndEncrypt" receptionAwareness="receptionAwareness" propertySet="ecodexPropertySet"errorHandling="demoErrorHandling"compressPayloads="false"></legConfiguration>

<legConfiguration name="pushNoSecnoSecAction" service="noSecService" action="noSecAction" defaultMpc="defaultMpc" reliability="noReliability"


security="noSigNoEnc" receptionAwareness="receptionAwareness" propertySet="ecodexPropertySet"errorHandling="demoErrorHandling"compressPayloads="false"></legConfiguration>

</legConfigurations><process name="tc1Process"

agreement="agreementEmpty" mep="oneway" binding="push" initiatorRole="defaultInitiatorRole" responderRole="defaultResponderRole">

<initiatorParties><initiatorParty name="domibus_de"/><initiatorParty name="ibmgw"/><initiatorParty name="flame"/><initiatorParty name="holodeck"/><initiatorParty name="axway"/><initiatorParty name="blue_gw"/><initiatorParty name="blue_gw_two"/><initiatorParty name="red_gw"/>

</initiatorParties><responderParties>

<responderParty name="domibus_de"/><responderParty name="ibmgw"/><responderParty name="flame"/><responderParty name="holodeck"/><responderParty name="axway"/><responderParty name="blue_gw"/><responderParty name="blue_gw_two"/><responderParty name="red_gw"/>

</responderParties><legs>

<leg name="pushTestcase1tc1Action"/></legs>

</process><process name="tc2Process"




<responderParty name="domibus_de"/>


<responderParty name="ibmgw"/><responderParty name="flame"/><responderParty name="holodeck"/><responderParty name="axway"/><responderParty name="blue_gw"/><responderParty name="blue_gw_two"/><responderParty name="red_gw"/>


<leg name="pushTestcase2tc2Action"/></legs>

</process><process name="tc3Process"

agreement="agreementEmpty" mep="twoway" binding="pushAndPush" initiatorRole="defaultInitiatorRole" responderRole="defaultResponderRole">



<responderParty name="domibus_de"/><responderParty name="ibmgw"/><responderParty name="flame"/><responderParty name="holodeck"/><responderParty name="axway"/><responderParty name="blue_gw"/><responderParty name="blue_gw_two"/><responderParty name="red_gw"/>


<leg name="pushTestcase3Leg1tc3ActionLeg1"/><leg name="pushTestcase3Leg2tc3ActionLeg2"/>

</legs></process><process name="noSecProcess"


<initiatorParties> <initiatorParty name="blue_gw_two"/>

<initiatorParty name="blue_gw"/><initiatorParty name="red_gw"/>



<responderParty name="blue_gw_two"/><responderParty name="blue_gw"/><responderParty name="red_gw"/>


<leg name="pushNoSecnoSecAction"/></legs>

</process></businessProcesses>

</db:configuration>

4 INFORMATION SOURCES

DocumenteDelivery Pilot Quick Start Guide_FINAL_3_2_0_ver03.pdf(Building Block DSI_IntroDocument) (eDelivery) (v1 02).pdf(PModes_Presentation) (eDelivery)(v1.1).pptxeDelivery Pilot Quick Start Guide_FINAL_3_2_0_ver03.docx

Ticket Title

Joinup Reference Title


Documents

Glossary - European Commission | Choose your … · Web viewJava EE 7 Java EE provides an API and runtime environment for developing and running enterprise software, including network