Format the Control Message Header
- Natalie Gesin (Deactivated)
- Kinga Huszno
- Dmitry Donosiyan (Unlicensed)
The Header node of a control message contains unique identifiers of the message and parties involved, as well as timestamps controlling the message lifespan.
The following table lists the options and descriptions for the <header> node of a control message.
Option | Description |
|---|---|
messageId | Specifies the unique identifier of the control message within the coding scheme assigned to the message by the creating BPM, that is, the identifier must be unique within any specific MessageIdScheme attribute used as an identification scheme. |
sentBy | Specifies the universal resource identifier (URI) for the originator of a message instance within the specific partyIdScheme attribute used as an identification scheme. |
sendTo | Specifies the URI for the intended recipient of the message within the specific partyIdScheme attribute used as an identification scheme. |
replyTo | Specifies the URI for the intended recipient of the reply message, within the specific partyIdScheme attribute used as an identification scheme. |
creationTimestamp | Specifies the date and time from the source system for the creation of this message instance. |
expiryTimestamp | Specifies the date and time for the message to expire. If you do not specify an expiry timestamp, then all the files must be present before can send the control message using the files. |
The header is required, but the actual content for the options is only relevant when using a BPM.
Example:Â <Header> Node
<header>
   <messageId messageIdScheme="testScheme">testmessage_101</messageId>
   <sentBy>http://www.client.com</sentBy>
   <sendTo>http://www.eagleinvsys.com/eagleml-2-0_control_messages</sendTo>
   <replyTo>http://www.client.com/EagleReplyMessages</replyTo>
   <creationTimestamp>2012-08-02T22:13:32.272-05:00</creationTimestamp>
</header>Â
Â