| Author |
Message
|
| fenway_frank |
 Posted: Fri Jan 04, 2013 7:26 am Post subject: Broker 8.0.0.1 Administration questions |
 |
|
Apprentice
Joined: 21 Oct 2011
Posts: 43
Location: Boston, MA USA
|
Hello, I did some digging into these topics (with broker 7.0.0.3 and 8.0.0.1) but haven’t come up with a straightforward solution or obscure command that already supports these capabilities.
1. Broker "core dump". Specifically, ability to return property values for all reportable entities (including configurable services) at a broker and/or execution group level. This would enable “snapshot” of a complete broker configuration profile before and after message flow applications are configured and deployed. Very handy for install verification.
Current option is to create a script that executes the following steps. Is there an easier way to accomplish this? Unfortunately, i don't believe there's a magic CMP API to handle this in a single command.
A. Returns list of all configurable services for the Broker :
mqsireportproperties <broker_name> -c AllTypes -o AllReportableEntityNames –a
B. For each configurable service returned in step A, execute mqsireportproperties <broker name> -c <service type> -o <service name> –r or equivalent
C. Return list of all reportable objects at EG level:
mqsireportproperties broker_name -e eg name -o AllReportableEntityNames –r
D. For each reportable entity from step C, execute mqsireportproperties broker_name -o <reportable entity name> -a -e execution_group or equivalent
2. Enable FLOWSTATS for more than just 1 flow, but not the entire set of flows in an execution group. Current mqsichangeflowstats command requires –j for all flows or –f for a single flow. Doesn’t appear you can chain together multiple flows within a single mqsichangeflowstats command. Furthermore, if you execute mqsichangeflowstats back-to-back each with –f directive, the last successful execution of mqsichangeflowstats overwrites the prior command.
3. Capture mqsicreatebar command from toolkit-initiated build. Does the toolkit log the actual mqsicreatebar/mqsipackagebar command it executes within the workspace? If so, this could seed an ANT script to automate our builds and save us some time.
It’s quite likely all of the above will require RFE but wanted to confirm I wasn’t missing something obvious prior to formally submitting enhancement requests. I think these enhanced capabilities are worth pursuing with IBM.
Thanks for your feedback. |
|
| Back to top |
|
 |
| lancelotlinc |
| Posted: Fri Jan 04, 2013 8:15 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
"Core dump" implies a catastrophic error. I think you want to report on various configuration items in a happy state. Core dump seems to indicate an unhappy state.
I think you are on the right track. Scripting is the way to go. Use cron or your favorite scheduler to kick off your script regularly and mail the output to your address. Build an exception file and use grep to test the output of the cron job to see if something you are interested in needs attention. Open a Service Manager incident if anything in your exception file tests positive.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| fenway_frank |
| Posted: Fri Jan 04, 2013 10:19 am Post subject: |
|
|
Apprentice
Joined: 21 Oct 2011
Posts: 43
Location: Boston, MA USA
|
| a poor choice of words, perhaps. core dump in this context was happy state report of every configuration property and value within the broker, down to the eg level. i'll await feedback from the forum on items #2 and #3 which i suspect will necessitate RFE. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Fri Jan 04, 2013 11:12 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
You should be able to issue a single mqsireportproperties with -r.
It should not be that issuing mqsichangeflowstats to enable a flow then disables all previous flows. If you can actually show this to be true, it should be a defect and fixable through a PMR.
v8 toolkit bar file editor allows you to retrieve an equivalent command to create the same bar. |
|
| Back to top |
|
|
| fenway_frank |
| Posted: Fri Jan 04, 2013 2:19 pm Post subject: |
|
|
Apprentice
Joined: 21 Oct 2011
Posts: 43
Location: Boston, MA USA
|
You should be able to issue a single mqsireportproperties with -r.
- yes, you can recurse all the properties of a specific broker object but cannot recursively capture all the objects and then recurse the properties of each object in a single command. at least not that i am aware of.
It should not be that issuing mqsichangeflowstats to enable a flow then disables all previous flows. If you can actually show this to be true, it should be a defect and fixable through a PMR.
if the following commands are executed one after the other, only "flow B" emits flowstat events. if this is not expected behavior, i'll open PMR. InfoCenter is not clear in this regard.
mqsichangeflowstats $BROKER_NAME -s -e ${EXEC_GROUP} -f ${FLOW_NAMEA} -c active -o xml
mqsichangeflowstats $BROKER_NAME -s -e ${EXEC_GROUP} -f ${FLOW_NAMEB} -c active -o xml
v8 toolkit bar file editor allows you to retrieve an equivalent command to create the same bar.
how did i miss that?  thanks for pointing it out. |
|
| Back to top |
|
|
| Vitor |
| Posted: Sat Jan 05, 2013 5:31 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| fenway_frank wrote: |
if the following commands are executed one after the other, only "flow B" emits flowstat events. if this is not expected behavior, i'll open PMR. InfoCenter is not clear in this regard.
mqsichangeflowstats $BROKER_NAME -s -e ${EXEC_GROUP} -f ${FLOW_NAMEA} -c active -o xml
mqsichangeflowstats $BROKER_NAME -s -e ${EXEC_GROUP} -f ${FLOW_NAMEB} -c active -o xml |
Raise a PMR. On my v7.0.0.3 I use this to selectively obtain stats for individual flows & currently have results happily turning up for 5 of the 9 flows in a given execution group.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Sat Jan 05, 2013 8:06 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| fenway_frank wrote: |
You should be able to issue a single mqsireportproperties with -r.
- yes, you can recurse all the properties of a specific broker object but cannot recursively capture all the objects and then recurse the properties of each object in a single command. at least not that i am aware of. |
Yes, I realized I dropped an important bit.
| Code: |
| mqsireportproperties $BROKER_NAME -s -e ${EXEC_GROUP} -a -r |
You need both the -a for "all" and the -r for "recursive descent". |
|
| Back to top |
|
|
| fenway_frank |
| Posted: Mon Jan 07, 2013 5:56 am Post subject: |
|
|
Apprentice
Joined: 21 Oct 2011
Posts: 43
Location: Boston, MA USA
|
-a and -r cannot be combined in mqsireportproperties plus i don't believe -s is a valid argument (not documented with version 7 or  . perhaps this was typo? |
|
| Back to top |
|
|
| mqjeff |
| Posted: Mon Jan 07, 2013 8:32 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| fenway_frank wrote: |
| -a and -r cannot be combined in mqsireportproperties plus i don't believe -s is a valid argument (not documented with version 7 or . perhaps this was typo? |
Hrm. I guess I'm thinking of -o AllReportableEntityNames and the fact that it used to support -n AllTypes to generate this. |
|
| Back to top |
|
|
| fenway_frank |
| Posted: Fri Jan 11, 2013 11:31 am Post subject: |
|
|
Apprentice
Joined: 21 Oct 2011
Posts: 43
Location: Boston, MA USA
|
| fyi, turns out that zip generated by mqsibackupbroker should meet our requirements. zip can get huge but has raw material we need to perform before/after compare of the environment. thx for all input on this. |
|
| Back to top |
|
|
|
|
