RE: about set requests and values kept in memory

[Dziembowski, Kinga]

Carlos, Great to hire that you are learning muse and that you are using muse example to better understand how things are working. Soon it will be more documentation – it will make the learning easier. Your questions: Please note that the Resources in muse example do not implement setResourceProperty operation – by this fact all Resources are read only from the point of view of the “client”. ( check wsdls – this operation is commented) It does not mean that the value of the properties are fixed. They change as the back end changes – but client cannot change them. This is the reason why you do not see any requests examples to change properties values. On the other hand you probably would like to see the notifications emitted by the resource each time the property value changes. At this point of time muse project does not support such notifications. It only supports notifications for the property changes when client uses setPropertOperation.   You are right that it is no persistence for Resources. In general the idea is that the resource is just in between client and the back end, and its role is to make the properties values available to the client application. The real state is maintained by the back end and each time the request for the property value is coming from the client, back end is examined for the current value. I can imagine that the muse management application can run on dedicated box and be able to automatically reconnect to the back end (running on separate boxes) after the failure. This way the management info will be not available for a moment of failure, but will gracefully reconnect and operate as expected. It is other persistence problem at the moment – for example, when you build your management model using the muse example, you created several instances of resources, you connected them with relationships, your client application controls the managed domain. If at this point you stop the app server – you will loose your management model - at the moment it is no mechanism to save and reconstruct the model on startup. On the other hand you can script your model creation procedure using ant, and after the app server stop rerun the script. The example for such script can be muse example “ test” ant task – modification of the sequence, addition of  new requests (modeled on the available requests) will do the job.     I hope this helped to better understand the muse example. Please do not hesitate to ask more questions.   Kinga Dziembowski Hewlett-Packard Company Applied Technology Office (ATO) 856.638.6065 [EMAIL PROTECTED]   From: Lombrera Lombrera [mailto:[EMAIL PROTECTED] Sent: Monday, July 18, 2005 10:09 PM To: muse-dev@ws.apache.org Subject: about set requests and values kept in memory   Hi all I have deployed Muse and I am very happy to see it working I would like to ask you two things:   a - if there is a sample of a set request, for example, to change the value of a propertie like CpuUsage from the Host Service. I have been using the requests in the requests dir, but there is not a example of a set request to change the value of some propertie. Existing this, could you share it with me?   b - I have perceived also, that when I will change the value of some propertie, this value will be kept in memory. This means that if the machine is rebooted it will loose the new values. Is this right ? What could be the best way to make this new values be mantained?   Thank you in advance Excuse me for my poor english Carlos Yahoo! Acesso Grátis: Internet rápida e grátis. Instale o discador agora!