xml.xsd.CommonMessageHeader.xsd Maven / Gradle / Ivy
The newest version!
Unique identification of the initiator.
Destination of the endpoint of the initiator. Use when discriminating the Id with an location is of importance.
Unique identification of the endpoint being invoked.
Destination of the endpoint being invoked.
Collaboration Protocol Agreement ID provided by the initiator of the business value chain of Transactions.
Global Unique IDdentifier (GUID) for the one particular Conversation a message participates in.
Global Unique Identifier (GUID) for this message within the scope of the Conversation (see above).
Contains the request MessageId as part of the response in order to correlate two messages as part of the same MEP.
Unique identifier referring to an id passed from an external (front-end) system. This often uniquely identifies the Transaction as known with the initiator.
Date and time message was sent, including the time zone.
Used as extension on the HeaderFields for future use without backwards compatibility issues in existing implementations.
Repeating structure to accommodate extra properties
Attribute describing the name of the property
Attribute describing the value of the property
ID or name of the front-end system or application
System name, Full Qualified Domain Name (FQDN) or IP address of the front-end system. Typically used for black-listing or for some investigation purposed.
The name of the service being invoked
The name of the service context being invoked.
Identification of the action being performed
Identification of the paradigm, can be Request, Response, Event, Action, Solicit, Notification
The name of the operation being invoked.
The major version of the operation being invoked.
The TraceHeaderList part of the message is used to carry over parts of the header while invoking another operation or service. When a service is composed of multiple other services each header that is received will make up one element in the TraceHeaderList. A new TraceHeader entry is added to the bottom of the list. The newest entry is the lowest entry in a list.
This is a copy of the From element
This is a copy of the To element
This is a copy of the Service element
This element contains a copy of certain fields of the HeaderFields element
Unique Identifier for this message within the scope of the Conversation (see above). This is a copy of.
Date and time message was sent, including the time zone. This is a copy of.
Unique identifier referring to an id passed from an external (front-end) system. This is a copy of.
A boolean indicating if the invocation can be retried
The TransactionList part of the message holds information regarding the transaction the message is part of. This part should ONLY be used for SOx or other regulatory compliance requirements that have been identified for a certain service or system interface. A new Transaction entry is added to the bottom of the list. The newest entry is the lowest entry in a list.
For each transaction a new Transaction is added to bottom of the TransactionList.
When a system is called that is not part of the ESB or SOA platform, this field will hold the value Frontend or Backend respective to the type of system that is called
The unique identification used as reference when a Transaction enters or leaves the ESB.
The identification of the message. Must be unique within the TransactionList when multiple calls to external system
The unique identification of the external system
Date and time the message was sent to or received from the external system
Element which is the parent of all errors elements. Will only be present if the status equals ERROR
Canonical error code with fixed value.
Canonical reason description of the canonical error. It provides the reason why an error has occurred.
Description in which service and operation the error occurred.
List of specific non canonical errors.
Service specific error code
Application specific error code
Detailed description of the error that occurred.
Detailing the language of the error based on ISO 639-1 Code.
A string indicating if the invocation was successful or not. The field may have the value OK or ERROR
© 2015 - 2024 Weber Informatics LLC | Privacy Policy