0% found this document useful (0 votes)
74 views8 pages

Introduction:: - Websphere Message Broker Offers The Following Features

WebSphere Message Broker is a powerful information broker that allows data to flow between disparate applications and across multiple platforms. It offers universal connectivity, routes and transforms messages using various protocols and data formats, and supports interactions like routing, filtering, transforming, and correlating messages. Key nodes and functions in Message Broker include the MQ input/output nodes, database node, compute node, filter node, and ESQL functions for transforming message content.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
74 views8 pages

Introduction:: - Websphere Message Broker Offers The Following Features

WebSphere Message Broker is a powerful information broker that allows data to flow between disparate applications and across multiple platforms. It offers universal connectivity, routes and transforms messages using various protocols and data formats, and supports interactions like routing, filtering, transforming, and correlating messages. Key nodes and functions in Message Broker include the MQ input/output nodes, database node, compute node, filter node, and ESQL functions for transforming message content.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 8

-> Introduction :

WebSphere Message Broker is a powerful information broker that allows


business data, in the form of messages, to flow between disparate
applications and across multiple hardware and software platforms.
Rules can be applied to the data that is flowing through the message broker
to route, store, retrieve, and transform the information

-> WebSphere Message Broker offers the following


features:
1) Universal connectivity:
2) Routes and transforms messages from anywhere, to anywhere:
3) Supports a wide range of protocols like WebSphere MQ, Java Message Service
(JMS), HTTP(S), Webservices (SOAP and REST), File, TCP/IP and User-Defined
protocols
4) Supports a broad range of data formats like binary (C/COBOL), XML, SWIFT,
EDI, IDoc, CSV and user-defined formats
5) Supports interactions and operations that allow you to route, filter, transform,
enrich, monitor, distribute, decompose, correlate, sequencing

-> Please find the below functions and nodes from


google and prepare (search in google eg : cast
function in WMB )
There are built in nodes which would help us to attain the functionality using WMB
1) MQ input node
2) MQ Output node
3) MQ Get Node
4) Input node
5) Database node
6) Compute node
7) Filter node
8) Reset Content Discriptor (RCD)
9) SOAP input
10) SOAP request
11) Soap Reply
Q:What is ESQL?
A: Extended Structured Query Language (ESQL)
is a programming language based on Structured Query Language (SQL),
which is commonly used with relational databases such as DB2.
ESQL extends the constructs of the SQL language to provide support for us to
work with both message and database content.

-> To attain the functionality using the ESQL we use some


functions
Cardinality
Collasce
Substring
Cast
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
:::::::::::::::::::::::::::::::: Q:What is the Command to Create Broker?
A:mqsicreatebroker is the command used to create broker

Q: Command to Deploy The Bar Files?


A:Using the mqsideploy command one can deploy the bar files

Q:What is the difference between a Root and OuputRoot?


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

Q:What is the significance of SCHEMA in Message Broker?


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

Q: What do you mean by ResetContentDescriptor node?


A: ResetContentDescriptor node request to parse the message with different
parser, leaving the message content unchanged
Q:What is the difference between an MQGet node & MQInput node?
A:The MQGet node reads a message from a specified queue, and establishes the
processing environment for the message. Whereas, The MQInput node receives a
message from a WebSphere MQ message queue that is defined on the queue
manager of the broker.
You can use an MQGet node anywhere in a message flow, unlike an MQInput
node, which you can use only as the first node in a message flow

Q:What is the difference between SOAPRequest node and


SOAPAsyncRequest node?
A:The SOAPAsyncRequest node sends a Web service request, but the node does
not wait for the associated Web service response to be received. This
asynchronous functionality enables multiple outbound requests to be made
almost in parallel because the outbound request is not blocked waiting for the
response.
Whereas, The SOAPRequest node is a synchronous request and response node,
which blocks processing after sending the request until the response is received.

Q:What is the difference between Mapping node and Compute node


transformation?
A:In Compute node you can transform the message by coding ESQL in the ESQL
resource file attached. Whereas, In mapping node you can use graphical maps to
transform input message by associating an input message model such as a DFDL
or XML schema, or an MRM Message Set and an output message model.
In compute node you can change the entire message even the header
assemblies. But, In mapping node you can change the message assembly,
message body, and properties.

Q:What is the difference between Input and MQInput node?


A:Use the Input node as an In terminal for an embedded message flow (a
subflow).The MQInput node receives a message from a WebSphere MQ message
queue that is defined on the queue manager of the broker. It is the first node of
your message flow.

