Making an existing queue manager the default

on version 5.3
"On Windows systems, use the WebSphere MQ Services snap-in to display the properties of the queue manager, and check the Make queue manager the default box. You need to stop and restart the queue manager for the change to take effect. "
the above instruction  are from Creating a queue manager

on version 6 and 7
On WebSphere® MQ for Windows® and WebSphere MQ for Linux® (x86 platform) systems, you can make an existing queue manager the default queue manager as follows:
1.Open the WebSphere MQ Explorer.
2.Right-click IBM WebSphere MQ, then select Properties.... The Properties for WebSphere MQ panel is displayed.
3.Type the name of the default queue manager into the Default queue manager name field.
4.Click OK.
thats from here http://publib.boulder.ibm.com/infocenter/wmqv7/v7r0/index.jsp?topic=/com.ibm.mq.amqzag.doc/fa10880_.htm


Yaniv

Configuring WebSphere MQ with the WebSphere MQ Explorer - Version: 5.3

The next link is a step by step of description + images , how to set queue manager , and local queue, via MQ explorer , i think its version 5.3.
i find it very useful for beginners .
http://support.sas.com/rnd/itech/doc9/dev_guide/messageq/mqexplor.html

enjoy
Yaniv T

Simple login page in asp.net form

sometimes you just want a simple login page , with user name and password, nothing more.
so here is a very quick and easy solution i just found.
ASP.NET version of "Login & Password" 

secure your pages
Yaniv T

Queue manager on mainframe / zos.

I have a program that put messages on MQ series its its working like a charm , the other side can pick up the message and everyone are happy, the MQ series installed on windows.
We try to deploy our program on the client environment they only changes was that the MQ series installed on mainframe, we knew that, but MQ is multi-platform OS there was no worries, so we manged to connect to the Queue manager and put a message , the problem was the other side could not pick up the message we sent.
we could not find what can cause it , untill we found this thread strange mq client behaviour whan connecting to mainframe

"Mainframe queue managers use syncpoint by default, other platforms do not. Messages are going onto the mainframe queue (causing the count to increase) but are not eligable to be read back (appearing to be blank) and eventually roll back (causing the count to decrease again). Use an explicit commit (like q.exe does). It won't affect running again non-mainframe queue managers."

so right after the put messages i used
qmgr.commit
and the other side could pick up my message from the mainframe queue - that's worked !!!

enjoy
Yaniv T

How to redirect requests from IIS to Tomcat server ?

i found very good links and articles that you will find them useful in case you want to redirect calls / requests from IIS to tomact server.
a step by step guide can be found here how to configure IIS 6 and tomcat with jk 1.2 connector also for IIS 7 on windows server 2008 .

and The Apache Tomcat Connector - Reference Guide
The Apache Tomcat Connector - Webserver HowTo

hope its get you to business
Yaniv T