Initiator Outbound Request—Private Process to BusinessConnect
The Initiator private process uses this message to handle outbound requests. Data that is sent is in a string or in binary form.
If both plainRequest
and inputFile
are passed, the plainRequest
node is used.
If both binaryRequest
and inputFile
are passed, the binaryRequest
node is used.
Subject Name |
prefix.installation.EZComm.INITIATOR.REQUEST External example: AX.BC.BC-ACME.EZComm.INITIATOR.REQUEST |
Field | Type | Required | Description |
---|---|---|---|
fromTp | String | No | Name of the trading partner initiating the transaction. |
toTp | String | Yes | Name of the trading partner receiving the transaction. |
transactionID | String | Yes |
It is a unique ID for transactions in the Initiator private processes environment. The private process creates this ID. |
closure | String | No | The private process generates the closure message and sends it to TIBCO BusinessConnect, it is required to return the contents of the closure to the
InitiatorResponse to ensure that the private process can match it with the original Initiator.Request.
|
binaryRequest | base64 Binary | No | Private processes use the binaryRequest field to send binary data to BusinessConnect Container Edition. |
as2-subject | String | No |
A short string identifying the topic of the AS2 message. The value in the as2-subject element overrides the value in the MIME Subject field. |
content-type | String | No | Content type of the passed data. |
content-disposition | String | No | Maps to MIME's content-disposition. This value, if provided, is set in the MIME Internet headers. |
inputFile | String | No | If a file reference is being passed to BusinessConnect Container Edition, this field is used. |
httpAttributes | |||
name | String | No |
Name of the httpAttribute. Note: It works only with
Request_Response operations.
|
value | String | No |
Value assigned to the httpAttribute. Note: It works only with
Request_Response operations.
|
Attachment | |||
name | String | No |
Name of the attachment file. For more information, see Multiple Attachments. |
content | Base64 Binary | No | Content for the attachment. |
fileName | String | No |
A file reference can be sent as an attachment. For more information, see Multiple Attachments. |
deleteFile | Boolean | No | If set to true, the file reference specified in the filename field is deleted after the completion (successful or otherwise) of the transaction. |
content-id | String | No |
Represents the content Id for the attachment. It must be specified and enforcement is performed at the BusinessWorks palette level. If this field is not specified, it is populated as |
content-type | String | No |
Represents the type of the message content. For more information, see Multiple Attachments. |