| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Literal value for simpleContent monitoring profile |
« View previous topic :: View next topic » |
| Author |
Message
|
| goffinf |
 Posted: Mon Sep 13, 2010 10:32 am Post subject: Literal value for simpleContent monitoring profile |
 |
|
Chevalier
Joined: 05 Nov 2005
Posts: 401
|
Version: 6.1.0.3
Platform: Windows
I have the following in a monitoring profile but the simpleContent value for example (foo) is NOT emitted. Other events in this profile which use queryText rather than a literal value work successfully.
Is this form of simpleContent where a literal value is supplied still supported??
If it IS can anyone see what I am doing wrong ?
If it isn't, is there a way of assigning a literal value to applicationData content ?
<p:monitoringProfile xmlns:p="http://www.ibm.com/xmlns/prod/websphere/messagebroker/6.1.0.3/monitoring/profile" p:version="2.0">
...
<p:applicationDataQuery>
<p:simpleContent p:name="example" p:dataType="string" p:value="foo"/>
Thanks
Fraser. |
|
| Back to top |
|
 |
| kimbert |
| Posted: Tue Sep 14, 2010 4:02 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
| Quote: |
| Is this form of simpleContent where a literal value is supplied still supported? |
No - I don't think so. Your question implies that v6.1.0.2 used to support this, but I can't find anything in the v6.1 infocenter that suggests that.
| Quote: |
| If it isn't, is there a way of assigning a literal value to applicationData content ? |
Not explicitly - but you could put something into the environment and then point the query at that.
If this really is a fixed, literal value then I wonder why your flow needs to emit it? |
|
| Back to top |
|
|
| goffinf |
| Posted: Tue Sep 14, 2010 11:30 am Post subject: |
|
|
Chevalier
Joined: 05 Nov 2005
Posts: 401
|
| kimbert wrote: |
| No - I don't think so. Your question implies that v6.1.0.2 used to support this, but I can't find anything in the v6.1 infocenter that suggests that. |
That's what I thought too, but thanks for looking.
| kimbert wrote: |
| If this really is a fixed, literal value then I wonder why your flow needs to emit it? |
Fair comment. The use I had in mind was passing this value to the flow which reads the event messages which it uses to configure itself (in this case it's an IPC name that is part of our unit test framework - we are using monitoring events to supply data to Junit assertions).
As you have said I can do this in a number of other ways, but it would have been quite nice to have this config external to the flow since we apply a number of different profiles for various purposes and it's easy to swap them around without the need for redeploying a flow. |
|
| Back to top |
|
|
| DanielG |
| Posted: Tue Oct 05, 2010 3:38 am Post subject: Use XPath |
|
|
Novice
Joined: 29 Mar 2003
Posts: 13
|
Probably a bit late... but you can exploit the XPath string() function in order to emit constant values:
<p:complexContent p:name="InterfaceType"
p:targetNamespace="http://www.xxx.org/meta">
<p:payloadQuery p:queryText="string('ConsumerInterface')">
</p:payloadQuery>
</p:complexContent>
Note: If I remember correctly, you will need at least 6.1.0.4 for this to work... |
|
| 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
|
|
|
|
