Issues (Dispatcher Error/FilteringNotSupported)

[Till Steinbach-2]

Hello to all,
I'm currently trying to setup openwsman(2.2.0) with sfcb (1.3.5).

I'm able to query Classes with the CIM-prefix when using the dmtf URI.  
When I try to query a class with the linux prefix and the sfcb.sf.net/...
  URI I get an Dispatcher Error:

Debug Output:

Dispatcher Error
dispatch == NULL
Fault Code: 9

I have not found any information concerning this fault jet.  
vendor_namespaces are set in the config file.

My other Problem is when i try to register for events as described in  
the tutorial, the Server answers FilteringNotSupported


can you give me a hint where i can find information about my problems?
Thanks in advance
Till Steinbach



------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Openwsman-devel mailing list
Openwsman-devel@...
https://lists.sourceforge.net/lists/listinfo/openwsman-devel

[Klaus Kaempf]

* Till Steinbach <till.steinbach@...> [Oct 30. 2009 12:59]:
> Hello to all,
> I'm currently trying to setup openwsman(2.2.0) with sfcb (1.3.5).
>
> I'm able to query Classes with the CIM-prefix when using the dmtf
> URI. When I try to query a class with the linux prefix and the
> sfcb.sf.net/... URI I get an Dispatcher Error:

Can you be a bit more specific on what you're trying to accomplish and
how ?

You probably need to set the correct CIM namespace ?!

>
> Debug Output:
>
> Dispatcher Error
> dispatch == NULL
> Fault Code: 9

This means "WSA_DESTINATION_UNREACHABLE", so the server could not
determine the correct endpoint.

>
> I have not found any information concerning this fault jet.
> vendor_namespaces are set in the config file.

openwsman will provide a textual error message in the soap reply.

>
> My other Problem is when i try to register for events as described
> in the tutorial, the Server answers FilteringNotSupported
>

Uh, might be a missing feature.

>
> can you give me a hint where i can find information about my problems?

The WS-Management standards are the only reliable source of
information I fear.

Hth,

Klaus
---
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)


------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Openwsman-devel mailing list
Openwsman-devel@...
https://lists.sourceforge.net/lists/listinfo/openwsman-devel

[Till Steinbach-2]

Hi Klaus,

Am 30.10.2009 um 13:18 schrieb Klaus Kaempf:
>
> Can you be a bit more specific on what you're trying to accomplish and
> how ?
>
> You probably need to set the correct CIM namespace ?!


I'm now a little bit further with debugging. It seems that my main  
problem is the setup of indications:

My Indication Source is in a "root/abc" Namespace
As I'm using the default sfcb setup the Indication Handler or Filter  
is in "root/interop" namespace

default_cim_namespace is "root/interop"
indication_source_namespace is "root/abc"

When i try to register without the --namespace option for example with:
subscribe http://schema.abc.com/wbem/wscim/1/cim-schema/2/ABC_FileIndication 
  -x "SELECT * FROM ABC_FileIndication" -Z "http://localhost:80/eventsink 
"
I get the wse:FilteringNotSupported Error, the request is NOT  
forwarded to the sfcb. I don't know what is happening there!?!

When I add the --namespace option I get destinationUnreachable

with --namespace=root/interop the request is forwarded by openwsmand,  
but sfcb is not able to find the ABC_FileIndication class in the root/
interop namespace and when I use --namespace=root/abc sfcb is not able  
to find CIM_IndicationHandlerCIMXML class.

it seems for me that --namespace overwrites the  
indication_source_namespace setting completely. Nevertheless the  
indication_source_namespace option seems to me like a workaround,  
because it limits the system to one namespace for indications.

I found a message in the archives that proposed adding an  
indication_namespace option to the config files to give openwsman a  
hint where the Indication related classes are stored.

Maybe I'm doing something completely wrong. I made my setup according  
to the information that are all around the internet.

Thanks for your replies
Till

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Openwsman-devel mailing list
Openwsman-devel@...
https://lists.sourceforge.net/lists/listinfo/openwsman-devel

[Suresh Sundriyal-2]

Hi Till,

