DOCSLIB.ORG

Developers Want: the End of Application Redeploys

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Developers Want: the End of Application Redeploys WHAT DEVELOPERS WANT: THE END OF APPLICATION REDEPLOYS True Story BRIEF INTRODUC- TION Email. Even 90-year-old grandmothers use it. We use email because it’s convenient and, in most cases, faster and more reliable than sending letters by post. And to some young people, even email is starting to seem antiquated and inefficient as a means of communication. But imagine that every time you wanted to write, send or receive an email, you needed to restart your computer. How much time would this take, and how annoying would that be? There is a similar threat faced by Java development teams worldwide: that of turnaround time due to application deployments (or restarts). This is a time drain that, according to over 1100 developers recently surveyed, forces the average coder to forfeit over 5, full 40-hour work weeks each year, time that could otherwise be spent writing code, testing and/or learning new things. This document presents a technology overview and business case for JRebel, as a commercial solution for eliminating the need to redeploy Java applications in order to see changes to code, such as when adding new features or fixing bugs. LITTLE HISTORYA Introduced in 1995 by Sun Microsystems, the Java programming language and Java Virtual Machine (JVM) is a highly regarded and well-respected piece of engineering. Not only is it widely adopted among Web and Enterprise App producers, Java benefits from continual improvements in recent years and even more good stuff is on the way. Java is a powerhouse in the program- ming world, based on widespread applica- bility and use, some excellent engineering behind the JVM platform, the clarity of syn- tax, the rich ecosystem of tools and libraries and the fact that Oracle says there are over 9 million Java developers out there (and many billions of app/device users). However, Java code changes cannot be dynamically reloaded, which means that quickly seeing what you do isn’t possible by default. When Java code is added or changed, the developer must build/compile and then deploy the code in a cycle that al- lows changes to be visible only after restart- ing the application server. Every time. SO WHAT’S THE PROBLEM WITH APPLICATION RESTARTS ANYWAY? For most changes a developer makes to their code – for example, adding a new feature, fixing a bug or improving functionality – a full application restart (or redeploy) is required for the changes to take effect. Depending on the size of the application, the application server, build tools, frameworks and hardware used, this can take anywhere from 30 seconds to 30 minutes (yep, we’ve heard this before!) So what do redeploys and application restarts mean for developers? A few things: • Constant interruptions instead of focusing on writing code • Slow feedback cycle to new changes • An average of 10.5 minutes per coding hour (over five 40-hour work weeks per year - yep!) of time forfeited to application restarts [1]. Ideally, a developer would make a single getting rid of the constant interruptions due to change and then quickly verify it is correct be- application server restarts (keep in mind, even fore moving on. This would consequently lead a 30 second restart is enough of an interrup- to less bugs and service requests later on, but tion to break concentration for as much as 15 the time drain would be intolerable – and we’ve minutes) seen the horrified faces of developers who JRebel provides this unique development expe- report having to spend 25-50% of each coding rience through eliminating the need to restart hour redeploying their application. Java applications in order to see code changes. To avoid that, developers line up a lot of new The ripple effect of eliminating interruptions code changes to launch in a single batch be- of this kind is well-proven since 2008; using cause to do otherwise is time consuming and JRebel developers can instantly reload indi- highly disruptive to a developers’ concentra- vidual changes to class structures, resources tion; however, now we see the slow feedback and framework configurations instead of com- cycle come into play. mitting a full application restart. This saves an average of 10.5 minutes per coding hour, which JRebel is a product designed to provide devel- comes out to over 5 work weeks each year. opers with a rapid feedback cycle, while also [1] Java Productivity Report 2011 WHERE DO THESE COME STATISTICS FROM Approximately 1100 Java developers from all over the world? shared their development environment in ZeroTurnaround’s Java EE Productivity Report in 2011. From this report we gathered information on the popularity and usage of build tools, Java IDEs, Java EE standards, Java application servers and web and server-side frameworks. In addition we asked the following two questions: • How long does it take to restart your Application Server and redeploy your app? • In an hour of coding, how many times do you redeploy? The results from these questions showed that the average redeploy time is 3.1 minutes, but the standard deviation is 2.8, which means that the redeploy time varies greatly. The average frequen- cy is 4 times an hour with the standard deviation of 3.2. Another interesting fact pointed to the statistically significant segment of respondents (just over 1 in every 10 developers) responded that it takes over 10 minutes to redeploy. The normalized data shows that an Time Redeploying in an Hour average of 10.5 minutes per coding hour, per developer, is forfeited to ap- plication restarts. Of course, this does not include build/compile time, nor the time is takes to get back into the “flow” after the interruption. If we assume 34% a 5-hour coding day, with the other 3 30% hours dedicated to planning, meetings, breaks, etc, then losses are: 14% 8% 5% • 52.5 minutes each day 5% 3% • Over 4.3 hours per week 1% • Almost 18 hours per month < 1 1-5 • More than five, 40-hour work 30+ 6-10 11-15 16-20 21-25 weeks each year 26-30 At this point, a good question to ask would be: “What can every developer in your team do with an extra 5+ weeks of development time each year?” SOLUTION JRebel eliminates redeploys, saving hours each week of time THE otherwise forfeited to redeployment. The first version of JRebel was created Since then, over 3000 companies have in a secret Estonian basement cubicle purchased JRebel, and at the time of under an even more secret codename this white paper the current version is in 2006 by Jevgeni Kabanov. It was JRebel 4.6. JRebel now supports every designed to be an internal tool to cut major application server available down on redeploy times in a software on the market, six different IDEs and company, which was suffering from nearly 50 web and server-side Java 10+ minute redeploy times. frameworks. But what does JRebel do? The beauty of JRebel is its simplicity - JRebel instantly reloads changes to class files, resources and framework configuration files. Whenever a developer adds/removes/changes methods, classes, JR ebel mapsyour rpojectwo rkspace directlyto your running application. W hen a annotations,de fieldsveloper or constructors,makes a changeto JRebel any class will rimmediately esouor rce in their reload IDE the theindividual change atchange, elyis immedi making a full application redeploy unnecessary. Below, you can see the typical Java EE development cycle: The Java EE Development cycle PHASE ONE Add feature, Þx bug, or improve PHASE TWO code using IDE of choice: Changes are compiled and optionally packaged into EARs / WARs. (Incremental builds comsume 60-260 hours annually) JRebel integrates directly with your IDE, app servers and frameworks of choice, letting you and your team skip Phases 2 & 3 and reclaiming over 5 weeks per year of lost time. PHASE FOUR PHASE THREE The application is redeployed to the and choose to improve the container. This phase consumes on change or move on to something average, 17% of development time new. Either way, go to Phase One. (210 hours - over 5 weeks annually). In Phase 1, code changes are added in the developer’s IDE. Then, the code is compiled or built in Phase 2. In Phase 3, the code is deployed, e.g. via application deploy, which can be only be done a few times before an OutOfMemoryException occurs. In that case, the application server itself must be restarted, which is when the time drain typically happens. Only after restarting in Phase 4 can the developer see the changes were committed. HOW DOES ? JREBEL WORK To put it briefly, Integration, Integration, Integration! IDEs Application Servers FRAMEWORKS BUILD TOOLS Without going too deeply into the technical side of things, JRebel works based on three specific areas of Java and the JVM: 1. Java Classes 2. Framework configuration changes 3. Workspace mapping Java Classes JRebel is a –javaagent that integrates with the JVM and rewrites each class to be updateable. JRebel versions each class individually, instead of an entire application or module at a time – and it does not use classloaders. With JRebel, changes to classes are always visible in the Reflection API. MyClass MyClass MyClass_3 Framework configuration changes JRebel integrates directly with application servers and frameworks to propagate configuration changes from the changed classes and resources, and annotation changes are always visible in Re- flection API. JRebel also provides an extensible SDK to allow contributions from third parties. Spring MVC, JSF, Struts, GWT, Velocity, Play!, Vaadin and dozens of other integrations have already been contributed. Workspace mapping JRebel maps a deployed application to the developer’s active workspace, which is how changes can be instantly visible during development.
Load more

