RE: [wsdm] Weather station WSDL and RequestProcessingDigest comments

["Springer, Ian P." <ian.springer@hp.com>]

Yes, I think it should also have GetManageabilityReferences. Also, in addition to WeatherStation.wsdl, we need a WeatherStationMgmt.wsdl, which represents the MOWS service, correct?

Ian

---

From: David Melgar [mailto:dmelgar@us.ibm.com]
Sent: Friday, March 25, 2005 10:22 AM
To: Sedukhin, Igor S
Cc: Hideharu Kato; wsdm@lists.oasis-open.org
Subject: RE: [wsdm] Weather station WSDL and RequestProcessingDigest comments

It is possible for a functional web service to use WSRF, I hadn't meant to imply it was a requirement.
I agree its cleaner to define a simple operation on the web service instead of relying on WSRF operations. GetCurrentTemperature sounds good.

In the attached WSDL, the weather station should also implement GetManageabilityReferences should it not?

David Melgar
Web Services Toolkit Development
Emerging Technologies
dmelgar@us.ibm.com

"Sedukhin, Igor S" <Igor.Sedukhin@ca.com>

03/25/2005 10:01 AM

To	"Hideharu Kato" <hideharu@sdl.hitachi.co.jp>, <wsdm@lists.oasis-open.org>
cc
Subject	RE: [wsdm] Weather station WSDL and RequestProcessingDigest comments

+1. WeatherStation is just a WS, not a WS-Resource and not WSA-enabled.
That was my interpretation all along.
Attached is the WSDL.

-- Igor Sedukhin .. (igor.sedukhin@ca.com)
-- (631) 342-4325 .. 1 CA Plaza, Islandia, NY 11749

-----Original Message-----
From: Hideharu Kato [mailto:hideharu@sdl.hitachi.co.jp]
Sent: Friday, March 25, 2005 7:18 AM
To: wsdm@lists.oasis-open.org
Subject: Re: [wsdm] Weather station WSDL and RequestProcessingDigest
comments

It is unclear to me whether WeatherStation is a WS-Resource or just a
Web service endpoint.

I don't think that the operation which causes the
RequestProcessingNotification is GetRP().

I think WeatherStation Web service is just a "Web servcie" not a
"WS-Resource".
The GetRP() operation is the operation WS-Resources expose.
I don't believe that MOWS restricts its target only to WS-Resources.

I know that in-band case is also possible in MOWS.
But even if in such a case, ManageableEndpoint(WeatherStation) has some
business operations(functional operations) like a
GetCurrentTemperature().
This operation causes the RequestProcessingState event.

The FCCID is a property of WeatherStation Web service, but it is not
necessary to be a Resource Property (defined in WSRF) of WeatherStation
service.

In the case of in-band, WeatherStation itself is the
ManageabilityEndpoint, so WeatherStation(ManageabilityEndpoint) has
stateful resource which represents its own state.
In this case, WeatherStation is a "WS-Resource".

In the case of out-band, another Web service endpoint (MOWS service) is
the ManageabilityEndpoint of WeatherStation.
So, MOWS service(ManageabilityEndpoint) has a stateful resource which
represents the state of WeatherStation.
In this case, FCCID is a Resource Property of MOWS service(stateful
resource).
The GetRP() operation is exposed by MOWS service in order for
requestor(manageability consumer) to get FCCID of WeatherStation.
So, WeatherStation is not necessary to be a WS-Resource nor to expose
GetRP().

Anyway I believe that WSDL of WeatherStation Web service(functional
porttype)should be provided before interop.

---------------------------------------
Hideharu Kato
2nd Research Dept.
Hitachi,Ltd.,Systems Development Laboratory E-mail :
hideharu@sdl.hitachi.co.jp Tel : +81-44-959-0248 Fax : +81-44-959-0853
--------------------------------------


----- Original Message -----
From: "David Melgar" <dmelgar@us.ibm.com>
To: "Campana Jr., Salvatore J" <sal.campana@hp.com>
Cc: <wsdm@lists.oasis-open.org>
Sent: Friday, March 25, 2005 4:14 PM
Subject: [wsdm] Weather station WSDL and RequestProcessingDigest
comments


> On the call today I questioned if we needed to define weather station
> WSDL. But it seems like we do need to define an operation on a web
> service.
> In the MOWS Request Processing Digest act, there needs to be some
> operation which is invoked which causes the event to be sent. This
> operation could be a GetResourceProperty(FCCID) or
> GetManageabilityReferences.
>
> It is unclear to me what resource is intended to be represented by the
> Weather Station Service. Is it a webservice (MOWS), or is the resource
a
> weather station? Correlateable properties are meant to indicate if two
> different EPRs represent management of the same resource. Using FCCID
> property to determine if two web services represent the same resource
> seems to indicate that the resource is the weather station, not the
web
> service.
>
> If the weather station web service is intended to be the web service
> managed using MOWS then the GetResourceProperty or
> GetManageabilityReferences operation can be invoked on this web
service to
> drive the Request Processing Digest act. This step should be added to
the
> act.
>
> The provided WSDL for weather station mixes the business web service,
and
> the management provider endpoint. These should be separate port types.
> They could be implemented at the same port, but this is not typical.
The
> resource properties document reference by each port type is different
> since the properties available through each port type differ.
>
> Weather station port type (business) should have the following
operations
> as a minimum:
> - GetResourceProperty:  FCCID is the only required property.
> - GetManageabilityReferences
>
> ManagementProvider port type which manages the weather station needs
to
> have these operations:
> - GetResourceProperty: WSDM defined properties, MOWS metrics, etc.
> - GetMultipleResourceProperties
> - Subscribe
> - GetCurrentMessage: This isn't used by the interop scenarios, but is
part
> of the NotificationProducer port type defined by WSN.
>
> David Melgar
> Web Services Toolkit Development
> Emerging Technologies
> dmelgar@us.ibm.com
>
>
>
>
> "Campana Jr., Salvatore J" <sal.campana@hp.com>
> 03/24/2005 01:43 PM
>
> To
> <wsdm@lists.oasis-open.org>
> cc
>
> Subject
> [wsdm] Interop Wsdl Files
>
>
>
>
>
>
>
> I've attached our WSDL files for the various interop services and the
> xsd (corrected xsd:String-> xsd:string) from the interop document..
> You'll notice that the spec WSDLs and XSDs are referenced using
relative
> paths..that will probably need to change....
>
> Note: I have the GetManageabilityReferences operation in the
> WeatherStation service, however I think it was noted that the
operation
> could exist in another service.
>
> Thx!
>
> -S
>
> --------------------
> Sal Campana
>
> HP Software Engineer
>
> phone: 856.638.6284
> email: sal.campana@hp.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: wsdm-unsubscribe@lists.oasis-open.org
> For additional commands, e-mail: wsdm-help@lists.oasis-open.org
>


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


> ---------------------------------------------------------------------
> To unsubscribe, e-mail: wsdm-unsubscribe@lists.oasis-open.org
> For additional commands, e-mail: wsdm-help@lists.oasis-open.org



---------------------------------------------------------------------
To unsubscribe, e-mail: wsdm-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: wsdm-help@lists.oasis-open.org



---------------------------------------------------------------------
To unsubscribe, e-mail: wsdm-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: wsdm-help@lists.oasis-open.org