225457982 the-sap-eclipse-story
-
Upload
roberto-faccini -
Category
Documents
-
view
233 -
download
0
Transcript of 225457982 the-sap-eclipse-story
The SAP Eclipse Story
Rainer Ehre, NW C ToolsMalte Kaufmann, NW C Tools10/11/2007
© SAP 2007 / Page 2
1. Eclipse Positioning in SAP‘s Product Strategy2. SAP Eclipse History3. Demo – SAP NetWeaver Developer Studio4. Eclipse related SAP Focus
4.1. Standard Java4.2. Business Process Modeling4.3. Web UI4.4. Development Infrastructure4.5. Modeling Infrastructure
5. Summary
Agenda
© SAP 2007 / Page 3
1. Eclipse Positioning in SAP‘s Product Strategy2. SAP Eclipse History3. Demo – SAP NetWeaver Developer Studio4. Eclipse related SAP Focus
4.1. Standard Java4.2. Business Process Modeling4.3. Web UI4.4. Development Infrastructure4.5. Modeling Infrastructure
5. Summary
Agenda
© SAP 2007 / Page 4
SAP NetWeaver –A Strategic Platform for eSOA
Business Suite is SAP’s major ProductBusiness Process Platform: Business Functionality via Enterprise SOA ProvisioningStable, scalable coreService-enabledReuse of SOA assets (more than 20 millions line of ABAP code)
SAP NetWeaver Composition Environment 7.1 (SP3 in Nov 2007)Java standards based Integration Platform (JEE App Server and Eclipse)Model-driven developmentLean consumptionLoose coupling
© SAP 2007 / Page 5
Java ApplicationServer
Eclipse DevelopmentEnvironment
Robust, enterprise-class Java EE 5application server
SAP NetWeaverDeveloper Studio:Eclipse baseddevelopment andmodeling environment
SAP NetWeaver Composition Environment 7.1
Proc
esse
s
Event FlowRole
View
s
Portal and Web FormsMobile
and VoiceAnalytics
Web Dynpro UISAP InteractiveForms by AdobeFederated PortalNetwork
Enterprise ServicesRepository andRegistry (ESR)Software lifecyclemanagement andlogistics (NWDI)
Bus
Dataor File
Web Services / EnterpriseServices Connectivity
Serv
ices
Servicefaçade
Newservice
Dataservice
Enterpriseservice
Basicservice
SAP CompositeApplicationFramework (CAF)business objectmodeling andservicecomposition
CompositeBusinessProcessing forcollaborativeprocesses
© SAP 2007 / Page 6
SAP NetWeaver Developer Studio
Eclipse is Foundation
Best Class Java Development Tools (JDT)Best Class Tool Platform
OpenExtensible Plug-in conceptEnhancement possibility by 3rd party
Industry-StandardExcellent UI Strategy
Workbench (Perspectives)Excellent User Experience (SWT, Jface)
SAP NW CE 7.1 SP3 (available in Nov 2007) is based onEclipse 3.3WTP 2.0
© SAP 2007 / Page 7
SAP NetWeaver Developer Studio
Development and ModelingSupport for standard Java - J2EE 1.4 and Java EE 5 –
Full benefits of WTP tool set, e.g. O/R mapping from EJB todatabase
SAP-specific programming models (e.g. Web Dynpro Java)Modeling and Metadata is key (integrated code-oriented andgraphical editors)
Software Lifecycle ManagementEclipse integrates with NetWeaver development infrastructure (NWDI) and3rd party toolsPossibility to package content from various meta data sources into oneshippable application
© SAP 2007 / Page 8
SAP NetWeaver Developer Studio –Welcome Page
© SAP 2007 / Page 9
1. Eclipse Positioning in SAP‘s Product Strategy2. SAP Eclipse History3. Demo – SAP NetWeaver Developer Studio4. Eclipse related SAP Focus
4.1. Standard Java4.2. Business Process Modeling4.3. Web UI4.4. Development Infrastructure4.5. Modeling Infrastructure
5. Summary
Agenda
© SAP 2007 / Page 10
2000 – 2003
2000
SAP decides to supportJava
SAP‘s choice:Borland‘s JBuilder 4
Best Java / JEE IDEwith minimal SAPextensions via Borland‘sOpen Tools API
JBuilder Licenses(1000) forSAP internal usage
2001
Borland negotiationsOEM not an optionfor SAP
Open Tools API notsufficient, Sourceaccess needed
More SAP specificTools push ToolPlatform
First evaluations ofEclipse and NetBeans
2002
Decisionto go forEclipse
IBM negotiationsJ2EE Feature
ShipmentSAP Web AS 6.20
Modeling Infrastr.needed
Cooperation withTogethersoft (TS)
2003
SAP NetWeaverDeveloper Studiowith SAP Web AS6.30
Based onJ2EE 1.3Eclipse 2.1
SAP Features:WebDynproand J2EE with NWDI
Borland takes overTogetherSoft
© SAP 2007 / Page 11
Studio Architecture 2003
Eclipse Platform
J2SETools
UMLModeler
Model Abstraction Layer
J2EETools
WebDynproUI andDDIC
SAPDev
Infrastr.
© SAP 2007 / Page 12
2004 – 2007
2006
JEE 5 Preview
WTP adoption
2007
CompositionEnvironment shipped
Based onJEE 5Eclipse 3.1
Eclipse 3.3 with WTP2.0 in Q4
SAP signs theEclipse CommitterAgreement
Presented on SAPTeched
2004
SAP joins thenew EclipseFoundation asStrategicConsumer
Gold Sponsor atthe firstEclipseCon
2005
Additional SAPspecific features asCAF, WS, AdminTools …
Eclipse is acceptedDeveloper ToolPlatform in SAP‘sJava offering
© SAP 2007 / Page 13
Studio Architecture 2008
Eclipse Platform
J2SETools
Development and Modeling Infrastructure (MOIN)
JEE andWS ontop ofWTP
WebDynpro
UI
CAFBPMNDevInfrast.
Admin,Support,
VC inEclipse,
…
Eclipse for ABAP Developing and Modeling in evaluation
© SAP 2007 / Page 14
1. Eclipse Positioning in SAP‘s Product Strategy2. SAP Eclipse History3. Demo – SAP NetWeaver Developer Studio4. Eclipse related SAP Focus
4.1. Standard Java4.2. Business Process Modeling4.3. Web UI4.4. Development Infrastructure4.5. Modeling Infrastructure
5. Summary
Agenda
© SAP 2007 / Page 15
Demo: SAP NetWeaver Developer Studio
<?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" targetNamespace="ht<wsdl:types><xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" targetNamespace="http
<xsd:element name="CustomerRequest" type="CustomerId"></xsd:element><xsd:element name="CustomerResponse" type="Customer"></xsd:element><xsd:simpleType name="CustomerId"><xsd:restriction base="xsd:string"></xsd:restriction>
</xsd:simpleType><xsd:complexType name="Customer"><xsd:sequence><xsd:element name="CustomerId" type="CustomerId" minOccurs="0"></xsd:elem<xsd:element name="CustomerName" minOccurs="0"><xsd:simpleType><xsd:restriction base="xsd:string"><xsd:maxLength value="200"></xsd:maxLength>
</xsd:restriction></xsd:simpleType>
</xsd:element><xsd:element name="AddressStreet" type="cAddress" minOccurs="0"></xsd:ele
</xsd:sequence></xsd:complexType><xsd:complexType name="cAddress">
Import backend serviceCustomerBasicDataByIDQueryResponse_In
Define simple Service InterfaceCustomerRead
Implement CustomerRead Service
Model Web Dynpro UI usingCustomerRead Service
© SAP 2007 / Page 16
1. Eclipse Positioning in SAP‘s Product Strategy2. SAP Eclipse History3. Demo – SAP NetWeaver Developer Studio4. Eclipse related SAP Focus
4.1. Standard Java4.2. Business Process Modeling4.3. Web UI4.4. Development Infrastructure4.5. Modeling Infrastructure
5. Summary
Agenda
© SAP 2007 / Page 17
Eclipse relevant SAP Focus – Java Standards
Standard Java, JEE and PersistencyEclipse offers with JDT a superior Java Development EnvironmentWTP offers infrastructure and basic tools for Java EESAP implemented its Java EE tools on top of WTP and will increase itsinvestments to support WTPSAP strongly supports persistency historically and will contribute to DTP(MaxDB, DDIC)Eclipse with WTP, DTP and STP can become a solid foundation forEnterprise SOA tools by alignment of roadmaps and concepts and byaccelerating the progress in tool support for “commoditized Java devparadigms” beyond JDT
Assessment of SAP/Eclipse consolidation: done
© SAP 2007 / Page 18
Eclipse relevant SAP Focus – SAP ToolsComposition Perspective
Development and Modeling Environment Enterprise SOAApplications Extending Open Standards
BPM and Service CompositionWeb UIDevelopment InfrastructureModeling InfrastructureServer Support
© SAP 2007 / Page 19
1. Eclipse Positioning in SAP‘s Product Strategy2. SAP Eclipse History3. Demo – SAP NetWeaver Developer Studio4. Eclipse related SAP Focus
4.1. Standard Java4.2. Business Process Modeling4.3. Web UI4.4. Development Infrastructure4.5. Modeling Infrastructure
5. Summary
Agenda
© SAP 2007 / Page 20
Eclipse relevant SAP Focus –Business Process Management (BPM)
Process ComposerGraphical modeler based on BPMN
Eclipse-basedSupport key process concepts(workflow, event, task, context, roles,UI) throughout their lifecycleCombine human interaction andsystem integration in one model
Direct path from business view to processexecution
Nothing ‘lost in translation’Dynamic role-based viewsSingle active modelFlexible execution
Embedded in SAP NetWeaver CEIntegrated composition experienceCommon UI technologyService-based connectivity
ProcessComposer
ProcessDesk
Process Server
© SAP 2007 / Page 21
Eclipse relevant SAP Focus – BPMProcess Composer
© SAP 2007 / Page 22
CAF Modeler in Eclipse
© SAP 2007 / Page 23
Eclipse relevant SAP Focus –Service Composition
Service Composition
Composite Application Framework for modeling of Enterprise Services andBusiness ObjectsJava EE based framework following the Enterprise SOA programming modelTouch points with SCA and STP. SAP invests in SCA, participates in thespecification and monitors STPSupport of enterprise standards like CCTS data types system important forSAPSlow “Commoditization Process” for SOA paradigms
Assessment of SAP/Eclipse consolidation: on track
© SAP 2007 / Page 24
1. Eclipse Positioning in SAP‘s Product Strategy2. SAP Eclipse History3. Demo – SAP NetWeaver Developer Studio4. Eclipse related SAP Focus
4.1. Standard Java4.2. Business Process Modeling4.3. Web UI4.4. Development Infrastructure4.5. Modeling Infrastructure
5. Summary
Agenda
© SAP 2007 / Page 25
Eclipse relevant SAP Focus – Web UI
© SAP 2007 / Page 26
Eclipse relevant SAP Focus – Web UI
Web UISAP invented Web Dynpro, an Enterprise quality Web UI frameworkMVC based convenient Web UI Modeling with best support of Reuse,Personalization and flicker free performanceWeb Dynpro overcomes many deficiencies of Java EE UI techniques. It isa key element of SAP’s Java strategy and will coexist with other UItechnologies like JSF and JSPLeverage Eclipse UI tooling for Java EE UI support and seamlesslyintegrate with it, e.g. JSF Editor from WTP and embedding of JSPcomponents in Web Dynpro UIs
Assessment of SAP/Eclipse consolidation: done
© SAP 2007 / Page 27
1. Eclipse Positioning in SAP‘s Product Strategy2. SAP Eclipse History3. Demo – SAP NetWeaver Developer Studio4. Eclipse related SAP Focus
4.1. Standard Java4.2. Business Process Modeling4.3. Web UI4.4. Development Infrastructure4.5. Modeling Infrastructure
5. Summary
Agenda
© SAP 2007 / Page 28
“Software development is becoming software assembly, with componentssourced from around the world and based on a wide range of implementationtechnologies. …objective is to leverage and extend the Eclipse platform to makemixed-component development as efficient as plug-in development. The basicapproach is to introduce a project-agnostic way of describing a developmentproject’s component structure and dependencies, and to provide a mechanismfor materializing source and binary artifacts for a project of any degree ofcomplexity.”
This quote from Eclipse Buckminster FAQ could be a quote for a FAQ ofSAP Component Model.
– http://wiki.eclipse.org/Buckminster_Project_FAQ
Eclipse relevant SAP Focus –Development Infrastructure
© SAP 2007 / Page 29
Eclipse relevant SAP Focus –Development Infrastructure
© SAP 2007 / Page 30
Eclipse relevant SAP Focus –Development Infrastructure
Development Infrastructure
SAP invented the SAP Component Model to support software structuringand reuse as well as software production and assemblingSAP NetWeaver Development Infrastructure (NWDI) is built around SAPCM with full-fledged Source Code Management System, Automated Buildand a Configuration and Change Management SystemSAP Tools are closely integrated with the SAP Component Model and theDevelopment InfrastructureSAP is monitoring upcoming component model standards and check them forconsolidation. Buckminster and STP(SCA) might be the right direction
Assessment of SAP/Eclipse consolidation: starting
© SAP 2007 / Page 31
1. Eclipse Positioning in SAP‘s Product Strategy2. SAP Eclipse History3. Demo – SAP NetWeaver Developer Studio4. Eclipse related SAP Focus
4.1. Standard Java4.2. Business Process Modeling4.3. Web UI4.4. Development Infrastructure4.5. Modeling Infrastructure
5. Summary
Agenda
© SAP 2007 / Page 32
Eclipse relevant SAP Focus –Modeling Infrastructure
Modeling Infrastructure
SAP developed a Modeling Infrastructure (MOIN)(Enterprise) design-time repository that manages modeling contentBased on standards like MOF, JMI, XMI, OCLPlatform independent, can run on Eclipse, on a JEE server, and standaloneenvironments
Frameworks and tools on top of MOINGraphical Framework for development of graphical modeling toolsTool Generation Framework (for generation form-based Editors/Viewers)Graphical tool for editing of MOF Meta-models (that also serves as showcase forMOIN and other frameworks)
© SAP 2007 / Page 33
MOIN – MOF Editor
© SAP 2007 / Page 34
Eclipse relevant SAP Focus –Modeling Infrastructure
Modeling Infrastructure and Server SupportSAP supports an Enterprise Ready Modeling Infrastructure(MOIN) based on MOF 1.4Enterprise Readiness means
Consistency of a huge and highly-connected modelnetwork (constraints, refactoring, concurrent changes)Information system on huge amounts of modeling contentwith efficient query capabilities (Server Scenario with DBsupport)Eclipse, JEE Server and Standalone Build scenario to besupported
Overlap with EMF, EMFT and GMF. Consolidation is of highvalue and SAP ready to invest in that
Assessment of SAP/Eclipse consolidation: starting
© SAP 2007 / Page 35
1. Eclipse Positioning in SAP‘s Product Strategy2. SAP Eclipse History3. Demo – SAP NetWeaver Developer Studio4. Eclipse related SAP Focus
4.1. Standard Java4.2. Business Process Modeling4.3. Web UI4.4. Development Infrastructure4.5. Modeling Infrastructure
5. Summary
Agenda
© SAP 2007 / Page 36
Summary SAP Eclipse Experience
The SAP Eclipse Story - SummaryExcellent Java development environment and best tool platform with hugeacceptance and market momentum. The right decision in 2002SAP NetWeaver Developer Studio is based on Eclipse.It is THE fundamental Design Time Environment in SAP’s important productSAP NetWeaver Composition EnvironmentEclipse is driver and enabler for tool consolidation in SAP’s JavaDevelopment and Modeling tools areaCurrent focus for SAP contribution is WTP and DTP. The SAP Memoryanalyzer is planned as contribution.Modeling and Development Infrastructure are key for SAP. SAP’s challengeis to align their Eclipse specific implementations to upcoming CommunityStandards. EMF, EMFT, Buckminster, STP, Team API, RCP are verypromising projects.Meritocracy is key and it is less about money and market support than aboutdevelopment engagement. Therefore SAP considers Strategic Consumermodel as honors towards Eclipse. SAP will increase its contributioninvestments.SAP loved to see fast commoditization (e.g. JEE), but the Business model…
© SAP 2007 / Page 37
Thank you!