Yu-Nong Zhang, Roland Hamm, SAP AG

Transcription

1 SAP NetWeaver Java Development Infrastructure (aka NWDI) Yu-Nong Zhang, Roland Hamm, SAP AG

2 NWDI - Inhouse Experience Demo: Migrating an J2EE application into NetWeaver Development Infrastructure

3 NWDI - Inhouse Experience Demo: Migrating an J2EE application into NetWeaver Development Infrastructure

4 Requirements on a common SAP wide development infrastructure 1. One manageable infrastructure for all SAP development locations 2. Enable Source Code delivery, enable customer modification adjustment and build support on customer side 3. Increase effectiveness of development process by componentization and software layering 1. Reduction in repair times and in the propagation of error corrections 2. Reduce impact of ongoing development in lower SW layers to development projects on higher SW layers 4. Development of Enterprise Service Architecture (ESA) based applications requires strong componentization and dependency management support SAP AG 2004, Title of Presentation / Speaker Name / 4

5 The Self Service Project in ERP 2004 Existing products were already out in the market High volume product (number of users in the millions) designed and developed More user groups ESS moves to every desktop and even into occasional users area (Kiosksystems) Technology: a new generation Replacement of the ITS by WebDynpro Simplification of the development landscape by use of the NWDI New standard in portal integration with EP 6.0 Reimplementation Replacement of a proven but aging product: reimplement the most popular services according to usage Up to 50 services such as Time Recording (CATS), Leave Request, Remuneration statement, Travel expenses, Headcount Planning Localized versions of Personal information scenarios (address, bank, family, ) for more than 30 country versions About 60 developers in 4 different locations: Walldorf, Bangalore, Palo Alto, Sophia Antipolis SAP AG 2004, Title of Presentation / Speaker Name / 5

6 Development Infrastructure Big Picture is Standards based J2EE WebDAV, DeltaV Repository standards for accessing and versioning arbitrary development objects supported by all major development tool vendors Developer frontend plugged into Eclipse (Open Source development tool) offers Substantial savings in Business Application Development Supports various parts of Business Applications beyond pure code like DB definitions, UI definitions, Web Services... will support all SAP NetWeaver Authoring Environments (PDK, MDK, IDE,...) Supports strong and well organized reuse between many developers Central administration frees developers from technical details is Adaptive to SAP AND customer needs from simple 2 developer projects to huge projects with hundreds of developers in multiple layers and mixed with SAP modifications SAP AG 2004, Title of Presentation / Speaker Name / 6

7 Overview: Java Development Infrastructure I < Local Installation on Developer s PC > < Central Infrastructure > SAP NetWeaver Developer Studio Component Model Local File System Local J2EE Engine SAP AG 2004, Title of Presentation / Speaker Name / 7 Component Build Service (CBS) Design Time Repository (DTR) Name Server Change Management Service (CMS) System Landscape Directory (SLD) Deploy Run Run Time J2EE Systems

8 How Self Services use the JDI Stepwise introduction of the NWDI building blocks Start with IDE and DTR in May 2003 Incl. a nightbuild on a central server Use of proprietary and hand-run scripts to feed the nightbuild server with the recent Self Service sources Installation of central test servers in September 2003 Still used proprietary and hand-run scripts to build and feed the test servers with the nightbuild archives Added CBS to achieve a central component build in January 2004 Developers can sync component archives rather than sources which have to be built locally Get rid of separate build step: component archives could be deployed to test server directly via proprietary script Installation of CMS in March 2004 Release of checked-in activities to ensure quality process Consolidate to production to enable final assembly Remaining manual process planned automation by end of 2004 Automatically deploy CBS-archives via CMS into system landscape SAP AG 2004, Title of Presentation / Speaker Name / 8