Your setup seems about correct. From the description that you have provided I think you have
everything in place. On my system the indication_source_namespace is root/cimv2 and as
usual the handler/filter classes are in root/interop and setting --namespace to root/interop
seems to work for me.

>From your query I do see that you are not specifying the filter dialect though, try adding
-D "http://schemas.microsoft.com/wbem/wsman/1/WQL" to your query and see if that
works.

If that doesn't work then it would be helpful to be able to see your config file and the actual
commands.

--
Regards,
Suresh

________________________________________
From: Till Steinbach [till.steinbach@...]
Sent: Friday, November 06, 2009 1:50 AM
Cc: openwsman-devel@...
Subject: Re: [Openwsman-devel] Issues (Dispatcher       Error/FilteringNotSupported)

Hi Klaus,

Am 30.10.2009 um 13:18 schrieb Klaus Kaempf:
>
> Can you be a bit more specific on what you're trying to accomplish and
> how ?
>
> You probably need to set the correct CIM namespace ?!


I'm now a little bit further with debugging. It seems that my main
problem is the setup of indications:

My Indication Source is in a "root/abc" Namespace
As I'm using the default sfcb setup the Indication Handler or Filter
is in "root/interop" namespace

default_cim_namespace is "root/interop"
indication_source_namespace is "root/abc"

When i try to register without the --namespace option for example with:
subscribe http://schema.abc.com/wbem/wscim/1/cim-schema/2/ABC_FileIndication
  -x "SELECT * FROM ABC_FileIndication" -Z "http://localhost:80/eventsink
"
I get the wse:FilteringNotSupported Error, the request is NOT
forwarded to the sfcb. I don't know what is happening there!?!

When I add the --namespace option I get destinationUnreachable

with --namespace=root/interop the request is forwarded by openwsmand,
but sfcb is not able to find the ABC_FileIndication class in the root/
interop namespace and when I use --namespace=root/abc sfcb is not able
to find CIM_IndicationHandlerCIMXML class.

it seems for me that --namespace overwrites the
indication_source_namespace setting completely. Nevertheless the
indication_source_namespace option seems to me like a workaround,
because it limits the system to one namespace for indications.

I found a message in the archives that proposed adding an
indication_namespace option to the config files to give openwsman a
hint where the Indication related classes are stored.

Maybe I'm doing something completely wrong. I made my setup according
to the information that are all around the internet.

Thanks for your replies
Till

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Openwsman-devel mailing list
Openwsman-devel@...
https://lists.sourceforge.net/lists/listinfo/openwsman-devel

[Till Steinbach-2]

Am 06.11.2009 um 11:54 schrieb Suresh Sundriyal:

> If that doesn't work then it would be helpful to be able to see your  
> config file and the actual
> commands.

My config looks like this:
------------------------------------
[server]
port = 5985
#ssl_port = 5986
ssl_cert_file = /etc/openwsman/servercert.pem
ssl_key_file = /etc/openwsman/serverkey.pem
#digest_password_file = /etc/openwsman/digest_auth.passwd
basic_password_file = /usr/local/etc/openwsman/simple_auth.passwd

min_threads = 4
max_threads = 10

#use_digest is OBSOLETED, see below.

#
# Authentication backend for BASIC authentication. Default is to read  
a configuration file defined with 'basic_password_file'
#

#basic_authenticator = libwsman_pam_auth.so
#basic_authenticator_arg = openwsman

#
# WS-Management unauthenticated wsmid:Identify file
#
#anon_identify_file = /etc/openwsman/anon_identify.xml

#
# WS-Management authenticated wsmid:Identify file
#
#identify_file = /etc/openwsman/identify.xml



[client]
port = 5985
agent = openwsman 2.2.0

#
# settings for the CIM plugin
#

[cim]
#default_cim_namespace = root/cimv2
default_cim_namespace = root/interop
#default_cim_namespace = root/abc

# can also be SfcbLocal for local connection with sfcb CIMOM running  
on same system
cim_client_frontend = XML
#cim_client_frontend = SfcbLocal

#indication_source_namespace is used to define namespace where the  
Indications originate
indication_source_namespace = root/abc

