nwdi slidedeck

Download NWDI Slidedeck

Post on 04-Jun-2018

225 views

Category:

Documents

1 download

Embed Size (px)

TRANSCRIPT

  • 8/13/2019 NWDI Slidedeck

    1/17

    Help Documentation on NWDI

    http://help.sap.com/saphelp_nw2004s/helpdata/en/f2/7c04702864304bb38e0b1cd6667c2b/frameset.htm

  • 8/13/2019 NWDI Slidedeck

    2/17

    Netweaver Development Infrastructure Central source file management in the Design Time Repository (DTR) Central build and archive management in the Component Build Service (CBS) Central landscape and transport management in the Change Management Service (CMS).

    The applications you develop are split into software components (SCs) (the installation units) anddevelopment components (DCs) (which are exactly on the granularity of projects and contain alldevelopment objects plus the aforementioned metadata).

    Development is performed in what is called a t rack

    The track also takes care of the phases deve lopment and conso l ida t ion and all transport processes fromstart to finish when the application is deployed to the productive system or delivered to customers.In this way you have better control over the development versions and the exact sourcedevelopment.

  • 8/13/2019 NWDI Slidedeck

    3/17

    Design

    LocalJava Installation

  • 8/13/2019 NWDI Slidedeck

    4/17

    CMS, DTR & CBSCMS defines source management (DTR) and archive management (CBS) for the new developmentproject. Usually, almost everything you develop is stored in a database.

    A connection to the database for the software catalog is obtained to keep a track of what isdeveloped. There are also runtime systems for automated deployment during all project phases. Theyare accessed by the developers either using the Developer Studio or the workplace.

    The DTR overcomes many of the limitations of file-based versioning systems for all kinds of development

    objects required in the development process. Java sources, XML files, and so on, are stored in adatabase, but still they are exposed to the client as files and folders, visible in the Developer Studio. Thelimitation we overcome is that the file version history is always transported together with the file, so thatwe can synchronize different DTR over repository boundaries by simple file transports.

    The CBS is responsible for building the sources that are stored in the DTR and is the central buildenvironment. Unlike in other central builds, the CBS also centrally hosts and makes available the latest

    archives and build results for all developers. The CBS also makes the integration available on the archiveslevel, even for those objects that are still under development. The build is component-based; if a build fails,only a component is delayed. All other components will simply use the latest valid (that is successfully built)version in a central build.In contrast to the conventional build tools, the goal of the CBS is to automate the build process in anincremental fashion. That is, only the changed files, as well as files that have a dependency on them, are builtinstead of building all sources from scratch.This incremental builds concept dramatically reduces the source code correction cycles.In addition, in CBS dependent objects are only rebuilt if the public parts they use have been changed

  • 8/13/2019 NWDI Slidedeck

    5/17

    Component Model Software components (SCs) are delivery and installation units; they

    group development components without overlapping. For moreinformation, see Software Components.

    Products these are the overlapping selections of softwarecomponents. One software component can be part of severalproducts

    Development components (DCs) are development and build units; theygroup development objects without overlapping. Development objectscreated in the context of development components; they are stored asversioned files in the Design Time Repository (DTR).

  • 8/13/2019 NWDI Slidedeck

    6/17

    User Management

    2 main groups - NWDI.Developer and NWDI.Administrators User name Cmsadm assigned to NWDI.Administrators group

    To allow communication with the SLD, you must additionally assign the UMEgroups to the following security roles in the J2EE engine:

    Administrators need the security role LcrInstanceWriterAll Developers need the security role LcrInstanceWriterNR

  • 8/13/2019 NWDI Slidedeck

    7/17

    Team oriented Development Prepare NWDS

    http://help.sap.com/saphelp_nw2004s/helpdata/en/f2/7c04702864304bb38e0b1cd6667c2b/frameset.htm

    Create USER1, USER2 and CMSADM in the UME of AS Java of NWDI and SLD. IF SLD and NWDI are on different host. Ensure identical password. The AS Java

    requires that you change the initial password of a user at the first logon. Therefore,after creating the users, log on to the AS Java once with every user and change theinitial password.

    USER1 Group : NWDI.Developers USER2 Group : NWDI.Developers CMSADM Group : NWDI.Administrators

    Track Management Create a software component in the SLD that contains the development track Register Prefix Create Domain Create Track Checking In Software Component

    http://help.sap.com/saphelp_nw2004s/helpdata/en/f2/7c04702864304bb38e0b1cd6667c2b/frameset.htmhttp://help.sap.com/saphelp_nw2004s/helpdata/en/f2/7c04702864304bb38e0b1cd6667c2b/frameset.htmhttp://help.sap.com/saphelp_nw2004s/helpdata/en/f2/7c04702864304bb38e0b1cd6667c2b/frameset.htmhttp://help.sap.com/saphelp_nw2004s/helpdata/en/f2/7c04702864304bb38e0b1cd6667c2b/frameset.htm
  • 8/13/2019 NWDI Slidedeck

    8/17

    Create a software component in the SLD that containsthe development track

    Define product

    Define software component

  • 8/13/2019 NWDI Slidedeck

    9/17

    Define Dependencies Under Software Catalog , choose

    the Software Components tabpage

    Define the followingdependencies :

    SAP J2EE ENGINE (SAP-JEE)

    SAP BUILD TOOL (SAP_BUILDT)

    SAP JAVA TECHNOLOGYSERVICES (SAP_JTECHS )

  • 8/13/2019 NWDI Slidedeck

    10/17

    Register Prefix The name server checks the uniqueness of the names and enables you to

    define name prefixes. The name server is a role of a SLD . The other role is thelandscape server role . The setup of the name server takes place in the sameway as the setup of the SLD server. Execute the following steps:

    Select the landscape type NWDI System .Enter a name for the landscape, for examp le NWDI.Choose Create .The new landscape is displayed.Select the new landscape.You see the details on the landscape.Choose Systems and thenchoose Add System to Landscape. Choose the hosted system typeSystem Landscape Directory .You see the installed SLD.Choose OK .Select the SLD . The Details view appears.Select the roles Landscape Server (and/) or Name Server .Save your changes.

  • 8/13/2019 NWDI Slidedeck

    11/17

    Register Prefix II

    Development Name Reservation Define Namespace Prefix

  • 8/13/2019 NWDI Slidedeck

    12/17

    Creating DOMAIN

    a domain in the Change Management Service (CMS). In this way, you make thedevelopment configuration for component-based development available to theSAP NetWeaver Developer Studio, and you define a transport environment. Youuse this transport environment to transport the software components (SCs) youdevelop through consolidation and quality assurance to production use.

    You can specify the Domain ID and the CMS Name only once. If you specifiedthe name Tst already in another example, you must first delete the domaindata in the SLD.

    Click on Update CMS to retrieve latest SC from SLD

  • 8/13/2019 NWDI Slidedeck

    13/17

    Create a TRACK

    SC assigned to this trackNote: This is the SC we justdefined on SLD

  • 8/13/2019 NWDI Slidedeck

    14/17

    Example ESS (SAP_ESS 600)

  • 8/13/2019 NWDI Slidedeck

    15/17

    Example ESS SLD (see dependencies)

  • 8/13/2019 NWDI Slidedeck

    16/17

    Transport with NWDI Transport Studio Procedure

    Check-in archives Import (change request or component)

    Change Request and Software Component CMS imports the source code into the appropriate repository CMS triggers the activation of the imported changes A central build is performed

    Import Check If you have modified SAP software component versions in your development track, these

    modifications can be overwritten by any updates to the component that you import into the track Restore System State Assembly

    (http://help.sap.com/saphelp_nw2004s/helpdata/en/f2/7c04702864304bb38e0b1cd6667c2b/frameset.htm)

    extracts the current state of the software in the DTR workspace of the consolidation system,gets the required archives from CBS, and uses these to assemble a uniquely defined state ofthe software component.

    assembly process packs the software component into an archive of type Software Component Archive (SCA).

    BROKEN - The SC contains broken DCs at assembly and is therefore technicallyinconsistent

    DIRTY - The SC contains dirty DCs at assembly. This means that the last SC buildprocess has not yet finished or was stopped in an inconsistent state

  • 8/13/2019 NWDI Slidedeck

    17/17

    Using CTS and NWDI Using Change and Transport System (CTS) and SAP NetWeaver Development

    Infrastructure (NWDI) separately CTS for ABAP and NWDI for Java-based

    Using CTS combined with NWDI. CTS for ABAP and mixed and NWDI for Java-based development single tool to transport parts of one and the same application instead of using different

    tools for transporting parts of one and the same application.

    Configure the AS Java System RFC destination - sap.com/com.sap.tc.di.CTSserver Visual Administrator ( Cluster Server Services Destinations )

    Connection Settings , enter the connection data of your CTS server. Under Logon Data , select the Current User (Logon Ticket) option as

    authentication for the connection to your CTS server. We recommend that youuse Single Sign-On (SSO). Use client number set underNON_ABAP_WBO_CLIENT

    Configure CMS track. You must mark the track as Connected to CTS In the Transport Studio, open the Approval tab. Choose Release to CTS from History button