Webshere Message Broker Interview Question and Answers - Part 3

This post contains 25 Interview Questions including Answers. If you find any answers are wrong , please comment below so that we can update them and help others. Check the next post for more....

51. Features of Message Broker?
  • Routing,
  • Transformation and
  • Integration
52. What is CVS (Concurrent Version System)?
Ans.  It is a repository that will store the previous versions.

53. Difference between compute and mapping node?
Ans.  In the compute node we can change the headers but in mapping node we can’t change.

54. Types of Queues in MQ?
  • Local queue
  • Remote queue Definition
  • Alias queue
  • Model queue
55. How do you test your message flows and design test case?
Ans.  By using debugging perspective. We can create the Test Case according to the client specification error codes.

56. What are the different ways for giving input without using MQInput node?
Ans. Custom input nodes

57. Advantages of compute node?
  • To construct one or more new output messages.
  • To build a new message using a set of assignment statements.
  • To copy messages between parsers
  • To convert messages from one code set to another
  • To transform messages from one format to another
58. How can you interact with Database using Compute node?
Ans. Specify in Data Source the name by which the appropriate database is known on the system on which this message flow is to execute.

59. How will you handle errors in Message Flow?
Ans.  By using Debugging perspective, and Trace node.

60. Difference between MQ pub-sub and MB pub-sub?
Ans. The differences in the publish/subscribe support provided by WebSphere MQ and WebSphere Message Broker are described in the following topics:
61. Aggregate nodes?
Ans.  Aggregation nodes are used in fan-out and fan-in process.
Fan-out: The initial request to the message flow, representing a collection of related requested items, is split into the appropriate number of individual requests to satisfy the subtasks of the initial request.
Fan-in:  Replies from the subtasks are combined and merged into a single reply that is returned to the original requester (or another target application) to indicate the completion of the processing.
WebSphere Message Broker provides three message flow nodes that support aggregation:
  • AggregateControl
  • AggregateRequest
  • AggregateReply
62. Filter node?
Ans.  To route a message according to message content.

63. Database node?
  • To interact with a database in the specified ODBC data source.
  • You can use specialized forms of this node to:
  • Update values within a database table (the Data Update node)
  • Insert rows into a database table (the Data Insert node)
  • Delete rows from a database table (the Data Delete node)
  • Store the message, or parts of the message, in a warehouse (the Warehouse node)
64. Logical Message Tree? Message Tree Structure?
Ans. The logical tree structure is the internal (broker) representation of a message.     The message tree is a part of the logical message tree in which the broker stores its internal representation of the message body

65. Can we create multiple instances of a message flow?
Ans. Yes we can. One way is by adding multiple nodes. For example a single message flow can handle DATA received across MQ and messages that are received across native IP connections.

66. About Resetcontentdescripter node, Label node?
Resetcontentdescripter Node: To request that the message is reparsed by a different parser.
Label Node:  use it in combination with a RouteToLabel node to dynamically determine the route that a message takes through the message flow, based on its content. The RouteToLabel node interrogates the Local Environment of the message to determine the identifier of the Label node to which the message must next be routed.

67. What is an Execution Group?
Ans. An execution group is a named grouping of message flows that have been assigned to a broker. The broker enforces a degree of isolation between message flows in distinct execution groups by ensuring that they execute in separate address spaces, or as unique processes

68. What are the properties of TRACE Node?

User Trace
The destination of the trace record written by the node. Valid choices are User Trace, File, Local Error Log, and None.
File Path

The fully-qualified file name of the file to which to write records. Valid only if Destination is set to File.

The data that is to be included in the trace record.
Message Catalog

The name of the message catalog from which the error text for the error number of the exception is extracted. The default value (blank) indicates that the message is taken from the message catalog supplied with WebSphere Message Broker.
Message Number
The error number of the message that is written.

The Description properties of the Trace node are described in the following table.

Short Description

A brief description of the node.
Long Description

Text that describes the purpose of the node in the message flow.

69. What are the types of TRACES?
  • User trace
  • Service trace.
User: used for debugging your applications. It can trace brokers, execution groups, and deployed message flows.
Service: More comprehensive Broker tracing. It starts tracing for workbench, configuration manager and username server.

70. What are the types of Trees?
  • Message Tree
  • Environment Tree
  • Local Environment Tree
  • Exception list Tree
71. What is the difference between Environment and Local Environment?
Ans. The Environment tree is a part of the logical message tree in which you can store information while the message passes through the message flow.

72. How to connect Broker in MB?
Ans. From Broker domain, using Configuration Manager.

73. How to connect to database to the remote system?
Ans.  By doing node catalog and the database catalog.

74. What is the role of configuration manager?
Ans.  Connecting to the broker and to deploy the message flows.

75. How to debug applications in message flow?
Ans. Using Debugging perspective and user traces.

What Others are Reading Now...

0 Comment to "Webshere Message Broker Interview Question and Answers - Part 3"

Post a Comment