| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| mqsireportproperties |
« View previous topic :: View next topic » |
| Author |
Message
|
| deepak_paul |
 Posted: Thu Nov 17, 2011 6:54 am Post subject: mqsireportproperties |
 |
|
Centurion
Joined: 04 Oct 2008
Posts: 147
Location: US
|
All,
Is there a way i can use mqsireportproperties to get the ESL content for the specific message flow as i learnt from here that we can use the same command to retrieve all ESQL content in the Execution Group(all message flow deployed in the EG).
Command to get all reportable Entity names:
| Code: |
| mqsireportproperties BROKER1 -e default -o AllReportableEntityNames -r >C:\temp\mqsireportproperties_AllReportableEntityNames.log |
Response:
| Code: |
ReportableEntityName='MessageFlow'
ReportableEntityName='AllMessageFlows'
ReportableEntityName='ComIbmAdapterResourceManager'
ReportableEntityName='ComIbmAggregateNodeFactory'
ReportableEntityName='ComIbmBasicNodeFactory'
ReportableEntityName='ComIbmCICSStatsManager'
ReportableEntityName='ComIbmCORBAStatsManager'
ReportableEntityName='ComIbmConfigurationNodeFactory'
ReportableEntityName='ComIbmCpiParserFactory'
ReportableEntityName='ComIbmDBTxnCtxManager'
ReportableEntityName='ComIbmDatabaseConnectionManager'
ReportableEntityName='ComIbmDummyParserFactory'
ReportableEntityName='ComIbmFTEAgentStatsManager'
ReportableEntityName='ComIbmFTPStatsManager'
ReportableEntityName='ComIbmFileStatsManager'
ReportableEntityName='ComIbmGeneralParserFactory'
ReportableEntityName='ComIbmGenericParserFactory'
ReportableEntityName='ComIbmGenericXmlParserFactory'
ReportableEntityName='ComIbmIDLResourceManager'
ReportableEntityName='ComIbmIDOCParserFactory'
ReportableEntityName='ComIbmJDBCConnectionPoolsStatsManager'
ReportableEntityName='ComIbmJSONParserFactory'
ReportableEntityName='ComIbmJVMManager'
ReportableEntityName='ComIbmJavaNodeFactory'
ReportableEntityName='ComIbmJavaPluginNodeFactory'
ReportableEntityName='ComIbmJmsTransformNodeFactory'
ReportableEntityName='ComIbmMQConnectionManager'
ReportableEntityName='ComIbmMQNodeFactory'
ReportableEntityName='ComIbmMQParserFactory'
ReportableEntityName='ComIbmMQeNodeFactory'
ReportableEntityName='ComIbmMtiParserFactory'
ReportableEntityName='ComIbmODBCStatsManager'
ReportableEntityName='ComIbmPEPNodeFactory'
ReportableEntityName='ComIbmPHPResourceManager'
ReportableEntityName='ComIbmParserManager'
ReportableEntityName='ComIbmSCADANodeFactory'
ReportableEntityName='ComIbmSCANodeFactory'
ReportableEntityName='ComIbmSOAPAsyncNodeManager'
ReportableEntityName='ComIbmSOAPHandleManager'
ReportableEntityName='ComIbmSOAPStatsManager'
ReportableEntityName='ComIbmSQLNodeFactory'
ReportableEntityName='ComIbmSecurityDirector'
ReportableEntityName='ComIbmSiebelManager'
ReportableEntityName='ComIbmSocketConnectionManager'
ReportableEntityName='ComIbmTCPIPClientNodesStatsManager'
ReportableEntityName='ComIbmTCPIPServerNodesStatsManager'
ReportableEntityName='ComIbmTimeoutNodeFactory'
ReportableEntityName='ComIbmWSNodeFactory'
ReportableEntityName='ComIbmWSParserFactory'
ReportableEntityName='ComIbmWTXManager'
ReportableEntityName='ComIbmXMLResourceManager'
ReportableEntityName='ComIbmXSDResourceManager'
ReportableEntityName='ComIbmXSLResourceManager'
ReportableEntityName='ComIbmXmlParserFactory'
ReportableEntityName='ContentBasedFiltering'
ReportableEntityName='EventLog'
ReportableEntityName='FTEAgent'
ReportableEntityName='HTTPConnector'
ReportableEntityName='HTTPSConnector'
ReportableEntityName='JAR'
ReportableEntityName='LabelManager'
ReportableEntityName='MIMEFactory'
ReportableEntityName='ServiceFederationManager'
ReportableEntityName='TraceLog'
ReportableEntityName='UserTraceLog'
ReportableEntityName='EventLog'
ReportableEntityName='UserTraceLog'
ReportableEntityName='TraceLog'
BIP8071I: Successful command completion.
|
Command to get all ESL content in the Execution Group.
| Code: |
| mqsireportproperties BROKER1 -e default -o AllMessageFlows -r >C:\temp\mqsireportproperties_AllESQLContent.log |
Response was written to its log file. I can see all ESQL content for all message flows in the EG.
When i am trying to get the ESQL content for a specific message flow, i am trying to use below command(not sure where i can give message flow name, though),
| Code: |
| mqsireportproperties BROKER1 -e default -o MessageFlow -r |
Response:
| Code: |
C:\Program Files (x86)\IBM\MQSI\7.0>mqsireportproperties BROKER_BPMS_RAJ -e default -o MessageFlow -r
BIP2087E: Broker BROKER1 was unable to process the internal configuration message.
The entire internal configuration message failed to be processed successfully.
Use the messages following this message to determine the reasons for the failure. If the problem cannot be resolved after reviewing these messages, contact your
IBM Support center. Enabling service trace may help determine the cause of the failure.
BIP4041E: Execution group 'default' received an invalid configuration message. See the following messages for details of the error.
The broker was asked to deploy a message flow which contained properties that were not recognized by the broker. This typically results from a message flow requ
iring a version or type of node that is not supported by the broker installation.
Check that the message flow is only using properties or nodes that are supported on the broker. Check that all necessary user-defined extensions are installed a
nd that they are of a version that is compatible with the message flow.
BIP2330E: Field 'uuid[0]' within field '(0x01000000:Name):MessageFlow' does not exist; diagnostic information '1610612736', '50331648'.
The message broker attempted to locate the field 'uuid[0]' contained within the field '(0x01000000:Name):MessageFlow' but the message did not contain this field
. Additional diagnostic information is '1610612736' '50331648'.
Check the message flow definition and the messages being processed by the message flow to ensure that the referenced field has been correctly specified. If nec
essary change the message flow to eliminate the reference to the nonexistent field.
BIP8036E: Negative response received.
This command sends an internal configuration message to the broker, the response received indicated that the internal configuration message was unsuccessful.
Check that the WebSphere MQ transport is available. Check the system log for further information. |
Just wondering what could be be the syntax to give the message flow name in order to get ESQL content of that message flow.
_________________
Regards
Paul |
|
| Back to top |
|
 |