# The following are in part fake namespaces for some publicly  
available CIM implementations.
vendor_namespaces = ABC=http://abc.com/wbem/wscim/1/cim-schema/2,  
Linux=http://sblim.sf.net/wbem/wscim/1/cim-schema/2

# CIMOM host, default is localhost
# host = localhost

# CIMOM port, default is 5988
# port = 5988

# boolean
# omit_schema_optional = 0

--------------------------

You can see i already played around with the parameters.

I think maybe I do the subscription wrong. I tried to follow the  
example from here: http://www.openwsman.org/openwsman-users-guide/using-ws-eventing

When I do my subscription like this:

wsman -h localhost -P 5985 -u abc -p abc123 subscribe http://schemas.dmtf.org/wbem/wscim/1/* 
  -x "SELECT * FROM ABC_FileIndication" -D "http://schemas.microsoft.com/wbem/wsman/1/WQL 
" -Z http://127.0.0.1:80/eventsink -r 600 -H 2 -G push -R

I get the Filtering Not supported Message

Thanks in advance
Till

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Openwsman-devel mailing list
Openwsman-devel@...
https://lists.sourceforge.net/lists/listinfo/openwsman-devel

[Suresh Sundriyal-2]

For the most part your config file seems OK, although I've rarely seen anybody's default
namespace set to root/interop. However, I doubt if that is the cause of your problem. :)

You can also probably drop the -H 2 from your request since I believe that is only used
while subscribing to heartbeats.

The only thing I do differently is, I usually subscribe to the parent CIM class, since the
http://schemas.dmtf.org/wbem/wscim/1/* usually corresponds to the all-classes ResourceURI.
Try subscribing to the parent CIM_Foo class that ABC_FileIndication derives from and
see if that works.

If not try directing the query to the ABC class ResourceURI and see if that works. In this case
your query should look like this:

wsman -h localhost -P 5985 -u abc -p abc123 subscribe http://abc.com/wbem/wscim/1/cim-schema/2/ABC_FileIndication
  -x "SELECT * FROM ABC_FileIndication" -D "http://schemas.microsoft.com/wbem/wsman/1/WQL" -Z
http://127.0.0.1:80/eventsink -r 600 -G push -R

In fact, I think in the above case you can leave out the filter all together and do the following:

wsman -h localhost -P 5985 -u abc -p abc123 subscribe http://abc.com/wbem/wscim/1/cim-schema/2/ABC_FileIndication
 -Z http://127.0.0.1:80/eventsink -r 600 -G push -R

I don't think you need to specify the namespace to be root/interop, since your default namespace
is already set to root/interop but it wouldn't hurt to try the above two commands using the
--namespace=root/interop switch as well.

According to the CIM mapping guide the above should work. If it does not, then it could be
a bug in Openwsman (I am guessing that you are able to subscribe for indications using
CIM-XML?).

--
Regards,
Suresh

________________________________________
From: Till Steinbach [till.steinbach@...]
Sent: Friday, November 06, 2009 3:24 AM
Cc: openwsman-devel@...
Subject: Re: [Openwsman-devel] Issues (Dispatcher       Error/FilteringNotSupported)

Am 06.11.2009 um 11:54 schrieb Suresh Sundriyal:

> If that doesn't work then it would be helpful to be able to see your
> config file and the actual
> commands.

My config looks like this:
------------------------------------
[server]
port = 5985
#ssl_port = 5986
ssl_cert_file = /etc/openwsman/servercert.pem
ssl_key_file = /etc/openwsman/serverkey.pem
#digest_password_file = /etc/openwsman/digest_auth.passwd
basic_password_file = /usr/local/etc/openwsman/simple_auth.passwd

min_threads = 4
max_threads = 10

#use_digest is OBSOLETED, see below.

#
# Authentication backend for BASIC authentication. Default is to read
a configuration file defined with 'basic_password_file'
#

#basic_authenticator = libwsman_pam_auth.so
#basic_authenticator_arg = openwsman

#
# WS-Management unauthenticated wsmid:Identify file
#
#anon_identify_file = /etc/openwsman/anon_identify.xml