9 With NWDI achievable Goals achievable by common utilization of NWDI: Increase effectiveness of development cycle: shortened bug-fixing cycles, de-coupling and resolving of cyclic code dependencies Guide and Manage each single developer: easy access, build on demand, early integration tests Consistent deployment and propagation of development changes in-house and into customer shipment Strong support for ESA based application development (component model, dependency control, sw layering, propagation management) SAP AG 2004, Title of Presentation / Speaker Name / 9

10 With NWDI achievable Goals achievable by common utilization of NWDI: Increase effectiveness of development cycle: shortened bug-fixing cycles, de-coupling and resolving of cyclic code dependencies Guide and Manage each single developer: easy access, build on demand, early integration tests Consistent deployment and propagation of development changes in-house and into customer shipment Strong support for ESA based application development (component model, dependency control, sw layering, propagation management) SAP AG 2004, Title of Presentation / Speaker Name / 10

11 Componentization and de-coupling Enhanced build services On demand by the developer Using formally known dependencies Mandatory central test build Reduction in repair times and in the propagation of error corrections Layered development Find correct sources The Component model with its multilevel visibility and formally known dependencies Together with an automated transport including approval steps Allows you to define and operate multiple development layers Reduced number of developers in one system Increased stability due to transport of versions with proven quality Basic Components Central test and release objects Central build Check-in changed files Local build, local test Change development objects Find correct foreign libraries Copy & checkout source files Feaure Components Basic Components Application Components Feature Components Basic Components SAP AG 2004, Title of Presentation / Speaker Name / 11

12 Componentization of the Self Services Self Service applications make use of software components from 3 layers TECHDEV: Basis functionality such as J2EE, WebDynpro etc. PCUI_GP: Generic Self Service components like Floorplan Manager, Utilities, ESS, MSS : all Self Services applications Layering of components Basis layer with different release schedules and completely decoupled development Layer PCUI_GP contains the Self Service runtime and utilities on which all Self Service applications are based on same release schedule as Self Service development Only limited number (5-10) of developers with own access profile comparably to ABA layer in R/3 world Application Layer (ESS/MSS) for Self Service development all Self Service developers only stable versions of Basis and PCUI_GP layer through use of compiled and activated archives instead of rebuilding the most recent sources SAP AG 2004, Title of Presentation / Speaker Name / 12

13 ADMINISTRATION / QM DEVELOPMENT ADMINISTRATION Development process with NWDI Product and Application define Track & Dev. Config. import Development release SL Change Mgmt. prepare Delivery define Next Release SAP AG 2004, Title of Presentation / Speaker Name / 13 Design Applications 1. PPMS/SLD: Define software to be developed Support Development Process 2. CMS: Define development system landscape 3. Dev. Studio/Component Model: Edit and build development objects 4. CMS: Propagation of SC s into next development stages, quality assurance, and assembly using the Change Management Service Support of shipment and Software maintenance 5. CMS: Deliver SCs and patches 6. CMS: For the next SC release define a new code line

14 The Component Model Elements Development Objects Stored as versioned files in the source repository (DTR) Product version i.e. Web Dynpro view, table definition, Java source file, *.jsp, ejb, Development Components (DCs) Development and build units Group development objects without overlapping Software Components (SCs) Delivery and installation units (like e.g. HR in ABAP) * * SC version 1 * DC version 1 1 0/1 Release Group development components without overlapping Own the release definition * DO version Products Overlapping selections of software components SAP AG 2004, Title of Presentation / Speaker Name / 14

15 System Landscape Directory Products and SC s PPMS Synchronize, XML Master Component Repository Component Types Landscape Patterns Possible Combinations Update SAP SAP AG 2004, Title of Presentation / Speaker Name / 15

16 Component Model - Features Encapsulation/Decoupling Reusable elements explicitly declared public Access control lists restrict component usage Nested components Controlling Dependencies Explicit declaration of dependencies Checked by build process Build Support Predefined build templates for component types Generic Model Independent of technology / programming language Tools Fully integrated in SAP NetWeaver developer studio DC B DC A DC C usage dependency ppa ppx DC X ppy DC Y SAP AG 2004, Title of Presentation / Speaker Name / 16

