| Typ | Titel | Speaker |
|---|---|---|
![]() |
Managing Complex Enterprise Environments | Schuppe, Dirkes |
![]() |
Buy AND build. A strategy for building applications that spans both packaged applications and custom development | Hearn |
![]() |
The State of Web Frameworks | McClanahan |
![]() |
Introducing Eclipse Callisto | Milinkovich |
![]() |
Aligning IT with Business Goals through SOA Using IBM Eclipse Based Tools | Bater |
![]() |
Integriertes Application Lifecycle Management | Wieske |
![]() |
Escaping the Technology Cycle | Johnson |
![]() |
SOA beherrschen | Totev |
![]() |
Essential EJB 3.0 Persistence in Practice | Clarke |



Das Management von Web-basierten Applikationen wird von den meisten System-Management-Systemen, wie wir sie heute kennen, nur unzureichend gehandhabt. Heutige IT-Teams müssen aber nicht nur die Soft- und Hardware überwachen, sondern auch die Kundenzufriedenheit mit einbeziehen. Daher gibt es mächtige Application Performance Management-(APM-)Werkzeuge, die in der Lage sind, die heutige komplexe, webfähige Applikationslandschaft sowohl aus Kundensicht als auch End-to-End mit Sicht auf die realen Geschäftstransaktionen in Echtzeit zu überwachen. Die Keynote zeigt auf, worauf beim Einsatz eines APM-Systems zu achten ist und wie IT-Organisationen damit bei ihrer täglichen Arbeit geholfen werden kann.


Classically companies have two choices when it comes to their IT strategies: build or buy (packaged applications versus custom development). Buy generally offers better long-term value for money; Build promises more flexibility. Of course, typically companies will deploy packaged applications (e.g. SAP) AND have in a different silo custom development (Java, .NET and so on). However, the two are weakly linked (generally with some sort of expensive and inflexible integration framework), there is redundancy of work, indeed the two groups often do not talk to one another. The result is a lack of agility in building out new applications in response to changing business requirements. This presentation will look at a strategy (particularly as regards custom development based on the Java stack) that can combine the best of both worlds.


The space of Web application frameworks has seen, and continues to see, a tremendous amount of innovation over the last few years. At the same time, standardization efforts around JavaServer Faces have energized their own burst of activity. How does an application architect choose between 50 or so available options? We will review the set of problems that Web application frameworks solve, and offer some ideas on what might be useful decision making criteria for your projects.


This summer Eclipse is shipping it's first ever release train, codenamed Callisto. Currently there are ten separate Eclipse projects which are working hard to ship on the very same day: BIRT, C/C++, Data Tools, Eclipse (including Java development tools and rich client platform), EMF, GEF, GMF, Test and Performance, Visual Editor and Web Tools. For the Java developer, this will give them a great collection of open source tools to use for development. Even more importantly, it will provide a comprehensive set of frameworks to build products and applications on top of. This talk will provide a look into the major new features coming from each of the projects, and how Callisto will impact the commercial businesses rapidly growing around the Eclipse technology.


This keynote will talk about the need for Business Driven Development for Service Oriented Architecture, what is different from what happened before, how it is an evolution, and how IBM is building its Eclipse Tools, Process and Methodologies on open-source technologies to provide business value.


Mit dem neuen Visual Studio 2005 Team System adressieren die Microsoft Developer Tools die erweiterte Zielgruppe um Projektmanager, Anforderungsspezialisten, Architekten, Entwickler und Tester. Damit betritt Microsoft mit einem innovativen Produkt auf bewährter Grundlage den Application-Lifecycle-Management-Markt mit Angeboten für alle Bereiche des Software-Entwicklungsprozesses. Die Lösung typischer Software-Entwicklungs-Probleme liegt aus der Sicht von Microsoft nicht nur in der technischen Weiterentwicklung der eingesetzten Werkzeuge, sondern auch in der besseren Integration der einzelnen Werkzeuge mit dem Ziel die Planung, Zusammenarbeit und Übersicht in Softwareprojekten zu verbessern. Mit der Integration der eingesetzten Werkzeuge als zentralem Entwurfsprinzip in Visual Studio 2005 Team System ergeben sich aus den folgenden vier Aspekten besondere Impulse für entsprechende Verbesserungen in Unternehmen, die sich für den Einsatz von Team System entscheiden: Integrations-Plattform für Lifecycle, Integrations-Plattform für Modellierung, Integrations-Plattform für Qualitäts-Management, Integrations-Plattform für Reporting.


The Java/Java EE technology platform continues to evolve at a rapid rate.
This pace of change is problematic for enterprise application development, as enterprise software assets must often serve for 5-10 years, rather than the typical 2 year generational changes of Java technology.
Fortunately, today's POJO-based technologies provide a way to maximize the life of your investment, by decoupling your business logic and domain model from volatile infrastructure.
In this keynote, Rod Johnson will discuss the challenges in building long-lived Java applications, and how to ensure that maintenance of your applications is primarily driven by changes in business requirements, rather than technology platform.


Immer mehr Unternehmen starten mit SOA-Projekten. Wie lassen sich solche Architekturen erfolgreich verwalten und betreiben? SOA Management und Governance sind hier die Stichworte. Diese Keynote beleuchtet die verschiedenen Ansätze und stellt Initiativen vor, um Themen wie SOA Lifecycle, Management und Governance weiter zu standardisieren.


A crash course introduction to EJB 3.0 Persistence of Java Enterprise Edition 5.0. The goal of this session is to demonstrate how to apply the EJB 3.0 Persistence functionality in enterprise application development. Attendees will leave with enough information to get them started building enterprise applications using this new standard. The material will be presented using live demos of application development, testing, and deployment. The persistence capabilities both within and outside of an EJB container will be highlighted.
The open source reference implementation of the EJB 3.0 Persistence, TopLink Essentials, will be used in conjunction with the Eclipse Dali EJB ORM Project tools to build an end to end application illustrating common patterns and best practices.