Q:What is the purpose or use of compute node?


A:The Compute node is used to:
Build a new message using a set of assignment statements
Copy messages between parsers
Convert messages from one code set to another
Transform messages from one format to another

Q:How the interaction with Database take place using Compute node?
A:In Data Source specify the name by which the appropriate database is known
on the system on which this message flow is to execute.

Q:Difference between Try Catch Node and Throw Node?


A:Include a Throw node to force an error path through the message flow if the
content of the message contains unexpected data.
If a downstream node (which can be a Throw node) throws an exception, the
TryCatch node catches it and routes the original message to its Catch terminal.
Connect the Catch terminal to further nodes to provide error processing for the
message after an exception.

Q:How will input messages with different - different delimiters between


the fields are handled in WMB?
A:Using MRM domain we can input messages with different - different delimeters
between the fields in WMB.

Q:What do you mean by Depth Of A Queue?


A:Queue depth, is the number of pending input/output messages in a queue.

Q:How can we know the Current Depth Of A Queue?


A:Using MQSC property CURDEPTH we can know the current depth of a queue.

Q:Message Broker supports what all formats?


A:Message Broker supports XML, TDS, CSV, CWF, EDIFACT, SWIFT, COBOL formats

Q:What all Nodes Used in ESQL?


A:ESQL can be used with the Compute, Database, and Filter nodes.
Q:What is ESQL?
A:Extended Structured Query Language (ESQL) is a programming language based
on Structured Query Language (SQL), which is commonly used with relational
databases such as DB2. ESQL extends the constructs of the SQL language to
provide support for you to work with both message and database content.

Q:What functionality ESQL provides?


A:Through ESQL you can
Change the message content.
Modify an existing message
Create a new message
Add dynamic terminals
Route a message
Propagate a new request

Q:What are the Types Of Variables In ESQL?


A:ESQL variables can be described as external variables, normal variables, or
shared variables.

Q:What are external variables, normal variables, or shared variables?


External variables:
Also known as user defined properties.
Exist for entire life time of a message flow and are visible to all messages
passed through the flow.
Defined at module or schema level.
You have to assign an initial value at the time of declaring an external variable
and then can modify the initial value at deployment time by using the BAR editor.
Normal Variables:
Have lifetime of just one message pass through a node.
Visible to that message only in which it was defined.
To define, omit both EXTERNAL and SHARED keyword.
Shared variable:
Used to implement in-memory cache in the message flow.
Have a long life time and are visible to multiple messages pass through the
flow.
Exist for the lifetime of Execution group, lifetime of flow or node, lifetime of
nodes ESQL that declares the variable.
Initialized when the first message pass through the node or flow after broker
startup.

Q:What are Patterns?


A:A pattern captures a tested solution to a commonly recurring problem,
addressing the objectives that you want to achieve.

Q:What are the Benefits Of Using Patterns?


A:Patterns provide the following benefits:
Give you guidance for the implementation of solutions
Increase development efficiency, because resources are generated from a set of
predefined templates
Result in higher quality solutions, through reuse of assets and common
implementation of programming approaches, such as error handling and logging

Q:How Do You Ensure That Messages Do Not Lose?


A:For application and internal messages traveling across WebSphere MQ, two
techniques protect against message loss:
Message persistence - If a message is persistent, WebSphere MQ ensures that it
is not lost when a failure occurs, by copying it to disk.
Sync point control - An application can request that a message is processed in a
synchronized unit-of-work .

Q:How To Use Functions In Your ESQL Code?


A:Use CALL keyword to call functions or methods.
Q:What are the Ways In Which You Can Access Databases From A Message
Flow?
A:You can access a database from a message flow in two ways:
You can design a message flow that responds to events generated by the
database.
After a flow has already started, you can access the database to read or update
information in it. Information from the database can be used to enhance or
influence the operation of the message flow.

Q:How can we See The Error Log Files In Broker?


A:The Windows Event Viewer is where WebSphere Message Broker writes records
to the local system.
Q:What are the different ways to give input without using MQInput node?
A:SCADAInput, HTTPInput, FileInput, Real-timeInput, JMSInput, Custom Input
nodes.

Q:What is PARSER? Difference between PARSER and FORMAT?


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

Q:Define Correlation names?


A: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.

Q:How will we use a Cobol copybook in MB?


A: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.

Q:What is PARSER and difference between PARSER and FORMAT?


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

You might also like