Explore topic-wise InterviewSolutions in .

Yes. We can create MULTIPLE instance of a MESSAGE flow by deploying the message flows to DIFFERENT EXECUTION group.

Yes. We can create multiple instance of a message flow by deploying the message flows to different execution group.

1. AggregateControl
2. AggregateRequest
3. AggregateReply

The mqsiapplybaroverride COMMAND is used to replace CONFIGURABLE values in the broker archive (BAR) with NEW values that you specify in a PROPERTIES file.

The mqsiapplybaroverride command is used to replace configurable values in the broker archive (BAR) with new values that you specify in a properties file.

mqsipackagebar COMMAND.

mqsipackagebar command.

 BROKER Archive or BAR is a package of message flows, message sets, java UTILITY CLASSES, xslts etc. that are grouped together to be deployed on the broker.

 Broker Archive or BAR is a package of message flows, message sets, java utility classes, xslts etc. that are grouped together to be deployed on the broker.

 Packaging SERVICES in a BAR FILE and deploy the BAR file on the BROKER.

 Packaging services in a BAR file and deploy the BAR file on the broker.

 PHYSICAL REPRESENTATION of a MESSAGE is a FORMAT.

 Physical Representation of a message is a Format.

A Parser is a program that takes the INCOMING message, interprets its BIT stream and CREATES an INTERNAL representation of it in a tree like structure, which can be then understand by message broker assembly.

A Parser is a program that takes the incoming message, interprets its bit stream and creates an internal representation of it in a tree like structure, which can be then understand by message broker assembly.

A message FLOW DESCRIBES the SEQUENCE of steps followed in the broker that processes an INPUT message when an input message is RECEIVED.

A message Flow describes the sequence of steps followed in the broker that processes an input message when an input message is received.

The perspectives MAINLY used while the development in message broker:

1. Administration PERSPECTIVE
2. Application Development Perspective
3. Debugging Perspective
4. JAVA Perspective (MB 6)

The perspectives mainly used while the development in message broker:

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.

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.

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.

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.

Enterprise Application INTEGRATION REFERS to the integration of one or more applications and processes together.

TOOLS: WBI Message Broker, TIBCO, WebMethods and IC

Enterprise Application Integration refers to the integration of one or more applications and processes together.

Tools: WBI Message Broker, Tibco, WebMethods and IC

 ADMINISTRATOR PERSPECTIVE is USED to DEPLOY the FLOW.

 Administrator perspective is used to deploy the flow.

To CONNECT to the remote BROKER or LOCAL broker and to deploy the message FLOWS onto the Broker.

To Connect to the remote broker or local broker and to deploy the message flows onto the Broker.

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

Using the mqsideploy COMMAND one can DEPLOY the bar FILES.

Using the mqsideploy command one can deploy the bar files.

Not a SINGLE QUEUE MANAGER cannot have TWO BROKERS.

Not a single queue manager cannot have two brokers.

The User Name Server interfaces with OPERATING system FACILITIES to PROVIDE information about valid USERS and groups in a broker domain.

The User Name Server interfaces with operating system facilities to provide information about valid users and groups in a broker domain.

The User Name Server is an optional RUNTIME component that PROVIDES AUTHENTICATION of USERS and groups and give an ADMINISTRATIVE control over who can publish and who can subscribe operations.

The User Name Server is an optional runtime component that provides authentication of users and groups and give an administrative control over who can publish and who can subscribe operations.

 mqsicreatebroker is the COMMAND USED to CREATE BROKER.

 mqsicreatebroker is the command used to create broker.

 TWO ways to create BROKER:

1. By using WEBSPHERE Message Broker Explorer.
2. By using COMMAND PROMPT.

 Two ways to create broker:

The RUNNING BROKER will ALSO be down at the moment when configuration manager is down.

The running broker will also be down at the moment when configuration manager is down.

 A MESSAGE FLOW NODE receives a message, performs a set of actions against the message, passes the ORIGINAL message or the changed message, to the NEXT node in the message flow.

 A message flow node receives a message, performs a set of actions against the message, passes the original message or the changed message, to the next node in the message flow.

