Explore topic-wise InterviewSolutions in .

ResetContentDescriptor node REQUEST to PARSE the MESSAGE with different parser, leaving the message CONTENT unchanged.

ResetContentDescriptor node request to parse the message with different parser, leaving the message content unchanged.

 mqsichangebroker COMMAND is USED to MODIFY BROKER PARAMETERS.

 mqsichangebroker command is used to modify broker parameters.

The Sequence NODE enables you to receive GROUPS of MESSAGES from an input SOURCE, and preserve the ORDER in which the messages in each group arrived.

The Sequence node enables you to receive groups of messages from an input source, and preserve the order in which the messages in each group arrived.

 The PROPAGATE statement is used to generate multiple output messages in the Compute NODE. The output messages may have same or different MESSAGE content. You can ALSO send output messages to any alternate output terminals of the Compute node.

 The PROPAGATE statement is used to generate multiple output messages in the Compute node. The output messages may have same or different message content. You can also send output messages to any alternate output terminals of the Compute node.

A MESSAGE is PUT to a QUEUE DEFINED as TRIGGERING.

A message is put to a queue defined as Triggering.

A multipart MESSAGE contains ONE or more other messages within its structure. The contained message is sometimes referred to as an embedded message. A multipart message must CONTAIN a group, or a COMPLEX type, with its Composition property set to Message.

A multipart message contains one or more other messages within its structure. The contained message is sometimes referred to as an embedded message. A multipart message must contain a group, or a complex type, with its Composition property set to Message.

A message DEFINITION file contains the messages, elements, types, and groups which make up a message MODEL within a message set. Every message set requires at least one message definition file to describe its messages. Message definition FILES USE the XML Schema LANGUAGE to describe the logical format of one or more messages.

A message definition file contains the messages, elements, types, and groups which make up a message model within a message set. Every message set requires at least one message definition file to describe its messages. Message definition files use the XML Schema language to describe the logical format of one or more messages.

 A MESSAGE set is a folder in a message set PROJECT that contains a LOGICAL grouping of your messages and the objects that COMPRISE them (ELEMENTS, types, groups).

 A message set is a folder in a message set project that contains a logical grouping of your messages and the objects that comprise them (elements, types, groups).

 The mqsicreatemsgdefs COMMAND has a BULK IMPORT CAPABILITY, but mqsicreatemsgdefsfromwsdl imports only one WSDL definition at a time.

 The mqsicreatemsgdefs command has a bulk import capability, but mqsicreatemsgdefsfromwsdl imports only one WSDL definition at a time.

You can create a message model by using the following methods:

• Importing an application message format that is described by an XML SCHEMA, XML DTD, C structure, COBOL structure, SCA IMPORT or export, or WSDL definition.
• By creating an empty message model file, then creating your message by using the editors provided in the WEBSPHERE Message Broker Toolkit.
• By using the ADAPTER Connection wizard to import EIS metadata.
• By creating a populated model file from example message data.

You can create a message model by using the following methods:

Even if your messages are self-defining, and do not REQUIRE modeling, message modeling has the FOLLOWING advantages:

1. Runtime validation of messages. Without a message model, a parser cannot check whether input and output messages have the correct structure and data values.
2. Enhanced parsing of XML messages. Although XML is self-defining, all data values are treated as strings if a message model is not used. If a message model is used, the parser is provided with the data type of data values, and can cast the data accordingly.
3. Improved productivity when writing ESQL. When you are CREATING ESQL programs for WebSphere Message Broker message flows, the ESQL editor can USE message models to provide code completion assistance.
4. Drag-and-drop operations on message maps. When you are creating message maps for WebSphere Message Broker message flows, the Message Mapping editor uses the message model to populate its source and target views. Without message models, you cannot use the Message Mapping editor.
5. Reuse of message models, in whole or in part, by creating additional messages that are based on existing messages.
6. Generation of documentation.
7. PROVISION of version control and access control for message models by storing them in a central repository.

Even if your messages are self-defining, and do not require modeling, message modeling has the following advantages:

Most message formats are not self-defining, and a parser must have access to a PREDEFINED model that describes the message, if it is to PARSE the message correctly. A message model is USED by WebSphere Message BROKER to model a message format.

Most message formats are not self-defining, and a parser must have access to a predefined model that describes the message, if it is to parse the message correctly. A message model is used by WebSphere Message Broker to model a message format.

 There are two general APPROACHES to handle errors in a message flow:

• FAILURE CHECKING
• CATCHING Exceptions

 There are two general approaches to handle errors in a message flow:

 We can TRANSFORM and enrich messages by USING one or more of the following techniques:

Mappings

ESQL

Java

XSL STYLE sheets

PHP

.NET

 We can transform and enrich messages by using one or more of the following techniques:

Mappings

ESQL

Java

XSL style sheets

PHP

.NET

Publish/subscribe is a STYLE of messaging APPLICATION in which the PROVIDERS of INFORMATION (publishers) are DECOUPLED from the consumers of that information (subscribers).

