Sreejobs Logo
   For Latest Job Updates  
sreenutech.com Online Exams
Home Govt Jobs IT Fresher Jobs IT Exp Jobs IT Walk-Ins MBA Jobs BPO Jobs Register FAQ’s Post Job Contact Us
Hot Jobs
Subscribe to Job Alerts
Your Email:

 Visit this group  
MQMB

1. Difference between Root and Output Root?
Ans. Root is used in the Database content changing and in Filter node.
Output Root is used in the ESQL code for a Compute node that creates a new output message based on the input message

2. Is it possible to set Properties of node apart from right click and setting the properties?
Ans. Windows à Show View à Basic à Properties

3. Which interface we have to implement when we are going to create an input custom node?
Ans. MbInputNodeInterface

4. Difference between RAD and ORDINARY deployment?
Ans. Using Resource adapter deployment, we can reuse the deployment till the server is re-booted.

5. Define BROKER, BAR, EXECUTION GROUP, SCADA, and COMPONENTS OF BROKER, WORKBENCH, WORKSPACE, and CMM?
Ans.
BROKER: A broker is a set of execution processes that hosts one or more message flows to route, transform, and enrich in-flight messages.
BAR: Flows and sets that are to be deployed are packed in it and sent to configuration manager
EXECUTION GROUP: 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.
SCADA: 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.
COMPONENTS OF BROKER: Broker, Configuration manager, User name service.
WORKBENCH:
WORKSPACE:

6. What is PARSER and difference between PARSER and FORMAT?
Ans.
A Parser is defined as a program that interprets the bit stream of an incoming message and creates an internal representation of it in a tree structure
Ex: MRM parser       
A Format is a physical representation of a message.
Ex: XML wire format

7. What is ResetContentDescriptor node?
Ans. Use the ResetContentDescriptor node to request that the message is reparsed by a different parser.

8. What is User name Server and where it is defined?
Ans. The User Name Server is an optional runtime component that provides authentication of users and groups performing publish/subscribe operations.

9. What is SCHEMA of broker?
Ans. A broker schema is a symbol space that defines the scope of uniqueness of the names of resources defined within it. The resources are message flows, ESQL files, and mapping files.

10. How can we see the error log files in broker?
Ans. The Windows Event Viewer is where WebSphere Message Broker writes records to the local system.

11. Default properties of Mqinput node?

Property

M

C

Default

Description

Message Domain

No

No

 

The domain that will be used to parse the incoming message.

Message Set

No

No

 

The name or identifier of the message set in which the incoming message is defined.

Message Type

No

No

 

The name of the incoming message.

Message Format

No

No

 

The name of the physical format of the incoming message.

Topic

No

Yes

 

The default topic for the input message.

12. Which node is used to change the message in the flow?
Ans. Compute Node, Filter Node and ResetContentDescriptor.

13. What is the use of commit for connection to Databases?
Ans. Any work that has been done using the respective data source in a message flow (including any actions taken in the node) is committed regardless of the subsequent success or failure of the message flow

14. Define Correlation names?
Ans. A correlation name is a field reference that identifies a well-defined starting point in the logical message tree and is used in field references to describe a standard part of the tree format.

15. MQInput node and INPUT node differences?
Ans. You must use an Input node to provide the in terminal to a subflow.
The Input node provides an in terminal for an embedded message flow (a subflow).

16. How many Built-in nodes are there? Categories them?
Ans. WebSphere Message Broker supplies built-in nodes that you can use to define your message flows. For information about each of these nodes, follow the appropriate link below. The nodes listed here are grouped according to the function that they provide.

Input and output
MQInput node
MQOptimizedFlow node
MQOutput node
MQGet node
MQReply node
Publication node
MQeInput node
MQeOutput node
SCADAInput node
SCADAOutput node
HTTPInput node
HTTPReply node
HTTPRequest node
Real-timeInput node
Real-timeOptimizedFlow node
Input node
Output node
JMSInput node
JMSOutput node
Message manipulation and transformation
Compute node
Database node
DataDelete node
Datalnsert node
DataUpdate node
Extract node
JavaCompute node
JMSMQTransform node
MQJMSTransform node
Mapping node
Warehouse node
XMLTransformation node
Collating requests
AggregateControl node
AggregateReply node
AggregateRequest node
Decision making
Check node
Filter node
FlowOrder node
Label node
ResetContentDescriptor node
RouteToLabel node
TimeoutControl node
TimeoutNotification node
Validate node
Subflow identification
Passthrough node
Error handling and reporting
Throw node
Trace node
TryCatch node

17. What are the perspectives we have?
Ans.

  • Administration Perspective
  • Application Development Perspective
  • Debugging Perspective.
  • Java Perspective (MB 6.0).

