Professional Documents
Culture Documents
MQ Interview Question
MQ Interview Question
MQ Interview Question
its provide
all the resources used by application during the runtime.
Domain: each and every weblogic server contain a domain, every weblogic server resources is
in the domain
IBM Middleware platform is implemented as SOA, which IBM call IBM WebSphere integration
reference architecture.
Synchronous: In this type of messaging, client waits for the server to respond to a message. Ex:
Telephone call, two way radio communication.
Asynchronous: In this type of messaging, client does not wait for a message from the server, but
automatically an event is created to trigger a message from a server. Ex: email, text messaging, blog
posting.
Answer :
MQ stands for MESSAGE QUEUEING. WebSphere MQ allows application programs to use message
queuing to participate in message-driven processing. Application programs can communicate across
different platforms by using the appropriate message queuing software products.
Answer :
- Integration.
- Asynchrony
- Assured Delivery
- Scalability.
Question 5. What Is Asynchrony?
Answer :
With message queuing, the exchange of messages between the sending and receiving programs is
independent of time. This means that the sending and receiving application programs are
decoupled; the sender can continue processing without having to wait for the receiver to
acknowledge receipt of the message. The target application does not even have to be running when
the message is sent. It can retrieve the message after it is has been started.
Ans: A message is a string of bytes that is meaningful to the applications that use it. Messages are
used to transfer information from one application program to another (or between different parts of
the same application). The applications can be running on the same platform, or on different
platforms.
1. The application data. The content and structure of the application data is defined by the
application programs that use it.
2. A message descriptor. The message descriptor identifies the message and contains additional
control information, such as the type of message and the priority assigned to the message by the
sending application. WebSphere MQ defines the format of the message descriptor
Q8.What is Queue?
Ans: A queue is a data structure used to store messages. A queue manager owns each queue. The
queue manager is responsible for maintaining the queues it owns, and for storing all the messages it
receives onto the appropriate queues
Ans: 1414
Q20.What is channel and mention different types of channels in MQ?
Ans: Channels are objects that provide a communication path from one queue manager to another.
Channels are used in distributed queuing to move messages from one queue manager to another.
They shield applications from the underlying communications protocols. The queue managers might
exist on the same, or different, platforms. Different types of Channels:
1. Sender-Receiver Channels
2. Requester-Server Channels
3. Client Connection channels
4. Server Connection Channels.
5. Cluster Sender.
6. Cluster Receiver Channels
Q21What is Cluster?
Ans: A cluster is a group of queue managers set up in such a way that the queue managers can
communicate directly with one another over a single network, without the need for transmission
queue, channel, and remote queue definitions.
Q22.What is MQ Client?
Ans: A Web Sphere MQ client is a component that allows an application running on a system to issue
MQI calls to a queue manager running on another system. The output from the call is sent back to
the client, which passes it back to the application.
Q23.What is MQ Server?
Ans: A Web Sphere MQ server is a queue manager that provides queuing services to one or more
clients. All the Web Sphere MQ objects, for example queues, exist only on the queue manager
machine (the Web Sphere MQ server machine), and not on the client. A Web Sphere MQ server can
also support local Web Sphere MQ
Applications.
Q24.What are commands used for creating the Queue manager from the Command prompt?
Here -q used to define the Queue manager QM1 as a Default Queue manager
-d is used to define the default transmission Queue -u is used to define the default dead letter
queue.
Q25.Where are the backup files are present after creating the Queue Manager?
Ans: Windows systems: If you use Web Sphere MQ for Windows NT and Windows 2000,
configuration information is stored in the Windows Registry.
UNIX Systems: 1. When you install the product, the Web Sphere MQ configuration file (mqs.ini) is
created. It contains a list of queue managers that is updated each time you create or delete a queue
manager. There is one mqs.ini file per node.
2. When you create a new queue manager, a new queue manager configuration file (qm.ini) is
automatically created. This contains configuration parameters for the queue manager.
The command waits until all applications have stopped and the queue manager has ended.
endmqm –i QMName
This type of shutdown does not wait for applications to disconnect from the queue manager.
Ans: The client can establish a connect with the Server using the command
Here SYSTEM.ADMIN.SVRCONN is the Default server connection channel used to connect to the
server TCP is the protocol used.IPADDRESS is the IP address of the server PORT: Port no is the no on
which the QueueManager is running
Ans: You can use MQSC commands to manage queue manager objects, including the queue manager
itself, clusters, channels, queues, namelists, process definitions, and authentication information
objects.
Display qmgr
Q40.What is Triggering?
Q43.What is the Default location where the logs are stored and mention the default sizes?
UNIX: /var/mqm/log
Ans: If the target queuemanager doesn.t contain the dead letter queue defined and if the messages
are running on a fast channel and of non persistant,Then there is a chance of the message loss.
Q63.How many no Full Repository Queue Managers are required for creating a cluster. What is the
difference between full and partial repositories?
Ans: In each cluster you must select at least one, preferably two, or possibly more of the queue
managers to hold full repositories. A cluster can work quite adequately with only one full repository
but using two improves availability. Every cluster has at least one (preferably two) queue managers
holding full repositories of information about the queue managers, queues, and channels in a
cluster. These repositories also contain requests from the other queue managers in the cluster for
updates to the information. The other queue managers each hold a partial repository, containing
information about the subset of queues and queue managers with which they need to
communicate.
Q64.Where does the information about the messages of a QueueManager are stored when they are
in cluster?
Ans: Each queue manager stores its repository information in messages on a queue called
SYSTEM.CLUSTER.REPOSITORY.QUEUE.
The queue managers exchange repository information in messages on a queue called
SYSTEM.CLUSTER.COMMAND.QUEUE.
Q65.What is the command that is used to provide authorization for the clients?
Ans: setmqaut -m QMName -t queue -n Queuename -p GUEST +all