Webshere Message Broker Interview Question and Answers - Part 5


This post contains last 36 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....

101. Exception Handling in MB?
Ans. By using the following nodes
  • Throw node
  • Trace node
  • Try Catch node
102. What is the difference between try catch node and throw node?
Ans. Throw node throws an exception where as a try catch node is used to handle the error, which is raised.

103. Difference between Root and Output Root?
Ans.  Both are correlation names. Root is used in nodes, which do not create a new output where as Output Root is used in a node, which can create a new output node.

104.In route to label node where we will gave label name, and syntax of the label name assignment in processing node?
Ans. By setting the Local Environment variable
Syntax:        
LocalEnvironment.Destination.Routerlist.DestinationData = ‘Label name’;

105. Define SCADA?
Ans. The SCADAInput node is used to receive messages from clients that connect to the broker across the WebSphere MQ Telemetry Transport. SCADA device clients use the MQIsdp protocol to send messages, which are converted by the SCADAInput node into a format recognized by WebSphere Message Broker. The node also establishes the processing environment for these messages.

106. Will broker run on AIX system or not?
Ans. Yes

107. Functionality of FlowOrder node?
Ans. FlowOrder node to control the order in which a message is processed by a message flow. The input message is propagated to the first output terminal and the sequence of nodes connected to this terminal process the message. When that message processing is complete, control returns to the FlowOrder node. If the message processing completes successfully, the input message is propagated to the second output terminal and the sequence of nodes connected to this terminal processes the message.

108. Is there any alternative for MQ to use along with MB?
Ans. No.

109. How to suspend a queue manager in a cluster?
Ans. In the Navigator view (in the Queue Manager Clusters folder), right-click the queue manager, the click Suspend cluster membership...

110. What happens if a message is sent to a local queue, which is filled, and a remote queue, which is filled? Any difference in them?
Ans. The message moves to the relevant default dead letter queue

111. Can we give all the format types in a single message set, If so how?
Ans.  YES.
112. How will you declare an array in MB and how will you retrieve the desired value from an array? Two types of representations?
Ans.
  • Dynamic Arrays
  • Structure-field arrays.
Dynamic Arrays:
Syntax: myDataItem01 CHAR(30)[] {maxSize=5}; 
        
Structure-field arrays:
Record myRecord01Part
10 name[3];
20 firstOne CHAR(20);
20 midOne CHAR(20);
20 lastOne CHAR(20);
End

To retrieve Values:
MyRecord01.name.lastOne[2]
MyRecord01.lastOne [2]
LastOne[2]

113. What are the properties of .bar file and when they are used?
Ans. The unit of deployment to the broker is the broker archive or bar file. The bar file is a zip-format file which can contain a number of different files:
A .cmf file for each message flow. This is a compiled version of the message flow. You can have any number of these files within your bar file.
A. dictionary file for each message set dictionary. You can have any number of these files within your bar file.
A broker.xml file. This file is called the broker deployment descriptor. You can have only one of these files within your bar file. This file, in XML format, resides in the META-INF folder of the zip file and can be modified using a text editor or shell script.
Any number of XML files(.xml) and style sheets (.xsl files) for use with the XMLTransformation node.
Any number of JAR files for use with the Java Compute node.
As a zip-format archive, the broker archive file can also contain any additional files you need. For example, you might want to include Java source files for future reference.

Also Read: Storage Area Network (SAN) Basic Free Tutorials

114. How will you handle an input message with different delimiters between the fields?
Ans. Using MRM domain          

115. What are the advantages of Message broker?
Ans. Comprehensive monitoring using predefined workspaces that provide statistical information such as Current Message Rates, Current Average Message Time, and Sub-flow Statistics.
Comprehensive solution for complex WebSphere MQ environments that enables drill down to problem components
Custom workspaces can be tailored for individual job functions

116. What happens when the queue name is not specified in the MQOutput node?
Ans. Message is backed out.

117. What are the differences between MB 5.0 and 6.0?
Ans. Some additional nodes are added Like Java Compute node.
Configuration manager can be created with out referring database.
Can be installed and configured on Aix also.

118. What is the difference between catch terminal and failure terminal in MQInput node?
Ans.
Catch terminal: The output terminal to which the message is routed if an exception is thrown downstream and caught by this node.
Failure terminal: failure terminal detects an internal error; it propagates the message to that terminal.
The output terminal to which the message is routed if an error occurs. Even if the Validation property is set, messages propagated to this terminal are not validated.

119. How to specify reference keyword in the ESQL and what is the use of it?
Ans. Declare ptr REFERENCE TO InputRoot.xml.emp.eno;
-- Here, ptr refers to a specific field reference
        
120. What is the need of transaction mode property in the compute node?
Ans. The transaction mode for the node. This can be Automatic or Commit. It is valid only if you have selected a database table for input

121. What are the types of data formats that MB will support?
Ans. XML, TDS, CWF.

122. What is the difference between TDS and CWF?
Ans. The Tagged/Delimited String format (TDS) is the physical representation of a message that has a number of data elements separated by tags and delimiters.
Custom Wire Format (CWF) is the physical representation of a message that is composed of a number of fixed format data structures or elements, which are not separated by delimiters

123. Command used to deploy?
Ans. Using mqsideploy

124. What should you do before creating the broker and the configuration manager?
Ans. We have to create the data source name and Queue manager

