| Author |
Message
|
| meaton78 |
 Posted: Tue Nov 26, 2013 7:22 am Post subject: Verify user defined properties after deployment |
 |
|
Centurion
Joined: 16 Oct 2008
Posts: 100
|
We are running MB 8.0.0.2 on AIX. I am testing scripting some overrides in a bar file. I ran mqsireadbar, got the properties that I wish to set, and set them using mqsiapplybaroverride. All appeared to go as planned, but for peace of mind, I'd like to be able to see if my deployed bar file has the correct properties set.
Is there a way to look at a deployed bar file's user defined properties to make sure my override actually worked? |
|
| Back to top |
|
 |
| McueMart |
| Posted: Tue Nov 26, 2013 7:56 am Post subject: |
|
|
Chevalier
Joined: 29 Nov 2011
Posts: 490
Location: UK...somewhere
|
Cant you just use mqsireadbar again after you have done mqsiapplybar override?
Else you might be able to use the CMP API to query the runtime configuration of the deployed bar file. |
|
| Back to top |
|
|
| meaton78 |
| Posted: Tue Nov 26, 2013 8:00 am Post subject: |
|
|
Centurion
Joined: 16 Oct 2008
Posts: 100
|
The automated deployment tool that we use applies the overrides and saves the bar file, then deploys. The default after that is to delete the deployment package. I suppose I could stop it from deleting this one package to do the read one more time.
I'll give the CMP a shot also and see what it shows. Thanks for the reply. |
|
| Back to top |
|
|
| meaton78 |
| Posted: Tue Nov 26, 2013 8:20 am Post subject: |
|
|
Centurion
Joined: 16 Oct 2008
Posts: 100
|
| McueMart wrote: |
| Else you might be able to use the CMP API to query the runtime configuration of the deployed bar file. |
This was the way to go, thanks! |
|
| Back to top |
|
|
| JosephGramig |
| Posted: Tue Nov 26, 2013 10:35 am Post subject: |
|
|
Grand Master
Joined: 09 Feb 2006
Posts: 1244
Location: Gold Coast of Florida, USA
|
| The MBX (Message Broker Explorer) also shows some interesting details of deployed artifacts that you will not see using the Toolkit. I was bummed to not see additional instances on Input nodes and only on the flow it self. Maybe it will get fix/added (I guess this is a point of view). In any case, MBX is just using CMP API. |
|
| Back to top |
|
|
|
|