18. In which perspective we deploy the flow?
Ans. Administrator perspective

19. How to create Broker from Command prompt?
Ans. Using mqsicreatebroker command.

20. Use of Configuration manager?
Ans. To deploy the message flows onto the Broker.

21. What is the uniqueness of MB over ICS?
Ans. Parallel processing

22. What is EAI? What are those tools?
Ans. Enterprise Application Integration refers to the integration of one or more applications and processes together.
Tools: WBI Message Broker, ICS, WebMethods and Tibco.

23. What is the Broker Domain?
Ans. Group of brokers that coordinate a single configuration manager constitute a Broker Domain

24. What error is going to occur when we didn't specify the queue name in the MQInput node?
Ans. The Error message is "Unset mandatory ‘Qname Name’ Property on node ‘MQInput’ “.

25. How to call the method or function in the coding?
Ans. Using the “CALL” keyword.

26. Performance monitoring tools?
Ans. WebSphere Application Server, Java Management Extensions (JMX),

27. Functional Testing and Unit Testing?
Ans.   Unità testing with different test cases
          Functional à testing with the exact input

28. How many objects are required for distribution queuing?
Ans. QueueManager, SenderChannel, ReceiverChannel, LocalQueue

29. MQ Objects?
Ans. Queue manager, Send queue, Receive queue, Administration queue, Administration queue, Restart queue, Spill queue

30. Unix Commands?
Ans. grep, find, sort...etc.

31. Difference between MCA and MQI channels?
Ans. A message channel connects two queue managers via message channel agents (MCAs). Such a channel is unidirectional. It comprises two message channel agents, a sender and a receiver, and a communication protocol. An MCA is a program that transfers messages from a transmission queue to a communication link, and from a communication link into the target queue. For bi-directional communication you have to define two channel pairs consisting of a sender and a receiver.
A Message Queue Interface (MQI) channel connects an MQSeries client to a queue manager in its server machine. Clients don’t have a queue manager of their own. An MQI channel is bi-directional.

32. How to configure MQ?
Ans. By using runmqsc <Qmanager> command.

33. How will you Test your Flows?
Ans. Using Debugging Mode, Trace Node…
 
34. What workflow will do?
Ans. A message Flow is a sequence of processing steps that execute in the broker when an input message when an input message is received.

35. MQSI Server, MQSI Client difference? How to connect these two through command prompt?
Ans.
MQSeries Client:
A client workstation does not have a queue manager of its own. It shares a queue manager in a server with other clients. All MQSeries objects, such as queues, are in the server. Since the connection between client and server is synchronous, the application cannot work when the communication is broken. You could refer to such workstations as "slim" clients.
MQSeries Server:   
A workstation can be a client and a server. A server is an intermediate node between other nodes. It serves clients that have no queue manager and manages the message flow between its clients, itself and other servers. In addition to the server software you may install the client software, too. This configuration is used in an application development environment
 
Connection:    strmqm QMA
Start runmqlsr -t tcp -m QMA -p 1414
Runmqsc
Start channel (QMA.QMB)
End

36. How will you install and configure CVS & How will you use in MB?
Ans.
Double-click the Windows cvsnt-2.0.5.exe file to launch the installer.
Displays CVS Setup window appears
Select the option to accept the licence agreement and click Next.
Select Destination Directory screen, the default installation location is set to Workspace\cvsnt. If you have enough space to install to this location click Next.
The next screen asks you to choose the components that you wish to install,
Make your selections and click Next.
The Typical installation option already contained all of the components and protocols that we needed.
The next screen asks where the program should appear on the Start menu.
Accept the default and click Next.
Ensure that both the check boxes to install the CVS services
The Ready to Install screen lists the options you have selected. Click Install to start the installation. A progress bar appears while the files are copied.
Finally, click Finish when the completion window appears.
Reboot the system. The installation of the CVS server is now complete.

37. Event Monitoring? (Performance monitoring--> Queue depth event)?
Ans. Q Depth High, Q Depth Low, Depth Full

38. How will we use a Cobol copybook in MB?
Ans. You can populate your message set with message definitions by importing COBOL copybook files, using either the New Message Definition File wizard or the mqsicreatemsgdefs command line utility.

39. Types of messages?
Ans. MRM, XML, XMLNS, XMLNSC, JMSMap, JMSStream, MIME, BLOB, IDOC.

40. Deadletter queue cases?
Ans.

  • Destination Q is full
  • Destination Q doesn’t exist
  • Message too large
  • Sender is not authorized to use the destination Q

41. How many types of clients in MQ?
Ans.
Two Types

  • Fat Clients
  • Slim clients

