ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Facing problem with migrated Aggregate Control node, in V6

Post new topic  Reply to topic
 Facing problem with migrated Aggregate Control node, in V6 « View previous topic :: View next topic » 
Author Message
ashish_halge
PostPosted: Tue Sep 09, 2008 3:30 am    Post subject: Facing problem with migrated Aggregate Control node, in V6 Reply with quote

Novice

Joined: 24 Aug 2008
Posts: 13
Location: Dubai, UAE

I have migrated some flows which are using Aggregation flow from V5 to V6. I also have declared the required Environmental variable to pass the control info for V6. I have promoted the 'Timeout' property of the Aggregate Control node, and also setting the same in main flow. But still after the Aggregate control node, its not populating the 'Timeout' property in the 'comIbmAggregateControl' in Environment after the node, but the same os working fine V5. Please help me.....
Back to top
View user's profile Send private message Send e-mail Yahoo Messenger
fjb_saper
PostPosted: Tue Sep 09, 2008 6:44 pm    Post subject: Reply with quote

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY

You do of course know that the Aggregation functions a little bit differently from V5 and that passing the info to the control is supported for backward compatibility but no longer strictly necessary.

Review the examples in 6.0/6.1 and check how you can bring your agg node up to speed. Be also aware that in 6.0 you want to apply maitenance beyond 6.0.0.3 or even 6.0.0.5 as there was a minor problem with aggregation. Enjoy
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
ashish_halge
PostPosted: Tue Sep 09, 2008 10:21 pm    Post subject: Reply with quote

Novice

Joined: 24 Aug 2008
Posts: 13
Location: Dubai, UAE

Thanks for the reply,

But the problem is like this;
For Aggregate Control node we have properties like 'Aggregate Name' and 'Timeout' which will get populated in LocalEnvironment under some 'ComIbmAggregateControl' folder.
Now, in V5 bothe of these propeties are getting populated in LocalEnvironment, but in V6, only 'Aggregate Name' property is getting populated not the 'Timeout' which my flows has been using for some other logic, and thats why it was failing.
Now, can anyone suggest me that how can I access the value for 'Timeout' property which is promoted and being set in the main flow in V6 as its working fine in V5. I have already added the environmental variable MQSI_AGGR_COMPAT_MODE, in Broker environment.
Back to top
View user's profile Send private message Send e-mail Yahoo Messenger
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Facing problem with migrated Aggregate Control node, in V6
Jump to:  



You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.