Author |
Message
|
paustin_ours |
Posted: Tue Aug 24, 2004 2:17 pm Post subject: Cannot deploy imported flows |
|
|
Yatiri
Joined: 19 May 2004 Posts: 667 Location: columbus,oh
|
I created a message flow on my toolkit when it was running on 5.0.0
then i exported it to a local directory and installed support pack 2 and my toolkit is 5.0.2 now, then i created a new domain and everything to connect to Config Mgr, then i imported that message flow that i had created into a project and treid to deploy it but it wont deploy for some reason, i dont get any errors, its just taking forever.
I tried creating a small test flow and that deploys, is there something in the way that i am importing. i even tried the rebuild all option after i imported the flow. Am i missing something? |
|
Back to top |
|
 |
paustin_ours |
Posted: Tue Aug 24, 2004 3:10 pm Post subject: |
|
|
Yatiri
Joined: 19 May 2004 Posts: 667 Location: columbus,oh
|
Well i guess i was wrong, even that simple message flow that i created wont deploy now...any theories? |
|
Back to top |
|
 |
solomita |
Posted: Wed Aug 25, 2004 4:47 am Post subject: |
|
|
Voyager
Joined: 06 May 2003 Posts: 94
|
Make sure that your configmgr and broker are up and running. If there is a separate qmgr for each, be sure that the channels are up and running. Also, be sure that there are no errors in your flow and the bar file has the most updated flows/sets. Are you getting an errors in the event viewer? _________________ IBM Certified Specialist - WebSphere MQ Integrator
IBM Certified System Administrator - WebSphere MQ V5.3
IBM Certified System Administrator - WebSphere Business Integration Message Broker V5 |
|
Back to top |
|
 |
paustin_ours |
Posted: Thu Aug 26, 2004 1:16 pm Post subject: |
|
|
Yatiri
Joined: 19 May 2004 Posts: 667 Location: columbus,oh
|
Sorry about the late reply, I am ont getting any errors, Yes my QMgrs are running on different boxes and the channels are up and running. It is wierd that it deploys once in a while and other times it just times out. MY toolkit is on a PIII 1GHz box with 256MB RAM, do you this could be the problem maker? do i have to have a 512. AS i said i am running a toolkit 5.02 version. |
|
Back to top |
|
 |
paustin_ours |
Posted: Thu Aug 26, 2004 2:27 pm Post subject: |
|
|
Yatiri
Joined: 19 May 2004 Posts: 667 Location: columbus,oh
|
I get this error:
BIP2062E: Broker SQSZ2MQ (UUID d10c015d-fd00-0000-0080-9aec7ed513bc) Execution Group 'POWER_PLANT_ATTR' (UUID 2c68fd92-fe00-0000-0080-8ea9241ec750) detected that the deployed configuration message received contained an invalid XML tag.
The configuration message received could not be applied to the broker's configuration. This could occur for any of the following reasons: The configuration message XML tag directs an execution group to be created but the execution group already exists. The configuration message XML tag directs an execution group to be changed but the execution group does not exist. The configuration message is rejected.
Use the Message Brokers Toolkit to redeploy to the Execution Group. Contact your IBM support center if you are unable to resolve the problem.
BIP2062E: Broker SQSZ2MQ (UUID d10c015d-fd00-0000-0080-9aec7ed513bc) Execution Group 'POWER_PLANT_ATTR' (UUID 2c68fd92-fe00-0000-0080-8ea9241ec750) detected that the deployed configuration message received contained an invalid XML tag.
The configuration message received could not be applied to the broker's configuration. This could occur for any of the following reasons: The configuration message XML tag directs an execution group to be created but the execution group already exists. The configuration message XML tag directs an execution group to be changed but the execution group does not exist. The configuration message is rejected.
Use the Message Brokers Toolkit to redeploy to the Execution Group. Contact your IBM support center if you are unable to resolve the problem. |
|
Back to top |
|
 |
PGoodhart |
Posted: Fri Aug 27, 2004 5:03 am Post subject: |
|
|
Master
Joined: 17 Jun 2004 Posts: 278 Location: Harrisburg PA
|
Now this I have seen before. Unfortunately you may not like the answer. I had a similar issue, but it was not in the middle of an upgrade. Our quick fix was to recreate the bar file from scratch. (We just created a new bar file and added in the previously created flows.) We then deleted the execution group and verified that the process was gone. We recreated the execution group and redeployed the flow. _________________ Patrick Goodhart
MQ Admin/Web Developer/Consultant
WebSphere Application Server Admin |
|
Back to top |
|
 |
jefflowrey |
Posted: Fri Aug 27, 2004 5:13 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
If you so much as *launched* the original version of WBIMB, which would be 5.0.0 after install and BEFORE installing at least FixPack 1, then you need to completely uninstall, and start over.
If and only if, that is, you actually have 5.0.0 the GA version. The packages available from IBM have been refreshed to at least FP1 since the GA came out. _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
|