42. MQ commands?
Ans.

  • CRTMQM
  • STRMQM
  • DLTMQM
  • ENDMQM

To create Queues, listeners, and channels

  • DEFINE QUEUE / CHANNEL
  • DISPLY – To display the queue or channel status  

43. Difference between Circular logging and linear logging?
Ans. Circular logging gives you restart recovery. Linear logging gives you both restart recovery and media recovery.

44. Difference between MQCONN and MQCONNX?
Ans.            
MQCONN (MQSTATE, qManagerName): Connects to a queue manager, which is identified by qManagerName, a string of up to 48 characters. MQSeries sets the connection handle  (MQSTATE.hconn) for use in subsequent calls.

MQCONNX (MQSTATE, qManagerName, MQCNO): Connects to a queue manager with options that control the way that the call works. The queue manager is identified by             qManagerName, a string of up to 48 characters. MQSeries sets the connection             handle (MQSTATE.hconn) for use in subsequent calls.

45. Difference between MQPUT and MQPUT1?
Ans.
MQPUT(MQSTATE, MQMD, MQPMO, BUFFER): Adds a message to the queue. The buffer cannot be more that 32767 bytes, but that restriction does not apply if you are using the EGL add statement.

MQPUT1(MQSTATE, MQOD, MQMD, MQPMO, BUFFER): Opens a queue, writes a single message, and closes the queue.

46. Can we use MQPUT1 in java?
Ans. Yes we can use.

47. If we want to perform some operation at receiving application when it receives some message, then what objects are required at the receiving application?
Ans.
Target QM,
Target Q,
Receiver channel and
Listener

48. How to get the depth of a queue?
Ans.  By using MQSC property CURDEPTH.

49. What formats MB support?
Ans. XML, TDS, CWF, EDI, SWIFT

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

51. Features of Message Broker?
Ans.

  • 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?
Ans.

  • 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?
Ans.

  • 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:

  • Message formats
  • Streams
  • Stream authority
  • Topics
  • Wildcard characters
  • Default topic routing
  • Retained publications
  • Metatopics
  • Subscription points
  • Content-based filtering & Throughput

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?
Ans.

  • 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?
Ans.
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?


Property

M

C

Default

Description

Destination

Yes

No

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

No

Yes

 

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

Pattern

No

No

 

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

Message Catalog

No

No

 

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

No

No

3051

The error number of the message that is written.

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


Property

 

C

Default

Description

Short Description

No

No

 

A brief description of the node.

Long Description

No

No

 

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

69. What are the types of TRACES?
Ans.

  • 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?
Ans.

  • 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.

76. What is the content of the configuration manager Repository?
Ans. It contains the information of the Broker Domain it is related to.

77. Exception Handling in MB?
Ans. By using Compute node, email node and java compute node.

78. What is the difference between try catch node and throw node?
Ans. The message routes out from the out terminal of the Try catch node and if any exception is thrown (say, by a throw node),then the try catch node catches it and sends the original message through the catch terminal for error processing

79. In route to label node where we will gave label name, and syntax of the label name?
Ans.
SET OutputLocalEnvironment.Destination.RouterList.DestinationData.labelname=’name of the label to which the message is to be routed ’;

80. What is the difference between hconn and hconnx?
Ans. Hconn is a handle used to connect to Queue manager in MQCONN and MQCONNX API calls.

81. Which is good based on performance IF or CASE. Why?
Ans. CASE

82. In clustering, which queue manager will contain the default full repository?
Ans. We will be setting the properties at the time of creation of the Queue manager.

83. In remote queuing, if the queue on the target queues manager is full, then to which dead letter queue will the message propagate?
Ans. Target dead letter queue

84. What are the different configuration management tools?
Ans. Tivoli, Clear case.

85. Functionality of mapping node?
Ans. Mapping node to construct one or more new messages and populate them with new information, with modified information from the input message, or with information taken from a database. You can modify elements of the message body data, its associated environment, and its exception list.

86. How will you handle CWF and TDS format?
Ans.  By developing message sets and using them in the message flow.

87. How will you trace the errors through command prompt? 
Ans.  Mqsiformatlog, Mqsilist, Mqsichangetrace, mqsireadlog and mqsireporttrace.

88. How can you validate the XML message in the flow?
Ans. Using a Message set with the required XML format or by using validate node.