#
# WS-Management authenticated wsmid:Identify file
#
#identify_file = /etc/openwsman/identify.xml



[client]
port = 5985
agent = openwsman 2.2.0

#
# settings for the CIM plugin
#

[cim]
#default_cim_namespace = root/cimv2
default_cim_namespace = root/interop
#default_cim_namespace = root/abc

# can also be SfcbLocal for local connection with sfcb CIMOM running
on same system
cim_client_frontend = XML
#cim_client_frontend = SfcbLocal

#indication_source_namespace is used to define namespace where the
Indications originate
indication_source_namespace = root/abc

# The following are in part fake namespaces for some publicly
available CIM implementations.
vendor_namespaces = ABC=http://abc.com/wbem/wscim/1/cim-schema/2,
Linux=http://sblim.sf.net/wbem/wscim/1/cim-schema/2

# CIMOM host, default is localhost
# host = localhost

# CIMOM port, default is 5988
# port = 5988

# boolean
# omit_schema_optional = 0

--------------------------

You can see i already played around with the parameters.

I think maybe I do the subscription wrong. I tried to follow the
example from here: http://www.openwsman.org/openwsman-users-guide/using-ws-eventing

When I do my subscription like this:

wsman -h localhost -P 5985 -u abc -p abc123 subscribe http://schemas.dmtf.org/wbem/wscim/1/*
  -x "SELECT * FROM ABC_FileIndication" -D "http://schemas.microsoft.com/wbem/wsman/1/WQL
" -Z http://127.0.0.1:80/eventsink -r 600 -H 2 -G push -R

I get the Filtering Not supported Message

Thanks in advance
Till

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Openwsman-devel mailing list
Openwsman-devel@...
https://lists.sourceforge.net/lists/listinfo/openwsman-devel

[Till Steinbach-2]

Am 06.11.2009 um 13:26 schrieb Suresh Sundriyal:

> For the most part your config file seems OK, although I've rarely  
> seen anybody's default
> namespace set to root/interop. However, I doubt if that is the cause  
> of your problem. :)

you are right! ;)

>
> According to the CIM mapping guide the above should work. If it does  
> not, then it could be
> a bug in Openwsman (I am guessing that you are able to subscribe for  
> indications using
> CIM-XML?).

Subscription via CIM-XML works fine.
I tried your sugestions for subscription but had no luck. It is really  
strange! After a getClass to the desired Indication Class the Handler  
is successfully created. Then openwsman tries to create a  
CIM_IndicationSubscription (no Filter is created prior) In the Filter  
Property the IndicationClass (ABC_FileIndication) is used as reference  
Class (no Filter Class!). That seems somehow logical when I see the  
last section in the howto: http://www.openwsman.org/openwsman-users-guide/using-ws-eventing 
  (Subscribe to an existing filter) so i think I need that http://schemas.dmtf.org/wbem/wscim/1/* 
  URI  to create a filter instance. But then I always get these  
Filtering over the event source not supported Messages.

I'm a bit confused. Am I the only person with those issues?

Regards
Till

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Openwsman-devel mailing list
Openwsman-devel@...
https://lists.sourceforge.net/lists/listinfo/openwsman-devel

[Klaus Kaempf]

* Till Steinbach <till.steinbach@...> [Nov 06. 2009 15:28]:
>
> Subscription via CIM-XML works fine.

Good, then the bug is not in your CIMOM or your providers ;-)

Can you post the (wbemcli ?) command you use for subscription via
cim-xml ? This would help in debugging openwsman.

> I tried your sugestions for subscription but had no luck. It is
> really strange! After a getClass to the desired Indication Class the
> Handler is successfully created. Then openwsman tries to create a
> CIM_IndicationSubscription (no Filter is created prior) In the
> Filter Property the IndicationClass (ABC_FileIndication) is used as
> reference Class (no Filter Class!).

Please run 'openwsmand' in debug mode (i.e. "openwsmand -d 999"). This
should point us to where openwsman fails.

>
> I'm a bit confused. Am I the only person with those issues?

Apparently ;-)

Klaus
---
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)


