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
1 year agoabidfrq
1 year, 2 months agoMj290511
1 year, 5 months agoThomasTheTank
1 year, 7 months agoViv2005
2 years ago1MK
2 years, 10 months agosanni27
2 years, 10 months agoGrump
2 years, 11 months agoPavan_Nagineni
3 years, 3 months agosiva_int
3 years, 3 months ago