英语翻译5.4.Application Delegated ManagerThe Application Delegat

英语翻译
5.4.Application Delegated Manager
The Application Delegated Manager plays the role of a
broker between components and resources.In addition,
the ADM will have the responsibility of supervising the
application execution at runtime to make sure we achieve
all the required autonomic properties identified in the
application service template as discussed in the
Application Management Editor subsection.The main
fbnctions of ADM can be outlined as follows:
Maintain an up-to-date list of resources as well as
available components that can participate in executing
a given application.
Select the set of resources that can meet the
autonomic requirements of an application.
0 Dispatch the appropriate number of mobile agents to
deploy,configure,perform on-line monitoring,
analysis,and adaptation when the application cannot
meet its requirements.
5.5.Fault handler
There are three types of fault handlers:System Fault
Handler,Component Fault Handler and Agent Fault
Handler.They deal with system fault,component fault
and agent faults,respectively.These handlers are created
by the ADM and they share the component deployment
information.The ADM registers with the Coordinate
Space (CS) that it is interested in the presence of the fault
entries in the Coordinate Space.The fault handlers are
designated as event listeners once the fault entries appear.
In the next subsections,we discuss the fault-detection and
recovery schemes adopted to achieve self-healing.We
also show the dumpscreens of our proof-of-concept
prototype implemented based on Autonomia architecture.
5.5.1.Fault Detection and Recovery Scheme.This
implementation has the capability to handle three different
kinds of faults defined as Component fault,Agent System
fault and Node fault.In our environment,the ADM
creates a Node Fault Handler,Component Fault Handler,
and Agent Fault Handler,which register with the
JavaSpaces their interest in the presence of the node fault
entry,the component fault entry and the agent fault entry,
respectively.The JavaSpaces will notify the appropriate
fault handler when a fault entry is written in the space.
Then,the fault handler will spawn a thread to recover that
fault using checkpointinglmigrating mechanism [25].
In Autonomia,whenever a fault is detected,the
corresponding fault entry is created and is then written to
the JavaSpaces.The lease of staying in the JavaSpaces for
the entry is renewed by a global Lease Renewal Manager
service.Any fault entry should stay in the JavaSpaces
until a fault handler takes it out and deals with the fault
even after their creators have crashed.
文章依旧很长,一定要尽量准确哦,

5.4 .申请授予经理
申请授予经理扮演一个
券商之间的组件和资源.此外,
有关行政管理部门将有责任监督
应用程序执行在运行时,以确保我们可实现
所需的全部自主性质确定在
应用服务模板讨论中
应用管理主编款.主
fbnctions署长可以概述如下：
维持一个不断更新的名单上的资源,以及
现有的组件,可以参与执行
一个特定的应用.
选择一套资源能够满足
自主要求的申请.
0派遣适当数量的移动代理商
部署,配置,履行对在线监测,
分析,并适应当申请不能
满足其要求.
5.5 .故障处理
有三种类型的故障处理：系统故障
处理程序,组件故障处理程序和代理故障
处理器.他们处理的系统故障,元件故障
与Agent故障,分别.这些处理都是创造
由ADM和他们分享组件部署
信息.能者多册与协调
空间（政务司司长）表示,这是有意在存在故障
参赛作品在协调空间.故障处理人员正
被指定为事件听众一旦故障作品出现.
在下一小节,我们讨论故障检测和
回收计划以达到自愈.我们
也显示dumpscreens我们的概念证明
样机的基础上实施建筑自治权.
5.5.1 .故障检测和恢复计划.这
实施有能力处理好三个不同
种故障定义为组件故障,代理制
故障和节点故障.在我们的环境中,阿霉素
创建一个节点故障处理程序,组件故障处理程序,
和代理故障处理程序,其中登记与
javaspaces兴趣在场的节点故障
入境,组件故障,进入的范围和代理故障入境,
分别.该javaspaces将通知合适
故障处理时,发生故障,进入写在太空生活.
届时,故障处理,将引发一个线程恢复那
故障使用checkpointinglmigrating机制[ 25 ] .
在自治权,哪怕是一个故障检测到,
相应的断层进入创造,然后写信给
该javaspaces .租赁下榻在javaspaces为
入职是新的,由一个全球性续期经理
服务.任何故障入境,应该留在javaspaces
直到故障处理程序需时出来,并处理故障
即使它们的创造者时坠毁.