EBMTracking Introducing EBM Header Concepts

Working with Message Transformations 23-29 IDCreate-Account-Request-Message ID InstanceID CREATEACCTREQMSG 9005 InstanceID BusinessScopeTypeCodeMessageBusinessScopeTypeCode EnterpriseServiceNameAccountEBSEnterpriseServiceName EnterpriseServiceOperationNameCreateAccountEnterpriseServiceOperationName BusinessScope BusinessScope ID Create-Account-Response-Message ID InstanceID CREATEACCTRESPMSG 9020InstanceID BusinessScopeTypeCodeMessageBusinessScopeTypeCode EnterpriseServiceNameAccountEBSEnterpriseServiceName EnterpriseServiceOperationNameCreateAccountEnterpriseServiceOperationName BusinessScope Message 6: Process Order Response EBM Example 23–26 shows two rows: ■ One for the process ■ One for the Process Order Response in the process Example 23–26 Process Order Response EBM BusinessScope IDEnd-to-End-Order-Processing ID InstanceID ORDPROCESSING1004 InstanceID BusinessScopeTypeCodeBusinessScopeBusinessScopeTypeCode EnterpriseServiceNameOrderEBSEnterpriseServiceName EnterpriseServiceOperationNameProcessOrderEnterpriseServiceOperationName BusinessScope BusinessScope ID Process-Order-Response-MessageID InstanceID PROCESSORDERRESPMSG 9019InstanceID BusinessScopeTypeCodeMessageBusinessScopeTypeCode EnterpriseServiceNameOrderEBSEnterpriseServiceName EnterpriseServiceOperationNameProcessOrderEnterpriseServiceOperationName BusinessScope

23.6.8 EBMTracking

EBMTracking contains tracking information about each node that the EBM has been through, a shown in Figure 23–16 . EBMTracking may appear multiple times, once for each execution unit it passes through. 23-30 Developers Guide for Oracle Application Integration Architecture Foundation Pack Figure 23–16 Structure of the EBMTracking element

23.6.8.1 SequenceNumber

This element contains the sequence number of the node the EBM has been through.

23.6.8.2 ExecutionUnitID

This element contains the ID of the execution unit, node, or process ID.

23.6.8.3 ExecutionUnitName

This element contains the fully qualified name of the execution unit, node, or process ID.

23.6.8.4 ImplementationCode

This element contains the category of the execution unit, which indicates the type of the execution unit such as BPEL, Mediator, or Java Service.

23.6.8.5 ActivityDateTime

This element contains the timestamp indicating when the EBM was processed by the execution unit. The timestamp should be presented in UTC, which can be presented in current datetime, and GMT offset as: yyyy - mm - dd T hh : mm : ss . s+? zzzzzz?

23.6.8.6 When to Populate EBM Tracking Information

Add an EBMTracking entry, as shown in Example 23–27 , to the EBM header whenever a message is processed by a service. This section should be populated when: ■ Transforming a request ABM into an EBM in a requester ABC implementation service. ■ Transforming a response ABM into an EBM is a provider ABC implementation service. ■ The message passes through a BPEL process. Example 23–27 Populating EBM Tracking Information EBMTracking SequenceNumber1SequenceNumber ExecutionUnitID6 8 56 8ExecutionUnitID ExecutionUnitName{http:xmlns.oracle.comABCSImplSiebelInvoicev0} Working with Message Transformations 23-31 QueryInvoiceSiebelReqABCSImplExecutionUnitName CategoryCodeBPELCategoryCode ActivityDateTime2 001-12-17T09:30:47-05:00ActivityDateTime EBMTracking EBMTracking SequenceNumber2SequenceNumber ExecutionUnitID4435ExecutionUnitID ExecutionUnitNameOrderEBSExecutionUnitName ExecutionUnitName{http:xmlns.oracle.comEnterpriseServicesCoreInvoicev0} QueryInvoiceEBSExecutionUnitName CategoryCodeESBCategoryCode ActivityDateTime2 001-12-17T09:30:47-05:00ActivityDateTime EBMTracking EBMTracking SequenceNumber3SequenceNumber ExecutionUnitID6 8 594ExecutionUnitID ExecutionUnitName{http:xmlns.oracle.comABCSImplPortalInvoicev0}Query InvoicePortalProvABCSImplExecutionUnitName CategoryCodeBPELCategoryCode Activity DateTime2 001-12-17T09:30:47-05:00ActivityDateTime EBMTracking

23.6.9 Custom