------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Openwsman-devel mailing list
Openwsman-devel@...
https://lists.sourceforge.net/lists/listinfo/openwsman-devel

[Klaus Kaempf]

* Till Steinbach <till.steinbach@...> [Nov 06. 2009 12:25]:

>
> When I do my subscription like this:
>
> wsman -h localhost -P 5985 -u abc -p abc123 subscribe
> http://schemas.dmtf.org/wbem/wscim/1/* -x "SELECT * FROM
> ABC_FileIndication" -D
> "http://schemas.microsoft.com/wbem/wsman/1/WQL" -Z
> http://127.0.0.1:80/eventsink -r 600 -H 2 -G push -R
>
> I get the Filtering Not supported Message

Thats to be expected since openwsmand does not implement WQL. You can
try 'CQL' (cim query language), which should be passed to the CIMOM
(and needs cimom support).

Klaus

---
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)


------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Openwsman-devel mailing list
Openwsman-devel@...
https://lists.sourceforge.net/lists/listinfo/openwsman-devel

[Till Steinbach-2]

Am 09.11.2009 um 12:02 schrieb Klaus Kaempf:

> * Till Steinbach <till.steinbach@...> [Nov 06. 2009 12:25]:
>>
>> When I do my subscription like this:
>>
>> wsman -h localhost -P 5985 -u abc -p abc123 subscribe
>> http://schemas.dmtf.org/wbem/wscim/1/* -x "SELECT * FROM
>> ABC_FileIndication" -D
>> "http://schemas.microsoft.com/wbem/wsman/1/WQL" -Z
>> http://127.0.0.1:80/eventsink -r 600 -H 2 -G push -R
>>
>> I get the Filtering Not supported Message
>
> Thats to be expected since openwsmand does not implement WQL. You can
> try 'CQL' (cim query language), which should be passed to the CIMOM
> (and needs cimom support).

But Filtering works great for the enumerate Action (with WQL and CQL). I tried the above query with -D "http://schemas.dmtf.org/wbem/cql/1/dsp0202.pdf" with no success. With the enumerate action it worked with that dialect.
I still get the FilteringNotSupported fault. Obviously I'm doing something completely wrong. But I don't get the problem. Perhaps someone can send me a query to subscribe for something (for example CIM_ProcessIndication) with wsman cli.

I'm running openwsman with "-d -s 6" but I cannot see the problem in the output:


Nov 12 11:51:42 [13465] decide_what_to_do: [/wsman]
Nov 12 11:51:42 [13465] is_alias: aliases []      
Nov 12 11:51:42 [13465] Checking basic for user: abc; password XXXXX
Nov 12 11:51:42 [13465] user: abc,  passwd: XXXX                    
Nov 12 11:51:42 [13465] user: abc,  passwd: XXXXX                  
Nov 12 11:51:42 [13465] Done reading request                        
Nov 12 11:51:42 [13465] Inbound call...                            
Nov 12 11:51:42 [13465] uri: http://schemas.dmtf.org/wbem/wscim/1/*, action: http://schemas.xmlsoap.org/ws/2004/08/eventing/Subscribe
Nov 12 11:51:42 [13465] namespace: http://schemas.dmtf.org/wbem/wsman/identity/1/wsmanidentity.xsd                                   
Nov 12 11:51:42 [13465] namespace: http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2
Nov 12 11:51:42 [13465] namespace: http://schemas.dmtf.org/wbem/wscim/1
Nov 12 11:51:42 [13465] Processing Filters: inbound
Nov 12 11:51:42 [13465] Checking Message ID: uuid:5409b260-782a-182a-8002-d60a06290c00
Nov 12 11:51:42 [13465] wsen:Expires = PT600.000000S
Nov 12 11:51:42 [13465] Processing Filters: outbound
Nov 12 11:51:42 [13465] destroy op
Nov 12 11:51:42 [13465] Inbound call completed
Nov 12 11:51:42 [13465] Response status=400 (Bad request)
Nov 12 11:51:42 [13465] 4 (null) stopped. 947 of content data, 947 now in a buffer
Nov 12 11:51:42 [13465] Disconnecting 4 ()



