When using the set of aggregation nodes, how does a developer tie the fan-out flow with the fan-in flow when it is included within the same message flow?
Options:
A.
No properties need to be set, since the fan-out and fan-in flows are in the same messages flow.
B.
Set the Aggregate Name property of the AggregateReply Node to the same value that you set for the Aggregate Name property in the corresponding Collector Node.
C.
Set the Aggregate Name property of the AggregateReply Node to the same value that you set for the Aggregate Name property in the corresponding AggregateControl Node.
D.
Set the Aggregate Name property of the AggregateReply Node to the same value that you set for the Aggregate Name property on each of the corresponding AggregateRequest Nodes in the fan-out flow.
Answer:
C
Explanation:
Explanation:
Set the Aggregate Name property of the AggregateReply node to the same value that you set for the Aggregate Name property in the corresponding AggregateControl node in the fan-out flow.
References:
Question 3
What is one to set the flow debugger port?
Options:
A.
Use the mqsichangebroker command to set the debug port.
B.
Use the mqsichangedebugport command to set the debug port.
C.
In the IBM Integration Bus Toolkit set the debug port in the Preferences.
D.
In the IBM Integration Bus Toolkit right-click on the Integration Server and set the debug port.
Answer:
C
Explanation:
Explanation:
Before you can debug a message flow, you must configure and enable the flow debug port. The flow debug port is also known as the Java debug port, and the JVM debug port.
Use the IBM Integration Explorer, or IBM Integration Toolkit to set the flow debug port value to enable the flow debugger to be connected to an integration server.
Note:
Using the IBM Integration Toolkit
To start debugging your message flows, switch to the Debug perspective. Right-click the integration server, and click Terminate Debugger to stop debugging on the selected integration server.