DOCSLIB.ORG

A Web Portal for CMS Grid Job Submission and Management

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
A Web Portal for CMS Grid Job Submission and Management 17th International Conference on Computing in High Energy and Nuclear Physics (CHEP09) IOP Publishing Journal of Physics: Conference Series 219 (2010) 072012 doi:10.1088/1742-6596/219/7/072012 A Web Portal for CMS Grid Job Submission and Management David Braun1 and Norbert Neumeister2 1 Department of Physics, Purdue University, W. Lafayette, IN 47907, USA 2 Rosen Center for Advanced Computing, Purdue University, W. Lafayette, IN 47907, USA E-mail: [email protected] Abstract. We present a Web portal for CMS Grid submission and management. The portal is built using a JBoss application server. It has a three tier architecture; presentation, business logic and data. Bean based business logic interacts with the underlying Grid infrastructure and pre-existing external applications, while the presentation layer uses AJAX to offer an intuitive, functional interface to the back-end. Application data aggregating information from the portal as well as the external applications is persisted to the server memory cache and then to a back- end database. We describe how the portal exploits standard, off-the-shelf commodity software together with existing Grid infrastructures in order to facilitate job submission and monitoring for the CMS collaboration. This paper describes the design, development, current functionality and plans for future enhancements of the portal. 1. Introduction The experiments at the Large Hadron Collider (LHC) at CERN will start producing event data when the collider begins operating in late 2009. As the moment when real LHC data will start to be collected approaches, it is important to provide to the community of LHC physicists powerful and user-friendly tools to analyse data using distributed computing resources. One way to achieve this is by providing access to these resources via scientific portals that clients, LHC physicists, will find attractive and easy to use. Grid portals can deliver complex Grid solutions to users without the need to download, install and maintain specialized software, or worrying about setting up site-specific components. The goal is to reduce the complexity of the user Grid experience and to bring the full power of the Grid to physicists engaged in LHC analysis through a standard web GUI. Currently users are exposed to different flavors of grid middle ware and the installation and maintenance of experiment specific software is still very complex for most physicists. The available Grid tools are not so user friendly at times and the Grid requires even more software and services to be installed and maintained. Moreover, currently only few platforms are supported and the handling of Grid user certificates is still a problem for many users. We have evaluated different technologies to provide a science portal in order to reduce the complexity of the user Grid experience. Because this is a missing functionality of the official tool set of the CMS collaboration, we developed a prototype of a CMS Grid submission portal and we currently provide this service to a local CMS Tier-2 community at Purdue University. The goal of the CMS Grid submission portal is to hide and integrate the complex infrastructure details that can hinder a user's ability to do science. A rich AJAX user interface c 2010 IOP Publishing Ltd 1 17th International Conference on Computing in High Energy and Nuclear Physics (CHEP09) IOP Publishing Journal of Physics: Conference Series 219 (2010) 072012 doi:10.1088/1742-6596/219/7/072012 provides users the functionality to create, submit, share and monitor Grid submissions. The Grid portal is built on J2EE [1] architecture employing enterprise technologies powered by a JBoss [2] application server. This technology has been used for many years in industry to provide enterprise class application deployments. The architecture is comprised of three tiers; presentation, business logic and data persistence. The presentation layer currently consists of a Java Server Faces (JSF) [3] web interface developed with NetBeans [4] Visual Web Page development tools. The business logic layer provides interfaces to existing Grid infrastructure such as VOMS [5], Globus [6], and CMS specific Grid submission tools. 2. Technology Integrated authentication systems and the easy integration of multiple data sources are key considerations when designing an interactive web-based Grid application. These requirements naturally led to a design where the architecture of the application is based upon J2EE components such as Java Server Faces (JSF), Java Server Pages (JSP), Servlets and Enterprise Java Beans (EJB) [7]. JBoss was used as the application server of choice because it combines both a web container and an EJB container to provide a unified platform for development. It has been industry proven to scale quite well using distributed caching technology and can be further broken in smaller components as needed to match the needs of the application [8]. State management is provided at the request, session and application levels. The life cycle management built into JBoss provides the mechanism to persist state items and control the overall rendering pipeline. Making the portal web session interactive and auto-updating the data displayed to the end user via JavaScript and AJAX was important to the use case, but made the browser to server interactions increasingly complex. The development of a complex web application meant that technology decisions for this project needed to be made in a way that allowed us to best leverage the available programming resources in the research project. In order to exponentially increase the amount of development a single professional programmer could accomplish, the NetBeans IDE was chosen to automate much of the GUI interface code generation. Of particular interest when selecting development tools was the use of graphical tools to create web pages. For this project, NetBeans was chosen as the integrated development environment and employed the visual web pages plugin, which meant we were able to generate complex AJAX interfaces with minimal JavaScript having to be hand written. Visual web pages are based on the use of JSF to supply a component based framework that is similar to the long existing tools that are used to layout Java swing user interfaces. This project was built on the Woodstock framework [9], which is the reference framework developed by Sun and the Java community. The motivation for this choice was the fact that the NetBeans visual web page development environment supported all the features in this framework. The advantage of using frameworks like this is that most of the cross browser issues are handled within the component or the life cycle management and do not have to be hand coded by the programmer. JSF is a framework that is composed of three major functions; GUI component, state management, and life cycle management. The GUI component items, such as drop down menus, include encapsulated code that specifies how the component should be rendered. Depending on the target, browser components can choose the correct JavaScript to send to the browser which eliminates the need for the typical testing of multiple browser targets. JSF employs the Expression Language (EL) [10] which allows the components to dynamically consume evaluated expressions that are used to bind component properties to state management items. Within the JSF specification state management is implemented as three distinct scopes: request, session, and application. Each scope will persist data for different periods of time ranging from page to page navigation, user sessions and global application. The lifecyle management provides support for how the component tree is restored, associated state is updated and completing the request 2 17th International Conference on Computing in High Energy and Nuclear Physics (CHEP09) IOP Publishing Journal of Physics: Conference Series 219 (2010) 072012 doi:10.1088/1742-6596/219/7/072012 with a generated response, as well as mechanisms to handle complex user interactions such as browser navigation. 3. Architecture The architecture of the CMS Grid Submission Portal is divided into three main pieces: presentation, logic and data layers. The presentation and logic layers are within a JBoss application server and the data layer is MySQL [11] and file store. Within the JBoss container, we deploy beans which wrap the CMS Remote Analysis Builder (CRAB) [12], allowing users to execute the CRAB functions they need from the portal web page. Figure. 1 shows a diagram of the chosen architecture. The presentation layer is implemented with JSF technology. The JSF servlets are managed within a JBoss managed Tomcat [13] container. The advantage of doing this is that the container is configured to support a unified security model such that all members of the architecture within the application server exist under one security domain. There are two main backing beans that the application relies upon, the application and user session bean. The application bean is used to hold application-wide state. In this case the state of the application bean is also being backed up in the lower layers. The state that is being managed at the application level is an in memory state that is required for fast response for polling queries, or static elements choice lists. The general use case of the application has three main steps: the user defines a project space, configures and loads required data, and then submits and monitors jobs using CRAB. The user's project is based on a release of CMSSW and may contain private code/libraries and configuration files. Data is extracted from the CRAB submission directory about the project and cached in a database. These actions all require that a valid proxy exists within the user's directory as an additional security measure. There are two active components within the architecture that will act upon the user's data autonomously: proxy expiration checking and project monitoring. A periodic proxy check will validate that the proxy has not expired.
Load more