GROUP of brokers under a single configuration manager constitute a BROKER DOMAIN.

Group of brokers under a single configuration manager constitute a Broker Domain.

The main COMPONENTS used in MESSAGE Broker NAME Server are

1. USER Name Server
2. Configuration Manager
3. Broker

The main components used in Message Broker Name Server are

Websphere message broker provides services, based on message brokers to allow you to:

1. Route a message to SEVERAL DESTINATIONS, using rules that act on the contents of one or more of the fields in the message or message header.
2. Transform a message, so that applications using different formats can EXCHANGE messages in their own formats.
3. Store a message, or part of a message, in a database.
4. Retrieve a message, or part of a message, from a database.
5. Modify the contents of a message; for example, by adding data EXTRACTED from a database.

Websphere message broker provides services, based on message brokers to allow you to:

WebSphere MQ facilitates communication between applications by sending and receiving message data via messaging queues. WebSphere MQ provides a secure and reliable layer of transport for MOVING data unchanged in the form of messages between applications but it is not aware of the content of the messages.

WebSphere Message Broker is built to extend WebSphere MQ, and it is capable of understanding the content of each message that it moves through the Broker.

Message Broker can do the following:

•  Matches and ROUTES communications between services
• Converts between different transport PROTOCOLS
• Transforms message formats between requestor and service
• Identifies and distributes business events from DISPARATE SOURCES.

WebSphere MQ facilitates communication between applications by sending and receiving message data via messaging queues. WebSphere MQ provides a secure and reliable layer of transport for moving data unchanged in the form of messages between applications but it is not aware of the content of the messages.

WebSphere Message Broker is built to extend WebSphere MQ, and it is capable of understanding the content of each message that it moves through the Broker.

Message Broker can do the following:

 Both MESSAGE broker and mq works as MIDDLEWARE programs, that is to help communicating DIFFERENT SYSTEMS, but mq has a slight DRAWBACK that it cannot transform the messages. It can just send the message to other system.

 Both message broker and mq works as middleware programs, that is to help communicating different systems, but mq has a slight drawback that it cannot transform the messages. It can just send the message to other system.

 A MESSAGE Broker is an INTERMEDIARY program that HELPS communicating MULTIPLE system to each other by transforming, routing the MESSAGES in the way they need.

 A Message Broker is an intermediary program that helps communicating multiple system to each other by transforming, routing the messages in the way they need.

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

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

SCADAInput, HTTPInput, FileInput, Real-timeInput, JMSInput, CUSTOM INPUT NODES.

SCADAInput, HTTPInput, FileInput, Real-timeInput, JMSInput, Custom Input nodes.

1. ADMINISTRATION PERSPECTIVE
2. Application DEVELOPMENT Perspective
3. Debugging Perspective
4.  Java Perspective .

We DEPLOY flows in Administration Perspective .

We deploy flows in Administration Perspective .

Root is used in the Database content changing and in Filter node. OutputRoot is used in the ESQL CODE for a Compute node that creates a NEW OUTPUT MESSAGE based on the input message.

Root is used in the Database content changing and in Filter node. OutputRoot is used in the ESQL code for a Compute node that creates a new output message based on the input message.

XML, TDS, CWF, EDI, SWIFT.

XML, TDS, CWF, EDI, SWIFT.

USING the “CALL” KEYWORD.

Using the “CALL” keyword.

1. MQInput NODE
2.  MQOUTPUT node
3. COMPUTE node
4. DATABASE node
5. AggregateControl node
6. FILTER node.

COMPUTE NODE, FILTER Node an ResetContentDescriptor node.

Compute Node, Filter Node an ResetContentDescriptor node.

MESSAGE Domain, Message SET, Message Type, Message FORMAT, Topic.

Message Domain, Message Set, Message Type, Message Format, Topic.

ROUTING, TRANSFORMATION and INTEGRATION.

Routing, Transformation and Integration.