SAP NetWeaver Composition Environment Software Change ...

© SAP AG 2007 1

SAP AG 2007

SAP Netweaver Composition Environment 1.0 ForService Software Providers

SAP NetWeaverComposition Environment

Software Change Management

Overview

© SAP AG 2007 2

SAP AG 2007

Course Objectives

After completing this course, you will be able to:

Understand the usage of External DevelopmentInfrastructure for SAP NetWeaver CompositionEnvironment

Develop composite applications on the SAPNetWeaver Composition Environment using theSAP Component Model

Setup, extend and exchange DevelopmentConfigurations within development teams for SAPNetWeaver Composition Environment

Use CTC Templates to setup an NWDI track forComposition Environment development

© SAP AG 2007 3

SAP AG 2007

Content

Software Change Management (SCM) - Overview

SCM Using External Development Infrastructure

SCM Using SAP NetWeaver Development Infrastructure (NWDI)

Software change management with SAP NetWeaver Development Infrastructure.

© SAP AG 2007 4

SAP AG 2007

Lesson: Software Change Management - Overview


Standard Java EE 5 Development

Development with External Development Infrastructure

Development with NWDI

© SAP AG 2007 5

SAP AG 2007

Lesson Objectives

After completing this lesson, you will be able to:

Explain the development scenarios

Understand the concepts and features of adevelopment infrastructure

© SAP AG 2007 6

SAP AG 2007

Overview

Setup acompositionenvironment*

Initial setup

Technicalconfiguration

Import ofreferencecomposites

Develop acomposite

Release / Shipa composite

Consume acomposite

Maintain acomposite

Manage change*

SAP / ISV CUSTOMER

Versioning

Team development

Internationalization

Build anddeployment

Packaging

Transport

Deployment

Configuration

Extension /Modification

Administration

Monitoring

Supportability

Managing changesto:

PlatformCompositesUnderlying

services

* Common to both providers and consumers

Composite Lifecycle Use-cases

© SAP AG 2007 7

SAP AG 2007

Lifecycle Of A Composite


Develop acomposite


Consume acomposite

Maintain /Operate Manage change*

Team development1

Tasks Capabilities and tools in SAP NetWeaver CE 7.1 SP3

Integrated development infrastructure (NWDI)

Usage of external (3rd Party) development infrastructurealso supported

Integrated development infrastructure (NWDI)

Usage of external (3rd Party) development infrastructurealso supported

© SAP AG 2007 8

SAP AG 2007


Develop acomposite


Consume acomposite

Maintain /Operate Manage change*

Build and Deploy1

Package2

Tasks Capabilities and tools in SAP NetWeaver CE 7.1 SP3

Local build and deployment, from SAP NetWeaver DeveloperStudio

Central build and deployment, using NWDI

Local build and deployment, from SAP NetWeaver DeveloperStudio

Central build and deployment, using NWDI

Packaging of Software components from SAP NetWeaverDeveloper Studio

Central assembly of Software components, using NWDI

Packaging of Software components from SAP NetWeaverDeveloper Studio

Central assembly of Software components, using NWDI

Transport3NWDI CMS and enhanced Change and Transport System

(CTS+) for transporting content of different technologiesspanning a composite

NWDI CMS and enhanced Change and Transport System(CTS+) for transporting content of different technologiesspanning a composite

Lifecycle Of A Composite

© SAP AG 2007 9

SAP AG 2007

Development Scenarios

Standard development of Java EE 5 applications on the SAPNetWeaver platform

Development based on the SAP component model with the fullSAP NetWeaver Development Infrastructure (NWDI) support

Focus for this unit:Development with the External Development Infrastructure:Development based on the SAP component model, without NWDIsupport

© SAP AG 2007 10

SAP AG 2007

Development Infrastructure Support

Option 1: NetWeaver Development Infrastructure (NWDI)Repository for Team development (versioning, check-out/checkin)Build Engine for on-demand central buildsConsolidation and central assembly (packaging)Good integration with design-time toolsets (like WebDynpro) SAPNetWeaver Developer Studio

Option 2: External (3rd Party) Development InfrastructureAny 3rd Party version control system can be used to store artifactsMinimal integration with design-time toolsets (like WebDynpro) SAPNetWeaver Developer StudioCommand-line build and packaging tools available

© SAP AG 2007 11

SAP AG 2007






© SAP AG 2007 12

SAP AG 2007

Standard Development Without SAP Component Model

Develop only standard applications (EJB, Servlet, JSP, JSF, …)

No proprietary SAP APIs, project types or libraries are used

development without SAP component model

Standard assembly and deployment to the AS Java

Administration via SAP NetWeaver Administrator

Optional:Usage of the source control and version system (e.g. DTR)

Optional:Usage of CE Command Line Tool (CECLT) for packaging to SCA format

© SAP AG 2007 13

SAP AG 2007






© SAP AG 2007 14

SAP AG 2007

Development With NWDI

