SAP's Integrated Development Environment for Java. Karl Kessler, SAP AG

SAP's Integrated

Development

Environment for Java

Agenda

è

Comparison ABAP Workbench /

Typical Java IDE

è

Eclipse

è

The SAP Framework

Comparison ABAP Workbench / Typical Java IDE

-+

Environment/Infrastructure

-+

Support for SAP

Technology

+

-Private Test Environment

+

-Offline Development

+

-Support for Standards

+

-Local Editing

-+

Large Scale Application

support

JAVA

ABAP

ABAP

n Server oriented

n Design Time and Run

Time Objects stored in

same database

n SAP System

determines „scope“

JAVA

n Operates on Local File

System

Design Time and Run

Time separated

n Development

environment

organized in local

„projects“

Comparison: ABAP / Java: Some highlights

ABAP

Ì

One frame (SE80) for all Design Time Tools

Ì

Highly convenient infrastructure environment seamlessly

integrated into Development Workbench

Ì

Build environment, Deployment, Software Logistics, ...

Ì

Proven environment for large-scale application development

Ì

Strong support for SAP Technologies

Ì

Structured „logical“, not physical, presentation of all SAP Design

Time Objects

Java

Ì

Local Development Environment

Ì

Editing support: Syntax Highlighting, Code Completion, ...

Ì

Offline development

Ì

Private test environment (partially)

SAP Java IDE

Goal: Combine the advantages of both approaches

Ì

Provide one frame for all tools and as integration point for all

infrastructure components

Ì

Provide convenient integrated infrastructure environment to

support large scale application development

Ì

Preserve principle of local IDE

Ì

Local editing support

Ì

Offline development

Ì

Optimal support for standard and SAP technologies

Ì

Logically structured presentation of all Design Time Objects

Local File System

Tool Integration Platform

Overall Java Development Infrastructure

Design

Time

Repository

(DTR)

Component

Build

Service

(CBS)

Software Logistics

(SL)

Run

Time

J2EE

Server

Deploy

DDIC

Web

Dynpro

Web

Service

DTR/CBS/SL

Integration

Generic Model Abstraction Layer

Graphics

Tool Service

Layer

Tool Integration Platform

Topics of this presentation

Design

Time

Repository

(DTR)

Component

Build

Service

(CBS)

Software Logistics

(SL)

Run

Time

J2EE

Server

DDIC

Web

Dynpro

Web

Service

DTR/CBS/SL

Integration

Generic Model Abstraction Layer

Graphics

Deploy

Tool Service

Layer

Local File System

Agenda

è

Comparison ABAP Workbench /

Typical Java IDE

è

Eclipse

è

The SAP Framework

Tool Integration Platform

Eclipse

Design

Time

Repository

(DTR)

Component

Build

Service

(CBS)

Software Logistics

(SL)

Run

Time

J2EE

Server

DDIC

Web

Dynpro

Web

Service

DTR/CBS/SL

Integration

Generic Model Abstraction Layer

Graphics

Deploy

Tool Service

Layer

Local File System

Eclipse

n

Open Source project "donated" by IBM

n

Eclipse is itself written in Java

n

Eclipse is only a framework:

Everything is a plugin!

n Formally defined Extension Points and Plugin dependencies

n Very small kernel (Platform Runtime): The framework itself is

implemented as a set of plugins

n Own UI approach (SWT / JFace)

n Workbench plugin as generic

framework for any tool

n Complete Java (J2SE) IDE comes with

Eclipse

u

Set of plugins

u

Open Source

n Eclipse is the basis of IBM‘s IDE WSAD

n Many vendors are providing Eclipse

Eclipse: Projects

n

Multiple projects can be

opened at the same time

n

Project dependencies can be

declared

n

Workspace principle: a

workspace defines the scope

of accessible resources

n

No workspace switch

at run time

Eclipse: Perspectives and Views

n Perspective

u

Is composed of all visual components (views) for one aspect of the

development

u

Examples

l

Java perspective: Package view, Java editor, Outline pane for Java

source/class files

l

Debug perspective: Java editor, thread display, breakpoint list, etc.

n Quick and easy switch

n Perspectives are personalizable

u

Add/remove views

u

Compose new perspectives from existing views

Java and Debug Perspective

Java

Perspective

Debug

Perspective

Eclipse: Java IDE

n

Refactoring features

u

Move/rename classes and

methods

u

Repackage

u

Extract methods

u

Surround with try/catch

n

Pretty Printing

u

Configurable

n

Code completion (IntelliSense)

n

Import management

u

Configurable

n

Search features

u

References

u

Definitions

u

Read/write access

Eclipse: Java IDE

n

Incremental Build

n

Ant based build support

n

Support for building

archives

n

State-of-the-Art Debugger

u

Local and remote

debugging

Eclipse: PlugIn Development

n

Runtime Workbench

u

debug possibility

n

PlugIn Development

Environment (PDE)

n

Lazy initialization of

PlugIns

n

Easy deployment

n

„Everything is a PlugIn“

u

PlugIn dependencies

u

