Community
Participate
Working Groups
COSMOS can provide a generic publication/subscription event mechanism in the context of web services. This can be done using the WS-Notification specification. The notification broker should be an entity registered with the management domain. A producer/consumer of notifications will go through the following steps to publish or consume an event: 1) Contact the management domain 2) Query for the notification broker (see WS-Notification) 3) Using the EPR of the notification broker, a producer can publish a set of topics (see WS-Topics). Similarly a consumer can subscribe to a set of published topics (see WS-BaseNotification). WEF should be used for embedding events as part of the notification procedure.
is this targeted for i8? currently the target milestone is blank
I think it should be targeted for i8. Hubert/Mark, your thoughts? This will likely fall through the cracks if a milestone is not set.
And while setting this milestone, you might also think about the milestone for bug 212297. Of course you'd need to let Tania know ASAP if these need to be for i8, so they can get on the official list.
We need this urgently at CA... However, is this even feasible for i12, given that there is no Management Domain? If need be, we will volunteer the development resources, assuming this is containable...
Jimmy, I think the existence of a notification broker is independent of a management domain. However, can you provide us with the requirements or the design of what you need? The term "notification broker" is quite overloaded. I want to make sure we have the same understanding of the role of a "notification broker".
Hubi, We will have an technical adopter in this week's architecture call. He can talk to his detailed requirements; and we can also put the design in place. Thanks, Jimmy
Decrementing the prio till the containability is known...
If it is feasible to have this capability in i12, we will have an adopter for this component from the CA end almost instantly... We need to do a few things before we can determine if this should be in i12: 1. This will not violate any of the i12 "Guidelines" / charter of i12 2. This indeed will be containable in i12 3. We will get the CA techical adopter to provide / review the design Thanks, Jimmy
Can this be implemented using MUWS? I know we have moved away from MUWS; but this is one area where MUWS may be relevant.
Jimmy, can CA provide the design for this enhancement? Thanks.
At this junture, the CA adopter has chosen to implement their own MUSE-based Notification Broker; MUSE being a requirement from them . Since bringing MUSE back into COSMOS cannot be justified due to one ER, I have deferred this to a future iteration. In the interim, this will be a topic of discussion in COSMOS, alongwith MUSE.
