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 » WebSphere Message Broker V7.0 Announced.

Post new topic  Reply to topic Goto page Previous  1, 2, 3, 4, 5  Next
 WebSphere Message Broker V7.0 Announced. « View previous topic :: View next topic » 
Author Message
LazyBoy
PostPosted: Mon Oct 05, 2009 9:34 am    Post subject: Reply with quote

Voyager

Joined: 04 May 2006
Posts: 78

I had read earlier that WMB will be built on top of WAS, but the announcement letter doesn't talk about this.

Any updates on this?

Also, Error handling and auditing is one feature which needs improvement, any improvements on that.
Back to top
View user's profile Send private message
Vitor
PostPosted: Mon Oct 05, 2009 9:48 am    Post subject: Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

LazyBoy wrote:
I had read earlier that WMB will be built on top of WAS


Where? Can you post a link?
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
LazyBoy
PostPosted: Mon Oct 05, 2009 9:56 am    Post subject: Reply with quote

Voyager

Joined: 04 May 2006
Posts: 78

The document was not from IBM, I found it in issue tracker document of our project , which was talking about invoking EJB 3.0 and that document said this issue will be fixed in next release of WMB by having the broker on WAS. I dont know where that information came from. So, I was curious about that.
Back to top
View user's profile Send private message
mqmatt
PostPosted: Mon Oct 05, 2009 10:17 am    Post subject: Reply with quote

Grand Master

Joined: 04 Aug 2004
Posts: 1213
Location: Hursley, UK

WMB V7 is NOT based on WAS.
And in case that wasn't clear enough, WMB V7 is NOT based on WAS.
Back to top
View user's profile Send private message
LazyBoy
PostPosted: Mon Oct 05, 2009 10:24 am    Post subject: Reply with quote

Voyager

Joined: 04 May 2006
Posts: 78

thanks mqmatt for confirming.

How abt Error handling and auditing improvements?
Back to top
View user's profile Send private message
mqmatt
PostPosted: Mon Oct 05, 2009 10:44 am    Post subject: Reply with quote

Grand Master

Joined: 04 Aug 2004
Posts: 1213
Location: Hursley, UK

LazyBoy wrote:
Error handling and auditing is one feature which needs improvement, any improvements on that.

That's been a huge focus area in this release! (Nice plant, thanks!) Removing the CM has allowed us to fix huge swathes of deployment and admin issues. So problems with cancel deployment, deployment locks, broker UUIDs, phantom/default EGs, topology deployment, synchronization etc. etc. will have gone away now, because these things no longer exist as concepts in v7!

And because the utilities go directly to the broker, it allows a load more information to be given to you (such as node information), yet because it's going direct means that connect and deploy times are loads quicker.

There's also an administration queue; concurrent deploys are now supported, and you can see what deployments etc. other users are currently doing. Sufficiently authorised admins can also remove specific named deploys if necessary.
This complements a new administration log, which tells you what user did what and when. But for standard developers, there's also a basic deployment view, which lists what deployments they've done recently, and whether or not each one worked (and if not, why not).

So all in all, It's all pretty neat - as you can probably tell, I'm getting swept up in the emotion just writing about it

-Matt
Back to top
View user's profile Send private message
LazyBoy
PostPosted: Mon Oct 05, 2009 10:53 am    Post subject: Reply with quote

Voyager

Joined: 04 May 2006
Posts: 78

Thats good news for administrators.

How about the replaying messages and handling exceptions in message flows.

I dont like to write user exit to audit and then have MDBs to replay messages.
Back to top
View user's profile Send private message
mqmatt
PostPosted: Mon Oct 05, 2009 11:04 am    Post subject: Reply with quote

Grand Master

Joined: 04 Aug 2004
Posts: 1213
Location: Hursley, UK

There are some improvements to the v6.1.0.3 monitoring support - if you're not aware, this allows you to grab message payload information non-invasively, including the entire bitstream, and collect it for subsequent processing - including message replay.
A complete solution for these replay scenarios isn't yet built-in, however you might like to contact your IBM account rep about a services offering called WMBTM (WebSphere Message Broker Transaction Monitor) - this may well provide what you need.
Back to top
View user's profile Send private message
PeterPotkay
PostPosted: Mon Oct 05, 2009 1:50 pm    Post subject: Reply with quote

Poobah

Joined: 15 May 2001
Posts: 7722