Till

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Openwsman-devel mailing list
Openwsman-devel@...
https://lists.sourceforge.net/lists/listinfo/openwsman-devel

[Klaus Kaempf]

* Till Steinbach <till.steinbach@...> [Nov 12. 2009 12:02]:

>
> Am 09.11.2009 um 12:02 schrieb Klaus Kaempf:
> > * Till Steinbach <till.steinbach@...> [Nov 06. 2009 12:25]:
> >>
> >> When I do my subscription like this:
> >>
> >> wsman -h localhost -P 5985 -u abc -p abc123 subscribe
> >> http://schemas.dmtf.org/wbem/wscim/1/* -x "SELECT * FROM
> >> ABC_FileIndication" -D
> >> "http://schemas.microsoft.com/wbem/wsman/1/WQL" -Z
> >> http://127.0.0.1:80/eventsink -r 600 -H 2 -G push -R
> >>
> >> I get the Filtering Not supported Message
> >
> > Thats to be expected since openwsmand does not implement WQL. You can
> > try 'CQL' (cim query language), which should be passed to the CIMOM
> > (and needs cimom support).
>
> But Filtering works great for the enumerate Action (with WQL and CQL).

Then you're lucky because your CIMOM supports both dialects ;-)

openwsman just check for valid filter dialects (via a simple string
compare of the value given via '-D') and passes them through.


> I tried the above query with -D
> "http://schemas.dmtf.org/wbem/cql/1/dsp0202.pdf" with no success. With
> the enumerate action it worked with that dialect. I still get the
> FilteringNotSupported fault.
> Obviously I'm doing something completely wrong.

Obviously, you don't ;-) Its the CIMOM which only supports enumeration
filtering but not event filtering.

Hth,

Klaus
---
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)


------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Openwsman-devel mailing list
Openwsman-devel@...
https://lists.sourceforge.net/lists/listinfo/openwsman-devel

[Till Steinbach-2]

Am 12.11.2009 um 12:31 schrieb Klaus Kaempf:
>> I tried the above query with -D
>> "http://schemas.dmtf.org/wbem/cql/1/dsp0202.pdf" with no success. With
>> the enumerate action it worked with that dialect. I still get the
>> FilteringNotSupported fault.
>> Obviously I'm doing something completely wrong.
>
> Obviously, you don't ;-) Its the CIMOM which only supports enumeration
> filtering but not event filtering.

Are you sure? How does openwsman know that sfcb does not support it? I cannot see any interaction between openwsman and sfcb when I send a query that results in a FilteringNotSupported answer. Not in Wireshark and not in the sfcb-Output (even with -t 8 (http debug output)). When I subscribe directly with sfcb I can create a filter with WQL-Dialect by setting QueryLanguage property to "WQL". I have not tried yet to create a filter via CIM-XML and then subscribe to that filter via openwsman. That may work but does not solve my problem.

Is there a compile option to enable filtering for event subscriptions in openwsman? Are there more locations where the filtering may be disabled in openwsman?

Thanks Till

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Openwsman-devel mailing list
Openwsman-devel@...
https://lists.sourceforge.net/lists/listinfo/openwsman-devel

[Till Steinbach-2]

I started to search for a bug in sourcecode and maybe I found the Problem. Below is the wsman request from my wsman cli:

