Friday, November 27, 2015

Some basic question on IBM MB..

Q: What exactly do you understand by message broker??
Ans: 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.

Q: Why do we require message broker when we have MQ?
Ans: 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.

Q:What is the difference between Message Broker and MQ?
Ans: 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.

Q:What are the advantages of using Websphere message broker?
Ans: Websphere message broker provides services, based on message brokers to allow you to:
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.
Transform a message, so that applications using different formats can exchange messages in their own formats.
Store a message, or part of a message, in a database.
Retrieve a message, or part of a message, from a database.
Modify the contents of a message; for example, by adding data extracted from a database.

Q: What all are the main components used in Message Broker?
Ans: The main components used in Message Broker Name Server are
User Name Server
Configuration Manager
Broker

Q: What do you understand by Broker Domain?
Ans: Group of brokers under a single configuration manager constitute a Broker Domain.

Q:What is the significance of nodes in message flows?
Ans: 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.

Q:If configuration manager is down, what are the effects on the running brokers?
Ans: The running broker will also be down at the moment when configuration manager is down.

Q:How can we create broker?
Ans: Two ways to create broker:
By using Websphere Message Broker Explorer.
By using command prompt.

Q:What is the command use to create broker?
Ans: mqsicreatebroker is the command used to create broker.

Q:What is User name Server?
Ans: 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.

Q:What is the Role of Username server?
Ans: The User Name Server interfaces with operating system facilities to provide information about valid users and groups in a broker domain.

Q:Can a single queue manager have two brokers?
Ans: No a single queue mnager cannot have two brokers.

Q:With Which command one can deploy the bar files?
Ans: Using the mqsideploy command one can deploy the bar files.

Q:What is the difference between a Root and OuputRoot?
Ans: 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 Use of Configmanager?
Ans: To Connect to the remote broker or local broker and to deploy the message flows onto the Broker.

Q:Which perspective you used to deploy the flow?
Ans: Administrator perspective is used to deploy the flow.

Q:What do you understand by EAI? Name some EAI tools?
Ans: Enterprise Application Integration refers to the integration of one or more applications and processes together.
Tools: WBI Message Broker, Tibco, WebMethods and ICS

Q: What are the Features of Message Broker?
Ans: WMB has many features, The main features are :
Routing
Transformation and
Integration

Q: What do you mean by an Execution Group?
Ans: 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.

Q: What is the significance of SCHEMA in message broker?
Ans: 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 are the perspectives you have mainly used while development in message broker?
Ans: The perspectives mainly used while the development in message broker are

Administration Perspective
Application Development Perspective
Debugging Perspective
Java Perspective (MB 6)

Wednesday, August 19, 2015

Troubleshooting and support

If you are having problems with your queue manager network or WebSphere® MQ applications, use the techniques described to help you diagnose and solve the problems.
For an introduction to troubleshooting and support, see Troubleshooting overview.
There are some initial checks that you can make for your platform to help determine the causes of some common problems. See the appropriate topic for your platform:
For information about solving problems, see Dealing with problems.
For information about solving problems for WebSphere MQ Telemetry, see Troubleshooting for WebSphere MQ Telemetry.
For information about solving problems when you are using channel authentication records, see Troubleshooting channel authentication records.
Information that is produced by WebSphere MQ can help you to find and resolve problems. For more information, see the following topics:
For information about recovering after a problem, see Recovering after failure.
You can also read the general troubleshooting guidance in the following topics:
If a WebSphere MQ component or command has returned an error, and you want further information about a message written to the screen or the log, you can browse for details of the message, see Reason codes.

Wednesday, May 27, 2015

WebSphere MQ Multi-Instance Queue Managers Creations

Server1:
Create the logs and qmgrs directory in the shared file system:
# mkdir logs
# mkdir data
# chown -R mqm:mqm /mqha
# chmod -R ug+rwx /mqha
Create the queue manager:
# crtmqm -ld /mqha/log/ -md /mqha/data/ TEST
WebSphere MQ queue manager created.
Directory '/mqha/data/TEST' created.
The queue manager is associated with installation 'Installation1'.
Creating or replacing default objects for queue manager 'TEST'.
Default objects statistics : 74 created. 0 replaced. 0 failed.
Completing setup.
Setup completed.
#
Copy the queuemanager configuration details from Server1:
#  dspmqinf -o command TEST
Copy the output of the above command to Notepad. The output will be in the following format:
addmqinf -s QueueManager -v Name=TEST -v Directory=TEST -v Prefix=/var/mqm -v DataPath=/mqha/data/TEST


Server:2
Paste the output of the command was saved in Notepad in Step 4:
# addmqinf -s QueueManager -v Name=TEST -v Directory=TEST -v Prefix=/var/mqm -v DataPath=/mqha/data/TEST
WebSphere MQ configuration information added.
#
Start the active instance of queue manager on Server 1:
# strmqm -x TEST
WebSphere MQ queue manager 'TEST' starting.
The queue manager is associated with installation 'Installation1'.
5 log records accessed on queue manager 'TEST' during the log replay phase.
Log replay for queue manager 'TEST' complete.
Transaction manager state recovered for queue manager 'TEST'.
WebSphere MQ queue manager 'TEST' started using V7.5.0.2.
#
Start the standby instance of queue manager on Server 2:
# strmqm -x TEST
WebSphere MQ queue manager 'TEST' starting.
The queue manager is associated with installation 'Installation1'.
A standby instance of queue manager 'TEST' has been started. The active
instance is running elsewhere.
#
Verify the setup using dspmq -x:
On Server1 (stallion)
# dspmq -x
QMNAME(TEST) STATUS(Running)
INSTANCE(ausul3mq03.us.dell.com) MODE(Active)

#
On Server2 (saigon)
# dspmq -x
QMNAME(TEST) STATUS(Running as standby)
INSTANCE(ausul3mq03.us.dell.com) MODE(Active)
INSTANCE(ausul3mq04.us.dell.com) MODE(Standby)


**Testing - Creating a client auto-reconnect setup:
Create a local queue called TESTQ with defpsist(yes).
# DEF QL(TESTQ) DEFPSIST(YES)
DEF QL(TESTQ) DEFPSIST(YES)
AMQ8006: WebSphere MQ queue created.

Create a svrconn channel called TEST.SVRCONN.01.
# DEF CHL(TEST.SVRCONN.01) CHLTYPE(SVRCONN) TRPTYPE(TCP)
DEF CHL(TEST.SVRCONN.01) CHLTYPE(SVRCONN) TRPTYPE(TCP)
      DEF CHL(TEST.SVRCONN.01) CHLTYPE(SVRCONN) TRPTYPE(TCP)
AMQ8014: WebSphere MQ channel created.

Create a listener TCP.LSTR with port 9898
# Def lstr(TCP.LSTR) trptype(TCP) port(9898)
Def lstr(TCP.LSTR) trptype(TCP) port(9898)
AMQ8626: WebSphere MQ listener created.

# Start lstr(TCP.LSTR)
Start lstr(TCP.LSTR)
AMQ8021: Request to start WebSphere MQ listener accepted.

**Executing the client auto-reconnect samples
ON Server 1 : Invoke the amqsphac sample program:

# amqsphac TESTQ TEST

In another window on Server 1, end the queue manager with the "-is" option so that it will switch over to a standby queue manager:

#  endmqm -is TEST

Verify that a switchover has occurred: On Server2
# dspmq -x -o standby