J2EE Application Deployment Framework. (Author: Atul Singh Chauhan) June 12, 2007
|
|
- Madlyn Day
- 6 years ago
- Views:
Transcription
1 WHITE PAPER J2EE Application Deployment Framework (Author: Atul Singh Chauhan) June 12, 2007 Copyright 2007 and HCL proprietary material. All rights reserved. No part of this document may be reproduced, reused, modified or distributed, in whole or in parts, in any form by any means without prior written authorization of HCL. The information provided in this document is intended for the sole use of the recipient and not for any commercial purpose. All the information provided is on AS IS" basis and without warranties of any kind either express or implied or to any derived results obtained by the recipient from the use of the information in the document. HCL does not guarantee the sequence, accuracy or completeness of the information and will not be liable in any way to the recipient for any delays, inaccuracies, errors in, or omissions of, any of the information or in the transmission thereof, or for any damages what so ever arising there from.
2 Table of Contents 1. Abstract 3 2. Introduction Current Approaches Short Coming of Current Approaches 4 3. Enabler Technology Overview of J2EE Deployment API Phases in a Deployment Process Configuring Applications for Deployment using J2EE Deployment AP Deployment Process in J2EE Deployment API 7 4. Technical Solution Generic Container Deployment Framework 8 5. Limitations Conclusion 12
3 1. Abstract The primary advantage of J2EE based products/applications is of portability across different application servers that gives flexibility to choose between application-server for production deployment of a particular application/product based on differentiating feature of a specifc applicationserver. However the challenge faced by most of the these J2EE application/product providers is to 1)automate the deployment process for various Application- Servers 2)Make the deployment process transparent of application-server specific nonstandard deployment mechanism. This paper proposes a Generic container deployment framework for automating and making the deployment process of a given J2EE application/product smooth, easily maintainable and transparent of application-server. The proposed framework is based on the J2EE Deployment API (JSR88) part of J2EE specifications since J2EE1.4 and introduces a new concept of Container deployment descriptor which is used by the framework utility for deploying the application/product across different application-servers. The framework also provides mechanism to automatically generate the Container deployment descriptor. The paper also discusses the limitations of the proposed framework and the complementing technologies like JSR Introduction In recent times J2EE-standard compliant application development has gained lot of popularity and momentum, and captured major share among the present internet/intranet application space. These applications are developed independently purely based on J2EE standards and are deployable on any of the specific vendor s Application server provided that application server is compliant to J2EE container specifications. Following figure describes a typical Development Life-cycle of a J2EE application: This paper focuses on the deployment of a standard J2EE application/component archive file to a J2EE compliant Application Server/container provided by different vendors. During the deployment phase of an application s life cycle, the application or the archive is installed on the target J2EE Application server/container and then is configured and integrated into the existing infrastructure/services of that application server. Typically the deployer of the J2EE application server is responsible for configuring and installing the J2EE application for the specific target Application Server and this where additional manual/development effort is involved which is not standard and varies from Application Server vendor to vendor. Creation Enterprise components created by component provider or developer J2EE Components Assembly Assembled into a standard portable archive by application assembler Deployment Deploy to target J2EE Container (Application Server) by applicationdeployer Enterprise Components J2EE Standard Archive Deploy J2EE Compliant Application Server/Container Fig: Development Life Cycle of J2EE Application
4 2.1. Current Approaches Primarily there are three approaches followed for deployment of J2EE Applications/components to the target Application Servers as follows: 1. Most of the Application server vendors such as Weblogic and Websphere provide a proprietary UI based tool for configuring and deploying J2EE applications/components, the end user or the deployer make use of this tool and manually configure and deploy the J2EE components onto the target Application server. 2. Some of the application server vendors such as Websphere also provide a custom scripting environment for deployment and the end-user can make use of this environment to create custom scripts for automating the deployment process. 3. Few of the application server have neither of the above two provisions, essentially because the deployment process is quite simplified requiring minimum configurations and whatever configurations are required they can be done directly into a XML configuration file, a typical example where this is applicable is Jboss Short Coming of Current Approaches The J2EE specification prior to 1.4 did not focus on imposing any standards for deployment and it was left open to the vendors to provide this support, because of which every vendor has a proprietary mechanism for deploying J2EE applications/components. Though deployment process of any Application server is not a very time consuming and complex process, still it requires some amount effort and knowledge of the proprietary deployment mechanism. The J2EE Applications/components can be broadly divided into two categories 1) Custom J2EE applications 2) J2EE Applications products. The short coming or challenges faced with current deployment approaches for the above two categories can be summarized as follows: - It is mostly a manual procedure unless the vendor provides a scripting environment and custom scripts created for deployment using those. - Familiarity with the vendor specific tool or any other deployment mechanism provided by the vendor. - Learning proprietary features such as scripting environment, in case provided by the vendor and automation is required - In case scripting environment is not provided by the vendor of target Application server and repeated or multiple deployments are required, then manual steps are to be repeated. - The most important and significant challenge is specifically for vendors providing J2EE Application Products which are supposed to be compatible with all J2EE compliant Application Server, since there cannot be a standard mechanism for deploying their products on these Application Server and scripts or manual steps are to be provided by these vendors for each of the supported Application server.
5 The cost of portability and standardization of application is paid in terms of proprietary and manual steps for deployment of that application and this is an overhead and needs to be eliminated or minimized. 3. Enabler Technology Before getting into the actual solution proposed for the challenges faced in the currently followed J2EE application deployment approaches, it is worth discussing here the core technology on which the solution is based. Considering the standardization requirement for deployment of J2EE application/components J2EE expert committee started working for a specification viz. JSR88 or J2EE deployment API and in J2EE1.4, this was made mandatory for all compliant Application Servers to provide required support for it 3.1. Overview of J2EE Deployment API The Deployment specification architecture defines the contracts that enable tools from multiple providers to configure and deploy applications on any J2EE platform product. The contracts define a uniform model between tools and J2EE platform products for application deployment configuration and deployment. The Deployment architecture makes it easier to deploy applications, deployers do not have to learn all the features of many different J2EE deployment tools in order to deploy an application on many different J2EE platform products. The Deployment architecture defines implementation requirements for both tools and J2EE platform products. The primary responsibilities of a Tool are: a) To access the J2EE application archive. b) To display for editing the deployment configuration information retrieved from the J2EE platform product. The J2EE platform product s primary responsibilities are to: a) Generate the product-specific deployment configuration information. b) To deploy the application. The API provided by the deployment specification describes: a) A minimum set of facilities(plug-in), that all J2EE Platform Product Providers must provide to Deployment Tool Providers so that portable J2EE applications can be deployed to the Product Provider s platform b) A minimum set of facilities that all Tool Providers must provide in order to interact with the Product Provider s plug-in Phases in a Deployment Process Any deployer tool would consist of 2 parts: a) Configuration b) Deployment The J2EE Deployment API standard differentiates between a configuration session and deployment. They are distinguished as follows: a) Application Configuration involves: Generation of vendor specific descriptors which, go into a Deployment Plan. b) Deployment involves: Distribute, Start, Stop, Redeploy, and Undeploy an Application.
6 3.3. Configuring Applications for Deployment using J2EE Deployment API The term configuration refers to the process of preparing an application or deployable resource for deployment to an Application Server. Types of Configuration Information The primary configuration information for an application falls into two distinct but related categories: a) J2EE Configuration b) App Server-specific Configuration The mapping between standard J2EE Configuration descriptors and App serverspecific Configuration descriptors is m a n a g e d v i a D D B e a n s a n d DConfigBeans object instances, which are described next. DDBeans - D D B e a n s a r e d e s c r i b e d b y t h e javax.enterprise.deploy.model package. These objects provide a generic interface to elements in standard J2EE deployment descriptors. -? The DDBean representation of a descriptor is a tree of DDBeans, with a specialized DDBean called DDBeanRoot, at the root of the tree. - DDBeans provide accessors for the element name, id attribute, root, and text of the descriptor element they represent. -? The DDBeans for an application are populated by the model plug-in, the tool p r o v i d e r i m p l e m e n t a t i o n o f javax.enterprise.deploy. model. -? A deployable module (such as WAR module, EJB module or EAR application) is r e p r e s e n t e d b y t h e javax.enterprise.deploy.model.deployable Object interface. - J2EE descriptor properties are represented by one or more DDBean objects that reside beneath the DDBeanRoot. DDBean components provide standard getter methods to access individual deployment descriptor properties, values, and nested descriptor elements. DConfigBeans -? DConfigBeans (config beans) are the objects used to convey server configuration requirements to a deployer tool, and are also the primary source of information used to create deployment plans.config beans are Java Beans and can be introspected for their properties. They also provide basic property editing capabilities. - DConfigBeans are created from information in embedded server descriptors, deployment plans, and input from a deployer tool. A DConfigBean is potentially created for every server descriptor element that is associated with a dependency of the application. Descriptors are entities that describe resources that are available to the application,
7 represented by a JNDI name provided by the server. - DConfigBean implementation is provided by the platform product provider (e.g. the App server provider). Deployment Configuration -? A deployment plan contains the environmental configuration for an application, referred to as its front-end configuration, which is persisted by storing externally. - The structure of deployment plan is App Server Specific. - The server specific deployment configuration for an application is encapsulated in the javax.enterprise.deploy.spi.deploymentconfi guration interface. - A DeploymentConfiguration can also be viewed as the object representation of a deployment plan. 3.4.Deployment Process in J2EE Deployment API The deployment Process involves following: a) Obtaining a Deployment Manager A deployment manager provides an interface to the Application Server deployment infrastructure. To initialize a deployment session in a tool, we create a new deployment manager. b) Application Distribution The distribution of new applications results in the application archive and the plan being staged on the selected targets/instances, and the application being configured into the domain. c) Application Start The start operation would start the applications distributed on the target servers, as represented by the TargetModuleID. 4. Technical Solution J2EE deployment specification introduces standardization for deployment with respect to contract between Application Servers and deployment Tool, however it still does not directly resolves all the challenges associated with currently followed deployment approaches, consider the following: - It only decouples the Deployment Tool from a Application Server and enables tool vendors to develop standard application server independent deployment tools - The standard deployment tool would still require human intervention since application server specific configuration (DConfigBean) is to be dynamically retrieved by the tool and provided to user based upon which user provides appropriate configuration information - Automation of deployment is possible for specific J2EE application by developing a custom deployment utility, however if there are changes in the configuration requirement of the J2EE application then the code of the utility also needs to be modified resulting in maintenance overhead of the utility. - In case an automated deployment service is to be developed for a particular J2EE Application/Product then it has to be developed for all the supported Application servers which add to maintenance overhead.
8 Although J2EE Deployment architecture does not solves the problem entirely, nevertheless it is a definitely an enabler technology which can be exploited and extended to achieve the desired objective of simplified automation of the deployment process of given J2EE based Application/Product. This paper introduces the concept of Generic Container Deployment Framework based upon the J2EE Deployment Specification and is described below: 4.1. Generic Container Deployment Framework The objective of this framework is to automate the Deployment process and eliminate/minimize the learning overhead of using Vendor specific deployment mechanism. Following are some of the key aspects on basis of which the framework is designed: - A typical J2EE Application Deployment requires to perform two things first is to configure the Application for the target Application (resulting in creation of Application server specific deployment plan) and second is to actually deploy it on the t a r g e t ( i n v o l v i n g distribute/start/stop/redeploy), however since automation of the second aspect is simple and straightforward using the J2EE deployment API therefore this framework focuses more on the first aspect which is more challenging. - This framework is built upon the concept of J2EE deployment API, where (as we have already discussed) there is a notion of DDBean and DConfigBean, DDBean corresponds to the standard configuration elements in a typical J2EE deployment descriptor and DConfigBean corresponds to the associated Application Server specific configuration details for that DDBean. - Now since DDBean and DConfigBean are simple stateful objects (POJOs) representing the standard J2EE deployment descriptor element and corresponding Application Server specific Configuration element details, therefore their states can be serialized and stored externally and later on instantiated when required. - Each DDBean or DConfigBean objects have set of attributes where each of them can either have a simple string value or their value can actually be another DDBean or DConfigBean, therefore for storing/representing their state externally XML is the most appropriate format. - The elements of standard J2EE deployment descriptors or in other words types of DDBean are predefined and hence the corresponding Application Server specific Configuration elements or in other words types of DConfigBeans for each of the Application Server, is also predefined. - During deployment of J2EE Application on target Application server broadly four actions can be performed : 1. CreateDeploymentPlan 2. Distribute 3. DistributeAndStart 4. Redeploy
9 Basic Architecture Taking into consideration the above aspects a simplified Generic Container Deployment Framework is depicted in the figure below and describe subsequently. Container Deployment Descriptor (CDD) XML file which is used by this framework for storing the application configurations of the specific J2EE Application to be deployed on the target Application Server. - The structure of this XML file is predefined (Schema/Dtd predefined) based on the existing standard DDBeans types and their Container Deployment Descriptor Input Generic Container Deployer (command-line utility) J2EE Deployment API (Tool Implementation) J2EE Deployment API Contract J2EE Deployment API (Server Implementation) J2EE1.4 Compliant Application Server of any Vendor Fig: Generic Container Deployment Framework corresponding DConfigBean types for all the Compliant J2EE Application Servers.- - The XML file or the Container Deployment Descriptor only stores the configuration details of DDBeans and their attributes which needs to be configured, for rest it assumes default values as present in the J2EE deployment descriptor for the Application archive being deployed. - XML file or the CDD also captures the relationship between a given DDBean detail/state and its corresponding DConfigBean detail/state. - The CDD also stores information for Deployment Actions to be performed during deployment out of the possible four viz. C r e a tedeploymentplan, D i s tribute, DistributeAndStart & Redeploy. - The CDD is specific to an Application Server therefore different CDDs would exist for each Application Server on which the given J2EE Application is to be deployed. Generic Container Deployer This is a command line utility which takes operation-type, the location of the CDD file and the deployment URL of the target Application Server as its argument and performs the actions specified in the CDD for the target server. The command would look something like this: c o n t a i n e r D e p l o y e r - d e p l o y f i l e C : \ c o n f i g \ s a m p l e C D D. x m l u r l deployer:weblogic:localhost:7001 This utility implements the Tool Provider part of
10 <ContainerDeploymentDescriptor> <CreateDeploymentPlan> <EnterpriseApplicationConfig> <DDBean> <Name>display-name</Name> <Value>sampleJ2EE-EAR</Value> </DDBean> <DConfigBean> <Name>application-name</Name> <Value>sampleJ2EE-EAR</Value> </DConfigBean> </EnterpriseApplicationConfig> <WebApplicationConfig> </WebApplicationConfig> </CreateDeploymentPlan> <DistributeAndStart/> </ContainerDeploymentDescriptor> the J2EE Deployment specifications, however unlike the normal implementations (as intended by the specification, since App-Server specific configuration attributes are retrieved dynamically) where the tool is essentially a GUI for user to interactively provide application server specific configuration information, this utility is simple and takes the consolidated inputs from a single XML file (CDD) instead, thereby eliminating any user interaction with tool. J2EE1.4 Compliant Application Server of any Vendor The Generic Container Deployment Framework i s c a p a b l e o f d e p l o y i n g J 2 E E Applications/Products on any Applications Server which is J2EE1.4 or later compliant, since from J2EE1.4 onwards support for J2EE Deployment API specifications is made mandatory for all the compliant Application Server Generation of Container Deployment Descriptor or CDD The above framework simplifies or rather provides a mechanism to automate the deployment of J2EE Applications/products across all vendor Application Server, however there is still some amount of learning/skill required to generate the target CDD XML files, and we need to minimize that aspect. Now as we are targeting to automate deployment specifically for situations where we need to do repeated or multiple deployment of the same J2EE application therefore by adding overhead of doing a manual deployment just for the first time we can achieve our objective of automating all the subsequent deployment of the same application. The details on how the framework achieves this follows: - Considering the fact that there are quite a few open-source GUI tools based on standard J2EE Deployment specification, we exploit them instead re-inventing the wheel, and essentially enhance them by developing a Generic Container Deployment Framework specific Plug-in for the tool. - The Plug-in is responsible for intercepting each of the Application server specific configuration and deployment actions performed by the end user for deploying the given J2EE Application, and store that information in the CDD XML file format. - The End-user has to manually perform the Configurations and deployment actions for the first time which would generate the required CDD file automatically and is used for all the subsequent deployment of that J2EE application using the Generic
11 Container Deployer command-line utility Generation of CDD for multiple Application Servers The above mechanism takes care of generating the CDD of one target Application Server for the given J2EE Application and can be used for automating all the subsequent deployment of that application on the same target server, however in case the if the application needs to be deployed repeatedly or multiple times on different Application server (particularly required for J2EE J2EE Deployment API Based, Open-Source, GUI Tool J2EE Deployment API (Server Implementation) J2EE Deployment API Contract J2EE1.4 Compliant Application Server of any Vendor User Provides Configuration Information J2EE Deployment API (Server Implementation) Generic Container Deployment Plug-In Output Container Deployment Descriptor Fig: Generating Container Deployment Descriptor using Open-Source J2EE Deployment Tool Application products) then additional mechanism needs to be provided in the framework, same is described below. - The Framework or particularly the Generic Container Deployer utility provides a mechanism to export the CDD of a given J2EE Application for one Application Server to a CDD of the same J2EE Application for another Application Server, using a command similar to : containerdeployer -export file C : \ c o n f i g \ s a m p l e C D D. x m l t a r g e t WebSphere? - The challenge for the utility is to translate from one Application Server specific DConfigBean to another Application Server specific DConfigBean for given standard DDBean information because DConfigBeans are not standard and each Application Server will have its own DConfigBean types. However since each DConfigBean corresponds to standard DDBean and there are limited number of popular J2EE compliant Application Servers, therefore the frameworks provides a repository of all the DConfigBean type definition for each popular Application Server in individual XML files. - The individual DConfigBean type definition files also stores the relationship with corresponding standard DDBean, and during the export operation the utility read/refers to this information to translate the DConfigBean type information for target Application Server and the value of individual DConfigBean attributes are picked up from the corresponding DConfigBean attribute of the source CDD
12 5. Limitations - For creating the DConfigBean type definition repository there is a dependency on the Application server vendor to make this information public and for Application Server who have not made this information public (or is not easily determined), cannot be Existing Container Deployment Descriptor Input Generic Container Deployer (commandline utility) Output Target Container Deployment Descriptor Reads Repository of every compliant App. Server specific DConfigBeans and their attributes Fig: Generating CDD for target Application server from CDD of existing (different) Application Server supported for the export feature of this framework - The framework does simplifies the deployment mechanism of J2EE Applications on different vendor Application servers however for practically installing a J2EE application on Target Application Server from scratch still requires some amount Application server specific steps particularly for creating platform services such as JDBC Datasource and connection pools, although J2EE expert committee has come-out with JSR77 which standardizes the management of these services but their creation is still Application Server specific 6. Conclusion Generic Container Deployment Framework provides, particularly ISVs (having J2EE based Products) a simple & transparent deployment user-experience of their product on different applications servers. It minimizes the learning curve required by end-customer of their product with respect to applicationserver specific deployment process. For ISV it s also a costsaving specially by reducing the overhead of maintaining Application-Server specific automated deployment scripts for all the supported Application-Server. For More Information contact Asvin Ramesh HCL Technologies, America Inc. 330 Potrero Avenue, Sunnyvale, CA United States Phone Fax Mobile Hello there. I am from HCL Technologies. We work behind the scenes, helping our customers to shift paradigms and start revolutions. We use digital engineering to build superhuman capabilities. We make sure that the rate of progress far exceeds the price. And right now, 45,000 of us bright sparks are busy developing solutions for 500 customers in 17 countries across the world.
BEAWebLogic. Server. Programming WebLogic Deployment
BEAWebLogic Server Programming WebLogic Deployment Version 10.0 Revised: March 30, 2007 Contents 1. Introduction and Roadmap Document Scope and Audience............................................. 1-1
More informationOracle Fusion Middleware
Oracle Fusion Middleware Programming Deployment for Oracle WebLogic Server 11g Release 1 (10.3.6) E13703-05 November 2011 This document describes the WebLogic Deployment API and performing deployment operations
More informationIn the most general sense, a server is a program that provides information
d524720 Ch01.qxd 5/20/03 8:37 AM Page 9 Chapter 1 Introducing Application Servers In This Chapter Understanding the role of application servers Meeting the J2EE family of technologies Outlining the major
More informationMigration to Service Oriented Architecture Using Web Services Whitepaper
WHITE PAPER Migration to Service Oriented Architecture Using Web Services Whitepaper Copyright 2004-2006, HCL Technologies Limited All Rights Reserved. cross platform GUI for web services Table of Contents
More informationChapter 6 Enterprise Java Beans
Chapter 6 Enterprise Java Beans Overview of the EJB Architecture and J2EE platform The new specification of Java EJB 2.1 was released by Sun Microsystems Inc. in 2002. The EJB technology is widely used
More informationComponent-based Architecture Buy, don t build Fred Broks
Component-based Architecture Buy, don t build Fred Broks 1. Why use components?... 2 2. What are software components?... 3 3. Component-based Systems: A Reality!! [SEI reference]... 4 4. Major elements
More informationChapter 2 Introduction
Chapter 2 Introduction PegaRULES Process Commander applications are designed to complement other systems and technologies that you already have in place for doing work. The Process Commander integration
More informationDeccansoft Software Services. J2EE Syllabus
Overview: Java is a language and J2EE is a platform which implements java language. J2EE standard for Java 2 Enterprise Edition. Core Java and advanced java are the standard editions of java whereas J2EE
More information(9A05803) WEB SERVICES (ELECTIVE - III)
1 UNIT III (9A05803) WEB SERVICES (ELECTIVE - III) Web services Architecture: web services architecture and its characteristics, core building blocks of web services, standards and technologies available
More informationJ2EE Interview Questions
1) What is J2EE? J2EE Interview Questions J2EE is an environment for developing and deploying enterprise applications. The J2EE platform consists of a set of services, application programming interfaces
More informationIntroduction. Enterprise Java Instructor: Please introduce yourself Name Experience in Java Enterprise Edition Goals you hope to achieve
Enterprise Java Introduction Enterprise Java Instructor: Please introduce yourself Name Experience in Java Enterprise Edition Goals you hope to achieve Course Description This course focuses on developing
More informationBuilding the Enterprise
Building the Enterprise The Tools of Java Enterprise Edition 2003-2007 DevelopIntelligence LLC Presentation Topics In this presentation, we will discuss: Overview of Java EE Java EE Platform Java EE Development
More information~ Ian Hunneybell: CBSD Revision Notes (07/06/2006) ~
1 Component: Szyperski s definition of a component: A software component is a unit of composition with contractually specified interfaces and explicit context dependencies only. A software component can
More informationComparative Analysis of EJB3 and Spring Framework
Comparative Analysis of EJB3 and Spring Framework Janis Graudins, Larissa Zaitseva Abstract: The paper describes main facilities of EJB3 and Spring Framework as well as the results of their comparative
More informationNetBeans IDE Field Guide
NetBeans IDE Field Guide Copyright 2005 Sun Microsystems, Inc. All rights reserved. Table of Contents Extending Web Applications with Business Logic: Introducing EJB Components...1 EJB Project type Wizards...2
More informationEnterprise Java and Rational Rose -- Part I
Enterprise Java and Rational Rose -- Part I by Khawar Ahmed Technical Marketing Engineer Rational Software Loïc Julien Software Engineer Rational Software "We believe that the Enterprise JavaBeans component
More informationIBM Operational Decision Manager Version 8 Release 5. Configuring Operational Decision Manager on WebLogic
IBM Operational Decision Manager Version 8 Release 5 Configuring Operational Decision Manager on WebLogic Note Before using this information and the product it supports, read the information in Notices
More informationBEAWebLogic. Server. Deploying Applications to WebLogic Server
BEAWebLogic Server Deploying Applications to WebLogic Server Version 9.2 Revised: August 10, 2006 Copyright Copyright 1995-2006 BEA Systems, Inc. All Rights Reserved. Restricted Rights Legend This software
More informationIBM Rational Application Developer for WebSphere Software, Version 7.0
Visual application development for J2EE, Web, Web services and portal applications IBM Rational Application Developer for WebSphere Software, Version 7.0 Enables installation of only the features you need
More informationWebSphere 4.0 General Introduction
IBM WebSphere Application Server V4.0 WebSphere 4.0 General Introduction Page 8 of 401 Page 1 of 11 Agenda Market Themes J2EE and Open Standards Evolution of WebSphere Application Server WebSphere 4.0
More informationWeek 2 Unit 3: Creating a JDBC Application. January, 2015
Week 2 Unit 3: Creating a JDBC Application January, 2015 JDBC Overview Java Database Connectivity (JDBC) Java-based data access technology Defines how a client can connect, query, and update data in a
More informationCocoBase Delivers TOP TEN Enterprise Persistence Features For JPA Development! CocoBase Pure POJO
CocoBase Pure POJO Product Information V5 CocoBase Delivers TOP TEN Enterprise Persistence Features For JPA Development! CocoBase Provides A Complete Enterprise Solution For JPA Based Development. CocoBase
More informationUsing JNDI from J2EE components
Using JNDI from J2EE components Stand-alone Java program have to specify the location of the naming server when using JNDI private static InitialContext createinitialcontext() throws NamingException {
More informationEnterprise JavaBeans (I) K.P. Chow University of Hong Kong
Enterprise JavaBeans (I) K.P. Chow University of Hong Kong JavaBeans Components are self contained, reusable software units that can be visually composed into composite components using visual builder
More informationSupports 1-1, 1-many, and many to many relationships between objects
Author: Bill Ennis TOPLink provides container-managed persistence for BEA Weblogic. It has been available for Weblogic's application server since Weblogic version 4.5.1 released in December, 1999. TOPLink
More informationWeb Design and Applications
Web Design and Applications JEE - Session Beans Gheorghe Aurel Pacurar JEE - Session Beans What is a session bean? A session bean is the enterprise bean that directly interact with the user and contains
More informationEllipse Web Services Overview
Ellipse Web Services Overview Ellipse Web Services Overview Contents Ellipse Web Services Overview 2 Commercial In Confidence 3 Introduction 4 Purpose 4 Scope 4 References 4 Definitions 4 Background 5
More informationTOPLink for WebLogic. Whitepaper. The Challenge: The Solution:
Whitepaper The Challenge: Enterprise JavaBeans (EJB) represents a new standard in enterprise computing: a component-based architecture for developing and deploying distributed object-oriented applications
More information"Web Age Speaks!" Webinar Series
"Web Age Speaks!" Webinar Series Java EE Patterns Revisited WebAgeSolutions.com 1 Introduction Bibhas Bhattacharya CTO bibhas@webagesolutions.com Web Age Solutions Premier provider of Java & Java EE training
More informationLightweight J2EE Framework
Lightweight J2EE Framework Struts, spring, hibernate Software System Design Zhu Hongjun Session 4: Hibernate DAO Refresher in Enterprise Application Architectures Traditional Persistence and Hibernate
More informationOracle Fusion Middleware
Oracle Fusion Middleware Deploying Applications to Oracle WebLogic Server 11g Release 1 (10.3.1) E13702-01 May 2009 This document describes deploying Java EE applications or application modules to WebLogic
More informationJava TM 2 Enterprise Edition Deployment API Specification, Version 1.1
Java TM 2 Enterprise Edition Deployment API Specification, Version 1.1 Rebecca Searls Part No. 8xx-xxxx-xx August 17 2002, Version 1.1 ii Final Release iii Java 2 Platform, Enterprise Edition Deployment
More informationJ2EE - Version: 25. Developing Enterprise Applications with J2EE Enterprise Technologies
J2EE - Version: 25 Developing Enterprise Applications with J2EE Enterprise Technologies Developing Enterprise Applications with J2EE Enterprise Technologies J2EE - Version: 25 5 days Course Description:
More informationOverview p. 1 Server-side Component Architectures p. 3 The Need for a Server-Side Component Architecture p. 4 Server-Side Component Architecture
Preface p. xix About the Author p. xxii Introduction p. xxiii Overview p. 1 Server-side Component Architectures p. 3 The Need for a Server-Side Component Architecture p. 4 Server-Side Component Architecture
More informationOpen Source. in the Corporate World. JBoss. Application Server. State of the Art: Aaron Mulder
Open Source in the Corporate World JBoss Application Server State of the Art: 2005 Aaron Mulder Agenda JBoss Basics J2EE Features Caching & Clustering Non J2EE Applications Compared to the Competition
More informationSUN Enterprise Development with iplanet Application Server
SUN 310-540 Enterprise Development with iplanet Application Server 6.0 http://killexams.com/exam-detail/310-540 QUESTION: 96 You just created a new J2EE application (EAR) file using iasdt. How do you begin
More informationB. Assets are shared-by-copy by default; convert the library into *.jar and configure it as a shared library on the server runtime.
Volume A~B: 114 Questions Volume A 1. Which component type must an integration solution developer define for a non-sca component such as a Servlet that invokes a service component interface? A. Export
More informationBEAWebLogic. Portal. Overview
BEAWebLogic Portal Overview Version 10.2 Revised: February 2008 Contents About the BEA WebLogic Portal Documentation Introduction to WebLogic Portal Portal Concepts.........................................................2-2
More informationComponent-Based Software Engineering. ECE493-Topic 5 Winter Lecture 26 Java Enterprise (Part D)
Component-Based Software Engineering ECE493-Topic 5 Winter 2007 Lecture 26 Java Enterprise (Part D) Ladan Tahvildari Assistant Professor Dept. of Elect. & Comp. Eng. University of Waterloo J2EE Application
More informationObject-relational mapping EJB and Hibernate
T A R T U Ü L I K O O L MATEMAATIKA-INFORMAATIKATEADUSKOND Arvutiteaduse instituut Infotehnoloogia eriala Aleksandr Tkatšenko Object-relational mapping EJB and Hibernate Referaat aines Tarkvaratehnika
More informationIntroduction to componentbased software development
Introduction to componentbased software development Nick Duan 8/31/09 1 Overview What is a component? A brief history of component software What constitute the component technology? Components/Containers/Platforms
More informationAppendix A - Glossary(of OO software term s)
Appendix A - Glossary(of OO software term s) Abstract Class A class that does not supply an implementation for its entire interface, and so consequently, cannot be instantiated. ActiveX Microsoft s component
More informationEnterprise Java Security Fundamentals
Pistoia_ch03.fm Page 55 Tuesday, January 6, 2004 1:56 PM CHAPTER3 Enterprise Java Security Fundamentals THE J2EE platform has achieved remarkable success in meeting enterprise needs, resulting in its widespread
More informationChapter 2 WEBLOGIC SERVER DOMAINS. SYS-ED/ Computer Education Techniques, Inc.
Chapter 2 WEBLOGIC SERVER DOMAINS SYS-ED/ Computer Education Techniques, Inc. Objectives You will learn: Domain - concept and implementation. Content of a domain. Common domain types. Production versus
More informationX-S Framework Leveraging XML on Servlet Technology
X-S Framework Leveraging XML on Servlet Technology Rajesh Kumar R Abstract This paper talks about a XML based web application framework that is based on Java Servlet Technology. This framework leverages
More informationEnterprise Java and Rational Rose - Part II
Enterprise Java and Rational Rose - Part II by Khawar Ahmed Technical Marketing Engineer Rational Software Loïc Julien Software Engineer Rational Software This is the second installment of a twopart series
More informationDeveloping Java TM 2 Platform, Enterprise Edition (J2EE TM ) Compatible Applications Roles-based Training for Rapid Implementation
Developing Java TM 2 Platform, Enterprise Edition (J2EE TM ) Compatible Applications Roles-based Training for Rapid Implementation By the Sun Educational Services Java Technology Team January, 2001 Copyright
More informationApplication Server Evaluation Method
Application Evaluation Method Janis Graudins, Larissa Zaitseva Abstract: The paper describes an server evaluation and selection for software systems implementation using client-server technology. The multi
More informationComponents and Application Frameworks
CHAPTER 1 Components and Application Frameworks 1.1 INTRODUCTION Welcome, I would like to introduce myself, and discuss the explorations that I would like to take you on in this book. I am a software developer,
More informationVision of J2EE. Why J2EE? Need for. J2EE Suite. J2EE Based Distributed Application Architecture Overview. Umair Javed 1
Umair Javed 2004 J2EE Based Distributed Application Architecture Overview Lecture - 2 Distributed Software Systems Development Why J2EE? Vision of J2EE An open standard Umbrella for anything Java-related
More informationOutline. Project Goal. Overview of J2EE. J2EE Architecture. J2EE Container. San H. Aung 26 September, 2003
Outline Web-based Distributed EJB BugsTracker www.cs.rit.edu/~sha5239/msproject San H. Aung 26 September, 2003 Project Goal Overview of J2EE Overview of EJBs and its construct Overview of Struts Framework
More informationPortal Application Deployment Scripting
Portal Application Deployment Scripting Graham Harper, IBM ISSL Senior Application Architect Contents Deployment scripting in context What is a portal application? Portal application components Applying
More informationApplication Servers in E-Commerce Applications
Application Servers in E-Commerce Applications Péter Mileff 1, Károly Nehéz 2 1 PhD student, 2 PhD, Department of Information Engineering, University of Miskolc Abstract Nowadays there is a growing demand
More informationWriting Portable Applications for J2EE. Pete Heist Compoze Software, Inc.
Writing Portable Applications for J2EE Pete Heist Compoze Software, Inc. Overview Compoze Business Aspects of Portability J2EE Compatibility Test Suite Abstracting out Vendor Specific Code Bootstrapping
More informationIntroduction to Web Application Development Using JEE, Frameworks, Web Services and AJAX
Introduction to Web Application Development Using JEE, Frameworks, Web Services and AJAX Duration: 5 Days US Price: $2795 UK Price: 1,995 *Prices are subject to VAT CA Price: CDN$3,275 *Prices are subject
More informationAn Oracle Technical White Paper September Oracle VM Templates for PeopleSoft
An Oracle Technical White Paper September 2010 Oracle VM Templates for PeopleSoft 1 Disclaimer The following is intended to outline our general product direction. It is intended for information purposes
More informationOracle Application Development Framework Overview
An Oracle White Paper July 2009 Oracle Application Development Framework Overview Introduction... 1 Oracle ADF Making Java EE Development Simpler... 2 THE ORACLE ADF ARCHITECTURE... 3 The Business Services
More informationServices Oriented Architecture and the Enterprise Services Bus
IBM Software Group Services Oriented Architecture and the Enterprise Services Bus The next step to an on demand business Geoff Hambrick Distinguished Engineer, ISSW Enablement Team ghambric@us.ibm.com
More informationOracle WebLogic Server 12c: Administration I
Oracle WebLogic Server 12c: Administration I Duration 5 Days What you will learn This Oracle WebLogic Server 12c: Administration I training teaches you how to install and configure Oracle WebLogic Server
More informationInstalling and Configuring the Runtime Processes 2
2 Installing and Configuring the Runtime Processes 2 The first step in deploying a J2EE application is setting up the production environment on the appropriate hosts. This involves installing all necessary
More informationComponent-Based Platform for a Virtual University Information System
Component-Based Platform for a Virtual University Information System Dr. IVAN GANCHEV, Dr. MAIRTIN O DROMA, FERGAL McDONNELL Department of Electronics and Computer Engineering University of Limerick National
More informationJava EE Application Assembly & Deployment Packaging Applications, Java EE modules. Model View Controller (MVC)2 Architecture & Packaging EJB Module
Java Platform, Enterprise Edition 5 (Java EE 5) Core Java EE Java EE 5 Platform Overview Java EE Platform Distributed Multi tiered Applications Java EE Web & Business Components Java EE Containers services
More informationChapter 1 GETTING STARTED. SYS-ED/ Computer Education Techniques, Inc.
Chapter 1 GETTING STARTED SYS-ED/ Computer Education Techniques, Inc. Objectives You will learn: WSAD. J2EE business topologies. Workbench. Project. Workbench components. Java development tools. Java projects
More informationExperiences in the management of an EJB-based e- commerce application. Abstract
Experiences in the management of an EJB-based e- commerce application Juan I. Asensio, Víctor A. Villagrá, Jorge E. López de Vergara, Roney Pignaton, Julio J. Berrocal. Department of Telematic Systems
More informationVisual Composer Build Process
Applies to: Visual Composer for Composition Environment 7.1 Summary This paper explains how Visual Composer builds & creates its applications, and what are the dependencies and naming consideration a modeler
More informationOCS INSTALLATION GUIDE
OCS INSTALLATION GUIDE 1. Application database preparation... 2 1.1. Oracle Database 11g... 2 1.2 MySQL 5.5+... 2 2. System initialisation... 3 2.1. Application file storage... 3 2.2. Security tool installation...
More informationEnterprise JavaBeans. Layer:01. Overview
Enterprise JavaBeans Layer:01 Overview Agenda Course introduction & overview. Hardware & software configuration. Evolution of enterprise technology. J2EE framework & components. EJB framework & components.
More informationGlassFish v3.1 EJB One Pager
GlassFish v3.1 EJB One Pager (template version: 1.91) Table of Contents 1. Introduction 1.1 Project/Component Working Name 1.2 Name(s) and e-mail address of Document Author(s)/Supplier 1.3. Date of This
More informationWeb Application Architecture (based J2EE 1.4 Tutorial)
Web Application Architecture (based J2EE 1.4 Tutorial) Dr. Kanda Runapongsa (krunapon@kku.ac.th) Department of Computer Engineering Khon Kaen University 1 Agenda Web application, components and container
More informationProfitability Application Pack Installation Guide Release
Profitability Application Pack Installation Guide Release 8.0.6.1.0 October 2018 Document Versioning Version Number Revision Date Changes Done 1.0 10 September 2018 Final version released 1.1 5 October
More informationOpen Development Tool Installation Oracle FLEXCUBE Universal Banking Release
Open Development Tool Installation Oracle FLEXCUBE Universal Banking Release 12.4.0.0.0 Table of Contents 1. OPEN DEVELOPMENT TOOL INSTALLATION... 1-1 1.1 INTRODUCTION... 1-1 1.2 INSTALLING OPEN DEVELOPMENT
More informationHibernate Interview Questions
Hibernate Interview Questions 1. What is Hibernate? Hibernate is a powerful, high performance object/relational persistence and query service. This lets the users to develop persistent classes following
More informationCOURSE 9 DESIGN PATTERNS
COURSE 9 DESIGN PATTERNS CONTENT Applications split on levels J2EE Design Patterns APPLICATION SERVERS In the 90 s, systems should be client-server Today, enterprise applications use the multi-tier model
More informationEnterprise JavaBeans. Layer 05: Deployment
Enterprise JavaBeans Layer 05: Deployment Agenda Discuss the deployment descriptor including its structure and capabilities. Discuss JNDI as it pertains to EJB. Last Revised: 10/2/2001 Copyright (C) 2001
More informationORACLE IDENTITY MANAGER SIZING GUIDE. An Oracle White Paper March 2007
ORACLE IDENTITY MANAGER SIZING GUIDE An Oracle White Paper March 2007 Note The following is intended to provide consideration guidelines for sizing Oracle Identity Manager. It is intended for information
More informationImplementing Business Objects in CAF and Developing Web Dynpro Application
Implementing Business Objects in CAF and Developing Web Dynpro Application Applies to: SAP Net Weaver CE 7.1.1 EHP1 (SP0, SP1, SP2 sand SP3). For more information, visit the Web Dynpro Java homepage. Summary
More informationOracle 10g: Build J2EE Applications
Oracle University Contact Us: (09) 5494 1551 Oracle 10g: Build J2EE Applications Duration: 5 Days What you will learn Leading companies are tackling the complexity of their application and IT environments
More informationJ2EE Development. Course Detail: Audience. Duration. Course Abstract. Course Objectives. Course Topics. Class Format.
J2EE Development Detail: Audience www.peaksolutions.com/ittraining Java developers, web page designers and other professionals that will be designing, developing and implementing web applications using
More informationJBoss SOAP Web Services User Guide. Version: M5
JBoss SOAP Web Services User Guide Version: 3.3.0.M5 1. JBoss SOAP Web Services Runtime and Tools support Overview... 1 1.1. Key Features of JBossWS... 1 2. Creating a Simple Web Service... 3 2.1. Generation...
More informationArtix for J2EE. Version 4.2, March 2007
Artix for J2EE Version 4.2, March 2007 IONA Technologies PLC and/or its subsidiaries may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject
More informationAdobe ColdFusion 11 Enterprise Edition
Adobe ColdFusion 11 Enterprise Edition Version Comparison Adobe ColdFusion 11 Enterprise Edition Adobe ColdFusion 11 Enterprise Edition is an all-in-one application server that offers you a single platform
More informationCreating Plug-n-Play Applications by Hansdip Singh Bindra
Creating Plug-n-Play Applications by Hansdip Singh Bindra In today s day-and-age of computing solutions for businesses the concept and usage of integrating Best of Breed applications is extremely popular
More informationThe 60-Minute Guide to Development Tools for IBM Lotus Domino, IBM WebSphere Portal, and IBM Workplace Applications
The 60-Minute Guide to Development Tools for IBM Lotus Domino, IBM WebSphere Portal, and IBM Workplace Stuart Duguid Portal & Workplace Specialist TechWorks, IBM Asia-Pacific Overview / Scope The aim of
More informationITdumpsFree. Get free valid exam dumps and pass your exam test with confidence
ITdumpsFree http://www.itdumpsfree.com Get free valid exam dumps and pass your exam test with confidence Exam : 310-090 Title : Sun Certified Business Component Developer for J2EE 1.3 Vendors : SUN Version
More informationJava EE Patterns 176
Java EE Patterns 176 What are Java EE Patterns?! " A collection of Java EE based solutions to common problems! " Address reoccurring problems found in enterprise class systems! " Intended to meet quality
More informationDemonstrated Node Configuration for the Central Data Exchange Node
Demonstrated Node Configuration for the Central Data Exchange Node DRAFT May 30, 2003 Task Order No.: T0002AJM038 Contract No.: GS00T99ALD0203 Abstract The Environmental Protection Agency (EPA) selected
More informationEnterprise JavaBeans, Version 3 (EJB3) Programming
Enterprise JavaBeans, Version 3 (EJB3) Programming Description Audience This course teaches developers how to write Java Enterprise Edition (JEE) applications that use Enterprise JavaBeans, version 3.
More informationThe team that wrote this redbook
Preface p. xix The team that wrote this redbook p. xix Comments welcome p. xxiii Overview of WebSphere Application Server V3.5 p. 1 What is WebSphere Application Server? p. 1 WebSphere Application Server
More informationINSTALLATION GUIDE Online Collection Software for European Citizens' Initiatives
INSTALLATION GUIDE Online Collection Software for European Citizens' Initiatives 1. Application database preparation... 2 1.1. Oracle Database 11g... 2 1.2. MySQL 5.5+... 2 2. System initialisation...
More informationIBM WebSphere Application Server V4.0. Performance. 10/02/01 Copyright 2001 IBM Corporation WS40ST11.prz Page 248 of of 28
IBM WebSphere Application Server V4.0 Performance Page 248 of 401 1 of 28 Performance Enhancements to WebSphere V4.0 Performance Enhancement Overview Dynamic Caching of Servlets/JSPs Performance Monitoring
More informationFor Version 10.3 or Later
Java Application Server Guide For Version 10.3 or Later 2005-08-11 Apple Inc. 2003, 2005 Apple Computer, Inc. All rights reserved. No part of this publication may be reproduced, stored in a retrieval system,
More informationIBM. Developing with IBM Rational Application Developer for WebSphere Software V6
IBM 000-255 Developing with IBM Rational Application Developer for WebSphere Software V6 Download Full Version : http://killexams.com/pass4sure/exam-detail/000-255 Answer: C QUESTION: 99 A developer is
More informationAttunity Connect and BEA WebLogic (Version 8.1)
Attunity Connect and BEA WebLogic (Version 8.1) Attunity Connect and BEA WebLogic (Version 8.1) 2006 by Attunity Ltd. Due to a policy of continuous development, Attunity Ltd. reserves the right to alter,
More informationOracle Corporation
1 2012 Oracle Corporation Oracle WebLogic Server 12c: Developing Modern, Lightweight Java EE 6 Applications Will Lyons, Director of WebLogic Server Product Management Pieter Humphrey, Principal Product
More informationEJB ENTERPRISE JAVA BEANS INTRODUCTION TO ENTERPRISE JAVA BEANS, JAVA'S SERVER SIDE COMPONENT TECHNOLOGY. EJB Enterprise Java
EJB Enterprise Java EJB Beans ENTERPRISE JAVA BEANS INTRODUCTION TO ENTERPRISE JAVA BEANS, JAVA'S SERVER SIDE COMPONENT TECHNOLOGY Peter R. Egli 1/23 Contents 1. What is a bean? 2. Why EJB? 3. Evolution
More informationOracle Banking APIs. Part No. E Third Party Simulation Guide Release April 2018
Oracle Banking APIs Third Party Simulation Guide Release 18.1.0.0.0 Part No. E94092-01 April 2018 Third Party Simulation Guide April 2018 Oracle Financial Services Software Limited Oracle Park Off Western
More informationTIBCO ActiveMatrix BusinessWorks Plug-in for Microsoft SharePoint Installation
TIBCO ActiveMatrix BusinessWorks Plug-in for Microsoft SharePoint Installation Software Release 6.1 January 2016 Two-Second Advantage 2 Important Information SOME TIBCO SOFTWARE EMBEDS OR BUNDLES OTHER
More informationIncremental improvements for the Spring Framework
Incremental improvements for the Spring Framework I am working as an architect for a middle-sized software development company, where we have been actively using J2EE extension frameworks for the last
More informationChapter 1 GETTING STARTED. SYS-ED/ Computer Education Techniques, Inc.
Chapter 1 GETTING STARTED SYS-ED/ Computer Education Techniques, Inc. Objectives You will learn: The IDE: Integrated Development Environment. MVC: Model-View-Controller Architecture. BC4J: Business Components
More informationWAS: WebSphere Appl Server Admin Rel 6
In order to learn which questions have been answered correctly: 1. Print these pages. 2. Answer the questions. 3. Send this assessment with the answers via: a. FAX to (212) 967-3498. Or b. Mail the answers
More information