<?xml version="1.0" encoding="UTF-8"?>
<s:Envelope xmlns:s="http://www.w3.org/2003/05/soap-envelope" xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing" xmlns:wsman="http://schemas.dmtf.org/wbem/wsman/1/wsman.xsd" xmlns:wse="http://schemas.xmlsoap.org/ws/2004/08/eventing">
        <s:Header><wsa:Action s:mustUnderstand="true">http://schemas.xmlsoap.org/ws/2004/08/eventing/Subscribe</wsa:Action><wsa:To s:mustUnderstand="true">http://localhost:5985/wsman</wsa:To><wsman:ResourceURI s:mustUnderstand="true">http://schemas.dmtf.org/wbem/wscim/1/*</wsman:ResourceURI><wsa:MessageID s:mustUnderstand="true">uuid:db33aee9-782b-182b-8002-d60a06290c00</wsa:MessageID><wsa:ReplyTo><wsa:Address>http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous</wsa:Address></wsa:ReplyTo><wsman:SelectorSet><wsman:Selector Name="__cimnamespace">root/interop</wsman:Selector></wsman:SelectorSet>
        </s:Header>
        <s:Body>
                <wse:Subscribe>
                        <wse:Delivery Mode="http://schemas.dmtf.org/wbem/wsman/1/wsman/Pull">
                                <wse:NotifyTo>
                                        <wsa:Address>http://test.de/</wsa:Address>
                                </wse:NotifyTo>
                        </wse:Delivery>
                        <wse:Expires>PT600.000000S</wse:Expires>
                        <wsman:Filter Dialect="http://schemas.dmtf.org/wbem/cql/1/dsp0202.pdf">SELECT * FROM ABC_FileIndication</wsman:Filter>
                </wse:Subscribe>
        </s:Body>
</s:Envelope>

As you can see the Filter-Tag has the wsman namespace not the wse namespace. Thats why openwsman does not find the filter in the request.
After looking in the WS-Eventing Specification I think the bug is in the wsman CLI, as the tag should be in wse Namespace. Right?

I will check whether I can solve my problem by patching wsman CLI

regards
Till




------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Openwsman-devel mailing list
Openwsman-devel@...
https://lists.sourceforge.net/lists/listinfo/openwsman-devel

[Klaus Kaempf]

* Till Steinbach <till.steinbach@...> [Nov 12. 2009 14:02]:
>
> As you can see the Filter-Tag has the wsman namespace not the wse namespace.

Uhm, this rings a bell.

Which version of openwsman are you using ?
There was a related fix in openwsman-2.2.0. Upgrade to this version.

If you're already at 2.2.0 then we've missed one more place to fix.


> Thats why openwsman does not find the filter in the request. After
> looking in the WS-Eventing Specification I think the bug is in the
> wsman CLI, as the tag should be in wse Namespace. Right?

Right.

Klaus

P.S.:
See
http://openwsman.svn.sourceforge.net/viewvc/openwsman/openwsman/trunk/src/lib/wsman-filter.c?r1=3172&r2=3248
for the diff
---
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)


------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Openwsman-devel mailing list
Openwsman-devel@...
https://lists.sourceforge.net/lists/listinfo/openwsman-devel

[Till Steinbach-2]

Am 12.11.2009 um 14:30 schrieb Klaus Kaempf:

> * Till Steinbach <till.steinbach@...> [Nov 12. 2009 14:02]:
>>
>> As you can see the Filter-Tag has the wsman namespace not the wse namespace.
>
> Uhm, this rings a bell.

> Which version of openwsman are you using ?
> There was a related fix in openwsman-2.2.0. Upgrade to this version.

Openwsmand 2.2.0
Wsmancli 2.1.0

>
> If you're already at 2.2.0 then we've missed one more place to fix.
>
>> Thats why openwsman does not find the filter in the request. After
>> looking in the WS-Eventing Specification I think the bug is in the
>> wsman CLI, as the tag should be in wse Namespace. Right?
>
> Right.

I think the issue must be fixed in wsmancli. I only found wsmancli 2.1.0. When I am wrong and the issue must be fixed in openwsman the fix is to change XML_NS_EVENTING in line 692 of file "wsman-soap-envelope.c" to XML_NS_WS_MAN.
But after looking into the Specification I think the Issue must be fixed in the client library


Regards
Till

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Openwsman-devel mailing list
Openwsman-devel@...
https://lists.sourceforge.net/lists/listinfo/openwsman-devel

[Klaus Kaempf]

* Till Steinbach <till.steinbach@...> [Nov 12. 2009 14:58]:
> > Which version of openwsman are you using ?
> > There was a related fix in openwsman-2.2.0. Upgrade to this version.
>
> Openwsmand 2.2.0
> Wsmancli 2.1.0

Good, so you have the latest released versions.

