IBM WebSphere Message Broker Interview Questions
Are you looking for a new opportunity as an IBM WebSphere Message Broker developer? Then you need a bunch of interview questions, which helps you to clear the interview.
Here, tekslate experts compiled IBM Websphere Message Broker Interview Question and Answers for freshers and experienced candidates. We collected in such a way we covered all IBM WebSphere Message Broker Interview questions from basic to advanced concepts where you can clearly understand.
Start reading and crack your interview and acquire your dream job with the right salary package in this tech industry.
Basic IBM WebSphere Interview Questions and Answers
Q1) Explain the main components of IBM/WMB?
Ans: Following are three IBM/WMB components:
Runtime: The broker runtime is the primary processing segment to which improvement aircraft are deployed.
Development: This toolkit is utilized for the development of aircraft and other message flows.
Administration: Message Broker Explorer is an organization tool used to enable flow monitoring, deploys, new execution groups, or create brokers. WMB V8 gives a WebUI device to represent the broker runtime or assets deployed in a portal.
Q2) Does WMB/IBM need a database to function?
Ans: There is no database requirement; the item doesn't need a database for internal operations. You may have database hubs or databases for other operations; thus, Message Broker gives functionalities to interface with the application database.
Q3) Explain about PARSER and the differences between PARSER and FORMAT?
- A Parser is characterized as a program representing the bitstream of incoming information and creates an internal illustration of it in a tree structure. Ex: MRM parser.
- A Format is a physical visualization of a message. Ex: XML wire design.
Q4) What are the features of Message brokers?
Ans: Features of Message Brokers are accompanying in the following way:
Q5) Explain what is the role of the configuration manager?
Ans: Configuration manager connects to the broker and deploys the information onto the broker.
Q6) How to create a Broker from Command Prompt?
Ans: To create a broker from Command Prompt, you can use the createbroker command.
Q7) Enlist the default properties of Mq Input nodes?
Ans: Following are the default properties of Mq Input nodes:
- Message domain
- Message type
- Message Format
- Message set
Q8) Which nodes are used to change the message in the flow?
Ans: Following nodes are used to change the message in the flow:
- Filter Node
- Computer Node
- ResetContent Descriptor Node.
Q9) What is the difference between MB and ICS?
Ans: Parallel Processing is the difference between MB and ICS.
Q10) What is meant by EAI and what are those tools?
Ans: EAI means Enterprise Application Integration which integrates more than one application and process together.
Tools Used: Tibco, Webmethods, Web message brokers, ICS.
Q11) Explain about Broker Domain?
Ans: Group of brokers that correspond to a particular configuration manager develop a Broker Domain.
Q12) Enlist 6 Built-in-nodes in MB toolkit?
Ans: Following are the 6 Built-in nodes in the MB toolkit:
- AggregateControl node
- MQOutput node
- Database node
- MQInput node
- Filter node.
- Compute node
Q13) How to call the method or function in the ESQL Coding?
Ans: Using the “CALL” Keyword you can call the method or function in the ESQL Coding.
Q14) Enlist the message formats that MB Support?
Ans: Following are the few message formats that Mb support:
Inclined to build a profession as IBM WebSphere Message Broker Developer? Then here is the blog post on, explore IBM WebSphere Message Broker Training
Q15) What is meant by an Execution group?
Ans: An execution group is a named collection of message streams that have been relegated to a broker. The broker upholds a detachment level between message streams in particular execution bunches by guaranteeing that they execute in independent location spaces or as exceptional cycles.
Q16) Differentiate between root and output root?
Ans: The root is used in the Database content changing and Filter node. OutputRoot is used in the ESQL code for a Compute node that produces new output information based on the input information.
Q17) What is meant by User Server Name and where it is defined?
Ans: The User Name Server is an arbitrary runtime segment that gives authentication of users and groups doing publish/subscribe operations.
Q18) How to see the error log files in Broker?
Ans: To see the error log files in the broker, the windows event viewer is where the Websphere message broker writes the records.
Q19) What are the perspectives there in the MB toolkit? In which perspective we deploy the flow?
Ans: Following are the MB toolkits:
- Application Development Perspective
- Java perspective
- Administration Perspective
- Debugging Perspective
In Administration Perspective we deploy the information flow.
Q20) Explain different ways to give inputs without using mqinput nodes?
Ans: Following are different ways to give the inputs without using the mqinput nodes:
Q21) What error is displayed when we didn’t specify the queue name in the MQinput node?
Ans: It shows “ 0” and the error message is “ Unset mandatory ‘Qname name property’ on node ‘MQInput’ “.
Q22) Differentiate between MCA and MQI channels?
- A message channel associates two queue administrators by message channel specialists (MCAs). Such a medium is unidirectional. It contains two message channel specialists, a sender and a receiver, and a communication convention. An MCA is a program that moves messages from a transmission queue to a correspondence interface and from a correspondence connected into the objective queue.
- For bidirectional communication, you should characterize two channel sets consisting of a sender and a receiver. A Message Queue Interface (MQI) channel associates an MQSeries customer with a queue administrator in a server machine. Customers don't have their very own queue administrator. An MQI channel is bidirectional.
Q23) Is it possible to set the properties of nodes apart from right-clicking and set the properties?
Ans: Yes, it is possible to set properties of nodes from the right-click and setting the properties: Windows shows a view of basic properties.
Q24) Which interface do we have to implement when we are going to create an input custom node?
Ans: We have a Mbinputnode interface to implement to create an input custom node.
Q25) Give detailed information about BAR, SCADA, Execution group, Broker, and components of a broker?
Broker: A broker is a bunch of execution methods that endure message flow to transform, enrich in-flight, and route.
BAR: Flows and sets that are to be conveyed are stuffed and assigned to the configuration manager.
Execution group: An execution bunch is a named grouping of information flows allowed to a broker. The broker authorizes a level of disengagement between information flows in particular execution bunches by guaranteeing that they execute in isolated location spaces or exciting cycles.
SCADA: The SCADAInput hub is utilized to get messages from customers that interface with the dealer across the WebSphere MQ Telemetry Transport. SCADA gadget customers use the MQIsdp convention to send messages, which are changed over by the SCADAInput hub into an arrangement perceived by WebSphere Message Broker. The hub additionally builds up the preparing climate for these messages.
Components Of BROKER: Broker, Configuration administrator, User name service.
Q26) What is meant by ResetContentDescriptor Node?
Ans: The ResetContentDescriptor node is used to request the message is rephrased by a different parser.
Q27) Explain about Schema Broker?
Ans: A broker schema is a symbol of scope that defines the uniqueness of the names of resources defined. The resources are ESQL files, message flows, and mapping files.
Q28) How will you use a Cobol copybook in MB?
Ans: Cobol Copybook in Mb is used either for mqsicreatemsgdefs command-line utility and the new message definition wizard.
Q29) Enlist various types of messages?
Ans: Following are the various types of messages:
Q30) Differentiate between MQPUT and MQPUT1?
Ans: MQPUT ( BUFFER, MQMD, MQSTATE, MQPMO ): Adds information to the queue. The buffer cannot be more than 32767 bytes, but that restriction does not apply if you use the EGL to add a statement. MQPUT1(MQSTATE, MQOD, MQMD, MQPMO, BUFFER): Opens a queue, writes a piece of single information, and closes the queue.
Q31) What is meant by CVS?
Ans: CVS means concurrent version system; it is a repository that stores the previous version.
Q32) Difference between compute and mapping nodes?
- You can change the message by coding ESQL in the ESQL asset document connected in the Compute node. In a mapping node, you can utilize visual maps to change input messages by associating an input information model, for example, the output message model, XML pattern, a DFDL, and an MRM Message Set.
- In the compute node, you can change the whole message, even the header congregations. You can yet change the message get together in the mapping node, message body, and properties.
Q33) List out various types of Queues in MQ?
Ans: Following are the various types of Queues in MQ:
- Local Queue
- Transmission Queue
- Remote Queue
- Dead letter Queue
- Alias Queue
Q34) What is the use of the keyword “Commit” for connection to the database?
Ans: Any work that has been finished utilizing the respective information source in a message stream (counting any activities taken in the hub) is submitted, paying little heed to the message stream's ensuing achievement or disappointment.
Q35) Explain correlation names?
Ans: A correlation name is a field reference that recognizes a definite starting point in the logical information tree and is utilized in field references to define a conventional part of the tree format.
Q36) List out the differences between the MQinput node and the Input node?
Ans: Utilize the Input node as an In terminal for an embedded information flow(a subflow). The MQInput node gets a message from a WebSphere MQ message queue described by the queue administrator's broker. It is the primary node of your message flow.
Q37) Explain the difference between Mq and message broker?
Ans: WebSphere MQ stimulates the communication between applications by sending and receiving information through messaging queues. WebSphere MQ gives a reliable and secure layer of a carrier for transferring information unaltered as messages between applications, yet it doesn't know about the messages' substance.
WebSphere Message Broker is developed to increase WebSphere MQ, and it can understand the content of each message that it passes through the Broker.
Message Broker can do the accompanying:
Matches and routes interchange between the services.
Converts between various transport rules.
Changes message formats among service and requestor.
Defines and distributes business events from disparate sources.
Q38) What are the advantages of using a Websphere Message Broker?
Ans: Websphere message broker offers various types of assistance because message broker to permit you to:
Route a message to various destinations, utilizing rules that follow up on the content of at least one of the fields in the message or message header.
Change a message to ensure that applications are utilizing various formats that can trade messages in their configurations.
Store a message, or part of a message, in an information base.
Obtain a message, or part of a message, from a database.
Alter the substance of a message, for instance, by adding information separated from a database.
Q39) If the configuration manager is down, what are the effects on the running broker?
Ans: If the configuration manager is down, then the running broker is also down.
Q40) What is the role of Username Server?
Ans: The User Name Server interfaces with operating system facilities to give information about legitimate users and groups in a broker domain.
Q41) Can a Single Queue Manager have two brokers?
Ans: No, it is not possible for a Single Queue Manager to have two brokers.
Q42) Explain the importance of Schema in Message Broker?
Ans: A broker schema is a representative space that characterizes the extent of the uniqueness of the names of sources described inside it. The sources are message streams, ESQL documents, and mapping records.
Q43) Explain about a BAR?
Ans: Broker Archive or BAR is a bundle of message streams, Xslts, Java utility classes, message sets, etc., that are assumed to be conveyed by the broker.
Q44) What does Mqsiapplybaroverride Command do?
Ans: The mqsiapplybaroverride command is used to replace configurable conditions in the broker archive (BAR) with new values that you define in a properties file.
Q45) Which nodes in WMB supports Aggregation?
Ans: Following node in WMB support Aggregation:
Advanced IBM WebSphere Interview Questions and Answers
Q46) When you hit any backend where all queue or backend details are stored?
Ans: To hit or call any backend framework from a message broker, we need to have URLs or Queues, and we store all the information in our database. At runtime, we can recover those details to create a call to the Host System.
Q47) When to use Soap input and HTTP input nodes?
Ans: We use HTTP and SOAP input nodes to connect with WEB services, to choose which node to utilize when we can consider the following points:
- We use the HTTP input node to utilize diverse messaging operations, including JSON, XMLNSC, BLOB, MRM.
- If we are not utilizing WS-Addressing or WS-Security, it is smarter to use HTTP input than the SOAP input node.
- If the incoming message is SOAP-based, SOAP with Attachments (SwA), or Message Transmission Optimization Mechanism (MTOM) message, we use the SOAP node.
- If we have a WSDL document to approve or check our message, we use the SOAP input Node.
- It promotes WS-Addressing and WS-Security.
Q48) Why is the message set used?
Ans: Message Sets are used for message modeling in WMB for various types of messages. We can use message sets to authenticate incoming messages to verify if it is in the desired format.
Q49) How to create an Asynchronous scenario in the age broker, and which nodes will you use?
Ans: Asynchronous Scenario: When we are making a request and not expecting a response or a reply, and continue to make another request. For this situation, our Message flow doesn't wait for a response from the backend framework and process another incoming request.
We can accomplish this by utilizing MQ Nodes, as MQ output and MQGet hubs, to place messages in the output queue and process other incoming messages.
Q50) Enlist various types of variables in Message Broker? What is meant by extended and shared variables?
Ans: Ordinary, EXTERNAL, and SHARED
These variables have a lifetime of just one message going through the node and initialize again for the next message.
These variables are proclaimed with a key phrase 'External'.
Declare EXTNVAR EXTERNAL CHARACTER:
- This is also known as User Defined Properties (UDP) because we can allocate a default value to them in message stream UDP or set at sending time in Broker Archive editorial manager. Additionally, we can dole out new incentives at runtime by utilizing IBM incorporation API.
- These variables have a lifetime of the whole message going through the flow.
- These are proclaimed at the module level or schema level. We can't declare EXTERNAL factors inside a module or a function or a method.
These factors are declared with a key phrase, 'SHARED.'
Declare SHARVAR SHARED CHARACTER:
- These are utilized for reserving in MB. The cache is a temporary memory that we use to store information to utilize it in a stream instead of bringing it repeatedly from the database.
- These are also called enduring factors as they initialize when the first message goes through the hub and stays noticeable to different notes.
Q51) Differentiate XMLNSC and XMLNS, and why do we use XMLNSC?
- XMLNS and XMLNSC both are utilized for Parsing XML messages. However, there are a few favorable circumstances in using XMLNSC over XMLNS as:
- XMLNSC parser is reduced and uses lower memory than XMLNS.
- XMLNSC can approve as we can apply for message set approval if utilizing XMLNSC, not if there should arise XMLNS.
Q52) How to install IIB/WMB?
Ans: IIB/WMB installation includes installing a Broker segment, the Toolkit, and Message Broker. On Windows, all the three elements can be installed utilizing Windows Launchpad furnished with the product. On Unix stages, the installment can be performed through an installment wizard or in quiet mode. On z/OS, the installment is performed utilizing SMP/E.
Q53) Differentiate Local environment and environment tree?
Ans: The environment tree varies from the local environment tree in that an isolated occurrence of it is kept up all through the message stream. On the off chance that you incorporate a Compute node, a Mapping node, or a JavaCompute node in your message stream, you don't need to determine whether you need the environment tree to be remembered for the output message. The environment tree is incorporated, and the whole substance of the information environment tree is held in the output environment tree. Any progressions that you make are accessible to resulting hubs in the message stream and previous hubs.
Q54) Is there any default configuration of IIB/WMB that can I use?
Ans: IIB/WMB provides a default configuration. This can be begun through the Toolkit Welcome screen. The default setup wizard makes a broker and all the assets required.
Q55) What are the major processes for running a broker?
Ans: A broker can start the accompanying process to get started, and they can be found in Task Manager (on Windows) and additionally ps listing(on UNIX's). On z/OS, these methods run under the USS.
bipservice – This is a bootstrap method that begins the broker runtime.
bipbroker- This entire organization that deals with the broker runtime.
biphttplistener – This is the http server method that gives HTTP and SOAP functionality in Message Broker
DataFlowEngine- This is the Execution Group method that runs message stream strings. Each message stream runs in this cycle as a string.
Q56) Why is it a message definition file?
Ans: A message definition record contains the messages, components, types, and groups that make up a message model inside a message set. Each message set needs one message definition record to describe its messages. Message definition records utilize the XML Schema language to describe the consistent configuration of at least one message.
Q57) Explain about a Multipart message?
Ans: A multipart message contains more than one message inside its structure. The enclosed message is also known as an implanted message. A multipart message should have a complex type or group, with its Composition characteristic set to Message.
Q58) What do you know about the Propagate keyword?
Ans: The PROPAGATE proclamation is utilized to create numerous output messages in the Compute hub. The output messages may have the same or diverse message content. You can likewise send output messages to other output terminals of the Compute hub.
Q59) Explain message modeling?
Ans: Most message purposes are not self-characterizing, and a parser should have access to a predefined model that depicts the message if it is to parse the message effectively. WebSphere Message Broker utilizes a message model to demonstrate a message format.
Q60) Explain the benefits of modeling messages?
Ans: If your messages are self-characterizing and don't need displaying, message demonstrating has the accompanying preferences:
- Runtime approval of messages. Without a message model, a parser can't check whether information and output messages have the right structure and information.
- Upgraded parsing of XML messages. Even though XML is self-characterizing, all information esteems are treated as strings if a message model isn't utilized. On the off chance that a message model is used, the parser is furnished with the information sort of information esteems and can appropriately project the data.
- Improved profitability when composing ESQL. When you make ESQL programs for WebSphere Message Broker message streams, the ESQL proofreader can utilize message models to give code consummation help.
- Intuitive procedure on message maps. When you are making message maps for WebSphere Message Broker message streams, the Message Mapping manager utilizes the message model to populate its source and target sees. Without message models, you can't use the Message Mapping editorial manager.
- Reuse message models, in entire or to some degree, by making different messages that depend on existing messages.
- Creation of documentation.
- Arrangement of rendition control and access control for message models by putting them away in a local store.
Q61) What are the ways to create Message models?
Ans: You can create a message model by utilizing the accompanying techniques:
- Introducing an application message design depicted by an XML Schema, XML DTD, C structure, COBOL structure, SCA import or fare, or WSDL definition.
- Making an empty message model document makes your message by utilizing the editors given in the WebSphere Message Broker Toolkit.
- By utilizing the Adapter Connection wizard to import EIS metadata.
- By making a populated model record from model message information.
Q62) Why do you use sequence nodes?
Ans: The Sequence node allows you to receive messages from an input reference and process the order in which each group's messages arrived.
Q63) Tell me about the monitoring tools that are available in IIb/WMB?
Ans: Business level monitoring can be determined in IIB/WMB message streams that empowers the various hubs in the message stream to produce events when processing messages. These events can be additionally taken care of to different applications, for example, WebSphere Business Monitor for exchange observing, exchange evaluating, and business measure checking. More data can be found in the online Information Center under the theme Performance and monitoring> Business-level monitoring.
Q64) Which command is used to modify the broker parameters?
Ans: mqsichangebroker command is used to modify the broker parameters.
Q65) What are the high-availability options available in WMB/IIB?
Ans: Message Broker can be set up to work with the accompanying High Availability alternatives:
- Multi-occasion mode utilizing multi-occurrence queue administrator
- Existing High Availability administrator/Windows group, for example, HACMP or MSCS bunch.
Q66) Tell me about existing message flow templates/patterns that can be used to design message flows?
Ans: Built-in templates/patterns are provided with the IIB/WMB Toolkit to make assets utilized to tackle explicit business issues. You can make user-defined designs by using the template creation layouts given in IIB/WMB Toolkit.
Patterns are accessible to a pattern client in the Patterns Explorer see in the Broker Application Development point of view of the IIB/WMB Toolkit.
Q67) Tell me how to migrate from the previous version to the new version?
Ans: You can migrate from the previous version to the new version in an accompanying way:
- Import all the advanced ancient artifacts into the Message Broker Toolkit, which will move them as essential and deploy them to the new form runtime. Migrate just the runtime by utilizing the mqsimigratecomponents command.
- For instance, mqsimigratecomponents <broker> - s <source version> - t <target version>The information might be found in the online Information Center under the subject Reference > Configuration and organization > Commands > Runtime orders > mqsimigratecomponents order.
Q68) What is triggering in mq?
Ans: Triggering means it put the message into a queue.
Q69) What are the basic error handling techniques that are available in message flow?
Ans: Two basic error handling techniques are available in the message flow are:
- Failure checking
- Catching exception
Q70) What are the techniques that help to transform and enrich the messages in WebSphere Message Brokers?
Ans: We can enrich and transform the messages in WMB in the following ways:
XSL style sheets