Hi Nilabja,<br><span class="gmail_quote"></span><br><div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">> I'm thinking of a tool which shows me, which
<br>> components are existing in the deployment and what their state is, maybe<br>> even the connection between the components.<br>><br>I am working on Target Manager which provides a resource provisioning<br>interface to book resources for components. As an extension to this
</blockquote><div><br>Wow, as I can see there's a lot of work going on in the area of DAnCE.<br>Is it correct, that this Target Manager is part of the OMG D&C specification?<br>I recognized that there is already a Target Manager executable in the
<br>DAnCE sources integrated with CIAO.<br>What is the current state of the development there?<br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
work, I am also working on monitoring a running application and to<br>characterize it's behavior in terms of resource usages. By resources, I<br>mean both hardware and software resources. Such monitoring will help in</blockquote>
<div><br>Will this include the interconnections between components and their<br>performance parameters, like connection response time, ...?<br><br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
two ways, first it will enable run-time detection of interesting events<br>in the system such as component failure, resource starvation etc.,</blockquote><div><br>Is it possible to provide a complete view of the running assembly, including
<br>all running components and its connections?<br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">second to create a profile of an application which will help in
<br>allocating it in future deployments.<br><br> The monitoring techniques use both internal and external probes to<br>measure performance. Overhead of such probes is an interesting aspect<br>which I am investigating.</blockquote>
<div><br>Will this be implemented as a standalone executable or is it planned<br>to integrate this functionality into something which exists already?<br></div><br>Thanks a lot for pointing this out. It is interesting to hear that
<br>the information necessary for component monitoring can be retrieved<br>from standard D&C tools.<br><br>Thanks,<br>Friedehelm<br></div>