>
> >
> > If you're already at 2.2.0 then we've missed one more place to fix.
> >
> >> Thats why openwsman does not find the filter in the request. After
> >> looking in the WS-Eventing Specification I think the bug is in the
> >> wsman CLI, as the tag should be in wse Namespace. Right?
> >
> > Right.
>
> I think the issue must be fixed in wsmancli. I only found wsmancli 2.1.0.

> When I am wrong and the issue must be fixed in openwsman the fix is to
> change XML_NS_EVENTING in line 692 of file "wsman-soap-envelope.c" to
> XML_NS_WS_MAN.
This line is the de-serialization (parsing) and it was changed from
XML_NS_WS_MAN to XML_NS_EVENTING in openwsman 2.2.0

> But after looking into the Specification I think the Issue must be
> fixed in the client library

Yeah. Let me find the serialization counterpart and fix it there also.
Would you be willing to test openwsman from svn trunk ?

Klaus
---
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)


------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Openwsman-devel mailing list
Openwsman-devel@...
https://lists.sourceforge.net/lists/listinfo/openwsman-devel

[Klaus Kaempf]

* Klaus Kaempf <kkaempf@...> [Nov 12. 2009 15:43]:
>
> > But after looking into the Specification I think the Issue must be
> > fixed in the client library
>
> Yeah. Let me find the serialization counterpart and fix it there also.

Its in filter_serialize() of wsman-filter.c which creates the filter
xml representation without taking enumerate vs. subscribe into account.

Klaus
---
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)


------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Openwsman-devel mailing list
Openwsman-devel@...
https://lists.sourceforge.net/lists/listinfo/openwsman-devel

[Till Steinbach-2]

Am 12.11.2009 um 15:48 schrieb Klaus Kaempf:
> * Klaus Kaempf <kkaempf@...> [Nov 12. 2009 15:43]:
>>
>>> But after looking into the Specification I think the Issue must be
>>> fixed in the client library
>>
>> Yeah. Let me find the serialization counterpart and fix it there also.
>
> Its in filter_serialize() of wsman-filter.c which creates the filter
> xml representation without taking enumerate vs. subscribe into account.

Yes, there is no information about the action in the filter structure. Quick fix would be to pass the desired namespace to the filter_serialize-Method.

Sure I'am willing to test the fix from svn.

Thanks for your involvement!
Till

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Openwsman-devel mailing list
Openwsman-devel@...
https://lists.sourceforge.net/lists/listinfo/openwsman-devel

[Klaus Kaempf]

* Till Steinbach <till.steinbach@...> [Nov 12. 2009 15:53]:

> Am 12.11.2009 um 15:48 schrieb Klaus Kaempf:
> > * Klaus Kaempf <kkaempf@...> [Nov 12. 2009 15:43]:
> >>
> >>> But after looking into the Specification I think the Issue must be
> >>> fixed in the client library
> >>
> >> Yeah. Let me find the serialization counterpart and fix it there also.
> >
> > Its in filter_serialize() of wsman-filter.c which creates the filter
> > xml representation without taking enumerate vs. subscribe into account.
>
> Yes, there is no information about the action in the filter structure.

> Quick fix would be to pass the desired namespace to the
> filter_serialize-Method.
Exactly, thats what I've just done.
>
> Sure I'am willing to test the fix from svn.
Just go ahead, rev 3279 of openwsman should have it fixed.

I still wonder how Microsofts winrm implements this and what the
standard says. Its the usual interoperability vs. standard compliance
struggle ;-)

>
> Thanks for your involvement!
Thanks for your patience and testing !

Klaus
---
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)


------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Openwsman-devel mailing list
Openwsman-devel@...
https://lists.sourceforge.net/lists/listinfo/openwsman-devel

[Till Steinbach-2]

Am 12.11.2009 um 16:11 schrieb Klaus Kaempf:

> Just go ahead, rev 3279 of openwsman should have it fixed.
Tested it now for a while, seems to work without a problem.

> I still wonder how Microsofts winrm implements this and what the
> standard says. Its the usual interoperability vs. standard compliance
> struggle ;-)
Yea, that's on my todo list, testing compatibility with winrm.


Till

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Openwsman-devel mailing list
Openwsman-devel@...
https://lists.sourceforge.net/lists/listinfo/openwsman-devel