89. How will you set headers in pub-sub?
Ans. By setting the MQRFH2 headers
E.g.:
SET OutputRoot.MQRFH2.(MQRFH2.Field)Version = 2;
SET OutputRoot.MQRFH2.(MQRFH2.Field)Format = 'MQSTR';
SET OutputRoot.MQRFH2.(MQRFH2.Field)NameValueCCSID = 1208;
SET OutputRoot.MQRFH2.psc.Command = 'RegSub';
SET OutputRoot.MQRFH2.psc.Topic = "InputRoot"."MRM"."Topel";
SET OutputRoot.MQRFH2.psc.QMgrName= 'DebugQM';
SET OutputRoot.MQRFH2.psc.QName = 'PUBOUT';
SET OutputRoot.MQRFH2.psc.RegOpt= 'PersAsPub';

90. Explain about PROPAGATE and LAST MOVE?   
Ans. The PROPAGATE statement is used to generate multiple output messages in the Compute node. The output messages that you generate can have the same or different content. You can also direct output messages to any of the four alternate output terminals of the Compute node, or to a Label node.
The LASTMOVE field function tells you whether the last MOVE function succeeded.

91. 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

92. Can we create multiple instances of a message flow?
Ans. Yes by deploying the message flow to different execution groups.

93. How to import COBOLCOPY BOOK or C format?
Ans. By importing the COBOLCOPY BOOK or C file into the existing project and building a message definition file from this imported structures.

94. 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.

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

96. What are the types of TRACES?
Ans. User trace, service trace, ODBC trace, WebSphere MQ Java Client trace, and Configuration Manager Proxy trace.

97. What are the types of Trees?
Ans. 
The input node creates the logical tree, which consists of four sub trees:

  • Message tree
  • Environment tree
  • Local Environment tree
  • Exception List tree

98. What is the difference between Environment and Local Environment?
Ans. Environment variable’s scope is defined for the whole flow where as the Local Environment variable’s scope is defined for that node and can be passed on to the next node as well.

99. How to connect Broker in MB?
Ans. Using configuration manager.

100. How to connect to database to the remote system?
Ans.  By ODBC driver name.

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.

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.

More Questions

1 how to change maxhandle limit of the queue manager?
2. how to migrate the MQ Versions? Is it neccesary to delete the previous version when you installing the MQ prior version?
3.how to change the log file size?
4. how to know about how many number of applications are connected to your queue manager what are the attributes?
5. how to take the linear logging backup for the disk finate?
6 what are the types of the logs? Path in aix and linux?
7. what you will do if channel goes to retrying state?
8. in which location do you find groups and users in unix and aix?
9. What are the distribution list of MQ?
10. Tell be about the channel exit?
11. Which attribute specified Round robin weight in queue manager in cluster?
12. MB topology?
13. what specifies ‘–w ‘in mqsideploy
14. MB topology?
15. how to increase heap size of execution group in broker?
16. how to solve the timeout errors?
17. logs locations in MB?
18. how to deploy bar file in MB using command?
19. what is the difference between Requester and reciver channel?
20. how to trouble shoot If deployment not successful?
21. how to create bar file?
22.How to define client connection channel and server connection channel?
23. what is the 2009 code error?
24 some other basic error codes 2085, 2035?
25. what is the difference between linear and circular logging?
26. How to increase the log file size?
27. Commands for recovery the queue manager in linear logging/
28. which queue stores statistics information?
29. what is the difference between Compute node and Database node?
30. How to create datasource in unix for broker?
31. How to handle the messages in dead letter queue?
32. Qload scripts?
33. how you will browse the message from queue manager (Command)
34. How many number of channels that you have to define in cluster?
35. what are the advantages of the cluster?
36. what happen if I write CRTMQM XYZ what else created rather than queue manager?
37 what is the use of channel initiator?
38. Is the Qremote queue is necessary in cluster?
39. what is the use of mapping node?
40. Is it necessary data base for broker in MB 7.0?
41. How you fallow the work if you get tickets?
42.what you will do if channel goes in-doubt?
43.what is the use of command server ?
44. How will check out messages in dead letter queue?
45. How to install MQ 7.0 in AIX?
46. How you check from application to Queue manager ?
47. What are the Message brokernodes that you been worked in message flow?
48. Types of triggers how you are using in your organizaiton?
49. Tell me about configuration files?
50. How you check out errors for brokers?
51. how you will set authorizations to objects of queue manager?
52. if you getting 2035 reason code how you will proceed to solve?
53. how you set the queue if number of applications want to put messges to the same queue which attribute value that you could change to do so?
54. tell me about some basic queues and its use?
55. what happened if both full repository crash?
56. how you add new queue manager and delete the queue manger from cluster/
57. what is difference between Suspend and stop queue manager?
58. how to take backup of a queue manager?
59.  how you perform the cold/start operation?
60. what you will do if suddenly queue manager got abnormal termination in cluster?

Home | Register for Job Updates | Contact Us