A Mule application is being designed to do the following:
Step 1: Read a SalesOrder message from a JMS queue, where each SalesOrder consists of a header and a list of SalesOrderLineltems.
Step 2: Insert the SalesOrder header and each SalesOrderLineItem into different tables in an RDBMS.
Step 3: Insert the SalesOrder header and the sum of the prices of all its SalesOrderLineltems into a table in a different RDBMS.
No SalesOrder message can be lost and the consistency of all SalesOrder-related information in both RDBMSs must be ensured at all times.
What design choice (including choice of transactions) and order of steps addresses these requirements?
gilofernandes
2 months, 3 weeks agoabidfrq
4 months, 2 weeks agoMj290511
7 months, 4 weeks agoThomasTheTank
9 months, 4 weeks agoViv2005
1 year, 2 months ago1MK
2 years agosanni27
2 years agoGrump
2 years, 1 month agoPavan_Nagineni
2 years, 5 months agosiva_int
2 years, 5 months ago