Nwdi Overview And Features

5,964 views

Published on

This presentation is intended to give overview of NWDI and its features

0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
5,964
On SlideShare
0
From Embeds
0
Number of Embeds
35
Actions
Shares
0
Downloads
136
Comments
0
Likes
2
Embeds 0
No embeds

No notes for slide
  • Core message: Microsoft and SAP have had a partnership for more than 11 years Comments from MS and SAP Presidents: “ More than any other company we work with, SAP has strong influence on our product development, and we see that growing in the future “ Bill Gates, Chairman and Chief Software Architect , Microsoft „ This relationship consists to 95% of partnership and 5% of competition.“ Henning Kagermann, CEO SAP AG (CeBIT, Germany 2003) Microsoft has been using SAP as its core ERP system since 1995 (one single global instance for more than 57’000 employees) – MS runs SAP on Windows Server 2003 and SQL Server 2005 Core message: Microsoft and SAP have had a partnership for more than 11 years Comments from MS and SAP Presidents: “ More than any other company we work with, SAP has strong influence on our product development, and we see that growing in the future “ Bill Gates, Chairman and Chief Software Architect , Microsoft „ This relationship consists to 95% of partnership and 5% of competition.“ Henning Kagermann, CEO SAP AG (CeBIT, Germany 2003) Microsoft has been using SAP as its core ERP system since 1995 (one single global instance for more than 57’000 employees) – MS runs SAP on Windows Server 2003 and SQL Server 2005 Core message: Microsoft and SAP have had a partnership for more than 11 years Comments from MS and SAP Presidents: “ More than any other company we work with, SAP has strong influence on our product development, and we see that growing in the future “ Bill Gates, Chairman and Chief Software Architect , Microsoft „ This relationship consists to 95% of partnership and 5% of competition.“ Henning Kagermann, CEO SAP AG (CeBIT, Germany 2003) Microsoft has been using SAP as its core ERP system since 1995 (one single global instance for more than 57’000 employees) – MS runs SAP on Windows Server 2003 and SQL Server 2005 Core message: Microsoft and SAP have had a partnership for more than 11 years Comments from MS and SAP Presidents: “ More than any other company we work with, SAP has strong influence on our product development, and we see that growing in the future “ Bill Gates, Chairman and Chief Software Architect , Microsoft „ This relationship consists to 95% of partnership and 5% of competition.“ Henning Kagermann, CEO SAP AG (CeBIT, Germany 2003) Microsoft has been using SAP as its core ERP system since 1995 (one single global instance for more than 57’000 employees) – MS runs SAP on Windows Server 2003 and SQL Server 2005
  • Microsoft have been working together since 1993 to make sure SQL and Windows work with SAP
  • Nwdi Overview And Features

    1. 1. NW 7.0 NWDI – Netweaver Development Infrastructure Anandha Krishnan R SAP NetWeaver Technology Consultant Kaar Technologies
    2. 2. Netweaver Development Infrastructure Motivation Design Time Repository Component Build Service Change Management Service
    3. 3. Netweaver Development Infrastructure Motivation Design Time Repository Component Build Service Change Management Service
    4. 4. Delivery Process – Shipment to Customer <ul><li>Challenge for Application Software Vendors – Customer Needs to change the Standard Software </li></ul><ul><ul><li>Need Complete build environment </li></ul></ul><ul><ul><li>Need the delivery format including all type of executables and sources </li></ul></ul><ul><ul><li>Need Concepts for handling of modifications </li></ul></ul><ul><li>With NWDI </li></ul><ul><ul><li>NWDI Package format enables the shipment of various software types (e.g. jars, java sources and dictionary) </li></ul></ul><ul><ul><li>Build Services option allows recompilation of modified sources </li></ul></ul><ul><ul><li>Source Code control system based on distributed versioning </li></ul></ul><ul><ul><ul><li>Enables controlled source delivery between different locations </li></ul></ul></ul><ul><ul><ul><li>Allows conflict resolution between customer modifications and new SAP deliveries </li></ul></ul></ul>
    5. 5. Development Cycle in Web AS ABAP <ul><li>Dev -> Qas -> Prod </li></ul><ul><li>Common Transport Directory or Local Transport Directory </li></ul><ul><li>The Objects will be available in the form of data file and control file. </li></ul>
    6. 6. Development with NWDI
    7. 7. Development Infrastructure – Learning from ABAP
    8. 8. Netweaver Development Infrastructure <ul><li>Is standards based </li></ul><ul><ul><li>J2ee </li></ul></ul><ul><ul><li>WebDav, DeltaV </li></ul></ul><ul><ul><ul><li>Repository standards for accessing and versioning arbitrary development object </li></ul></ul></ul><ul><ul><ul><li>Supported by all development tool vendors </li></ul></ul></ul><ul><ul><li>Developer front-end plugged into eclipse (open source Development tool) </li></ul></ul><ul><li>Offers Substantial savings in business application Development </li></ul><ul><ul><li>Supports various parts of Business Applications beyond pure code like DB definitions, UI definitions, web services… </li></ul></ul><ul><ul><ul><li>Supports all SAP Netweaver Authoring Environments (PDK, MDK, IDE,…) </li></ul></ul></ul><ul><ul><li>Supports strong and well organized reuse between many developers </li></ul></ul><ul><ul><li>Central administration frees developers from technical details </li></ul></ul><ul><li>Is Adaptive to customer needs </li></ul><ul><ul><li>From simple projects to huge projects </li></ul></ul><ul><ul><li>Support projects with hundreds of developers in multiple layers and mixed with SAP modifications </li></ul></ul>
    9. 9. Components of NWDI
    10. 10. Design Time Repository Component Build Service Change Management Service Motivation Netweaver Development Infrastructure
    11. 11. DTR – Goals and Basics <ul><li>Distributed concurrent development </li></ul><ul><ul><li>Distributed Versioning that spans repositories </li></ul></ul><ul><ul><li>Conflict detection </li></ul></ul><ul><ul><li>Support for conflict resolution </li></ul></ul><ul><li>Open standard </li></ul><ul><ul><li>Based on open standard – WebDAV, DeltaV </li></ul></ul><ul><li>Files and folders </li></ul><ul><ul><li>DTR has knowledge on files and folders </li></ul></ul><ul><ul><li>No knowledge on objects of programming model </li></ul></ul><ul><ul><li>(classes, tables, screens) </li></ul></ul><ul><li>Check in/check out model </li></ul><ul><ul><li>Files are checked out from DTR and modified “Offline” </li></ul></ul><ul><ul><li>After correction the files are checked in again </li></ul></ul>
    12. 12. DTR - Architecture
    13. 13. DTR - Architecture <ul><li>DTR Client </li></ul><ul><ul><li>SAP NetWeaver Development Studio – Eclipse based client to perform common tasks with DTR </li></ul></ul><ul><ul><li>Command line client – Performs Administrative task’s </li></ul></ul><ul><ul><li>Web browser – Access to DTR contents using web browser or WebDAV enabled client </li></ul></ul><ul><li>DTR Server </li></ul><ul><ul><li>Handles file versioning </li></ul></ul><ul><ul><li>Uses relational database to store files </li></ul></ul><ul><ul><li>Resources are accessed in context of workspace </li></ul></ul><ul><ul><li>Versions are managed in context of activities </li></ul></ul><ul><li>Integration </li></ul><ul><ul><li>Data transferred between client and server using WebDAV and DeltaV+ </li></ul></ul>
    14. 14. DTR – Integration Conflict <ul><li>Same file was changed in two workspace concurrently </li></ul><ul><li>The changes are propagated and meet in workspace </li></ul><ul><li>Conflict is detected and stored </li></ul>
    15. 15. DTR – Conflict resolution <ul><li>Conflict resolution </li></ul><ul><ul><li>Create new merge version </li></ul></ul><ul><ul><li>Accept Current Version </li></ul></ul><ul><ul><li>Accept Integrated Version </li></ul></ul><ul><li>Merges </li></ul><ul><ul><li>Are propagated </li></ul></ul><ul><ul><li>Conflict can be resolved by integration </li></ul></ul>
    16. 16. DTR – Distributed Versioning <ul><li>Propagation of changes between repositories </li></ul><ul><li>Distributed versioning and conflict resolution </li></ul><ul><ul><li>Changes are recognized as versions of same file </li></ul></ul><ul><ul><li>Imported versions are correctly placed into version graph </li></ul></ul><ul><ul><li>No risk of overwriting changes in target repository </li></ul></ul><ul><li>Allows upgrade of source code modified by customers </li></ul>
    17. 17. DTR – User Management
    18. 18. Netweaver Development Infrastructure Motivation Design Time Repository Component Build Service Change Management Service
    19. 19. Component Based Development <ul><li>CBS </li></ul><ul><ul><li>Is responsible for building the sources stored in DTR </li></ul></ul><ul><ul><li>Provides Central Build environment </li></ul></ul><ul><ul><li>Automated Build Process </li></ul></ul><ul><ul><li>Build process happens in Incremental fashion </li></ul></ul><ul><ul><li>Successfully built DC’s are put into DTR and will be ready for release. </li></ul></ul><ul><ul><li>The source state will be changed to Active </li></ul></ul><ul><ul><li>Activation concept guarantees consistent build environment </li></ul></ul>
    20. 20. CBS Usage <ul><li>CBS is J2EE based database application </li></ul><ul><li>CBS is accessed with </li></ul><ul><ul><li>SAP NetWeaver Developer Studio: Activation view and Activation Request view are integrated into Developer Studio </li></ul></ul><ul><ul><li>The CBS Web User Interface for CBS Administration </li></ul></ul><ul><ul><li>Command line tools: There is a dedicated command line tool for working with the CBS </li></ul></ul>
    21. 21. CBS - Architecture
    22. 22. CBS Architecture & Integration with other Services <ul><li>CBS Request Receiver </li></ul><ul><ul><li>J2EE Application which accepts request from clients </li></ul></ul><ul><ul><li>Places in request queue and assigns request number </li></ul></ul><ul><ul><li>Execution later done by CBS J2EE Service </li></ul></ul><ul><ul><li>User can Query the process status </li></ul></ul><ul><li>CBS Database </li></ul><ul><ul><li>Contains the request queue and the archive pool with the built and imported archives </li></ul></ul><ul><ul><li>Contains data on the buildspaces, the activated development components and the activation state of activities in the DTR. </li></ul></ul><ul><li>CBS J2EE Service </li></ul><ul><ul><li>Service of the J2EE Engine, which implements the actual build engine </li></ul></ul><ul><ul><li>Takes the requests from the request queue and starts a build task for every request to execute the request </li></ul></ul><ul><ul><li>Can execute Several build task in parallel </li></ul></ul><ul><ul><li>Several server nodes with individual CBS J2EE services in one J2EE cluster </li></ul></ul>
    23. 23. Cont., <ul><li>Build Directory in File system </li></ul><ul><ul><li>To start the build for a request, the CBS J2EE service first creates a temporary directory </li></ul></ul><ul><ul><li>source text from the DTR and the required libraries from the archive pool are copied </li></ul></ul><ul><ul><li>Also copies the build space-related components of the build environment, the build plug-ins </li></ul></ul><ul><li>CBS Build Controller </li></ul><ul><ul><li>Build Controller loads the required build plug-ins and requests them to execute the actual build. </li></ul></ul><ul><ul><li>Is a Java command line application, which is started as a separate process </li></ul></ul><ul><li>CBS Web UI </li></ul><ul><ul><li>a Web Dynpro-based Web interface, which allows users to use the CBS from within a Web browser. </li></ul></ul>
    24. 24. The Component Model - Explanation <ul><li>Development Objects </li></ul><ul><ul><li>Stored as versioned files in the source repository (DTR) </li></ul></ul><ul><li>Development Components </li></ul><ul><ul><li>Development and build units </li></ul></ul><ul><ul><li>Group development objects without overlapping </li></ul></ul><ul><li>Software Components </li></ul><ul><ul><li>Delivery and installation units (like e.g. HR in ABAP) </li></ul></ul><ul><ul><li>Group development components without overlapping </li></ul></ul><ul><ul><li>Own the release definition </li></ul></ul><ul><li>Products </li></ul><ul><ul><li>Overlapping selections of </li></ul></ul><ul><ul><li>software components </li></ul></ul>
    25. 25. CBS Features <ul><li>Encapsulation/Decoupling </li></ul><ul><ul><li>Reusable elements explicitly declared public </li></ul></ul><ul><ul><li>Nested components </li></ul></ul><ul><ul><li>Access control lists restrict component usage </li></ul></ul><ul><li>Controlling Dependencies </li></ul><ul><ul><li>Explicit declaration of dependencies </li></ul></ul><ul><ul><li>Checked by build process </li></ul></ul><ul><li>Build Support </li></ul><ul><ul><li>Predefined build templates for component types </li></ul></ul><ul><li>Generic Model </li></ul><ul><ul><li>Independent of technology / programming language </li></ul></ul><ul><li>Tools </li></ul><ul><ul><li>Fully integrated in SAP NetWeaver Developer Studio </li></ul></ul>
    26. 26. Development Components <ul><li>Development Component (DC): </li></ul><ul><ul><li>Container for development objects and built units </li></ul></ul><ul><ul><li>DCs are grouped to make software components </li></ul></ul><ul><li>Nested DCs </li></ul><ul><ul><li>DCs may be contained in another DC </li></ul></ul><ul><li>Public parts </li></ul><ul><ul><li>Elements of a DC that may be used by other DCs (DC-interfacing) </li></ul></ul><ul><li>Usage dependencies </li></ul><ul><ul><li>Declare that a DC uses parts of other DCs during build or runtime </li></ul></ul>
    27. 27. Components and Development Studio Integration <ul><li>Eclipse project handling </li></ul><ul><ul><li>Development Components are mapped to eclipse projects </li></ul></ul><ul><ul><li>DC types are mapped to eclipse project types (natures) </li></ul></ul><ul><ul><li>Projects automatically created from DC data in the repository </li></ul></ul><ul><ul><li>Automatic references to used libraries based on DC dependencies </li></ul></ul><ul><li>Local Component Build </li></ul><ul><ul><li>Checks rules of component model </li></ul></ul><ul><ul><li>Same build procedure as on CBS </li></ul></ul><ul><li>Preconfigured DC types </li></ul><ul><ul><li>Web Dynpro, Data Dictionary, J2EE, Web Services, Java … </li></ul></ul>
    28. 28. Component Model Structure
    29. 29. CBS, Build Process
    30. 30. Netweaver Development Infrastructure Motivation Design Time Repository Component Build Service Change Management Service
    31. 31. NW Development Infrastructure - Big Picture
    32. 32. JAVA Development Life Cycle <ul><li>SLD – Definition of software to be developed </li></ul><ul><ul><li>Define a product </li></ul></ul><ul><ul><li>Define one or more software components (SCs) that form the product </li></ul></ul><ul><li>CMS – Definition of development landscape </li></ul><ul><ul><li>Define a track for the specific release of the SC </li></ul></ul><ul><ul><li>Development configurations are generated for each development state of an SC (DEV or CONS) </li></ul></ul><ul><li>Dev Studio – Edit and Build development objects </li></ul><ul><ul><li>Use the SAP NetWeaver Developer Studio with access to the SAP NW DI for all development projects </li></ul></ul><ul><ul><li>Release objects for further processing by QM/Admin. </li></ul></ul><ul><li>CMS – Define further use of SC’s </li></ul><ul><ul><li>Transport into next dev. steps, quality assurance, and assembly using the Change Management Service </li></ul></ul><ul><li>CMS – Deliver Software components and patches </li></ul><ul><ul><li>Deliver software component versions building products as well as support packages </li></ul></ul><ul><li>CMS – New track for next software release </li></ul>
    33. 33. Track definition in CMS <ul><li>A track comprises configurations and runtime systems (systems in CMS) required for developing software component versions. </li></ul><ul><li>It ensures stable states of deliverables used by subsequent tracks . </li></ul>
    34. 34. Local and Central Development Integration <ul><li>environment defined by development configuration </li></ul><ul><li>based on SAP Component Model </li></ul><ul><li>NetWeaver Developer Studio as local IDE </li></ul><ul><li>Central versioning with the Design Time Repository (DTR) </li></ul><ul><li>Local build and test cycles while developing components in inactive state </li></ul><ul><li>For activating a development component, central build using the Component Build Service (CBS) is necessary </li></ul><ul><li>Tests can run on central test system of the development system </li></ul>
    35. 35. Summary – Java Development Steps
    36. 36. Summary – NWDI Benifits <ul><li>Higher efficiency in development & maintenance </li></ul><ul><li>Allow Source-Delivery for applications </li></ul><ul><li>Component concept </li></ul><ul><ul><li>better means to structure the software </li></ul></ul><ul><ul><li>control of dependencies </li></ul></ul><ul><li>CBS & BuildTool </li></ul><ul><ul><li>no handwritten build scripts </li></ul></ul><ul><ul><li>consistent and up-to-date libraries for IDE </li></ul></ul><ul><ul><li>activation check </li></ul></ul><ul><li>Design Time Repository </li></ul><ul><ul><li>controlled source delivery & modifications </li></ul></ul><ul><ul><li>avoidance of multiple maintenance </li></ul></ul><ul><li>Change Management Service </li></ul><ul><ul><li>central control of logistics (similar to TMS) </li></ul></ul><ul><ul><li>immediate deployment into central test runtime </li></ul></ul><ul><ul><li>early integration </li></ul></ul>
    37. 37. Questions? Q&A Source: http://help.sap.com , http://sdn.sap.com
    38. 38. Thank You

    ×