17 SCs and DCs of the Self Services (ERP 2005) Software Components ESS - Employee Self Services ~ 200 Development Components ~ 220 Self Service Applications ~ 1000 WebDynpro components PCUI_GP - Reusable parts for all self service applications 9 Development Components ~ 50 WebDynpro Components MSS Manager Self Services ~ 70 Development Components ~ 80 Self Service Applications ~ 400 WebDynpro components SAP AG 2004, Title of Presentation / Speaker Name / 17

18 Experiences when working with SCs and DCs Granularity / size of DCs during development and build time General Rule for Granularity: 1 DC normally reflects 1 Self Service application Reduce local build time DCs with more than 10 WebDynpro components have proven to need more than 2 minutes build time on a developer s workstation Enable working in teams Increasing number of components results in several persons working on the same DC No use of nested DCs Did not reduce build time Still all sub-dcs needed to be compilable as only parent-dcs can be deployed no advantage in comparison with parallel DCs Software Components Size of SC ESS already close to 200 MB With implementation of every Support Package, customers have to download this from SAPNet Service Marketplace Deployment of whole SC on J2EE takes up to 3 hours Deployment of single DCs from a support package not feasible Whole SC has to be deployed to ensure consistency SAP AG 2004, Title of Presentation / Speaker Name / 18

19 Shipment of source code to customers I ~ 90 % of the Self Service customers do modifications on the scenarios Adapt terminology and other texts Change the screen display a field on the screen (where it has not been before) remove the field from the screen (where is has been before) change the position or any other property of the field on the screen (where it has been before, whether it was read-only or editable, etc.) Adapt dialog process flow (e.g. omit review screen) Adapt properties of screen elements On various UI elements change properties like enabled, length, read-only With NetWeaver04 there are no possibilities for modification-free screen adaptation, only for text adaptation Shipment of sources was necessary to enable this as a modification Self Services are the pilot shipping non-abap sources to customers SAP AG 2004, Title of Presentation / Speaker Name / 19

20 Shipment of source code to customers II Consequences for SAP development No restrictions in comparison with other development Consequences on customer site Customers need to install and setup a full NWDI When applying support packages, conflicts need to be detected and resolved Restrictions when modifying sources Patches are only available as archives, these can not be applied on modified sources; only Support Packages contain sources Manual corrections required Rudimentary tool support for conflict resolution Merge Tool to detect and compare versions (SAP customer) Restrictions on tool side No automatic merge of conflicts, e.g. like SCWB, SPAM, SPAU,... in R/3 world SAP AG 2004, Title of Presentation / Speaker Name / 20

21 With NWDI achievable Goals achievable by common utilization of NWDI: Increase effectiveness of development cycle: shortened bug-fixing cycles, de-coupling and resolving of cyclic code dependencies Guide and Manage each single developer: easy access, build on demand, early integration tests Consistent deployment and propagation of development changes in-house and into customer shipment Strong support for ESA based application development (component model, dependency control, sw layering, propagation management) SAP AG 2004, Title of Presentation / Speaker Name / 21

22 ADMINISTRATION / QM DEVELOPMENT ADMINISTRATION Development process with NWDI Product and Application define Track & Dev. Config. import Development release SL Change Mgmt. prepare Delivery define Next Release SAP AG 2004, Title of Presentation / Speaker Name / 22 Design Applications 1. PPMS/SLD: Define software to be developed Support Development Process 2. CMS: Define development system landscape 3. Dev. Studio/Component Model: Edit and build development objects 4. CMS: Propagation of SC s into next development stages, quality assurance, and assembly using the Change Management Service Support of Shipment and Software Maintenance 5. CMS: Deliver SCs and patches 6. CMS: For the next SC release define a new code line

23 Guide and Manage each single Developer SAP AG 2004, Title of Presentation / Speaker Name / 23