Recommended publications
  • Pragmatic Guide to Javascript
    www.allitebooks.com What Readers Are Saying About Pragmatic Guide to J a v a S c r i p t I wish I had o w n e d this book when I first started out doing JavaScript! Prag- matic Guide to J a v a S c r i p t will take you a big step ahead in programming real-world JavaScript by showing you what is going on behind the scenes in popular JavaScript libraries and giving you no-nonsense advice and back- ground information on how to do the right thing. W i t h the condensed years of e x p e r i e n c e of one of the best JavaScript developers around, it’s a must- read with great reference to e v e r y d a y JavaScript tasks. Thomas Fuchs Creator of the script.aculo.us framework An impressive collection of v e r y practical tips and tricks for getting the most out of JavaScript in today’s browsers, with topics ranging from fundamen- tals such as form v a l i d a t i o n and JSON handling to application e x a m p l e s such as mashups and geolocation. I highly recommend this book for anyone wanting to be more productive with JavaScript in their web applications. Dylan Schiemann CEO at SitePen, cofounder of the Dojo T o o l k i t There are a number of JavaScript books on the market today, b u t most of them tend to focus on the new or inexperienced JavaScript programmer.
    [Show full text]
  • Jquery: Novice to Ninja
    SECOND Pantone: EDITION CMYK: JQUERYGrey scale PANTONE Orange 021 C PANTONE 2955 C NOVICE TO NCMYK IO, 53, N100, 0 JCMYKA 100, 45, 0, 37 NEW KICKS ANDBlack 50% TRICKSBlack 100% BY EARLE CASTLEDINE & CRAIG SHARKIE SIMPLE, FAST, POWERFUL — JAVASCRIPT THE WAY IT SHOULD BE Summary of Contents Preface . xvii 1. Falling in Love with jQuery . 1 2. Selecting, Decorating, and Enhancing . 19 3. Animating, Scrolling, and Resizing . 53 4. Images and Slideshows . 93 5. Menus, Tabs, Tooltips, and Panels . 139 6. Construction, Ajax, and Interactivity . 187 7. Forms, Controls, and Dialogs . 239 8. Lists, Trees, and Tables . 305 9. Plugins, Themes, and Advanced Topics . 347 A. Reference Material . 409 B. JavaScript Tidbits . 419 C. Plugin Helpers . 425 Index . 431 JQUERY: NOVICE TO NINJA BY EARLE CASTLEDINE & CRAIG SHARKIE wnload from Wow! eBook <www.wowebook.com> o D iv jQuery: Novice to Ninja by Earle Castledine and Craig Sharkie Copyright © 2012 SitePoint Pty. Ltd. Product Manager: Simon Mackie Assistant Technical Editor: Diana MacDonald Technical Editor: Tom Museth Indexer: Michele Combes Expert Reviewer: Jörn Zaefferer Cover Designer: Alex Walker Editor: Kelly Steele Printing History: Latest Update: February 2012 First Edition: February 2010 Second Edition: February 2012 Notice of Rights All rights reserved. No part of this book may be reproduced, stored in a retrieval system, or transmitted in any form or by any means without the prior written permission of the publisher, except in the case of brief quotations included in critical articles or reviews. Notice of Liability The authors and publisher have made every effort to ensure the accuracy of the information herein.
    [Show full text]
  • The Definitive Guide to Grails
    apress.com Graeme Rocher, Jeff Scott Brown The Definitive Guide to Grails This will be the first and only definitive book on the agile open source lightweight Grails (“Groovy on Rails” analogous to Ruby on Rails) Framework 1.0 release Written by the open source Grails project founder and lead, Graeme Rocher Emerging growth area with support from key open source lightweight projects like Spring, Hibernate, Wicket and more The rise of Ruby on Rails has signified a huge shift in how we build web applications today; it is a fantastic framework with a growing community. There is, however, space for another such framework that integrates seamlessly with Java. Thousands of companies have invested in Java, and these same companies are losing out on the benefits of a Rails–like framework. Enter Grails. Grails is not just a Rails clone. It aims to provide a Rails–like environment that is more familiar to Java developers and employs idioms that Java developers are comfortable 2nd ed., 648 p. using, making the adjustment in mentality to a dynamic framework less of a jump. The concepts within Grails, like interceptors, tag libs, and Groovy Server Pages (GSP), make those in Printed book the Java community feel right at home. Grails' foundation is on solid open source technologies Softcover such as Spring, Hibernate, and SiteMesh, which gives it even more potential in the Java space: 39,99 € | £36.99 | $46.99 Spring provides powerful inversion of control and MVC, Hibernate brings a stable, mature object [1]42,79 € (D) | 43,99 € (A) | CHF relational mapping technology with the ability to integrate with legacy systems, and SiteMesh 53,55 handles flexible layout control and page decoration.
    [Show full text]
  • Technologies We Use IT Project Management
    SolDevelo Sp. z o.o. is a dynamic software development and information technology outsourcing company, focused on delivering high quality software and innovative solutions. Our approach is a unique mix of highly experienced development team, client-oriented service and passion for IT. This guarantees projects to be completed on time, with the superior quality and precisely the way client imagined it. IT Project Management Requirements Specification Architecture Implementation Detailed Design Testing Integration Validation Maintenance Technologies We Use Software development and Integration Ý Application Servers Languages Web Servers Glassfish, JBOSS, Geronimo Java/JEE, Python, C#/.NET Nginx, Apache HTTP Android, PHP, Objective-C, Swift, Ruby Frameworks Web Technologies Database Environments Hibernate, Datanucleus, J2EE, PHP, XML, JavaScript, Oracle, SQL, PL/SQL, MySQL, OSGi, Spring Integration, SOAP, WSDL, RichFaces, PostgreSQL, HSQLDB, CouchDB, Quartz, Spring Batch, jQuery, JSP, JSF, AJAX, (S)CSS, SQLite3, Hypersonic Android Designer, LESS, XHTML, ASP.NET, Robotium, JBoss Seam Node.js Mobile Technologies Servlet Containers Android, iOS Tomcat, Jetty Web Frameworks AngularJS, Django, Spring WebFlow, Bootstrap, Zend, Ə CMS ǡ Business Intelligence Symfony, Express, Ruby on Rails Drupal, Wordpress, Joomla! DHIS2, Tableau 01 Competence Map Tools we use IDE Wiki < Knowledge Sharing IntelliJ IDEA, Eclipse, Android Confluence, Assembla Wiki, Trac Studio, Xcode, PHPStorm Project Methodology Issue/Bug Tracking Agile/Scrum JIRA, Assembla,
    [Show full text]
  • A Bad Case of Stripes
    A Bad Case of Stripes A Bad Case of Stripes Author: David Shannon Publisher: Scholastic Paperbacks (2004) Binding: Paperback, 32 pages Item Call Number: E SHANN Camilla Cream loves lima beans, but she never eats them. Why? Because the other kids in her school don't like them. And Camilla is very, very worried about what other people think of her. In fact, she’s so worried that she's about to break out in a bad case of stripes! Questions to talk about with your child: Why did Camilla break out in stripes (and other patterns?) What did you notice about the patterns that break out on Camilla? Do they have anything to do with what’s happening around her? Look at each of the pictures. Was there anything about Camilla that stayed the same each time she changed? What made Camilla finally turn back into herself? Did Camilla learn anything from having a bad case of stripes? Look at the last page. Was there anything different about the way Camilla looks? Fun things to do together: David Shannon always hides a picture of his white terrier Fergus somewhere in each of his books. Look for the picture of Fergus in this book. Camilla loves lima beans. Have lima beans for lunch or dinner one day. Draw a picture of yourself with stripes, polka dots or some other pattern. Check out a book about patterns, for example, Pattern Bugs by Trudi Harris or Patterns at the Museum by Tracey Steffora. Recognizing and completing simple patterns is an important kindergarten readiness skill.
    [Show full text]
  • Pragmatic Bookshelf Groovy Recipes.Pdf
    What readers are saying about Groovy Recipes This is the go-to guide for turning Groovy into every Java developer’s perfect utility knife. Whether you need to quickly parse an Atom feed, serve up an Excel spreadsheet from your Grails app, or create a tar- ball on the fly, this book will show you how. In true Groovy style, Scott does away with all unnecessary ceremony and gets right down to business. In almost every section, the very first thing you see is code— the recipe for solving the problem at hand—and if you want to stick around for the clear and informative explanation, well, that’s strictly optional. Jason Rudolph Author, Getting Started with Grails Groovy Recipes is the book that I want to have in reach whenever I work in my Groovy bakery. Nothing gets you faster up to speed than having well-thought-out recipes for your everyday tasks. Dierk König Canoo Engineering AG The format of this book is ideal for rapidly obtaining crucial informa- tion just when you need it. An agile text for agile development! Joe McTee Software Engineer, JEKLsoft Groovy is on my radar as one of the next big things in Java, and this book gets you up to speed quickly with lots of great code examples. David Geary Author, Clarity Training, Inc. Scott does a fantastic job of presenting many little nuggets of “groovi- ness” here in a way that is easy to read and follow. There is plenty here for Groovy newcomers and veterans alike. Thanks, Scott! Jeff Brown Member of the Groovy and Grails Core Development Teams Adding Groovy to Java is like adding rocket fuel to your SUV.
    [Show full text]
  • 2Nd USENIX Conference on Web Application Development (Webapps ’11)
    conference proceedings Proceedings of the 2nd USENIX Conference Application on Web Development 2nd USENIX Conference on Web Application Development (WebApps ’11) Portland, OR, USA Portland, OR, USA June 15–16, 2011 Sponsored by June 15–16, 2011 © 2011 by The USENIX Association All Rights Reserved This volume is published as a collective work. Rights to individual papers remain with the author or the author’s employer. Permission is granted for the noncommercial reproduction of the complete work for educational or research purposes. Permission is granted to print, primarily for one person’s exclusive use, a single copy of these Proceedings. USENIX acknowledges all trademarks herein. ISBN 978-931971-86-7 USENIX Association Proceedings of the 2nd USENIX Conference on Web Application Development June 15–16, 2011 Portland, OR, USA Conference Organizers Program Chair Armando Fox, University of California, Berkeley Program Committee Adam Barth, Google Inc. Abdur Chowdhury, Twitter Jon Howell, Microsoft Research Collin Jackson, Carnegie Mellon University Bobby Johnson, Facebook Emre Kıcıman, Microsoft Research Michael E. Maximilien, IBM Research Owen O’Malley, Yahoo! Research John Ousterhout, Stanford University Swami Sivasubramanian, Amazon Web Services Geoffrey M. Voelker, University of California, San Diego Nickolai Zeldovich, Massachusetts Institute of Technology The USENIX Association Staff WebApps ’11: 2nd USENIX Conference on Web Application Development June 15–16, 2011 Portland, OR, USA Message from the Program Chair . v Wednesday, June 15 10:30–Noon GuardRails: A Data-Centric Web Application Security Framework . 1 Jonathan Burket, Patrick Mutchler, Michael Weaver, Muzzammil Zaveri, and David Evans, University of Virginia PHP Aspis: Using Partial Taint Tracking to Protect Against Injection Attacks .
    [Show full text]
  • Preparing for Banner Powered by Ellucian XE
    Preparing for Banner powered by Ellucian XE Mark Hoye, Services Portfolio Consultant Ellucian September 25, 2015 Introduction • This session is about moving forward with Banner powered by Ellucian XE. • It explains Ellucian XE, how it adds value to your investment in Banner, and how you can take advantage of its power today. © 2015 ELLUCIAN. ALL RIGHTS RSERVED Agenda 1 Ellucian XE 2 Banner powered by Ellucian XE 3 Preparing for Banner powered by Ellucian XE 4 Summary and Questions © 2015 ELLUCIAN. ALL RIGHTS RSERVED Ellucian XE Ellucian: Future-proof Technology Evolutionary approach Extensible ecosystem strategy Global and mobile-first technology strategy Published roadmaps and product plans Investment in our products and our processes protects our customers’ investments © 2015 ELLUCIAN. ALL RIGHTS RSERVED The XE Strategy and Design Principles Mobile Self-Service Admin UI Cloud XE Design Principles Usability Features/Func7on Cloud Readiness/Scalability Configuraon over Customizaon Extensibility APIs/Integraon Single Global Product © 2015 ELLUCIAN. ALL RIGHTS RSERVED Banner powered by Ellucian XE Applications Leveraging XE Strategy Banner Applications Integrated Applications • Catalog & Schedule • Ellucian eTranscripts • Faculty Grade Entry • Ellucian Mobile • Attendance Tracking • Ellucian Elevate • Event Management • Ellucian Pilot (Student Success) • Advising Student Profile • Ellucian Portal for Banner • Student Registration • Intelligent Learning Platform (ILP) • Employee Profile • APIs (Services) • Academic history • Student • Communication Management © 2015 ELLUCIAN. ALL RIGHTS RSERVED ReSTful services and the Higher Education Data Model • Expose “Resources” - important concepts and objects • Each resource is uniquely Resources (Nouns) “addressable” • Provide “representations” of those resources Verbs • Provide a consistent interface (Get, Post, Put, Delete) based upon standard HTTP methods • Interaction with the API is stateless Output (XML, JSON) © 2015 ELLUCIAN.
    [Show full text]
  • Oralcard: Web Information System for Oral Health
    Universidade de Aveiro Departamento de Electrónica, Telecomunicações e 2011 Informática José Manuel OralCard: Sistema de Informação Web para a Saúde Santos Melo Oral OralCard: Web Information System for Oral Health Universidade de Aveiro Departamento de Electrónica, Telecomunicações e 2011 Informática José Manuel OralCard: Web Information System for Oral Health Santos Melo OralCard: Sistema de Informação Web para a Saúde Oral Dissertação apresentada à Universidade de Aveiro para cumprimento dos requisitos necessários à obtenção do grau de Mestre em Engenharia de Computadores e Telemática (M.I.E.C.T.), realizada sob a orientação científica do Professor Doutor José Luís Guimarães Oliveira, Professor Associado do Departamento de Electrónica, Telecomunicações e Informática da Universidade de Aveiro. Dedico este trabalho à minha família. o júri presidente Professor Doutor Armando José Formoso de Pinho Professor Associado com Agregação do Departamento de Electrónica, Telecomunicações e Informática da Universidade de Aveiro vogais Professor Doutor António Manuel de Jesus Pereira Professor Coordenador do Departamento de Engenharia Informática da Escola Superior de Tecnologia e Gestão do Instituto Politécnico de Leiria Professor Doutor José Luís Guimarães Oliveira Professor Associado do Departamento de Electrónica, Telecomunicações e Informática da Universidade de Aveiro agradecimentos Um obrigado especial ao Professor José Luís Oliveira pela minha integração no grupo de trabalho de Bioinformática, no Instituto de Engenharia Electrónica e Telemática de Aveiro (IEETA). Um obrigado especial ao Pedro Lopes e ao Joel P. Arrais, que me ajudaram com grande dedicação no desenvolvimento deste trabalho. Um obrigado ao Nuno Rosa pela ajuda na parte biológica e científica do trabalho. Este projecto não estaria concluído sem reconhecer a ajuda prestada pelos meus pais e irmãs, não só na dissertação como em todo o percurso académico na Universidade de Aveiro.
    [Show full text]
  • The Definitive Guide to Grails
    G. Rocher, J.S. Brown The Definitive Guide to Grails ▶ This will be the first and only definitive book on the agile open source lightweight Grails (“Groovy on Rails” analogous to Ruby on Rails) Framework 1.0 release ▶ Written by the open source Grails project founder and lead, Graeme Rocher ▶ Emerging growth area with support from key open source lightweight projects like Spring, Hibernate, Wicket and more The rise of Ruby on Rails has signified a huge shift in how we build web applications today; it is a fantastic framework with a growing community. There is, however, space for another such framework that integrates seamlessly with Java. Thousands of companies have invested in Java, and these same companies are losing out on the benefits of a Rails– 2nd ed., 648 p. like framework. Enter Grails. A product of Apress Grails is not just a Rails clone. It aims to provide a Rails–like environment that is more familiar to Java developers and employs idioms that Java developers are comfortable Printed book using, making the adjustment in mentality to a dynamic framework less of a jump. The concepts within Grails, like interceptors, tag libs, and Groovy Server Pages (GSP), make Softcover those in the Java community feel right at home. ▶ 39,99 € | £36.99 | $46.99 ▶ *42,79 € (D) | 43,99 € (A) | CHF 53.55 Grails' foundation is on solid open source technologies such as Spring, Hibernate, and SiteMesh, which gives it even more potential in the Java space: Spring provides powerful eBook inversion of control and MVC, Hibernate brings a stable, mature object relational mapping technology with the ability to integrate with legacy systems, and SiteMesh handles Available from your bookstore or flexible layout control and page decoration.
    [Show full text]
  • Open Source Katalog 2009 – Seite 1
    Optaros Open Source Katalog 2009 – Seite 1 OPEN SOURCE KATALOG 2009 350 Produkte/Projekte für den Unternehmenseinsatz OPTAROS WHITE PAPER Applikationsentwicklung Assembly Portal BI Komponenten Frameworks Rules Engine SOA Web Services Programmiersprachen ECM Entwicklungs- und Testumgebungen Open Source VoIP CRM Frameworks eCommerce BI Infrastrukturlösungen Programmiersprachen ETL Integration Office-Anwendungen Geschäftsanwendungen ERP Sicherheit CMS Knowledge Management DMS ESB © Copyright 2008. Optaros Open Source Katalog 2009 - Seite 2 Optaros Referenz-Projekte als Beispiele für Open Source-Einsatz im Unternehmen Kunde Projektbeschreibung Technologien Intranet-Plattform zur Automatisierung der •JBossAS Geschäftsprozesse rund um „Information Systems •JBossSeam Compliance“ •jQuery Integrationsplattform und –architektur NesOA als • Mule Enterprise Bindeglied zwischen Vertriebs-/Service-Kanälen und Service Bus den Waren- und Logistiksystemen •JBossMiddleware stack •JBossMessaging CRM-Anwendung mit Fokus auf Sales-Force- •SugarCRM Automation Online-Community für die Entwickler rund um die •AlfrescoECM Endeca-Search-Software; breit angelegtes •Liferay Enterprise Portal mit Selbstbedienungs-, •Wordpress Kommunikations- und Diskussions-Funktionalitäten Swisscom Labs: Online-Plattform für die •AlfrescoWCMS Bereitstellung von zukünftigen Produkten (Beta), •Spring, JSF zwecks Markt- und Early-Adopter-Feedback •Nagios eGovernment-Plattform zur Speicherung und •AlfrescoECM Zurverfügungstellung von Verwaltungs- • Spring, Hibernate Dokumenten; integriert
    [Show full text]
  • Beginning Jboss Seam
    Beginning JBoss® Seam From Novice to Professional Joseph Faisal Nusairat Beginning JBoss® Seam: From Novice to Professional Copyright © 2007 by Joseph Faisal Nusairat All rights reserved. No part of this work may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying, recording, or by any information storage or retrieval system, without the prior written permission of the copyright owner and the publisher. ISBN-13 (pbk): 978-1-59059-792-7 ISBN-10 (pbk): 1-59059-792-3 Printed and bound in the United States of America 9 8 7 6 5 4 3 2 1 Trademarked names may appear in this book. Rather than use a trademark symbol with every occurrence of a trademarked name, we use the names only in an editorial fashion and to the benefit of the trademark owner, with no intention of infringement of the trademark. Java™ and all Java-based marks are trademarks or registered trademarks of Sun Microsystems, Inc., in the U.S. and other countries. Apress, Inc., is not affiliated with Sun Microsystems, Inc., and this book was written without endorsement from Sun Microsystems, Inc. JBoss® is a registered trademark of Red Hat, Inc., in the U.S. and other countries. Apress, Inc., is not affili- ated with Red Hat, Inc., and this book was written without endorsement from Red Hat, Inc. Lead Editor: Steve Anglin Technical Reviewer: Floyd Carver Editorial Board: Steve Anglin, Ewan Buckingham, Gary Cornell, Jason Gilmore, Jonathan Gennick, Jonathan Hassell, James Huddleston, Chris Mills, Matthew Moodie, Dominic Shakeshaft, Jim Sumser, Keir Thomas, Matt Wade Project Manager: Denise Santoro Lincoln Copy Edit Manager: Nicole Flores Copy Editor: Sharon Wilkey Assistant Production Director: Kari Brooks-Copony Production Editor: Lori Bring Compositor: Patrick Cunningham Proofreader: Dan Shaw Indexer: John Collin Artist: April Milne Cover Designer: Kurt Krames Manufacturing Director: Tom Debolski Distributed to the book trade worldwide by Springer-Verlag New York, Inc., 233 Spring Street, 6th Floor, New York, NY 10013.
    [Show full text]