A service interacts with a backend system which replies with a message correlation. When processing request/response messages from the backend, no messages were received by the flow. Which may be…

The correct answer is A. The transaction was set to automatic on the MQOutput Node. When you define an MQOutput node, the option that you select for the Transaction Mode property defines whether the message is written under sync point: If you select Yes, the message is written under sync point (that is, within a WebSphere MQ unit of If you select Automatic…

Message Flow Development

Question

A service interacts with a backend system which replies with a message correlation. When processing request/response messages from the backend, no messages were received by the flow. Which may be the probable cause of failure?

Exhibit

Options

AThe transaction was set to automatic on the MQOutput Node.
BThe developer should have used the MQInput Node instead of the MQGet Node.
CThe Integration Node is configured in a MQ cluster for load balancing and the object descriptor is
DThe backend request/reply message processing can only be accomplished by breaking up the flow

How the community answered

(35 responses)

A
71% (25)
B
9% (3)
C
17% (6)
D
3% (1)

Explanation

When you define an MQOutput node, the option that you select for the Transaction Mode property defines whether the message is written under sync point: If you select Yes, the message is written under sync point (that is, within a WebSphere MQ unit of If you select Automatic (the default), the message is written under sync point if the incoming input message is marked as persistent. If you select No, the message is not written under sync point. Incorrect Answers: B: You can use an MQGet node anywhere in a message flow, unlike an MQInput node, which only as the first node in a message flow.

Topics

#MQOutput node#message correlation#transaction mode#request-reply

Community Discussion

No community discussion yet for this question.

Full C9530-001 Practice