125. Explain about web services nodes?
Ans. WebSphere MQ Web Services Transport connects Web services and clients that use the HTTP protocol for messaging. A WSDL definition for that service can be imported into a message set using the new WSDL importer.
HTTPInput: This node to receive Web service requests for processing by a message        flow Use the HTTPRequest node to interact with a Web service
SET OutputRoot.HTTPResponseHeader = NULL;
HTTPReply: This node to return a response from the message flow to the Web service client.
Select the Ignore Transport Failures check box if you want transport-related failures to be ignored (for example, if the client is disconnected). If you clear the check box, and a transport-related error occurs, the input message is propagated to the failure terminal. If you clear the check box, you must supply a value for Reply send timeout.
Set the Reply send timeout value if you are not ignoring transport failures. This is the length of time that the node waits for an acknowledgment that the client has received the reply.

126. Explain about JMS nodes?
Ans. JMS Input Node: to receive messages from JMS destinations.
The JMSInput node receives and propagates messages with a JMS message tree. You can set the properties of the JMSInput node to control the way that the JMS messages are received. JMS Output Node: to send messages to JMS destinations

127. Process of clustering and what are the advantages of clustering?
Ans. Grouping up of two or more Queue managers
Advantages: load balancing, reduces network traffic

128. Working of XML Transformation node?
Ans. Used to transform an XML message to another form of XML message, according to the rules provided by an XSL (eXtensible Stylesheet Language) style sheet.
You can use node properties. This ensures that the transformation defined by this single style sheet is applied to every message processed by this node.
You can use the content of the XML data within the message itself. This transforms the message according to a style sheet that the message itself defines. This behavior is only available for XSL and XML files that are located within a Message Flow project.
You can set a value within the LocalEnvironment folder associated with the message. This provides a dynamic choice of style sheet, because you must set this value (in a Compute node) within the message flow after receipt of the message. You can therefore use a variety of inputs to determine which style sheet to use for this message, such as the content of the message data or a value in a database.

129. Configuration of HTTP Input Node?        
Ans.
HTTP INPUT Node:
In URL Selector, put the path part of the URL from which this node receives Web service requests. Do not give the full URL.
Enter the Maximum client wait time timeout interval, as a number of seconds. This is the length of time that the TCP/IP listener that received the input message from the Web service client waits for a response from the HTTPReply node in the message flow. If a response is received within this time, the listener propagates the response to the client. If a response is not received in this time, the listener sends a SOAP Fault message to the client that indicates that its timeout has expired.
Select the Fault Format as one of SOAP 1.1, SOAP 1.2 or HTML.
If the node is to accept secure HTTP, select the Use HTTPS check box.
Select Default in the properties dialog navigator and set values for the properties describing the message domain, message set, message type, and message format that the node uses to determine how to parse the incoming message.
In the Message Domain field, select the name of the parser that you are using from the drop-down list. You can choose from:
  • MRM
  • XML
  • XMLNS
  • XMLNSC
  • JMSMap
  • JMSStream
  • IDOC
  • MIME
  • BLOB
If you are using the MRM or IDOC parser, select the correct message set from the drop-down list in the Message Set field. This list is populated with available message sets when you select MRM or IDOC as the domain.

Leave the Message Set field blank for XML, XMLNS, XMLNSC, JMS, MIME, and BLOB parsers.
If you are using the MRM parser, select the correct message from the drop-down list in Message Type. This list is populated with messages that are defined in the message set that you have selected.
Leave Message Type blank for XML, XMLNS, XMLNSC, JMS, IDOC, MIME, and BLOB parsers.
If you are using the MRM or IDOC parser, select the format of the message from the drop-down list in the Message Format field. This list includes all the physical formats that you have defined for this message set.

Leave the Message Format field blank for XML, XMLNS, XMLNSC, JMS, MIME, and BLOB parsers.

Select Validation in the properties dialog navigator if you want the MRM parser to validate the body of messages against the dictionary generated from the message set. (If a message is propagated to the failure terminal of the node, it is not validated.)

Select General Message Options in the properties dialog navigator. Parse Timing is, by default, set to On Demand. This causes validation to be delayed until it is parsed by partial parsing. If you change this to Immediate, partial parsing is overridden and everything in the message is parsed and validated, except those complex types with a Composition of Choice or Message that cannot be resolved at the time. If you change this to Complete, partial parsing is overridden and everything in the message is parsed and validated; complex types with a Composition of Choice or Message that cannot be resolved at the time cause a validation failure.

Select Description in the properties dialog navigator to enter a short description, a long description, or both.

Click Apply to make the changes to the HTTPInput node without closing the properties dialog. Click OK to apply the changes and close the properties dialog. Click Cancel to close the dialog and discard all the changes that you have made to the properties.

130. Where do you place pass-thru node in message flow?
 Ans. in the sub flows immediate to the input node

131. Features of Message Broker?
Ans. Routing, Transformation, Integration,

132. What is CVS (Concurrent Version System)?
Ans. It is a repository that will store the previous versions.

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

134. What are the properties MQMD and MQRFH2 Headers?
Ans. MQMD are a must headers and are present from starting to end of the message flow but MQRFH2 are optional and are set according to the business need.

135. What are the properties of TRACE Node?
Ans. Destination, File Path, Pattern, Message Catalog and Message Number

136. What are the types of TRACES?

Ans. User trace, service trace, ODBC trace, WebSphere MQ Java Client trace, and Configuration Manager Proxy trace.




What Others are Reading Now...

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

Post a Comment