Use Case: Request-Response Use Case: Asynchronous Process

23-24 Developers Guide for Oracle Application Integration Architecture Foundation Pack ■ One row with type Business Process describes the end-to-end business process the message is part of. ■ The second row describes the main message associated in the flow, for example, the order message in ProcessOrder flow. In most cases, each end-to-end process has only one message. However in complex business scenarios there could be multiple messages spawned or forked from the process. In that case each spawned message must be a row in this section. The use case example below describes how this works. To keep things simple the example limits the messages to the immediate child of the process and the subsequent chaining of messages is not taken into account.

23.6.5 Use Case: Request-Response

GetAccountBalance: Sends a request message with account number as input and receives account balance as response, as shown in Figure 23–12 . Figure 23–12 Use Case: Request-Response

23.6.5.1 Request EBM

Example 23–18 shows two rows: one for the Process and one for the Request EBM Message involved in the process. Example 23–18 Request EBM for Request-Response Use Case BusinessScope IDSiebel- Portal-Get -Account-BalanceID InstanceIDGETACCTBAL1001InstanceID BusinessScopeTypeCodeBusinessScopeBusinessScopeTypeCode EnterpriseServiceNameAccountEBSEnterpriseServiceName EnterpriseServiceOperationNameGetAccountBalance EnterpriseServiceOperationName BusinessScope BusinessScope ID AccountBalanceReqMessage ID InstanceID ACCTBALMSG9001[the EBMID in the top element to be used here] InstanceID BusinessScopeTypeCodeMessageBusinessScopeTypeCode EnterpriseServiceNameAccountEBSEnterpriseServiceName EnterpriseServiceOperationNameGetAccountBalance EnterpriseServiceOperationName BusinessScope

23.6.5.2 Response EBM

Example 23–19 shows two rows: one for the process and one for the Response EBM Message involved in the process. Example 23–19 Response EBM for Request-Response Use Case BusinessScope IDSiebel- Portal-Get -Account-BalanceID Working with Message Transformations 23-25 InstanceIDGETACCTBAL10 01InstanceID BusinessScopeTypeCodeBusinessScopeBusinessScopeTypeCode EnterpriseServiceNameAccountEBSEnterpriseServiceName EnterpriseServiceOperationNameGetAccountBalance EnterpriseServiceOperationName BusinessScope BusinessScope ID] AccountBalanceResMessage ID InstanceID ACCTBALMSG9002[the EBMID in the top element to be used here InstanceID BusinessScopeTypeCodeMessageBusinessScopeTypeCode EnterpriseServiceNameAccountEBSEnterpriseServiceName EnterpriseServiceOperationNameGetAccountBalance EnterpriseServiceOperationName BusinessScope

23.6.6 Use Case: Asynchronous Process

SyncProduct: Portal sends an async message to Siebel to sync the product details, as shown in Figure 23–13 . Figure 23–13 Use Case: Asynchronous Process

23.6.6.1 Request EBM

Example 23–20 shows two rows: one for the process and one for the Request EBM Message involved in the process. Example 23–20 Request EBM for Asynchronous Use Case BusinessScope IDPortal-Siebel-Product-SyncID InstanceIDPRODSYNC1003InstanceID BusinessScopeTypeCodeBusinessScopeBusinessScopeTypeCode EnterpriseServiceNameProductEBSEnterpriseServiceName EnterpriseServiceOperationNameSyncProductEnterpriseServiceOperationName BusinessScope BusinessScope ID ProductSyncReqMessage ID InstanceID PRODSYNCREQ9003 InstanceID BusinessScopeTypeCodeMessageBusinessScopeTypeCode EnterpriseServiceNameProductEBSEnterpriseServiceName EnterpriseServiceOperationNameSyncProductEnterpriseServiceOperationName BusinessScope

23.6.7 Use Case: Synchronous Process with Spawning Child Processes