| Author |
Message
|
| Keka |
 Posted: Sun Mar 27, 2005 2:18 am Post subject: MQSI 2.1 on XP PRO |
 |
|
Voyager
Joined: 28 Dec 2002
Posts: 96
|
Hi,
I installed MQSI v2.1 with CSD#3 on XP PRO with SP2.
When I try to create msgflow it lets me create the msgflow but when I try to drag and drop the nodes, it does not do anything. Also when I go to the topolozy tab and right click I do not see any option to register. To me it looks like there is something silly I am missing or incompatibility. As per IBM, MQSI CSD#3 is suported.
Can somebody help me out here..
_________________
Keka |
|
| Back to top |
|
 |
| hopsala |
| Posted: Sun Mar 27, 2005 4:44 am Post subject: |
|
|
Guardian
Joined: 24 Sep 2004
Posts: 960
|
Seems like you forgot to checkout the message flow.
Right-Click the message flow and select "Check Out", Only then you can dragdrop and edit nodes. When you finish editing rightclick and select "Check In", and then deploy the flow to update changes... |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Sun Mar 27, 2005 4:54 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
You are not running a supported configuration.
http://www-306.ibm.com/software/integration/mqfamily/platforms/supported/wsmq_integ_for_nt2000_2_1.html
| Quote: |
Microsoft Windows XP Professional (with SP1) for the Control Center and Configuration Manager components only.
The Broker can be installed on Windows XP Professional for development and testing activities, but not for production use.
(See Note 1).
|
| Quote: |
* Note 1 : The minimum supported combination is WMQIv2.1 CSD#5 + WMQ5.3 CSD#4.
|
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| Keka |
| Posted: Sun Mar 27, 2005 7:08 am Post subject: |
|
|
Voyager
Joined: 28 Dec 2002
Posts: 96
|
hopsala to answer your question, when I create a new msgflow, this is already checked out..So no need to check out separately.
Peter, when you say I am not running supported configuration, ou mean the SP2 on my XP??I thought at that time the notice was posted on IBM, the SP2 for XP did not come. I can roll back the SP2 and check but can you confirm..
Thanks for all the help
_________________
Keka |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Sun Mar 27, 2005 7:56 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Keka -
You should upgrade to the most recent CSD of 2.1.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| Keka |
| Posted: Sun Mar 27, 2005 11:08 am Post subject: |
|
|
Voyager
Joined: 28 Dec 2002
Posts: 96
|
I did that too. I installed CSD#8 . Recreated the config manager. Still the same. The only part I am missing is the CSD 4 for WebMQ but I don't think that is causing it as I did not even try deploying anything. I am just trying to create a msgflow by dragging and dropping the nodes and nothing happens..
_________________
Keka |
|
| Back to top |
|
|
| EddieA |
| Posted: Sun Mar 27, 2005 2:26 pm Post subject: |
|
|
Jedi
Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles
|
Sounds like the userID isn't part of the correct security groups.
Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| Back to top |
|
|
| Keka |
| Posted: Sun Mar 27, 2005 9:04 pm Post subject: |
|
|
Voyager
Joined: 28 Dec 2002
Posts: 96
|
There is no domain involved here. So the UserId is just part of the admin on the XP machine. There are no groups involved here..
Kiran
_________________
Keka |
|
| Back to top |
|
|
| EddieA |
| Posted: Sun Mar 27, 2005 11:20 pm Post subject: |
|
|
Jedi
Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles
|
I'm talking about the mqb* groups that are created when you install MQSI. You need to add your userID to some, or most, of these. Please read the Quick Beginnings Guide.
Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Mon Mar 28, 2005 12:37 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
| Keka wrote: |
Peter, when you say I am not running supported configuration, ou mean the SP2 on my XP??I thought at that time the notice was posted on IBM, the SP2 for XP did not come. I can roll back the SP2 and check but can you confirm..
Thanks for all the help |
IBM does not say SP2 is supported - you are running SP2.
If you were at XP SP1, you have to be at CSD5 (or higher) of WMQI 2.1, and you were only at CSD3. You do not indicate your MQ level, but there is a minumum with that as well.
That you went to CSD8 for WMQI is good, but check out your MQ version, and who knows what problems XP SP2 is giving you (maybe none - maybe all).
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| hopsala |
| Posted: Mon Mar 28, 2005 2:21 pm Post subject: |
|
|
Guardian
Joined: 24 Sep 2004
Posts: 960
|
Contrary to common opinion here, this does not sound like a compatibility problem to me.
Also, I just remembered that I once had a similar problem (i worked with the product several years ago), and that when first installing an MQSI broker there is a trick one must use to start working. I fear I do not remember the precise details but this should probably give you a good lead:
as you described, for some god forsaken reason, there is no way to register the broker in the Topology window. To begin working with MQSI you must first load (or import, I don't remember precisely the term) a sample topology that comes with the product (search the product libraries, you'll find it), then change the name of the broker registered to your broker, and deploy it. This should do the trick.
If this works, you should probably post here the exact solution, for future generations and all.
(I know MQSI is one of the most frustrating products out there, so my sympathies are with you...) |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Mon Mar 28, 2005 3:49 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| hopsala wrote: |
| as you described, for some god forsaken reason, there is no way to register the broker in the Topology window. |
That's not true.
| hopsala wrote: |
| (I know MQSI is one of the most frustrating products out there |
THAT's not true either!
You've obviously never tried to work with Portal 5.0.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| hopsala |
| Posted: Tue Mar 29, 2005 1:35 am Post subject: |
|
|
Guardian
Joined: 24 Sep 2004
Posts: 960
|
Well, don't just tell me it's not true. Tell me (and Keka here) how to do it properly.
However, from my experience and others', in MQSI (the old WBI) this was the only way to do it.
I have seen people banging their heads against keyboards and walls as a result of MQSI overload, I have heard programmers say "why am I not going to do it? why?! because I can't, I just g**am can't!". Some even speak woefully of the original developer, who commited sepuku in shame. (clearly an exaggeration, but i'm sure he was forced to move to Congo or something)
but still, admittadly I have'nt worked with Portal5.0, and upon you're recommendation I will henceforth try to avoid it  |
|
| Back to top |
|
|
| sjensen |
| Posted: Tue Mar 29, 2005 2:18 am Post subject: |
|
|
Centurion
Joined: 18 Dec 2003
Posts: 134
Location: London
|
Hi,
You did create and deploy the broker right?
Cheers
Stefan |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Mar 29, 2005 3:39 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
In order to create a broker in 2.1, you have to follow the instructions given in the manuals!
It's been quite a while since I've done it, but it's really not much different than in 5 (except for names).
You have to run mqsicreatebroker on the broker machine.
You have to ensure that the broker QM has functional two-way communications with the configmgr QM.
You have to ensure that the broker service user is in the mqbrks user on the broker machine.
You have to ensure that the configmgr service user has permissions on the broker QM.
You have to ensure that your desktop user is in the necessary mqbr* groups on the ConfigMgr machine.
You have to ensure that you have a working Control Center connection to the configmgr.
You have to check out the topology, and create a broker.
You have to check in the topology, and then deploy it.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
|
|
