pub.xi.Router:outboundMessageObject
The outboundMessageObject service pub.xi.Router:outboundMessageObject, receives data from an outbound service on a webMethods adapter, creates a MessageObject from the data, and sends the MessageObject to one or more business partners through an SAP PI/PO Server. If you send the MessageObject synchronously, the service can also return results from the business partners.
Input Parameters
Name | Description |
payload | Document Type that contains the data from the outbound service. |
serviceName | Optional. String that contains the fully qualified name of the outbound service (for example, sample.xi.AddInts:sendAddIntsInput). Use this field if you want to step through or trace the outbound service. |
messageID | Optional. String that contains the message ID you want to use. Use this field if you want to override the GUID that the outboundMessageService automatically creates for the outbound MessageObject. The message ID must be a GUID and must conform to ISO Standard 11578. In addition, the message ID must be in the following format, where x is a number from 0 through 9 or letter from a through f: For example: 40c693b4-e592-11d6-90c1-f9060a125f3a The message ID must be globally unique or the SAP PI/PO Server will ignore the MessageObject. |
queueID | Optional. String that identifies the queue to which to send the outbound MessageObject. Use this field if you call the outboundMessageObject service from an asynchronous outbound service. If you specify this field, XI Adapter automatically sets the qualityOfService field in the outbound MessageObject's message header to ExactlyOnceInOrder. For more information about ExactlyOnceInOrder, see
Viewing Messages. |
traceLevel | Optional. String that specifies whether you want XI Adapter and the SAP PI/PO Server to store trace information in the reply MessageObject. The string also indicates how much trace information to store. Values are as follows:  0. Do not store trace information. 1. Store minimal trace information. 2. Store intermediate trace information. 3. Store all trace information. The default value is 0. |
Output Parameters
Name | Description |
SAP:MessageHeader | Document Type that contains the message header of the reply MessageObject. The Document Type contains the sender endpoint, the receiver endpoint, and the quality of service value, among other fields, from the reply MessageObject's message header. If an application error occurred on the business partner's system when the outboundMessageObject service tried to send the MessageObject, the message header also contains information about that error. To see the fields in the SAP:MessageHeader Document Type, see the wm.xi.interfaces.records folder in XI Adapter package. |
SAP:ErrorHeader | Optional. Document Type that contains a description of the technical error if a technical error occurred in the SAP PI/PO environment or on the business partner's system when the outboundMessageObject service tried to send the MessageObject. The Document Type contains the following fields: SAP:Code. Error code that consists of a category and an ID, separated by a period(For example, ROUTING.NO_RECEIVER_CASE_BE). See the SAP PI/PO Server documentation for a complete list of error codes. SAP:Text. Error message text. See the SAP PI/PO Server documentation for a complete list of messages. |
SAP:TraceHeader | Optional. String that contains the trace information, if you set the traceLevel input field to store trace information. |
payload | Optional. Document Type that contains a payload containing results from the business partner, if you sent the MessageObject synchronously. |