| lancelotlinc |
| Posted: Thu Nov 17, 2011 11:38 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
We normally get our old ESQL code out of the source code repository. We use ClearCase tool to accomplish this.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| mqjeff |
| Posted: Thu Nov 17, 2011 2:24 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| Just remove all the flows that you don't want the ESQL for, from the EG, and then get all the ESQL deployed to that EG, and then deploy the rest of the flows again. |
|
| Back to top |
|
|
| deepak_paul |
| Posted: Thu Nov 17, 2011 5:08 pm Post subject: |
|
|
Centurion
Joined: 04 Oct 2008
Posts: 147
Location: US
|
| mqjeff wrote: |
| Just remove all the flows that you don't want the ESQL for, from the EG, and then get all the ESQL deployed to that EG, and then deploy the rest of the flows again. |
Well..This could be a way to getting around with EntityName ExecutionGroup in order to get ESQL for a specific message flow. But...
What if i dont want to touch my production or QA Broker Execution Group which has 20-30 message flows and get lost with finding my source(atleast ESQL) from my SCM?
I am trying to find a way through Entityname MessageFlow as i believe it could retrieve ESQL from that message flow but i dont know how as it gives negative response and error message also not clear enough.
_________________
Regards
Paul |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Thu Nov 17, 2011 10:12 pm Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
Why not get everything and then sort it out using a decent (UltraEdit/TextPad/Emacs) text editor?
Surely it is not that difficult?
If the current mqsireportproperties does not give you what you want please feel free to sumbit an improvement request to IBM.
Personally, I feel that this feature is a 'method of last resort' and would only be useful in cases where source code management has messed up big time.
Again personally, I don't ONLY rely on tools like ClearCase/Subgersion/Git. I make full workspace exports at regular intervals and especially at identifiable baselevel points. These are then zipped up and stored on a contact admin/Share somewhere. Just in case....
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Fri Nov 18, 2011 3:09 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| deepak_paul wrote: |
| mqjeff wrote: |
| Just remove all the flows that you don't want the ESQL for, from the EG, and then get all the ESQL deployed to that EG, and then deploy the rest of the flows again. |
Well..This could be a way to getting around with EntityName ExecutionGroup in order to get ESQL for a specific message flow. But...
What if i dont want to touch my production or QA Broker Execution Group which has 20-30 message flows and get lost with finding my source(atleast ESQL) from my SCM? |
Then you should hand the full big pile of ESQL output back to the DEVELOPERS WHO LOST THEIR OWN CODE and tell them to sort it out.
You would never attempt to recover source code from compiled jar files on your WAS server, would you? I mean, sure, it's possible, but you'd never actually do it, right?
If you've gotten lost trying to identify the correct source code for the deployed objects in your SCM, then you've done the wrong thing with your SCM and you need to focus on changing your procedures so that you stop having this problem in the future.
You change your procedures to stop having this problem by changing HOW you put code INTO the SCM, and by how you label the code that you deploy.
That is, you need to make a fixed, identifiable version of code in your SCM, and then deploy this again to your environments in a way that ensures you can see this identifiable version. |
|
| Back to top |
|
|
| deepak_paul |
| Posted: Sun Nov 20, 2011 2:44 pm Post subject: |
|
|
Centurion
Joined: 04 Oct 2008
Posts: 147
Location: US
|
| smdavies99 wrote: |
Why not get everything and then sort it out using a decent (UltraEdit/TextPad/Emacs) text editor?
Surely it is not that difficult?
If the current mqsireportproperties does not give you what you want please feel free to sumbit an improvement request to IBM.
Personally, I feel that this feature is a 'method of last resort' and would only be useful in cases where source code management has messed up big time.
|
Thanks for your response. Yes. i am going with Entity name AllMessageFlows for now. If anybody has executed mqsireportproperties command for entity name MessageFlow successfully, please share your experience here.
_________________
Regards
Paul |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
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
|
|
|
|