Recommended publications
  • The Dzone Guide to Volume Ii
    THE D ZONE GUIDE TO MODERN JAVA VOLUME II BROUGHT TO YOU IN PARTNERSHIP WITH DZONE.COM/GUIDES DZONE’S 2016 GUIDE TO MODERN JAVA Dear Reader, TABLE OF CONTENTS 3 EXECUTIVE SUMMARY Why isn’t Java dead after more than two decades? A few guesses: Java is (still) uniquely portable, readable to 4 KEY RESEARCH FINDINGS fresh eyes, constantly improving its automatic memory management, provides good full-stack support for high- 10 THE JAVA 8 API DESIGN PRINCIPLES load web services, and enjoys a diverse and enthusiastic BY PER MINBORG community, mature toolchain, and vigorous dependency 13 PROJECT JIGSAW IS COMING ecosystem. BY NICOLAI PARLOG Java is growing with us, and we’re growing with Java. Java 18 REACTIVE MICROSERVICES: DRIVING APPLICATION 8 just expanded our programming paradigm horizons (add MODERNIZATION EFFORTS Church and Curry to Kay and Gosling) and we’re still learning BY MARKUS EISELE how to mix functional and object-oriented code. Early next 21 CHECKLIST: 7 HABITS OF SUPER PRODUCTIVE JAVA DEVELOPERS year Java 9 will add a wealth of bigger-picture upgrades. 22 THE ELEMENTS OF MODERN JAVA STYLE But Java remains vibrant for many more reasons than the BY MICHAEL TOFINETTI robustness of the language and the comprehensiveness of the platform. JVM languages keep multiplying (Kotlin went 28 12 FACTORS AND BEYOND IN JAVA GA this year!), Android keeps increasing market share, and BY PIETER HUMPHREY AND MARK HECKLER demand for Java developers (measuring by both new job 31 DIVING DEEPER INTO JAVA DEVELOPMENT posting frequency and average salary) remains high. The key to the modernization of Java is not a laundry-list of JSRs, but 34 INFOGRAPHIC: JAVA'S IMPACT ON THE MODERN WORLD rather the energy of the Java developer community at large.
    [Show full text]
  • Java Server Face
    Java Server Face From the specification 2.0 JSF sources ● JSF specification 2.0 ● JSF sun tutorials EE6 ● Core Java server face (http://horstmann.com/corejsf/) ● http://jsftutorials.net/ ● JSF Lectures from Pascal URSO (Mcf Nancy) ● JSF Lectures from François Charoy (Mcf Nancy) ● Intro à JSF : [email protected] ● JSF and ICEFaces (?? anonymous) My Source ?? Overview and motivations ● JavaServer Faces (JSF) is a user interface (UI) framework for Java web applications. It is designed to significantly ease the burden of writing and maintaining applications that run on a Java application server and render their UIs back to a target client. JSF provides ease-of-use in the following ways: ● Makes it easy to construct a UI from a set of reusable UI components ● Simplifies migration of application data to and from the UI ● Helps manage UI state across server requests ● Provides a simple model for wiring client-generated events to server-side application code ● Allows custom UI components to be easily built and re-used Solving pratical problems of the web ● Managing UI component state across request ● Supporting encapsulation of the differences in markup across different browsers and clients ● Supporting form processing (multi-page, more than one per page, and so on) ● Providing a strongly typed event model that allows the application to write server- side handlers (independent of HTTP) for client generated events ● Validating request data and providing appropriate error reporting ● Enabling type conversion when migrating markup values (Strings) to and from application data objects (which are often not Strings) ● Handling error and exceptions, and reporting errors in human-readable form back to the application user ● Handling page-to-page navigation in response to UI events and model interactions.
    [Show full text]
  • Icefaces Getting Started Guide V1.7 Iii Prerequisites
    Getting Started Guide Version 1.7 Copyright Copyright 2005-2008. ICEsoft Technologies, Inc. All rights reserved. The content in this guide is protected under copyright law even if it is not distributed with software that includes an end user license agreement. The content of this guide is furnished for informational use only, is subject to change without notice, and should not be construed as a commitment by ICEsoft Technologies, Inc. ICEsoft Technologies, Inc. assumes no responsibility or liability for any errors or inaccuracies that may appear in the informational content contained in this guide. ICEfaces is a registered trademark of ICEsoft Technologies, Inc. Sun, Sun Microsystems, the Sun logo, Solaris and Java are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and in other countries. All other trademarks mentioned herein are the property of their respective owners. ICEsoft Technologies, Inc. Suite 200, 1717 10th Street NW Calgary, Alberta, Canada T2M 4S2 Toll Free: 1-877-263-3822 (USA and Canada) Telephone: 1-403-663-3322 Fax:1-403-663-3320 For additional information, please visit the ICEfaces web site: http://www.icefaces.org ICEfaces v1.7 April 2008 About this Guide The ICEfaces® Getting Started Guide will help you quickly get started building ICEfaces applications. By reading through this guide, you will: • Gain a basic understanding of what ICEfaces is and what it can do for you. • Install ICEfaces and run the sample applications on your local application server. • Work through a basic ICEfaces tutorial that transforms a standard JSF application into a rich web application powered by ICEfaces.
    [Show full text]
  • Ajax, State of The
    AjAjaax,x, ststaattee ooff tthhee aarrtt Tarek Ziadé, Nuxeo [email protected] WWhhoo aamm ii ● I am engineer at Nuxeo ● I work on CPS, the famous ECM Plateform ;) ● I©ve been lately in charge of Ajax stuff in CPS ● I read Ajax related feeds before I go to bed WWhhaatt iiss AAjjaaxx ?? A dutch football club (a good one) A cleanser (really works) AA WWeebb 22..00 tteechchnnoollooggyy Asynchronous Javascript And XML WWhhaatt©©ss WWeebb 22..00 ?? TTiimm OO©©RReeiillllyy©©ss ©©ccoommppaacctt©© ddeeffiinniittiioonn:: Web 2.0 is the network as platform, spanning all connected devices; Web 2.0 applications are those that make the most of the intrinsic advantages of that platform: delivering software as a continually-updated service that gets better the more people use it, consuming and remixing data from multiple sources, including individual users, while providing their own data and services in a form that allows remixing by others, creating network effects through an "architecture of participation," and going beyond the page metaphor of Web 1.0 to deliver rich user experiences. MMaarrkkuuss AAnnggeerrmmeeiieerr©©ss vviieeww ooff WWeebb 22..00:: (courtesy of Markus Angermeier) WWeebb 22..00 AAppppss ✔ del.icio.us ✔ flickr ✔ Voo2do ✔ Digg ✔ Google Mail (Gmail) ✔ Writely ✔ Basecamp ✔ ... AjAjaaxx bbiigg ppiictctuurere 11//22 (courtesy of J. J. Garett) AjAjaaxx bbiigg ppiictctuurere 22//22 (courtesy of J. J. Garett) TThhee LLiistst ooff tthhiinnggss AjAjaaxx rereaallllyy bbririnnggss ✔ Increases interactivity ✔ Save bandwidth ✔ Helps avoiding some interactive
    [Show full text]
  • Third-Party License Acknowledgments
    Symantec Privileged Access Manager Third-Party License Acknowledgments Version 3.3.5 Symantec Privileged Access Manager Third-Party License Acknowledgments Broadcom, the pulse logo, Connecting everything, and Symantec are among the trademarks of Broadcom. Copyright © 2019 Broadcom. All Rights Reserved. The term “Broadcom” refers to Broadcom Inc. and/or its subsidiaries. For more information, please visit www.broadcom.com. Broadcom reserves the right to make changes without further notice to any products or data herein to improve reliability, function, or design. Information furnished by Broadcom is believed to be accurate and reliable. However, Broadcom does not assume any liability arising out of the application or use of this information, nor the application or use of any product or circuit described herein, neither does it convey any license under its patent rights nor the rights of others. 2 Symantec Privileged Access Manager Third-Party License Acknowledgments Contents Activation 1.1.1 ..................................................................................................................................... 7 Adal4j 1.1.2 ............................................................................................................................................ 7 AdoptOpenJDK 1.8.0_272-b10 ............................................................................................................ 7 Aespipe 2.4e aespipe ........................................................................................................................
    [Show full text]
  • Plasticité Des IHM & Web2.0
    IHM du Web 2.0 & plasticité Module Plasticité SI5 – Master IFI http://users.polytech.unice.fr/~pinna/MODULEIHM/Plasticite/ (c) 2009, Occello Audrey, Plasticité IHM / Web2.0 - 1 - Plan du cours • Nouveaux usages d'Internet => naissance du Web2.0 • Impacts sur les IHM => naissance des interfaces dites “riches”, les RIA (Rich Internet Applications) • Vers un Web3.0 ? Analyse des besoins Evaluation ergonomique Tests Utilisateurs Espace de conception Conception Propriétés ergonomiques Tests d’intégration Conception logicielle Modèle d’architecture Tests Unitaires logicielle Boîtes à outils Codage Mécanismes généraux (c) 2009, Occello Audrey, Plasticité IHM / Web2.0 - 2 - IHM du web2.0 & plasticité . Plasticité ? capacité d’adaptation d’une IHM : à la conception / exécution au contexte d’usage : langage, plate-forme logicielle/matérielle, utilisateur, environement, ... dans le respect de la valeur attendue par l’utilisateur cible : utilisabilité, ergonomie . Quelles formes de plasticité pour les IHM du web2.0 ? (c) 2009, Occello Audrey, Plasticité IHM / Web2.0 - 3 - Web2.0 : nouveaux usages (c) 2009, Occello Audrey, Plasticité IHM / Web2.0 - 4 - Evolution d'Internet : point de vue des usages Web1.0Web1.0 Web2.0Web2.0 Admin Admin Admin Admin publie publie gère gère Interagissent (RSS, services web, mashups) consultent consultent contribuent contribuent Utilisateurs Utilisateurs Utilisateurs/communauté Utilisateurs/communauté (c) 2009, Occello Audrey, Plasticité IHM / Web2.0 - 5 - Évolution des IHMs source: adobe.org (c) 2009, Occello Audrey, Plasticité IHM / Web2.0 - 6 - Web2.0, définition et points clé . Met l'accent sur l'agilité et la réutilisabilité des applis : Focalisation sur les services rendus et sur les données mais pas sur les applications Faiblement couplé pour faciliter l’assemblage de services en applications Faciliter la réutilisabilité des contenus .
    [Show full text]
  • Evaluating Presentation Layer Development Frameworks for EJB Applications in J2EE Architecture
    International Conference on Computer Science and Information Technology (ICCSIT'2011) Pattaya Dec. 2011 Evaluating Presentation Layer Development Frameworks for EJB Applications in J2EE Architecture Ohm Samkoses, Dipl. -Inform. Matthias Vianden, Prof. Dr. rer. nat. Horst Lichter gathering and analysis, multiple rounds of frameworks Abstract—For medium to large organizations, information selection with different criteria, prototype implementations, systems play an important role for information storage and retrieval. and results evaluation. The chosen frameworks for prototype They are used to support business processes such as decision-making. development should fulfill most of the requirement and the In information systems, huge amountof data needs to be manipulated prototypes implementation should reflect the solution for each and visualized. One way to handle this complexity is to use Enterprise JavaBeans (EJB) [1] in a J2EE architecture. Since EJB has requirement clearly, and must be able to work with the not been designed to work in the Presentation Layer, suitable existing system's environment: the back-end is managed by Presentation Layer Development frameworks are introduced to EJB 3.0, and IBM Websphere Application Server 7.0. enhanced thepresentation layer of the information systems. The MeDIC (Metric Definition Integration Calculation) system and XAM II. TASKS / STEPS (eXam Assignment and Management) system [2] are typical representatives of such information system. A. First frameworks selection Nowadays, many frameworks, such as Java Server Faces (JSF), First step was to narrow-down the scope of the focused Wicket, and Tapestry, exist to cover the Presentation Layer. They framework based mainly on framework popularity. Other provide a variety of features and architecture enhancements.
    [Show full text]
  • Icefaces Developer's Guide, Community Edition
    Developer’s Guide Version 1.7 Beta Copyright Copyright 2005-2008. ICEsoft Technologies, Inc. All rights reserved. The content in this guide is protected under copyright law even if it is not distributed with software that includes an end user license agreement. The content of this guide is furnished for informational use only, is subject to change without notice, and should not be construed as a commitment by ICEsoft Technologies, Inc. ICEsoft Technologies, Inc. assumes no responsibility or liability for any errors or inaccuracies that may appear in the informational content contained in this guide. ICEfaces is a registered trademark of ICEsoft Technologies, Inc. Sun, Sun Microsystems, the Sun logo, Solaris and Java are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and in other countries. All other trademarks mentioned herein are the property of their respective owners. ICEsoft Technologies, Inc. Suite 200, 1717 10th Street NW Calgary, Alberta, Canada T2M 4S2 Toll Free: 1-877-263-3822 (USA and Canada) Telephone: 1-403-663-3322 Fax:1-403-663-3320 For additional information, please visit the ICEfaces web site: http://www.icefaces.org ICEfaces Developer’s Guide v1.7 Beta February 2008 About this Guide The ICEfaces® Developer’s Guide is your manual to developing ICEfaces applications. By reading through this guide, you will: • Gain a basic understanding of what ICEfaces is and what it can do for you. • Understand key concepts related to the ICEfaces Rich Web Presentation Environment. • Examine the details of the ICEfaces architecture. • Access reference information for the following: — ICEfaces system configuration —JSF Page Markup — Java API reference — JavaScript API reference — Custom Component TLD • Learn to use advanced ICEfaces development features.
    [Show full text]
  • Diseño E Implementación De Un Framework De Presentación Curso 2012/13
    PFC – Diseño e implementación Framework Presentación (2012/13) Licencia Esta obra está bajo una licencia Reconocimiento - No comercial- Sin obras derivadas 2.5 España de Creative Commons. Puede copiarlo, distribuirlo y transmitirlo públicamente siempre que cite al autor y la obra, no se haga un uso comercial y no se hagan copias derivadas. La licencia completa se puede consultar en: http://creativecommons.org/licenses/by-nc-nd/2.5/es/deed.es 1 PFC – Diseño e implementación Framework Presentación (2012/13) Estudios de Informática y Multimedia Proyecto Fin de Carrera Diseño e implementación de un Framework de Presentación Curso 2012/13 Nombre: Daniel Rodríguez Simó Username: drodriguezsi Tutor : Óscar Escudero Sánchez 2 PFC – Diseño e implementación Framework Presentación (2012/13) Agradecimientos Quiero agradecer el apoyo a Isabel, mi mujer, de cara a todo el tiempo invertido para poder sacar adelante estos años de estudio y esfuerzo. Y en general a toda mi familia, especialmente a mis padres Eugenia y Juan Pedro, porque sin ellos y sin la educación que se han esforzado en darme, esto nunca habría sido posible y a Pilar y Eugenia, mis abuelas, que aunque no se encuentren entre nosotros, siempre algo de ellas que nos acompaña en el día a día. Por último agradecer a mi tutor Óscar su apoyo y orientación de cara a la consecución de este objetivo y al buen desarrollo de este Proyecto Fin de Carrera. A todos vosotros, Gracias! 3 PFC – Diseño e implementación Framework Presentación (2012/13) Descripción General El presente proyecto se centra en el estudio y elaboración de un marco de trabajo basado en un Framework de Presentación, dedicado al desarrollo de aplicaciones web bajo la plataforma J2EE.
    [Show full text]
  • Accessibility and Computing
    ISSUE 94, JUN 2009 Accessibility and Computing A regular publication of the ACM Special Interest Group on Accessible Computing A Note from the Editor Inside This Issue Dear SIGACCESS member: 1 A Note from the Editor Welcome to the new look of the online edition of the 2 SIGACCESS Officers and Information SIGACCESS Newsletter – with new layout, the use of 3 Web Toolkits Accessibility Study sans-serif and larger font throughout, left-justification, 9 Pitch in Non-verbal Vocal Input and the inclusion of authors’ short biographies and 17 Combating Obesity Trends in Teenagers photographs (so that you can say hi when you meet through Persuasive Mobile Technology them in meetings and conference). 26 ASSETS 2009 CFP This issue reports three articles. The first, titled Web Toolkits Accessibility Study, investigates accessibility functions of two open source web toolkits. The second article discusses the human factors element of non-verbal vocal interaction. The third presents the development of mobile exercise companion for teenagers’ weight management. Finally, this issue includes a Call for Participation for ASSETS 2009. Sri Kurniawan Newsletter editor PAGE 1 SIGACCESS NEWSLETTER, ISSUE 94, JUN 2009 SIGACCESS Officers and Information Chairperson Who we are Vicki Hanson SIGACCESS is a special interest group of IBM T.J. Watson Research Center ACM. The SIGACCESS Newsletter is a regular 19 Skyline Drive online publication of SIGACCESS. We Hawthorne, NY 10532, USA. encourage a wide variety of contributions, +1-914-784-6603 ( work ) such as: letters to the editor, technical [email protected] papers, short reports, reviews of papers of products, abstracts, book reviews, Vice-chairperson conference reports and/or announcements, interesting web page URLs, local activity Andrew Sears reports, etc.
    [Show full text]
  • Icefaces Getting Started Guide, Community Edition
    Getting Started Guide Version 1.6 Copyright Copyright 2005-2007. ICEsoft Technologies, Inc. All rights reserved. The content in this guide is protected under copyright law even if it is not distributed with software that includes an end user license agreement. The content of this guide is furnished for informational use only, is subject to change without notice, and should not be construed as a commitment by ICEsoft Technologies, Inc. ICEsoft Technologies, Inc. assumes no responsibility or liability for any errors or inaccuracies that may appear in the informational content contained in this guide. ICEfaces is a trademark of ICEsoft Technologies, Inc. Sun, Sun Microsystems, the Sun logo, Solaris and Java are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and in other countries. All other trademarks mentioned herein are the property of their respective owners. ICEsoft Technologies, Inc. Suite 200, 1717 10th Street NW Calgary, Alberta, Canada T2M 4S2 Toll Free: 1-877-263-3822 (USA and Canada) Telephone: 1-403-663-3322 Fax:1-403-663-3320 For additional information, please visit the ICEfaces website: http://www.icefaces.org ICEfaces v1.6 June 2007 About this Guide The ICEfaces Getting Started Guide will help you quickly get started building ICEfaces applications. By reading through this guide, you will: • Gain a basic understanding of what ICEfaces is and what it can do for you. • Install ICEfaces and run the sample applications on your local application server. • Work through a basic ICEfaces tutorial that transforms a standard JSF application into a rich web application powered by ICEfaces.
    [Show full text]
  • Jquery – JSON REST
    Develop Rich Web Applications with Seam, RESTEasy and ExtJS Jeremy Davis – JBoss Solutions Architect Derrick Kittler – JBoss Solutions Architect 02 May 2011 Who are these guys? Agenda ● What is the current landscape? ● Why this approach? ● RESTEasy, ExtJS, jQuery, Seam ● Look at some code (Demo) ● Recap ● How and why you may want to pitch ● Questions and Resources Current Landscape A view of the lake of Kawah Ijen; one of the most acidic craters in the world. Current Landscape - Detail ● Seam for JPA, EJB and JSF integration ● GWT good but maybe not everywhere ● RichFaces, IceFaces, *Faces ! ● Development struggles, widget creation ● REST and SOAP ● Spring Web Flow, Struts, etc... Why this Approach? ● Seam – strong DI & integration application stack (EJB, JSF, JPA, RF) ● ExtJS – client-side, JavaScript framework for building web applications. ● REST – simple web service implemented using HTTP ● jQuery – library that simplifies HTML document traversing, event handling, animating, and Ajax interactions Demo Time ! Gene Wilder, YOUNG FRANKENSTEIN 1974, Director - Mel Brooks jQuery – JSON REST REST URI Execute the request Bind data to HTML element REST – JSON REST URI JSON ! Write out the object Recap ● It works ● REST is easy ● ExtJS provides a lot of capability OOB ● Seam provides DI and heavy lifting ● jQuery works too ● Solid tooling Why to Pitch ● For me: ● Front-end all in JS; back-end all Java ● Add cool tech to your toolkit; mobile too! ● Less re-inventing the wheel; do other cool stuff ● For Management: ● More deterministic development times ● 'Standardization' of UI technology ● Less re-inventing the wheel and provide for service re-use How to Pitch ● Rich UI widgets; rapid development ● ExtJS does have a learning curve..
    [Show full text]