Create Free Blog | Random Blog »   Report Abuse | Login   

 

Setting up Message Broker environment

Technical, websphere message broker No Comments »

=> Setting up the command environment
After you have installed the product on any of the distributed systems, you must initialize the environment before you can use any runtime component or command.

When you start a runtime component on Linux and UNIX systems, it inherits the environment from where you issue the mqsistart command. You must therefore initialize the environment before you start a component; the command mqsiprofile located in the directory install_dir/bin, performs this initialization.

You must not change the location of the mqsiprofile command, or make user modifications to the command, because it might be replaced if you install service, or an update, to the product.

If you want to run your own additional environment settings, add a script called your_file_name.sh to the broker’s work_path directory which contains the:  /common/profiles subdirectory. When you run mqsiprofile again, the command automatically calls the additional user-written scripts in this location. The newly added script will not be picked up if you run an mqsistart command from an existing initialized command shell. work_path identifies the broker’s working directory; if you are unsure of the broker’s work path, enter the following command: echo $MQSI_WORKPATH Read the rest of this entry »

Websphere MQ Clustering presentation

Technical, WebSphere MQ 2 Comments »

http://www.youtube.com/v/DjsdTIpAxP0&hl=en&fs=1

Websphere MQ Triggering presentation

Technical, WebSphere MQ No Comments »

Whats up?

Uncategorized No Comments »

Hi Guys…

Seems like this weekend and next week, i’ll free. Of course i’ve one important think to do, its EPL match.

Want to see what am i doin? check: http://twitter.com/activexpert

Some of you mailed me that - Why were you not making any videos?

Actually i lost the software, which i used for making those MQ videos :-(.  I bought the same software again, so let me try few more videos on Saturday.

This sunday is Liverpool vs Manchester United march….waiting for it.

Websphere MQ Dead Letter Queue (DLQ)

Technical, WebSphere MQ No Comments »

Dead Letter Queue
- When messages can not be delivered to the intended queue, the messages may be delivered to a Dead Letter Queue (DLQ) if the queue manager has one defined.
- By default a queue manager does not have a DLQ but you should define one for every queue manager.

Dead Letter Messages
Messages can be placed on the DLQ by the queue manager, the channels (MCA) or by applications
When the messages are put onto DLQ, they should have a Dead Letter Header (DLH). DLH will be generated by Queue manager and MCA.
If application are putting the messages onto DLQ, applications must create the DLH.

MQRC and MQFB
Reason code in the MQDLH will be a value from either the MQRC reason codes or MQFB feedback codes Read the rest of this entry »

creating a cluster in websphere MQ (code)

Technical, WebSphere MQ 1 Comment »


Queue Managers: QM1,2 (full repos), QM3,4 (partial repos)
NOTE: all queue managers are on same machine
Change my name in the commands, if you don’t want it in your machine :-):) Read the rest of this entry »

Bridging clusters in Websphere MQ

Technical, WebSphere MQ No Comments »
Bridging two clusters in mq

Bridging two clusters in mq

The above picture has:

BLOG cluster with QM1 having Q1
WIKI cluster with QM3 having Q3
QM2 is the bridge for the two clusers. Read the rest of this entry »

Theme & Icons by N.Design Studio.
All rights reserved. http://activexpert.blog.co.in | Powered by Blog.co.in
Entries RSS Comments RSS Log in