iBS Lab Ness KDC

1
iBS Lab _at_ Ness KDC

• Introduction iBS AG
• Authors Jaroslav Letan, Jozef Kubov

2
iBS - Innovative Banking solutions AG

• iBS - Innovative Banking Solutions AG is the
  leading developer of add-ons for SAP AG's mySAP
  Banking components.
• The company focuses on developing functions for
  automating business processes in banks and
  financial institutions.
• iBS AG is a software partner of SAP AG and is
  headquartered in Wiesbaden in Germany.

www.ibs-banking.de
3
iBS - Innovative Banking solutions AG

• iBS KDC Lab from 06/2007 .... 11 employees
• ( 2 Java EE, 9 SAP
  developers )
• Development and support of SAP Modules
• CYT Capital Yield Tax
• RBD Reserve for Bad Debts
• RRA Regulatory Reports Analyzer
• Java EE solution
• ALP Automatic Loan Processor

www.ibs-banking.de
4
JAVA Technologies In SAP Environment
5
Java in SAP
6
Complete Set of Development Tools for all Aspects
of JavaBusiness Applications

• SAP delivers an integrated development
  environment for all aspects of J2EE development
• User Interface
• Developing flexible web user interfaces with Web
  Dynpro Tools
• E-business logic
• Development and deployment of enterprise Java
  beans (EJB)
• Definition and publication of web services
• Enterprise Services
• Java persistence
• Container managed persistence (CMP)
• Embedded SQL in Java (SQLJ)
• Java data objects (JDO)
• Creating central data types and database objects
  (Java dictionary)
• Design time support for HTML, XML and XSLT
  (Validation, Code completion)

7
SAP NetWeaver Developer Studio

• SAPs environment for developing Java-based,
  multiple-layered business applications
• Based on the open-source tools framework of
  Eclipse 3.3
• Single point of entry for all Java development
  tools
• Integration point for all SAP infrastructure
  components
• Features
• Support for the component model
• Significantly reducing development costs
• Supports standard Java technologies as well as
  SAP technologies
• Web services support
• On-the-fly application debugging
• Hot deployment

8
Web Dynpro

• Web Dynpro design criteria
• Create UI programming paradigm that would become
  standard for all future SAP software
• Eliminate repetitive coding task the fewer
  lines of handwritten code in UI, the better
• Full use of abstract modeling. Web Dynpro apps.
  Should not need care about
• The communication technology required to access
  backend system
• The client technology being used to render the
  screens
• Full use of generic services. Functionality that
  is required should be made available form a
  standard library of services
• SAPs standard toolset for UI development and
  execution
• Deliver an enterprise quality web development
  environment
• Minimize coding, maximize design
• Support interaction with arbitrary backend
  systems
• Provide component based development
• Strong focus on code reuse (business level)
• Achieve client device independence
• Run on multiple client device without the need to
• Write client specific coding
• Modify deployed coding
• No need to install client based software

9
A High Level View Of Web Dynpro
10
Model-View-Controller in Web Dynpro

• Views
• Layout
• assembled from standardized UI elements
• View composition
• (possible) sequence of views in the application
• Controllers
• Context
• holds the controllers (local) data
• hierarchically structured
• Methods Event handlers
• contain Java custom coding
• Events
• controllers can consume and fire events
• Models
• Contain proxies for access to encapsulated
  business functions
• typically several proxies (for the same backend
  system) in one model
• Different types of models
• Call ABAP BAPIs (via JCo)
• Call Web Services

11
Web Dynpros UI Layer

• In order to implement all of SAPs design
  requirements, certain flexibilities to which
  developers have become accustomed have had to be
  removed
• The ability to create your own UI elements
• Ability to run on different devices
• No need to alter part of the Web Dynpro framework
  (Server Side Rendering) in order to implement
  each device specific version of new UI element
• No access to the coding of the Web Dynpro
  framework (stability support)
• Pixel-perfect alignment of UI elements
• Different algorithms are used by different
  clients (e.g. Mac PC) Words change length
  after translation
• All UI elements alignment is handled
  automatically by Web Dynpro framework

12
Key Differentiators Web Dynpro vs. Other Tools

• Web Dynpro software design focuses strongly on
• Code reusability
• Coding is bad if you have to write same piece
  of code twice
• Code maintainability
• Extra time spent trying to understand the coding
  written by the last developer only adds to an
  applications TCO
• Separation of concerns
• Web Dynpro Components are divided into distinct
  functional units that are designed to play
  specific roles

13
Using Web Dynpro with Other UI Technologies

• Web Dynpro JSF Integration
• Allow usage of JSF (composite) UI components in
  Web Dynpro UIs
• UI Mashups with Web Dynpro and JSF combine
  content from different UI technologies to create
  a novel form of reuse
• Web Dynpro Flash Islands
• Provide a subset of WD4VC Analytics UI Elements
  like the AnalyticsChart
• Provide a GenericFlash UI element to integrate
  additional Flash Controls
• Support transition effect, drag drop, sliders
  etc.

14
Summary

• SAP NetWeaver offers a variety of Java
  programming model
• SAP NetWeaver Developer Studio supports J2EE
  compliance
• Web Dynpro is SAPs powerful UI technology

15
Thank You for your Attention!

• jaroslav.lestan_at_ness.com
• jozef.kubov_at_ness.com