| Author |
Message
|
| AkankshA |
 Posted: Sun Jun 25, 2006 4:11 am Post subject: Content Based Filtering in v6 pub sub |
 |
|
Grand Master
Joined: 12 Jan 2006
Posts: 1494
Location: Singapore
|
Hi,
I want to do content based filtering in MB v6 pub sub but my message contains namespaces which to my knowledge is not supported by broker...
Any ideas for implementation.. |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Sun Jun 25, 2006 10:10 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
I'd suggest you just try it the way the way that makes sense.
If that doesn't work, post what you tried and what happened.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| AkankshA |
| Posted: Mon Jun 26, 2006 2:02 am Post subject: |
|
|
Grand Master
Joined: 12 Jan 2006
Posts: 1494
Location: Singapore
|
I am still in design phase so don have enough infrastructure in place for trial.... 
I have read that eSQL is not namespace aware and one can extract the data from a message with name space using xpath syntax in java compute node... is this correct??? |
|
| Back to top |
|
|
| Bill.Matthews |
| Posted: Mon Jun 26, 2006 4:20 am Post subject: |
|
|
Master
Joined: 23 Sep 2003
Posts: 232
Location: IBM (Retired)
|
| Akanksha wrote: |
I am still in design phase so don have enough infrastructure in place for trial....
I have read that eSQL is not namespace aware and one can extract the data from a message with name space using xpath syntax in java compute node... is this correct??? |
eSQL can deal with Namespaces - that is why there is a DEFINE NAMESPACE. So the first part of your assumption is incorrect. The second part, using XPATH in a JavaCompute node is correct.
Both V6 and V5 provide support for Namespaces.
_________________
Bill Matthews |
|
| Back to top |
|
|
| AkankshA |
| Posted: Mon Jun 26, 2006 4:27 am Post subject: |
|
|
Grand Master
Joined: 12 Jan 2006
Posts: 1494
Location: Singapore
|
I am working in v6
but is the esql expression specified for content filter is name space aware.... |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Mon Jun 26, 2006 4:31 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Try it.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| martc |
| Posted: Mon Jan 22, 2007 11:46 am Post subject: |
|
|
Apprentice
Joined: 23 Mar 2005
Posts: 39
|
Try to specify your content filter this way, at least this is how I got it to work for me.
"Root.XMLNS.soapenv:Envelope.soapenv:Header.wsa:To"='http://xxxxx'
FYI - I do have these namespaces declared in my ESQL flow as such:
DECLARE soapenv NAMESPACE 'http://schemas.xmlsoap.org/soap/envelope/';
DECLARE xsd NAMESPACE 'http://www.w3.org/2001/XMLSchema';
DECLARE xsi NAMESPACE 'http://www.w3.org/2001/XMLSchema-instance';
DECLARE wsa NAMESPACE 'http://schemas.xmlsoap.org/ws/2004/08/addressing';
DECLARE wsse NAMESPACE 'http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd';
DECLARE FTMFErrNamespace NAMESPACE 'http://middleware.frk.com/XMLSchemas/Common/v100';
Im not sure if taking them out would make the content filter fail.
Here is what is interesting about this. The documentation says that namespaces in CBF are not supported yet like I said it worked. Could this have been a CSD upgrade? Were using WBI 6.0 csd 3.
-----
An MQRFH2 subscriber can also request that some content-based filtering is performed on the MQRFH publications that they are subscribing to. Content-based filtering can be done only if the body of the publication is in a format that can be parsed by the broker; that is, if the publication message can be interpreted by one of the broker's default parsers. For example, messages in XML or MQPCF format can be processed in this way.
You cannot use the XMLNS parser, or the MRM XML parser with namespace, for content-based filtering, but you can use the XML parser, and reference an element that is in the format namespace:field because the XML parser treats this reference as one element called namespace:field.
-- |
|
| Back to top |
|
|
|
|
