| Author |
Message
|
| PeterPotkay |
 Posted: Tue Dec 28, 2004 11:03 am Post subject: Changes I would like to see in WBIMB 6.0 ... |
 |
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
WB-IMB - When you stop a flow, you STOP a flow. Currently, all it does is force the flow out of its MQGET loop. The Queues it has open remain open, meaning you can't clear them, or more importantly, you can't change the remote queue name or remote queue manager name. You have to stop them, remove them from the EG, deploy, change/clear the queue, add the flow, redeploy. 
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
 |
| JT |
| Posted: Tue Dec 28, 2004 11:00 pm Post subject: |
|
|
Padawan
Joined: 27 Mar 2003
Posts: 1564
Location: Hartford, CT.
|
| Quote: |
| WB-IMB - When you stop a flow, you STOP a flow. Currently, all it does is force the flow out of its MQGET loop. The Queues it has open remain open, meaning you can't clear them, or more importantly, you can't change the remote queue name or remote queue manager name. You have to stop them, remove them from the EG, deploy, change/clear the queue, add the flow, redeploy |
Peter,
A simpler solution may be to issue the mqsireload for the execution group to release all resources acquired by the message flow(s). We typically, stop the message flow first, then issue the mqsireload. Upon completion, the message flow remains in a stopped state, and all of the resources are released, allowing us to clear queues
| Quote: |
When you issue this command, a message is sent to the broker, which stops and restarts all its execution groups. You can specify a single execution group to be reloaded, but you are recommended to use the default form of this command to reload all execution groups.
Because an execution group does not stop until all message flows within it terminates, the ability of the broker to reload quickly depends on the processing time for the longest running message flow. This affects the performance of this command, and you are recommended to review any long-running message flows.
If you have included a plug-in node or parser within a message flow on the broker, these are deleted by this command, and the relevant termination functions called. When message flows are restarted, the resources used by these nodes and parsers are re-accessed and reacquired. However, you are recommended to ensure that user-written plug-in nodes and parsers provide their own mechanism to reload persistent state and data dynamically, and do not rely on the use of this command. |
|
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Wed Dec 29, 2004 6:00 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
JT, the problem with that command is that it effects the entire execution group (or, as recommended, the enire Broker!). If I want to to tinker with queues used by FlowA, I don't want to effect Flows B and C that are in the same Execution Group (or Broker).
Stop should mean Stop. Currently Stop acts more like a Pause.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| kirani |
| Posted: Wed Dec 29, 2004 9:56 am Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
May be we should start a different thread for "Changes I would like to see in WBIMB 6.0 ..."
If I see more posts related to WBIMB here then I will split the post into two (WMQ and WBIMB).
_________________
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 |
|
|
| PeterPotkay |
| Posted: Wed Dec 29, 2004 10:52 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
Go ahead and start the thread in the WMQI forum. I bet it will fill up quickly!
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| kirani |
| Posted: Wed Dec 29, 2004 11:03 am Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
OK .. I seperated WBIMB part from the original post.
_________________
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 |
|
|
| PeterPotkay |
| Posted: Wed Dec 29, 2004 11:09 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
I would like to know for a fact what version of a flow I have currently deployed. Right now the only way is to test it with a message whose ouput well tell me if my changes are in there, or to embedd Trace Nodes or something.
Why not have the ability to just right click on a deployed flow and have a comments/version field display that tells me what is deployed at the flow level?
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| kirani |
| Posted: Wed Dec 29, 2004 11:39 am Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
I would like to see "un-deploy/remove" feature for a BAR file.
For example, Currently, if I have 4 message flows and 2 message sets deployed to an EG as a result of two different BAR files. If I were to remove the components of one BAR file, then I will have to perform Remove action for each component individually. Instead I'd like to see a feature where more than one components are removed from the Broker.
_________________
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 |
|
|
| moorej_gl |
| Posted: Wed Dec 29, 2004 1:16 pm Post subject: |
|
|
Apprentice
Joined: 01 Dec 2003
Posts: 35
Location: Madison, WI
|
How about the ability to uninstall just the latest fixpack on your system? From what I understand, right now if you apply a fixpack that breaks everything, the only option is to uninstall the whole product and start from scratch.  |
|
| Back to top |
|
|
| kirani |
| Posted: Wed Dec 29, 2004 3:09 pm Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
Is that so .. I never tried that with WBIMB 5.0
Witn WMQ I was able to uninstall only the CSD/Fixpack.
_________________
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 |
|
|
| javaforvivek |
| Posted: Thu Dec 30, 2004 1:01 am Post subject: |
|
|
Master
Joined: 14 Jun 2002
Posts: 282
Location: Pune,India
|
In one of my earlier posts I wrote:
| Quote: |
Do we have any commands which can be typed in command prompts for:
1. Deploying message flow to a particular EG on Broker
2. Starting and stopping a particular message flow
3. changing its trace mode from 'none' to 'normal' or 'debug'
4. Creating new execution groups
etc.
(Basically all the activities which can be done via Broker Administration perspective)??
|
Kiran wrote:
| Quote: |
| They don't have commands for all activities in Broker Administration Perspective. For example, there is no command to create an Execution Group from command line. |
I would like to see these commands to operate from command prompt rather than using toolkit in v6.0. (is it an unreasonable expectation?) 
_________________
Vivek
------------------------------------------------------
...when you have eliminated the impossible, whatever remains, however improbable, must be the truth. |
|
| Back to top |
|
|
| PGoodhart |
| Posted: Thu Dec 30, 2004 4:58 am Post subject: |
|
|
Master
Joined: 17 Jun 2004
Posts: 278
Location: Harrisburg PA
|
1. Fix all the datetime millisecond related bugs. Addition and Subtraction should work!
2. Extend the ODBC management currently used for the broker databases to client/remote datasources. I hate having to explain over and over that the datasource was "closed" and the developer needs to code for it.
3. Enhanced/Fixed message validation.
4. Actually meet the W3C standards on XML!
5. Eliminate the Configuration Manager altogether. Instead of Toolkit-Configuration Manager-Broker, why not Toolkit-Broker. It's just an extra historical artifact at this point.
6. Improve the ESQL editor. It's still just a sightly improved text editior, see Microsoft Visual Studio for some ideas (I know, everyone hates MS)...
_________________
Patrick Goodhart
MQ Admin/Web Developer/Consultant
WebSphere Application Server Admin |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Dec 30, 2004 5:02 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| PGoodhart wrote: |
| 5. Eliminate the Configuration Manager altogether. Instead of Toolkit-Configuration Manager-Broker, why not Toolkit-Broker. It's just an extra historical artifact at this point. |
I'm going to disagree.
Configuration Manager plays the same role in a WBIMB environment that the Deployment Manager plays in a WAS environment.
It allows you to centralize network traffic, and centralize SECURITY. And enforce security, too. These are good things.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| wmqiguy |
| Posted: Thu Dec 30, 2004 7:13 am Post subject: |
|
|
Centurion
Joined: 09 Oct 2002
Posts: 145
Location: Florida
|
Lessen the impact of the EVAL statement. For instance, in a Dot Notation field reference, you can limit the impact of the EVAL by using {} for just the small portion that you want EVAL'd. I want that same functionality for Function calls or Database Schemas. Wouldn't it be nice to just use:
SELECT * FROM Database.{DynamicSchemaName}.TableName
Instead of:
EVAL('SELECT * FROM Database.' || DynamicSchemaName || '.TableName') |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Dec 30, 2004 7:24 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| wmqiguy wrote: |
Lessen the impact of the EVAL statement. For instance, in a Dot Notation field reference, you can limit the impact of the EVAL by using {} for just the small portion that you want EVAL'd. I want that same functionality for Function calls or Database Schemas. Wouldn't it be nice to just use:
SELECT * FROM Database.{DynamicSchemaName}.TableName
Instead of:
EVAL('SELECT * FROM Database.' || DynamicSchemaName || '.TableName') |
Shouldn't that first one work?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
|
|