24 Self Service development process with NWDI Support Development Process Development configuration in the IDE can be downloaded from a central server This ensures same development landscape for all developers in all our 4 different locations no need for specific personal adjustments Support of Shipment and Software Maintenance Support package process still includes manual steps for translation Generating the translation pool (in an R/3 translation system) Retrofit of the translated.xlf files to DTR SAP AG 2004, Title of Presentation / Speaker Name / 24

25 A typical Self Service developer s workstation Local installation of NetWeaver Developer Studio (IDE) J2EE engine incl. MaxDB No use of a central J2EE engine to avoid conflicts when several developers are changing the same DC at the same time Concurrent debugging is possible in the meantime: A central J2EE will be used for support landscape in the near future Hardware requirements: 2GB RAM, 2,4 GHz CPU Central use of CBS CMS to get archives from Basis development, PCUI_GP to build the checked-in sources centrally to release the activities after successful activation Test server contains all activated activities Use of Windows Terminal Service (WTS) for IDE versions in Support Package Landscape SAP AG 2004, Title of Presentation / Speaker Name / 25

26 With NWDI achievable Goals achievable by common utilization of NWDI: Increase effectiveness of development cycle: shortened bug-fixing cycles, de-coupling and resolving of cyclic code dependencies Guide and Manage each single developer: easy access, build on demand, early integration tests Consistent deployment and propagation of development changes in-house and into customer shipment Strong support for ESA based application development (component model, dependency control, sw layering, propagation management) SAP AG 2004, Title of Presentation / Speaker Name / 26

27 Development Track The System landscape for development of a Software component Development Configuration Consolidation Configuration SLD Workspaces Change Request Workspaces Component A Version i 3 Component Pool Buildspace Buildspace Central Development System Consolidation System Test System Production System 1 Activate 2 Release 1 Import 2 Assembly 3 Approval < Developer > < Administrator > SAP AG 2004, Title of Presentation / Speaker Name / 27

28 Change Management Service (CMS) Landscape Configurator Domain Track Track Track Track Track Track Dev. Config. DEV Dev. Config. CONS SC Development Configuration DTR-Workspaces: Track RTS DEV RTS CONS RTS QA RTS PROD CBS Buildspace Compartment Workspace Transport Studio Source Track Target Track DEV Workspaces build Buildspace Propagation CONS Workspaces build Buildspace Assembly SC Propagation / Transport DEV Workspaces build Buildspace CONS Workspaces build Buildspace SC deploy deploy deploy deploy deploy deploy RTS DEV RTS CONS RTS QA RTS PROD RTS DEV RTS CONS RTS QA RTS SAP AG 2004, Title of Presentation / Speaker Name / 28

29 SAP inhouse: JDI Landscape Overview Landscape Directory Nameserver Landscape Directory Nameserver SLD JDI Development SLD TechDev and Application Development Staging Public/Test Preprod. Production DTR DTR DTR DTR CBS CBS CBS CBS CBS CBS CBS CBS CBS CBS CBS CBS CMS CMS CMS CMS JDI Tests LDAP test Sandbox for Test Projects LDAP prod User Management User Management JSS test JSS prod SAP AG 2004, Title of Presentation / Speaker Name / 29

30 SAP inhouse: JDI Landscape Walldorf Basis Development Application Development Staging Public/Test Preprod. Production Final Assembly DTR DTR 8000 DTR 8100 DTR 2100 DTR 2000 DTR 4000 DTR 6000 CBS CMS CMS 8000 SLD 8000 CBS8000 CBS8100 CBS8010 CBS8012 CBS2100 CMS 2100 CBS2000 CBS2002 CBS2004 CBS2006 CBS2008 CBS4000 DTR 4010 CBS6002 LDAP test WDF JSS test JSS prod LDAP prod WDF SLD SAP Name Server CMS MAIN SAP AG 2004, Title of Presentation / Speaker Name / 30

