Explore topic-wise InterviewSolutions in .

USING a MESSAGE set with the required XML format or by using validate node.

Using a Message set with the required XML format or by using validate node.

Mqsiformatlog, Mqsilist, Mqsichangetrace, mqsireadlog and mqsireporttrace.

Mqsiformatlog, Mqsilist, Mqsichangetrace, mqsireadlog and mqsireporttrace.

Hconn is a HANDLE USED to connect to QUEUE manager in MQCONN and MQCONNX api calls.

Hconn is a handle used to connect to Queue manager in MQCONN and MQCONNX api calls.

SET OutputLocalEnvironment.Destination.RouterList.DestinationData.labelname=’NAME of the LABEL to which the MESSAGE is to be ROUTED ’;

SET OutputLocalEnvironment.Destination.RouterList.DestinationData.labelname=’name of the label to which the message is to be routed ’;

By USING COMPUTE NODE, EMAIL node and JAVA compute node.

By using Compute node, email node and java compute node.

It CONTAINS the INFORMATION of the BROKER DOMAIN it is RELATED to.

It contains the information of the Broker Domain it is related to.

USING DEBUGGING PERSPECTIVE, USER TRACES.

Using Debugging perspective, User traces.

CONNECTING to the BROKER and to DEPLOY the MESSAGE FLOWS.

Connecting to the broker and to deploy the message flows.

By doing NODE CATALOG and the DATABASE catalog.

By doing node catalog and the database catalog.

• Message TREE
• Environment Tree
• LOCAL Environment Tree
• Exception LIST Tree

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.

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.

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.

Yes we can. One WAY is by ADDING multiple NODE. For ex. A single message flow can handle DATA received across MQ and Messages that are received across native IP connections.

Yes we can. One way is by adding multiple node. For ex. A single message flow can handle DATA received across MQ and Messages that are received across native IP connections.

By USING DEBUGGING PERSPECTIVE, and TRACE NODE.

By using Debugging perspective, and Trace node.

Specify in Data Source the name by which the APPROPRIATE DATABASE is known on the SYSTEM on which this message flow is to EXECUTE.

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

• To construct one or more new output messages.
• To build a new message using a SET of assignment statements.
• To OPY messages between parsers
• To convert messages from one code set to another
• To TRANSFORM messages from one FORMAT to another

CUSTOM INPUT NODES

Custom input nodes

By using debugging PERSPECTIVE. We can CREATE the Test Case ACCORDING to the client SPECIFICATION error CODES.

By using debugging perspective. We can create the Test Case according to the client specification error codes.

In the COMPUTE NODE we can CHANGE the HEADERS but in MAPPING node we can’t change.

In the compute node we can change the headers but in Mapping node we can’t change.

It is a REPOSITORY that will STORE the PREVIOUS VERSIONS.

It is a repository that will store the previous versions.

1. ROUTING,
2. TRANSFORMATION and
3. INTEGRATION

In the SUB FLOWS IMMEDIATE to the INPUT NODE.

In the sub flows immediate to the input node.

XML, TDS, CWF, EDI, SWIFT.

XML, TDS, CWF, EDI, SWIFT.

By USING MQSC PROPERTY CURDEPTH

By using MQSC property CURDEPTH

• TARGET QM,
• Target Q,
• RECEIVER CHANNEL and
• LISTENER

YES we can USE.

Yes we can use.

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

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

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

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

CIRCULAR logging GIVES you restart recovery. Linear logging gives you both restart recovery and media recovery.

Circular logging gives you restart recovery. Linear logging gives you both restart recovery and media recovery.

• CRTMQM
• STRMQM
• DLTMQM
• ENDMQM

TWO TYPES

1. a FAT CLIENTS
2. a SLIM clients

Two Types

• Destination Q is FULL
• Destination Q doesn’t EXIST
• Msg too large
• SENDER is not authorized to use the destination Q

• MRM
• XML
• XMLNS
• XMLNSC
• JMSMap
• JMSStream
• MIME
• BLOB
• IDOC

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.

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 DEPTH HIGH,Q Depth LOW,Q Depth FULL

Q Depth High,Q Depth Low,Q Depth Full

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

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

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

A message Flow is a SEQUENCE of PROCESSING STEPS that execute in the BROKER when an INPUT message when an input message is received.

A message Flow is a sequence of processing steps that execute in the broker when an input message when an input message is received.

USING DEBUGGING MODE, TRACE NODE ..etc..

Using Debugging Mode, Trace Node ..etc..

By USING runmqsc <Qmanager> COMMAND.

By using runmqsc <Qmanager> command.

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

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

GREP, FIND, sort…etc.

grep, find, sort…etc.

Queue MANAGER , SEND queue ,RECEIVE queue ,ADMINISTRATION queue, Administration queue ,RESTART queue ,Spill queue.

Queue manager , Send queue ,Receive queue ,Administration queue, Administration queue ,Restart queue ,Spill queue.

QUEUEMANAGER, SenderChannel, ReceiverChannel, LocalQueue

QueueManager, SenderChannel, ReceiverChannel, LocalQueue

UNIT TESTING with different TEST cases
Functional testing with the exact INPUT

Unit testing with different test cases
Functional testing with the exact input

WebSphere APPLICATION SERVER , Java MANAGEMENT Extensions (JMX).

WebSphere Application Server , Java Management Extensions (JMX).

USING the “CALL” KEYWORD.

Using the “CALL” keyword.

The ERROR message is “UNSET MANDATORY ‘Qname NAME’ Property on NODE ‘MQInput’ “.

The Error message is “Unset mandatory ‘Qname Name’ Property on node ‘MQInput’ “.

Group of brokers that coordinate a SINGLE configuration MANAGER constitute a Broker DOMAIN.

Group of brokers that coordinate a single configuration manager constitute a Broker Domain.

Enterprise APPLICATION INTEGRATION refers to the integration of ONE or more applications and processes together.

Tools: WBI Message Broker, ICS, WEBMETHODS and Tibco

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

Tools: WBI Message Broker, ICS, WebMethods and Tibco