算机科学与技术毕业论文中英文资料外文翻译文献(编辑修改稿)

算机科学与技术毕业论文中英文资料外文翻译文献(编辑修改稿)内容摘要：

ddress application ponent dependencies on application server services, their configuration and deployment, • provide simple but expressive abstractions to control adaptation through dynamic deployment and undeployment of ponents, • enable reuse of services and ponents to maintain efficient use of work nodes’ resources, • provide these facilities without incurring significant additional design effort on behalf of application programmers. In this paper we propose the infrastructure for automatic dynamic deployment of J2EE applications, which addresses all of the aforementioned issues. The infrastructure defines architecture description languages (ADL) for ponent and link description and assembly. The Component Description Language is used to describe application ponents and links. It provides clear separation of application ponents from system ponents. A flexible type system is used to define patibility of ponent ports and links. A declaration and expression language for configurable ponent properties allows for specification of interponent dependencies and propagation of properties between ponents. The Component (Replica) Assembly Language allows for assembly of replicas of previously defined ponents into application paths by Connecting appropriate ports via link replicas and specifying the mapping of these ponent replicas onto target application server nodes. The Component Configuration Process evaluates an application path’s correctness, identifies the dependencies of application ponents on system ponents, and configures ponent replicas for deployment. An attempt is made to match and reuse any previously deployed replicas in the new path based on their configurations. We implement the infrastructure as a part of the JBoss open source Java application server [11] and test it on several Sample J2EE applications – Java Pets tore [23], Rubies [20] and TPCWNYU [32]. The infrastructure implementation utilizes the JBoss’s extendable microkernel architecture, based on the JMX [27] specification. Componentized architecture of JBoss allows incremental service deployments depending on the needs of deployed applications. We believe that dynamic reconfiguration of application servers through dynamic deployment and undeployment of system services is essential to building a resourceefficient framework for dynamic distributed deployment of J2EE applications. The rest of the paper is anized as follows. Section 2 provides necessary background for understanding the specifics of the J2EE ponent technology which are relevant to this study. Section 3 gives a general description of the infrastructure architecture, while section 4 goes deeper in describing particularly important and interesting internal mechanisms of the infrastructure. Section 5 describes the implementation of the framework, and related work is discussed in section 6. 2 J2EE Background Introduction Component frameworks. A ponent framework is a middleware system that supports applications consisting of ponents conforming to certain standards. Application ponents are ―plugged‖ into the ponent framework, which establishes their environmental conditions and regulates the interactions between them. This is usually done through containers, ponent holders, which also provide monly required support for naming, security, transactions, and persistence. Component frameworks provide an integrated environment for ponent execution, as a result significantly reduce the effort .it takes to design, implement, deploy, and maintain applications. Current day industry ponent framework standards are represented by Object Management Group’s CORBA Component Model [18], Sun Microsystems’ Java 2 Platform Enterprise Edition (J2EE) [25] and Microsoft’s .NET [17], with J2EE being currently the most popular and widely used ponent framework in the enterprise arena. J2EE. Java 2 Platform Enterprise Edition (J2EE) [25] is a prehensive standard for developing multitier enterprise Java applications. The J2EE specification among other things defines the following: • Component programming model, • Component contracts with the hosting server, • Services that the platform provides to these ponents, • Various human roles, • Compatibility test suites and pliance testing procedures. Among the list of services that a pliant application server must provide are messaging, transactions, naming and others that can be used by the application ponents. Application developed using J2EE adhere to the classical 3Tier architectures – Presentation Tier, Business Tier, and Enterprise Information System (EIS) Tier (see Fig. 1). J2EE ponents belonging to each tier are developed adhering to the Specific J2EE standards. 1. Presentation or Web tier. This tier is actually subdivided into client and server sides. The client side hosts a web browser, applets and Java applications that municate with the server side of presentation tier or the business tier. The server side hosts Java Servlet ponents [30], Java Server Pages (JSPs) [29] and static web content. These ponents are responsible for presenting business data to the end users. The data itself is typically acquired from the business tier and sometimes directly from the Enterprise Information System tier. The server side of the presentation tier is typically accessed through HTTP(S) protocol. 2. Business or EJB tier. This tier consists of Enterprise Java Beans (EJBs) [24] that model the business logic of the enterprise application. These ponents provide persistence mechanisms an。