Author |
Message
|
csongebalazs |
Posted: Tue Jan 25, 2005 2:54 am Post subject: connecting local configmgr v2.1 beside the new v5.0 toolkit |
|
|
Voyager
Joined: 30 Jan 2004 Posts: 78
|
Some weeks ago I have found a tip, how can I install the new v5.0 WBIMB Toolkit onto my machine, where the v2.1 integrator product had been installed.
I had a local config manager v2.1 on my machine, but I used to connect to a v2.1 config manager, which was created on the other machine.
Today I tried to connect to my local config manager, but it was unsuccessful. I read the following log in the event viewer:
( ConfigMgr ) Unable to start executable D:/Program Files/IBM/WBIMB_Toolkit/bin/bipconfigmgr.exe.
The WebSphere MQ Integrator service could not start an executable.
Make sure that the executable is in the correct directory and that the WebSphere MQ Integrator service userid has permission to start the executable. Ensure that there is adequate memory available on the system. Reissue the command.
Where and how can I change this path in order to make a succesful connection between my local v2.1 config manager and my control center v2.1? /Therewith I would like to keep my new toolkit fully operational./
Hi
Balazs |
|
Back to top |
|
 |
shra_k |
Posted: Tue Jan 25, 2005 3:58 am Post subject: |
|
|
Apprentice
Joined: 30 Dec 2002 Posts: 37
|
I could do this before. I had both v2.1 and V5 on the same windows 2000 box and two configmrs and two brokers happpily running. But later when i was doing some debgging on both the versions, i had my configmgr corrupted and came to know that this is not a healthy practise. So now i have only V5.
Pertaining to your question, if you have setup the box correctly, then you have to run all the V2.1 commands from the "<install-v2.1-dir>\bin" diorectory only and not from anyother place.
All other V5 commands can be issued from anywhere  |
|
Back to top |
|
 |
csongebalazs |
Posted: Tue Jan 25, 2005 4:15 am Post subject: |
|
|
Voyager
Joined: 30 Jan 2004 Posts: 78
|
I started a Control Center from Start\Programs\IBM\IBM WebSphere MQ Integrator 2.1, then in the File menu wanted to use Connection menu item.
I set the required properties, than the answer was the following:
BIP1350E: The current operation has timed out.
One or more requests have been sent to the Configuration Manager to process the current operation, but no reply has been received for the last request sent.
Either your request has queued up behind a long-running request by another user, or the Configuration Manager has stopped. Check that it is up and running then retry the operation. Because the link to the Configuration Manager is via MQSeries, it is important to note that the original operation may have fully completed, or have partly completed, even though no reply was received in the allotted time. The results of the retried operation should indicate this, and will determine subsequent actions. For example, if a check-in operation timed out then the update may have occurred, but the object may still be locked. A subsequent check-in would then fail with a locked response. The action would then be to unlock the object.
After it I checked the event viewer where I saw the following:
( ConfigMgr ) Unable to start executable D:/Program Files/IBM/WBIMB_Toolkit/bin/bipconfigmgr.exe.
The WebSphere MQ Integrator service could not start an executable.
Make sure that the executable is in the correct directory and that the WebSphere MQ Integrator service userid has permission to start the executable. Ensure that there is adequate memory available on the system. Reissue the command.
So I don't understand your answer, because I didn't issue any command manually from nowhere.
May be I must modify some registry settings, but I don't know which ones.
Hi
Balazs |
|
Back to top |
|
 |
csongebalazs |
Posted: Tue Jan 25, 2005 5:32 am Post subject: |
|
|
Voyager
Joined: 30 Jan 2004 Posts: 78
|
I have an another problem.
If I try to issue an mqsilist command on my problematical machine I got the following message twice:
Make sure that the message catalog is available and that the mqsi response is in the message catalog. If the problem continues contact your IBM support centre.
If I issue this command from the bin subdirectory of both version, the result is same. /Otherwise there is only an enroll.exe in the bin directory of the new version./
What should I do?
Hi
Balazs |
|
Back to top |
|
 |
jefflowrey |
Posted: Tue Jan 25, 2005 5:41 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
You should start from scratch.
I think you have overwritten your 2.1 install with your 5 install, at least partially.
Also, you will not be able to put both a 2.1 AND a 5.0 config manager or Broker on the same machine - ONLY the Control Center and the Toolkit.
You should be able to have a config manager and broker for ONE of the two versions as well. _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
csongebalazs |
Posted: Tue Jan 25, 2005 5:57 am Post subject: |
|
|
Voyager
Joined: 30 Jan 2004 Posts: 78
|
I haven't got two different type config managers.
There were config manager v2.1 and control center v2.1 on my machine (no brokers).
Later only the toolkit of the v5 was installed by the toolkit.txt trick.
Could Config manager v2.1 and toolkit v5 to work on same machine, or not? /And I don't want to connect to the old configmgr with the new toolkit, because it is not allowed, just use them separately./
Hi
Balazs |
|
Back to top |
|
 |
kirani |
Posted: Tue Jan 25, 2005 11:33 pm Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001 Posts: 3779 Location: Torrance, CA, USA
|
Not sure if you can install Toolkit on a machine where 2.1 Config Mgr already exist. As one of the earlier post said, it's not officially supported by IBM and its not a healthy practice.
Have you tried installing the toolkit on a machine where only WMQI 2.1 Control Center exist? _________________ Kiran
IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries
|
|
Back to top |
|
 |
|