Publish/subscribe is a style of messaging application in which the providers of information (publishers) are decoupled from the consumers of that information (subscribers).

We can ACCESS a database from a MESSAGE FLOW by USING the following NODES:

Compute

Database

DatabaseInput

DatabaseRetrieve

DatabaseRoute

Filter

JavaCompute

Mapping

We can access a database from a message flow by using the following nodes:

Compute

Database

DatabaseInput

DatabaseRetrieve

DatabaseRoute

Filter

JavaCompute

Mapping

 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.

 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.

USE CALL KEYWORD to call FUNCTIONS or METHODS.

Use CALL keyword to call functions or methods.

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 .

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 .

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.

Patterns provide the following benefits:

 A pattern CAPTURES a tested SOLUTION to a commonly RECURRING problem, addressing the objectives that you want to achieve.

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

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 node’s ESQL that DECLARES the variable.
• Initialized when the first message pass through the node or flow after broker startup.

External variables:

Normal Variables:

Shared variable:

ESQL VARIABLES can be DESCRIBED as external variables, NORMAL variables, or SHARED variables.

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

• 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

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.

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.

ESQL can be USED with the COMPUTE, Database, and FILTER NODES.

ESQL can be used with the Compute, Database, and Filter nodes.

 Message Broker supports XML, TDS, CSV, CWF, EDIFACT, SWIFT, COBOL FORMATS

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

USING MQSC property CURDEPTH we can KNOW the current depth of a QUEUE.

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

 QUEUE DEPTH, is the NUMBER of PENDING input/output MESSAGES in a queue.

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

 Using MRM domain we can INPUT MESSAGES with DIFFERENT – different DELIMETERS between the fields in WMB.

 Using MRM domain we can input messages with different – different delimeters between the fields in WMB.

 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.

 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.

In DATA Source specify the NAME by which the appropriate database is KNOWN on the system on which this message flow is to execute.

In Data Source specify the name by which the appropriate database is known on the system on which this message flow is to execute.

 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

 The Compute node is used to:

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.

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.

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.

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.

The SOAP ASYNC Request 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.

The SOAP Async Request 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.

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.

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.

ResetContentDescriptor NODE request to parse the MESSAGE with DIFFERENT PARSER, leaving the message content unchanged.

ResetContentDescriptor node request to parse the message with different parser, leaving the message content unchanged.

A correlation NAME is a FIELD REFERENCE referencing a well-defined starting point in the logical MESSAGE tree and to describe a standard PART of the tree format.

A correlation name is a field reference referencing a well-defined starting point in the logical message tree and to describe a standard part of the tree format.

 WMB provide SUPPORT for FOLLOWING type of messages:

1. MRM
2. XML
3. XMLNS
4. XMLNSC
5. JMSMap
6. JMSStream
7. MIME
8. BLOB
9. IDOC
10. TOP

 WMB provide support for following type of messages:

1. When the Destination queue is full
2. When the Destination queue doesn’t exist
3. When the INCOMING MESSAGE too large
4. When the SENDER is not authorized to USE the destination queue.

The environment tree differs from the LOCAL environment tree in that a single INSTANCE of it is maintained throughout the message flow. If you include a COMPUTE node, a Mapping node, or a JavaCompute node in your message flow, you do not have to specify whether you WANT the environment tree to be included in the output message. The environment tree is included automatically, and the entire contents of the input environment tree are retained in the output environment tree. Any changes that you make are available to subsequent nodes in the message flow, and to previous nodes.

The environment tree differs from the local environment tree in that a single instance of it is maintained throughout the message flow. If you include a Compute node, a Mapping node, or a JavaCompute node in your message flow, you do not have to specify whether you want the environment tree to be included in the output message. The environment tree is included automatically, and the entire contents of the input environment tree are retained in the output environment tree. Any changes that you make are available to subsequent nodes in the message flow, and to previous nodes.

Then the MESSAGE GOES to the RELEVANT DEAD LETTER queue.

Then the message goes to the relevant dead letter queue.

Message will be BACKED out and an EXCEPTION will be thrown with the message no queue NAME is DEFINED.

Message will be backed out and an exception will be thrown with the message no queue name is defined.

COMPUTE Node, Message Mapping Node, Filter Node, ResetContentDescriptor Node CA CHANGE message in a message flow.

Compute Node, Message Mapping Node, Filter Node, ResetContentDescriptor Node ca change message in a message flow.

There are two TYPES of clients in MQ:

1. Fat Clients: Does have a local queue manager.
2. SLIM clients: Does not have a local queue manager, whereas the queue manager reside on the server.

There are two types of clients in MQ:

1. Local QUEUE
2. REMOTE queue
3. TRANSMISSION queue
4. Alias queue
5. Dead letter queue

• USER TRACE
• SERVICE trace.

 The purpose of a FILTER NODE is to route a MESSAGE based on the CONTENT dynamically

 The purpose of a filter node is to route a message based on the content dynamically

LOGICAL MESSAGE TREE is the INTERNAL REPRESENTATION of a message.

Logical message tree is the internal representation of a message.