mqmatt wrote:
LazyBoy wrote:
Error handling and auditing is one feature which needs improvement, any improvements on that.

That's been a huge focus area in this release! (Nice plant, thanks!) Removing the CM has allowed us to fix huge swathes of deployment and admin issues. So problems with cancel deployment, deployment locks, broker UUIDs, phantom/default EGs, topology deployment, synchronization etc. etc. will have gone away now, because these things no longer exist as concepts in v7!

And because the utilities go directly to the broker, it allows a load more information to be given to you (such as node information), yet because it's going direct means that connect and deploy times are loads quicker.

There's also an administration queue; concurrent deploys are now supported, and you can see what deployments etc. other users are currently doing. Sufficiently authorised admins can also remove specific named deploys if necessary.
This complements a new administration log, which tells you what user did what and when. But for standard developers, there's also a basic deployment view, which lists what deployments they've done recently, and whether or not each one worked (and if not, why not).

So all in all, It's all pretty neat - as you can probably tell, I'm getting swept up in the emotion just writing about it

-Matt


Thank you, thank you, thank you. The majority of the time and effort spent resolving problems since we've moved to WMB 6.1 have all been related to the Config Manager somehow.

How about diminishing /eliminating the need for Broker restarts to pick up relatively minor changes? If I want to add a DSN name so one new flow can talk to its DB, it pains me to have to beg for an outage for the 200 other flows that run on the same Broker. Sorta like when MQ got the REFRESH SECURITY command removing the need to bounce a QM to pick up a minor change in the O/S (new ID in a group), I hope WMB 7 has some improvemts here?
_________________
Peter Potkay
Keep Calm and MQ On
Back to top
View user's profile Send private message
mgk
PostPosted: Mon Oct 05, 2009 2:36 pm    Post subject: Reply with quote

Padawan

Joined: 31 Jul 2003
Posts: 1642

Quote:
If I want to add a DSN name so one new flow can talk to its DB


Well we have made steps in that direction in V7. The mqsisetdbparms command can now be run without requiring the broker to be stopped. However, changes made are not picked up dynamically, instead they are picked up per execution group when an execution group is restarted rather than whole broker having to be stopped at once...

Regards,
_________________
MGK
The postings I make on this site are my own and don't necessarily represent IBM's positions, strategies or opinions.
Back to top
View user's profile Send private message
PeterPotkay
PostPosted: Mon Oct 05, 2009 2:46 pm    Post subject: Reply with quote

Poobah

Joined: 15 May 2001
Posts: 7722

Well that is an improvement, glad to here it. mqsireload only impacts 1 EG and is much faster than a Broker restart. Hopefully this trend continues and eventually we won't even have to do that.

Don't underestimate the political, not technical, difficulty in restarting a Broker or even EG in a production environment.
_________________
Peter Potkay
Keep Calm and MQ On
Back to top
View user's profile Send private message
TonyD
PostPosted: Mon Oct 05, 2009 3:30 pm    Post subject: Reply with quote

Knight

Joined: 15 May 2001
Posts: 540
Location: New Zealand

If the CM and the Broker database have disappeared .... where is stuff stored now?!
Back to top
View user's profile Send private message Send e-mail
Gaya3
PostPosted: Mon Oct 05, 2009 10:07 pm    Post subject: Reply with quote

Jedi

Joined: 12 Sep 2006
Posts: 2493
Location: Boston, US

TonyD wrote:
If the CM and the Broker database have disappeared .... where is stuff stored now?!


file system, where else, it will store it as a file...
_________________
Regards
Gayathri
-----------------------------------------------
Do Something Before you Die
Back to top
View user's profile Send private message
zpat
PostPosted: Mon Oct 05, 2009 10:12 pm    Post subject: Reply with quote

Jedi Council

Joined: 19 May 2001
Posts: 5866
Location: UK

More likely in a queue?
Back to top
View user's profile Send private message
mgk
PostPosted: Tue Oct 06, 2009 12:29 am    Post subject: Reply with quote

Padawan

Joined: 31 Jul 2003
Posts: 1642

Quote:
If the CM and the Broker database have disappeared .... where is stuff stored now?!


On the file system
_________________
MGK
The postings I make on this site are my own and don't necessarily represent IBM's positions, strategies or opinions.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Goto page Previous  1, 2, 3, 4, 5  Next Page 2 of 5

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » WebSphere Message Broker V7.0 Announced.
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.