Click here to Skip to main content
15,884,177 members
Please Sign up or sign in to vote.
0.00/5 (No votes)
See more:
Hi,

I am working on a VB6.0 to VB.Net migration project. Also currently there is an IBM MQ setup to which the VB6.0 application connects in the output mode and then puts messages in the Queue which I believe is in xml format.

We also have a requirement of getting rid of this IBM MQ and implementing MSMQ instead of it.

So these are my Questions:

1) Is it possible?
2) Will the applications which are reading this Queue also require some change?
3) How complex or difficult will this be?
4) Can someone give an overview of steps which need to be followed to achieve this?

I am really confused about this. Please help.
Posted
Updated 31-Jul-12 6:44am
v3

1 solution

-- 1) Is it possible?
Yes.

-- 2) Will the applications which are reading this Queue also require some change?
Absolutely.

-- 3) How complex or difficult will this be?
Depends on what the queue does.

-- 4) Can someone give an overview of steps which need to be followed to achieve this?
A. Learn MSMQ
B. (Probably) write an API that wraps MSMQ and yet looks similar to what you are using for IBM MQ.
C. Modify existing code to use B.

On gotcha that might or might not matter...MSMQ has a hard limit of 4 megs of data (so 4 megs of bytes including MSMQ overhead). In practice in specific applications then limited my usage to about 1.5 megs of text data.

Other potential problem areas is that if at least (maybe all) cases if MSMQ persistence storage (files) reach their max of 2 gigs then MSMQ just locks up.
And figuring out how MSMQ routes is ridiculously hard. Especially if you choose to use 'public' queues (which then rely on Active Directory.)
 
Share this answer
 

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)



CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900