Describing the FaultNotification Element

24-26 Developers Guide for Oracle Application Integration Architecture Foundation Pack

24.7.3 Describing the FaultNotification Element

This section includes the following topics: ■ Section 24.7.3.1, FaultMessage Element ■ Section 24.7.3.2, IntermediateMessageHop Elements ■ Section 24.7.3.3, FaultingService Element This section provides details about the FaultNotification element in the Oracle AIA fault message schema, as shown in Figure 24–9 . Fault notification elements are discussed in Table 24–4 . Table 24–3 B2BMReference Elements Name Purpose Details B2BMID Provides the message ID used to identify the transaction in Oracle B2B. A user can use this message ID to query for a failed business message in Oracle B2B and retry the failed transaction. For more information, see Chapter 16, Introduction to B2B Integration Using AIA. CollaborationID Provides the collaboration ID that is common across multiple request-and-response messages related to the same business transaction. For more information, see Chapter 16, Introduction to B2B Integration Using AIA. ReplyToMessageID Provides the ID of the reply-to message. For more information, see Chapter 16, Introduction to B2B Integration Using AIA. B2BDocumentType TypeCode Provides the document type of the failed transaction in Oracle B2B. This information from the fault can be used to define document-type-specific error processing. For example, you could assign errors resulting from different document types to different users for resolution. For more information, see Chapter 16, Introduction to B2B Integration Using AIA. B2BDocumentType Version Provides the document type version of the failed transaction in Oracle B2B. For more information, see Chapter 16, Introduction to B2B Integration Using AIA. SenderTradingPartne rTradingPartnerID Provides the name of the sending trading partner in the B2B flow. For more information, see Chapter 16, Introduction to B2B Integration Using AIA. ReceiverTradingPartn erTradingPartnerID Provides the name of the receiving trading partner in the B2B flow. For more information, see Chapter 16, Introduction to B2B Integration Using AIA. GatewayID Provides the name of the B2B software used to initiate the flow, for example, Oracle B2B. For more information, see Chapter 16, Introduction to B2B Integration Using AIA. Configuring Oracle AIA Processes for Error Handling and Trace Logging 24-27 Figure 24–9 FaultNotification Element and Its Child Elements

24.7.3.1 FaultMessage Element

Table 24–5 discusses fault message elements. Table 24–4 FaultNotification Elements Name Purpose Details BusinessComponentI D Unique key for the application. Provides an agnostic representation of the object instance. ReportingDateTime Provides the date and time at which the service faulted. The date and time at which the service faulted. CorrectiveAction Provides the possible corrective action for the fault. The corrective action for the fault. FaultMessage Provides details of the actual fault message. For more information see Section 24.7.3.1, FaultMessage Element. FaultingService Provides details of the faulting service. For more information see Section 24.7.3.1, FaultMessage Element. Table 24–5 FaultMessage Elements Name Purpose Details Code Provides the error code. This is the fault code that was received. Text Provides error details. This describes the details of the fault. 24-28 Developers Guide for Oracle Application Integration Architecture Foundation Pack

24.7.3.2 IntermediateMessageHop Elements

Figure 24–10 illustrates IntermediateMessageHop elements. Intermediate message hop elements are discussed in Table 24–6 . Figure 24–10 IntermediateMessageHop Elements Severity Provides the severity of the error. This is the severity of the fault expressed as an integer. Stack Provides the error stack. This is the complete fault stack. ApplicationFaultData Enables the fault message to be extended to accept any kind of XML input. Enables a fault message to be extended to include any kind of XML input, as decided by the implementation scenario. For more information about extending fault messages, see Section 24.8, Extending Fault Messages. IntermediateMessageHo p Captures properties specific to a message in a multi-hop transaction. Properties that are captured here can be used to support use cases implementing guaranteed message delivery and message recovery. For more information about implementing guaranteed message delivery and message recovery, see Section 24.5, Implementing Error Handling and Recovery for the Asynchronous Message Exchange Pattern to Ensure Guaranteed Message Delivery. Table 24–6 IntermediateMessageHop Elements Name Purpose Details SenderResourceType Code Used for storing the type of resource or system that is the sender of this message in the multi-hopping messaging layer. Example values of this element are Queue, Topic, or Resequence Store. Table 24–5 Cont. FaultMessage Elements Name Purpose Details Configuring Oracle AIA Processes for Error Handling and Trace Logging 24-29

24.7.3.3 FaultingService Element

24.8 Extending Fault Messages