31 AGENDA: Delivery ADMINISTRATION DEVELOPMENT ADMINISTRATION Development Infrastructure Track define define Development Configuration import Development release SL Change Management prepare Delivery define Next Release 1. SLD: Define software to be developed Define a product Define one or more software components (SCs) that form the product 2. CMS: Define development landscape Define a track for the specific release of the SC Development configurations are generated for each development state of an SC (DEV or CONS) 3. Dev. Studio: Edit and build development objects Use the SAP NetWeaver Developer Studio with access to the SAP NW JDI for all development projects Release objects for further processing by QM/Admin. 4. CMS: Define further use of SCs Transport into next dev. steps, quality assurance, and assembly using the Change Management Service 5. CMS: Deliver Software Components and patches Deliver software component versions building products as well as support packages 6. CMS: For the next SC release define a new track SAP AG 2004, Title of Presentation / Speaker Name / 31

32 Component Model in Delivery and Maintenance Products P1 P2 Installation / Upgrade Software Components S1 S2 Support Packages D6 D8 D11 Development Components D4 D5 D7 D9 D10 Patches D1 D2 D3 SAP AG 2004, Title of Presentation / Speaker Name / 32

33 Components and Versions: Maintenance Software Maintenance from the customer s point of view is organized in three layers A Release is a full delivery of SCs providing extra features and enhancements defines new Support Intervals Delivery of new functions and new user interfaces A Support Package is a full delivery of an SC bundling bug fixes should not require new trainings for the end users should be fully compatible with the original delivery of the SC does not extend the Support Interval A Patch is a full delivery of a DC providing a new Bug Fix SAP AG 2004, Title of Presentation / Speaker Name / 33

34 Shipment to customers Unique problem for business application software vendors: Customers need to modify standard software Need delivery format including all types of executables, build archives and sources Need complete build environment Need concepts for handling of modifications SAP Customer Applications Applications With JDI NetWeaver NetWeaver jars, java sources, dictionary, NetWeaver JDI package format enables shipment of various software types (e.g. jars, java sources and dictionary) Build services at customer site allow recompilation of modified sources A source code control system based on distributed versioning Enables controlled source delivery between different locations (e.g. SAP customer) Allows conflict resolution between customer modifications and new SAP deliveries SAP AG 2004, Title of Presentation / Speaker Name / 34

35 SAP Delivery into Customer Landscape ( like Transport between Tracks) SAP Customer Track Customer Track Cust. Track 2 Dev. Configuration SC_Dev Dev. Configuration SC_Cons 1 Workspaces Change Request Workspaces SAP SC Version i 2 Modified SC Version j Buildspace Buildspace Central Development System Consolidation System Test or Production System SAP AG 2004, Title of Presentation / Speaker Name / 35

36 NWDI - Inhouse Experience Demo: Migrating an J2EE application into NetWeaver Development Infrastructure

37 Demo Scenario SUN RI 2005Q1 Web Container Employee,jsp EJB Container Client (Web Browser) SAP J2EE Engine 6.40 Web Dynpro Container RT Employee,jsp Employee EJB Container A J2EE application on top of SUN s reference implementation with: A JSP page as presentation layer, A stateless session bean, An entity bean with container-managed persistence, A DB table. EmployeeServiceBean EmployeeBean EmployeeServiceBean EmployeeBean Tranfering this application into the SAP J2EE Engine using NWDI. EDM_Employee EDM_Employee Pepping up the UI with Web Dynpro. Database Database SAP AG 2004, Title of Presentation / Speaker Name / 37

38 Developer 1: Pure J2EE application (IDE) 1. Create database table using Java Dictionary (Done) Define table columns Expose the table as Public Part for compilation purpose 2. Transfer the existing J2EE application into NWDI Create DCs for EJB, Web and EAR modules Copy sources Adapte vendor-specific deployment descriptors Re-define the Public Part ejb-client Reserve application context root Reserve and add data source alias to the application Local build and test 3. Check-in sources, activate changes and release the activity for transport SAP AG 2004, Title of Presentation / Speaker Name / 38

