Skip to main content
Jump to: navigation, search

Scout/Workshop/2014/Session Abstracts

Scout at RID, Netherlands

In the talk I will shortly provide insight in the selection of Scout for our project at the Regional Institute for Dyslexia (RID). Next I will describe the major requirements of our project and product and show the solutions we use.

Although I will give examples illustrating different aspects of the application, the focus is on the the use of multiple databases. The solutions will be explained with real code examples.

Presenter: Bertin Kiekebosch, RID

Modernisation of Legacy Applications at Swiss Federal Railways

When faced with replacing a legacy application (Swing UI, Cobol on Mainframe) with a modern rich client we decided to use Eclipse Scout to hide the complexities of RCP. I will outline our decision process, our architecture in relation to backend integration, show some of the gains and costs this decision carried and finally look into some custom controls we migrated from a pure Eclipse RCP application to Scout

Presenter: Urs Beeli, SBB

Entwicklung und Customizing des BSI CRMs auf Basis Scout

Abstract: ERGO Direkt had different pieces of software for the front- and back-office. One was based on Java Swing, the other one was a customized callcenter-software written in POP which was EOL. Together with BSI we built a new crm-system based on Eclipse Scout and the core of bsicrm. We managed to integrate over 20 backend-systems in one new frontend.

Our customer now has one piece of software for nearly all the work in the front- and backoffice including the channels phone, chat, skype, fax and letters.

In this talk I will give you some Informations about the project "Intelligente Kundenprozesse", building and supporting the new System for our Customer.

Presenter: Stefan Nachtrab, ERGO Direkt

e-AMIS Mobile, a Wealth Management System Frontend with Scout

Abstract: e-AMIS is a portfolio management solution for banks and asset managers covering the whole investment process, from portfolio analysis, performance and risk calculation, to automatic rebalancing, order generation and comprehensive customer reporting. While the existing software is powerful in functionality, its user interface is currently limited to a desktop client.

To meet customer demand to make the application available on mobile devices and to profit from simple distribution scenarios offered by web applications, we have selected the Eclipse Scout framework and developped a prototype application called e-AMIS Mobile. First client feedback has shown that e-AMIS Mobile is a perfect extension to the e-AMIS solution to be used for customer self service and mobile advisors.

In this session we briefly introduce both e-AMIS and the new fontend prototype e-AMIS Mobile, discuss our experiences with adopting Eclipse Scout and present the current state of the prototype.

Presenter: Daniel Hümbeli works for Profidata since 2008 and is responsible for the portfolio management solution e-AMIS. Besides leading the development and services teams he drives strategic initiatives such as architecture transformation, development offshoring or Web/Mobile frontend for e-AMIS. Before, he worked as IT Architect Manager at IBM Global Business Services and Principal Consultant at PricewaterhouseCoopers.

Presentation: https://wiki.eclipse.org/File:E-AMIS_Mobile_-_Eclipse_Scout_Workshop_2014.pdf

Build a Scout backend with Spring

Abstract: The overall promise of Eclipse Scout is to ease development of applications that run simultaneously on the desktop, in the browser and on mobile devices. Looking at big Scout applications like the ones developed by BSI this definitely holds true and it is obvious, that the Scout approach is more as suitable for a typical back-office application.

However when you start building your own Scout based application, you will wonder whether directly using database tables or passing object Arrays from the backend to the frontend are the only options you have. Having used Spring or JEE in the past you will wonder how to re-use concepts like beans, annotations, JPA and messaging service. How would you do data validation on the backend? If you overcame that hurdle and were able to combine a suitable backend technology stack with Scout, you have to take the next hurdle: how do you create a common build and deployment for the two technology stacks?

In this talk we present how we addressed the above questions when building a new back office application for Sixt Leasing AG. We will sketch an application architecture using Eclipse Scout plus Spring to be used as blocks in a service oriented architecture.

Presenter: Wolfgang Strunk, Sixt Leasing AG, Nejc Gasper, Result

Migration of a large Oracle Forms application to Scout

Abstract: The Logitrack application is an ERP system for Air-, Sea- and Road logistics developed at Rhenus Logistics. The system is a large, long-grown application developed with Oracle Forms, consisting of >1000 forms and a database with 1300 tables. As part of the company’s technology strategy it has been decided to fade out Oracle Forms from the technology stack.

After the evaluation of different migration approaches it was chosen to use a semi-automatic migration approach, based on Eclipse technologies. The target was to build an Eclipse integrated tool-chain that allows to generate as most as possible from the existing application and build a development environment that allows developers to easily maintain the application.

The information about the existing application is gained from exported Forms XML files and the database metadata, and transformed to textual DSL (Domain Specific Language) models. These models are input for a code generator, which creates a working application frame. Only custom PL/SQL code holding UI and business logic needs to be manually translated to Java.

The target application should be a Rich Internet Application, where Scout has been chosen as the central application framework of the target architecture. Other central elements of the technology stack are the Spring framework and EclipseLink. The tool chain is based on DSLs developed with Xtext, and the code generator was based on the Xtend programming language. Large portions of the generated code are Scout based, while the DSL models are kept agnostic to the underlying target technology. In this talk I will explain the tool chain in detail and demonstrate it to build a fully functional application from scratch within minutes. We will discuss our experience with using Scout the first time in a non-trivial environment.

Presenter: Karsten Thoms, itemis; Max Vollmer, Rhenus

Back to the top