Show TOC

Migrating from Local Development to NWDILocate this document in the navigation structure

Use

You have started a component based development project in Developer Studio and would like to move into NWDI now to reap the benefits of version control, central builds, and central configuration services.

Prerequisites

You have installed and configured NWDI. See Configuring the Development Infrastructure .

Procedure

To move from local development into NWDI you have to perform the following steps:

  1. Add local SC definition to System Landscape Directory (SLD).

    For more information about how to add SC in the SLD, see Creating and Removing Third-Party Software Components .

    Note

    Alternatively you can create the SC together with the dependency definitions with the Configuration Wizard. In this case the next two steps can be skipped. For more information, see Setting Up Tracks Using the Configuration Template .

  2. Add the required SC dependencies in the SLD. Note that you have to manually configure the required SC dependencies, as they are not automatically transferred to the SLD.

    For more information about adding SC dependencies in the SLD, see Defining and Removing Software Dependencies .

  3. Add SCs to your development configuration in CM Services Configuration Services. See Using Configuration Services .

  4. Download central development configuration into Developer Studio.

    For more information, see Managing Development Configurations .

  5. Copy and paste local development to central development configuration.

    For more information, see Moving Development Components .

  6. Create activity and checkin source files into DTR.

    For more information, see Managing Activities .

  7. Continue development.

    For more information, see Central Development with NWDI .

Start Team Development with NWDI

  1. Download development configuration and start developing.

  2. After development, checkin the sources.

  3. Activate centrally (Central Build Environment CBS takes care of a continuously buildable software).

  4. Release for transport (CMS).