39 Developer 2: Web Dynpro UI (IDE) 1. Create Web Dynpro application (Done, but not buildable yet!) 2. Reference the EJB module for compile time usage 3. Re-build the Web Dynpro application and finish up the work SAP AG 2004, Title of Presentation / Speaker Name / 39

40 Project lead: Transport, tests and release (CMS) 1. Import change requests into the consolidation system 2. Integration test 3. Assembly and quality test 4. Release the software for shipping SAP AG 2004, Title of Presentation / Speaker Name / 40

41 Questions? Q&A SAP AG 2004, Title of Presentation / Speaker Name / 41

42 Copyright 2004 SAP AG. All Rights Reserved No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iseries, pseries, xseries, zseries, z/os, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, and Informix are trademarks or registered trademarks of IBM Corporation in the United States and/or other countries. Oracle is a registered trademark of Oracle Corporation. UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc. HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C, World Wide Web Consortium, Massachusetts Institute of Technology. Java is a registered trademark of Sun Microsystems, Inc. JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. MaxDB is a trademark of MySQL AB, Sweden. SAP, R/3, mysap, mysap.com, xapps, xapp, SAP NetWeaver and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary. These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. SAP AG 2004, Title of Presentation / Speaker Name / 42

43 Copyright 2004 SAP AG. Alle Rechte vorbehalten Weitergabe und Vervielfältigung dieser Publikation oder von Teilen daraus sind, zu welchem Zweck und in welcher Form auch immer, ohne die ausdrückliche schriftliche Genehmigung durch SAP AG nicht gestattet. In dieser Publikation enthaltene Informationen können ohne vorherige Ankündigung geändert werden. Die von SAP AG oder deren Vertriebsfirmen angebotenen Softwareprodukte können Softwarekomponenten auch anderer Softwarehersteller enthalten. Microsoft, Windows, Outlook, und PowerPoint sind eingetragene Marken der Microsoft Corporation. IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iseries, pseries, xseries, zseries, z/os, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, und Informix sind Marken oder eingetragene Marken der IBM Corporation in den USA und/oder anderen Ländern. Oracle ist eine eingetragene Marke der Oracle Corporation. UNIX, X/Open, OSF/1, und Motif sind eingetragene Marken der Open Group. Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, und MultiWin sind Marken oder eingetragene Marken von Citrix Systems, Inc. HTML, XML, XHTML und W3C sind Marken oder eingetragene Marken des W3C, World Wide Web Consortium, Massachusetts Institute of Technology. Java ist eine eingetragene Marke von Sun Microsystems, Inc. JavaScript ist eine eingetragene Marke der Sun Microsystems, Inc., verwendet unter der Lizenz der von Netscape entwickelten und implementierten Technologie. MaxDB ist eine Marke von MySQL AB, Schweden. SAP, R/3, mysap, mysap.com, xapps, xapp, SAP NetWeaver und weitere im Text erwähnte SAP-Produkte und - Dienstleistungen sowie die entsprechenden Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und anderen Ländern weltweit. Alle anderen Namen von Produkten und Dienstleistungen sind Marken der jeweiligen Firmen. Die Angaben im Text sind unverbindlich und dienen lediglich zu Informationszwecken. Produkte können länderspezifische Unterschiede aufweisen. In dieser Publikation enthaltene Informationen können ohne vorherige Ankündigung geändert werden. Die vorliegenden Angaben werden von SAP AG und ihren Konzernunternehmen ( SAP-Konzern ) bereitgestellt und dienen ausschließlich Informationszwecken. Der SAP-Konzern übernimmt keinerlei Haftung oder Garantie für Fehler oder Unvollständigkeiten in dieser Publikation. Der SAP-Konzern steht lediglich für Produkte und Dienstleistungen nach der Maßgabe ein, die in der Vereinbarung über die jeweiligen Produkte und Dienstleistungen ausdrücklich geregelt ist. Aus den in dieser Publikation enthaltenen Informationen ergibt sich keine weiterführende Haftung. SAP AG 2004, Title of Presentation / Speaker Name / 43