PlugIn versioning

n

Extension Point technology

u

Every PlugIn extends other

PlugIns at predefined

Extension Points

u

Every PlugIn can provide

Extension Points

Eclipse: Presenting the Workspace

n Direct

presentation of files and folders structure (Resource

Perspective)

n Special

abstraction layer for Java Perspective:

package -> class -> method / attr.

n

No generic abstraction layer

Resource

Perspective

Java

Agenda

è

Comparison ABAP Workbench /

Typical Java IDE

è

Eclipse

è

The SAP Framework

è

The J2EE toolset

Tool Integration Platform

The SAP Framework

Design

Time

Repository

(DTR)

Component

Build

Service

(CBS)

Software Logistics

(SL)

Run

Time

J2EE

Server

Java

DDIC

J2EE

Web

Dynpro

Web

Service

DTR/CBS/SL

Integration

Generic Model Abstraction Layer

Graphics

Deploy

Tool Service

Layer

The SAP Framework

Technological Approach

n

Use Eclipse as Java IDE (J2SE)

n

Use Eclipse as Tool Integration Platform for all development related

tools

u

SAP Technology (WebDynpro, Java Dictionary, ...)

u

Standard Technologies not supported by Eclipse (J2EE, XML, ...)

u

Infrastructure (Repository, Build, Software Logistics, ...)

Drawbacks

n

Lack of generic Model Abstraction Layer

u

No generic support for presenting Design Time Objects in a logical (not

physical) way

u

No basis for generic graphics enabling

Service Layer not sufficient

n

SWT / JFace UI approach instead of Swing

u

Little documentation

IDE overview

Eclipse Platform

J2SE

Tools

Model Abstraction Layer

Model Abstraction Layer

J2EE

Tools

Java

Dictionary

View

Designer

Service Layer

Service Layer

Application

Modeler

Example: WebDynpro Application Modeler

Diagramming based on

Graphics Engine

Diagramming based on

Graphics Engine

Eclipse

Framework

Model View based on

Model Abstraction

Layer

Grahics based on

Model Abstraction

Layer

Grahics based on

Model Abstraction

Layer

Service Layer Example: SAP UI layer

n

Validation against DTD

n

Schema based editing support: XMLInsight

n

Pretty Printer

n

Used in multiple multi-page editors (J2EE, Component Editor, ...)

Agenda

è

Comparison ABAP Workbench /

Typical Java IDE

è

Eclipse

è

The SAP Framework

Tool Integration Platform

J2EE Toolset

Design

Time

Repository

(DTR)

Component

Build

Service

(CBS)

Software Logistics

(SL)

Run

Time

J2EE

Server

Java

DDIC

Web

Dynpro

Web

Service

DTR/CBS/SL

Integration

Generic Model Abstraction Layer

Graphics

Deploy

Tool Service

Layer

Local File System

J2SE

Tools

J2EE Toolset

n

J2EE 1.3 support

n

Diagramming

n

Direct support of SAP J2EE Engine 6.30

Eclipse Platform

Model Abstraction Layer

J2EE

Tools

Java

Dictionary

View

Designer

Service Layer

Application

Modeler

Standard J2EE 1.3

Support

SAP J2EE Engine

Integration

J2EE Toolset: Supported J2EE 1.3 features

EJB

n

EJB 2.0

u

Session, Entity, Message Driven

n

EJB Assembly (EJBJar)

Web

n

Servlet

n

JSP

n

Filter

n

Listener

n

HTML

n

Web Archive (WAR)

Enterprise

Standard J2EE 1.3

Support

SAP J2EE Engine

Integration

J2EE Toolset

J2EE Toolset

Creation wizards for

n

Projects: EJB, EJB Assembly, Web, Web Assembly, Enterprise

Application

J2EE Toolset

Multi-Page Editors for all deployment descriptors

n

ejb-jar.xml, web.xml, application.xml

J2EE Toolset: SAP J2EE Engine Integration

Standard J2EE 1.3

Support

SAP J2EE Engine

Integration

SAP J2EE Engine

Developer‘s PC

Deployment

Local testing and debugging

SAP J2EE Engine

SAP J2EE Engine

LAN

Deployment

SAP Java IDE

SAP J2EE Engine

Developer‘s PC

Deployment

Local testing and debugging

SAP J2EE Engine

SAP J2EE Engine

LAN

Deployment

EAR Deployment

n

Launching of Visual

Deployment Tool from J2EE

Perspective

n

Local storage and editing of

Deployment Configurations

SAP Java IDE

SAP J2EE Engine

Developer‘s PC

Local Testing and debugging

LAN

Deployment

SAP J2EE Engine

SAP J2EE Engine

Local Test and Debug

Environment

n

Specify Server Settings in

„Preferences“ page

n

Start / Stop local J2EE Engine

from J2EE View

u

Normal or debug mode

n

Direct testing or debugging of

servlets / JSPs on local server

Q&A

Feedback

Please complete your session

evaluation and drop it in the box on

your way out.

Be courteous — deposit your trash,

and do not take the handouts for the

following session.