W3C home > Mailing lists > Public > www-ws-arch@w3.org > September 2002

RE: [MTF] Updated WS Management Architecture concepts

From: Mark Potts <mark.potts@talkingblocks.com>
Date: Wed, 25 Sep 2002 15:15:31 -0700
Message-ID: <6A852758A8437041A389D1AE74D8760A1B15DC@mach5.talkingblocks.com>
To: "Sedukhin, Igor" <Igor.Sedukhin@ca.com>, "Heather Kreger" <kreger@us.ibm.com>, "Eckert, Zulah Karen" <zulah_eckert@hp.com>, "Willits, Jim" <jim.willits@hp.com>, "Colleen Evans" <colleen.evans@sonicsoftware.com>, "Husband, Yin-Leng" <Yin-leng.Husband@hp.com>, "Sandeep Kumar" <sandkuma@cisco.com>, "Prasad Yendluri" <pyendluri@webmethods.com>
Cc: <www-ws-arch@w3.org>, "Mark Perreira (E-mail)" <mperr@ix.netcom.com>
Igor
 
Looks really good at first pass my only concerns is around the relationships between Services, Service Instances, Hosted Services, Intermediary. There are probably many ways to model the relationships between these but I think that Service needs to be treated as an abstract in every sense.
 
A Service (always abstract) can either be a Service Instance, or Service Proxy The relationship from Proxy -> Service is on of "represents" (in the true proxy pattern), while the relationship from Service Instance -> Service is one "aggregation" (in the shape of a composite pattern, to either proxies or instances).
 
That leaves a relationship between Service (abstract), to Host (again abstract), where Host can be either a WSEE or an Intermediary.
 
To be clear the rationale for the an aggregation relationship between Service Instance and Service, is that WSEE could be a container or be a process engine where the process  - again a Service aggregates other services abstract and executes the process.
 
Just my thoughts  - 

-----Original Message-----
From: Sedukhin, Igor [mailto:Igor.Sedukhin@ca.com]
Sent: Wednesday, September 25, 2002 1:04 PM
To: Heather Kreger; Eckert, Zulah Karen; Willits, Jim; Colleen Evans; Husband, Yin-Leng; Sandeep Kumar; Mark Potts; Prasad Yendluri
Cc: www-ws-arch@w3.org
Subject: [MTF] Updated WS Management Architecture concepts



I have updated the document I sent earlier with an informal use case diagram and text. It provides place for for things like Management Protocol, Interfaces, etc.

<<WS Management Architecture Concept.doc>> 

PS. I'm cross-posting to the WS-Arch list. May be some of the basic concept UML diagrams could be used in the architecture document that the outer group is working on.

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

	 -----Original Message----- 
From:   Sedukhin, Igor  
Sent:   Wednesday, September 25, 2002 12:40 PM 
To:     Heather Kreger; Eckert, Zulah Karen; Willits, Jim; Colleen Evans; 'Husband, Yin-Leng'; Sandeep Kumar; 'mark.potts@talkingblocks.com'; Prasad Yendluri

	Subject:        WS Management Architecture concepts 

	I took an AI at our last MTF call to formalize some of the basic concepts of management of the WS Architecture. Attached is my attempt to do so. First set of diagrams and text explain management of the WS-Arch "traingle". Second set of diagrams and text formally expresses it in UML.

	 << File: WS Management Architecture Concept.doc >> 

	-- Igor Sedukhin .. (igor.sedukhin@ca.com) 
-- (631) 342-4325 .. 1 CA Plaza, Islandia, NY 11788 
Received on Wednesday, 25 September 2002 18:16:05 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 3 July 2007 12:25:06 GMT