Note that this transaction is made up of two activity groups, each of which
contributes to the bill payment process. The first activity section asynchronously updates the customer
profile information denoted by the grayed-out synchronization flag (and thus no timeline
is depicted). These two activities are carried out by the account balances composite service and
the portfolio allocation composite service. Each of these services invokes the updateCustPro-
fileNotification interface simultaneously. The second activity group involves two function calls
that are executed by the pay bill atomic service: (1) getCustomerProfileReq to verify account and
portfolio balance and (2) payBills, which executes bill payments.
SERVICECOMPOSITIONSTYLES SHAPE TRANSACTIONACTIVITIES. As has been noticed, logical
relationships between services and their consumers influence the dynamics of service-oriented
updaetCustProfileNotification(custBalancesInput.string)
Account
Balances
composite
service
Customer
Profile
atomic service
Pay Bills
atomic service
Portfolio
Allocation
composite
service
ORC
2
Customer Support
service cluster
updateCustProfileNotification(portAllocationInput.string)
ORC
getAccountBalanceReq(customerIDinput.string) 1
getAccountBalanceRes(balanceOutput.string)
payBills(customerID.string)
2
getCustProfileReq(customerIDinput.string)
1
getCustProfileRes(customerProfOutput.
Pages:
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519