Development within the SAP Component ModelDefine Products and Software Components (SCs) in SLDDefine Development Components (DCs) in NetWeaver Developer Studio(NWDS)

Development with central Development ConfigurationsTrack definition within CMS results in a centrally stored developmentconfiguration

Development using SAP Netweaver Developer StudioIntegrated development environment

Design Time Repository (DTR)central source and version control

Component Build Server (CBS)central build management tool

Change Management System (CMS)managing development landscape, software production and transport

© SAP AG 2007 15

SAP AG 2007






© SAP AG 2007 16

SAP AG 2007

Development With External DevelopmentInfrastructure

Development within the SAP Component ModelNo Product DefinitionDefinition of Software Components (SCs) and Development Components (DCs)within NWDS

Development with local Development Configurationsbased on the file systemexchanged via file export/import

Development using SAP Netweaver Developer StudioIntegrated development environment

Development of SAP and non-SAP technologiesWeb Dynpro, Guided Procedures, Composite Application Framework, standardJava EE 5 applications

Free choice of development infrastructure processes and tools

© SAP AG 2007 17

SAP AG 2007

External Development Infrastructure –Benefits/Drawbacks

No assumption regarding processes/tools employed by thecustomer for development infrastructure purposes.

BenefitsDevelopment can start immediately without having to set up aninfrastructure first.Fits small development teams that may not even need a full featureddevelopment infrastructure.Free choice for customers regarding development infrastructureprocesses/tools.

DrawbacksLevel of integration of development infrastructure services and thusconvenience for the developer cannot be the same as with NWDI.

E.g. all developers have to manually retrievethe necessary sources (e.g. from a version control system)all used libraries (e.g. from a central night make)

Effort for integration of customers development infrastructureprocesses/tools.

© SAP AG 2007 18

SAP AG 2007

Developer Workplace

FileSystem

CEServer

Component Model

Development Based On The File System

Version Control System

Central Build

Eclipse Plugins

For the development itself, you use the SAP NetWeaver Developer Studio. Since the Developer Studio isbased on the Eclipse open-source development platform, you can add additional plug-ins and in this wayintegrate third party technologies. You choose the processes and the tools you use to cope with sharing ofsource and libraries within a development team, change management and versioning, central build,transport, testing, deployment and so on.

© SAP AG 2007 19

SAP AG 2007

External Development Infrastructure – SoftwareLifecycle

Software Lifecycle Steps:Create a Development ConfigurationCreate Software Component(s)Create Development Component(s) (Eclipse projects wrapped in DCs)Build Development ComponentsAdd Sources to Version Control System (third-party or DTR)Group DCs in Build/Deploy ArchivesDeploy & Test locallyPackage Software Components (SCA files)Shipment of SCA files to customers

Hint: Transport aspect see next slide

© SAP AG 2007 20

SAP AG 2007

Recommendations for Transport Tool – NW CECustomers

NWDI CMSNWDI for CE available starting with NW04sSPS13.Usage Type DI is not available with NW CE –a NW04s based installation for NWDI has tobe used.

Third party Transport solutionCould be used to transport SoftwareComponent Archives (SCAs) developed andproduced with NW CE.

JEE Only LandscapeCE runtime systems embedded into landscapecontaining only JEE based systems.E.g. 3-System-landscape (Dev, QA, Prod)containg CE systems only.

Enhanced Change and TransportSystemsAvailable starting with NW04s SPS12.

Mixed ABAP/JEE LandscapeCE runtime systems are embedded intolandscape containing JEE based and ABAPbackend systems.E.g. 3-System-landscape (Dev, QA, Prod)containing ABAP based backend systems inparallel to JEE based systems.

Transport Tool RecommendationsType of Landscape

© SAP AG 2007 21

SAP AG 2007

Lesson Summary

You should now be able to:

Explain the development scenarios

Understand the concepts and features of adevelopment infrastructure

© SAP AG 2007 22

SAP AG 2007

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 containedherein 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.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 aretrademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned arethe trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.

The information in this document is proprietary to SAP. No part of this document may be reproduced, copied, or transmitted in any form or for any purpose withoutthe express prior written permission of SAP AG.This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This document contains only intendedstrategies, developments, and functionalities of the SAP® product and is not intended to be binding upon SAP to any particular course of business, product strategy,and/or development. Please note that this document is subject to change and may be changed by SAP at any time without notice.SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of the information, text, graphics, links,or other items contained within this material. This document is provided without a warranty of any kind, either express or implied, including but not limited to theimplied warranties of merchantability, fitness for a particular purpose, or non-infringement.SAP shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use ofthese materials. This limitation shall not apply in cases of intent or gross negligence.The statutory liability for personal injury and defective products is not affected. SAP has no control over the information that you may access through the use of hotlinks contained in these materials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages.

Copyright 2007 SAP AG. All Rights Reserved

SAP NetWeaver Composition Environment Software Change ...

Documents

Transcript of SAP NetWeaver Composition Environment Software Change ...