Show TOC

Working with Development ConfigurationsLocate this document in the navigation structure

Use

No matter which development scenario you follow, you use a development configuration to configure the development environment. The difference is in the way you create your development configuration. Note that for you as a developer, it should not matter where the development configuration was created - it is up to the administrator to decide that. You always use the development configuration in the same way. The difference in the way the development configuration is created is in its purpose:

  • For local development - you can create your development configuration from scratch using the SAP NetWeaver Developer Studio. For more information about creating such a development configuration, see the procedure below.

  • For third party development infrastructure - again, you use locally created development configurations.

  • For development with SAP NetWeaver Development Infrastructure (NWDI) - your administrator created the development configuration using Change Management Services (CM Services). This allows the integration of the landscapes that use AS ABAP, AS Java, or both.

The development configurations can be distributed among developers using a landscape directory. However, in small development landscapes, the development configurations may be distributed by download from a Web server. The SAP NetWeaver Developer Studio is able to import configurations from the local file system. The Developer Studio can hold several imported development configurations at the same time.

Prerequisite

  • When using a local development configuration within the Development Studio, you have to ensure that the used workspace is located on the same drive as the Development Studio installation.

  • You work in the Development Infrastructure perspective.

  • If you want to use a development configuration that was created with an older SAP NetWeaver version, make sure that the list of software components for development corresponds to the SAP NetWeaver version you are working in. For more information, see SAP Note 1457908 Information published on SAP site.

Procedure

Importing a local development configuration

This implies that you have already prepared a development configuration and it is downloaded locally on your PC. You only have to import it into your Developer Studio.

  1. Choose New/Import Development Configuration icon.

  2. In the dialog that appears, select Import from Development Configuration File . Choose Next .

  3. Point to the location of the development configuration. Choose Next .

  4. Specify the name of the development configuration as you want it to be displayed in the Developer Studio. Choose Finish .

Importing a development configuration from the System Landscape Directory

This option is valid if you are using a system with NWDI and have access to a System Landscape Directory (SLD).

Note

When you import a development configuration, if it contains already configured DTR clients for the Developer Studio, you will not be able to edit the associated access control list (ACL) files in the Permissions view. To solve this issue, leave the existing DTR client as it is. Then create and configure a new DTR client for the same repository, and use it to configure the ACL files. ACL editing works only with the manually created client.

  1. Configure the access to the development configurations in the SLD.

    Set the Landscape Directory in the Developer Studio:

    1. From the menu path, choose Start of the navigation path Window Next navigation step Preferences... End of the navigation path.

    2. Open Start of the navigation path Development Infrastructure  Next navigation step Landscape Directory End of the navigation path.

    3. In URL , enter the address of the SLD server. For example, http://my_server:8080 .

    4. Choose OK .

  2. Set the proxy connection, if required:

    1. From the menu path, choose Start of the navigation path Windows  Next navigation step Preferences... End of the navigation path.

    2. Choose Start of the navigation path General Next navigation step Network Connections End of the navigation path.

    3. Specify the proxy settings.

  3. From the menu path, choose Start of the navigation path Window Next navigation step Open Perspective  Next navigation step  Other End of the navigation path. Choose the Development Infrastructure perspective.

  4. To import a development configuration from the SLD, choose the New/Import Development Configuration icon.

  5. Choose Import from System Landscape Directory (SLD) . Choose Next .

  6. In the dialog that appears, log on to the SLD.

  7. Choose a development configuration to load from the SLD and complete the dialog.

Creating a development configuration from scratch

With this option, you create and configure a new development configuration file. In this case, you have to choose an archive provider to be used. The archive provider allows you to retrieve development component (DC) archives. For that purpose, it can also detect what DCs are there (just to associate to which DC the archives belong).

The DC archives themselves are located in a DC archive store. Examples of such archive stores are: Software Component Archive (SCA), the file system, the Component Build Service (CBS), and the Developer Studio's default archive pool.

The Developer Studio uses the DC archive provider to download DC archives (typically needed for the build) from the archive store to the local development configuration. Typically it requires that you sync the sources in the Component Browser view.

Example

You use a file share to store the results from the central build, that is, producing DC build archives. The share itself is a store for the file system archive provider. Another developer can reference this store in his or her development configuration, and the archives will be downloaded on to his or her PC. This developer can also find out whether or not these archives in the local folder are outdated, and decide if there is a need to resynchronize to the archive store state.

  1. Choose the New/Import Development Configuration icon.

  2. Select the option Create from Scratch to create the development configuration manually. Choose Next .

  3. Specify a name for the development configuration. Choose Next .

  4. Select the Archive Provider Type :

    • Archive Pool - the Developer Studio's archive pool DC archive provider.

      This option retrieves DCs or archives from the archive pool that belongs to the Developer Studio.

    • File System - the file system DC archive provider.

      This option scans for DC archives in subfolders of the folder you specify and you are using as an archive store. Then it retrieves whatever it finds for a DC (this can also be SDA or DCIA files).

      Caution

      The file system share must have read permissions for everyone.

    • localonly

      You use this option if you have already copied the archives to the local configuration manually, or you are using your own automated procedure. It is up to you to keep the files up-to-date in this case.

    • Software Component Archive - the SCA DC archive provider.

      This option retrieves DC archives (SDAs or DCIAs) from an SCA that resides somewhere in the file system and plays the role of an archive store. A typical SCA contains SDAs (deployable results) and DCIAs (build archives). The archive provider is able to retrieve archives from SCA files.

  5. Browse to the location of the archive store.

    To do that, choose the Browse... button and navigate to the location of the archive store.

    The list of the SCs available in the archive store is displayed in the table.

  6. Choose the SC(s) that you want to include or to exclude from your development configuration.

  7. Choose Finish .

Exporting a development configuration

To export the development configuration to distribute it, in the Development Infrastructure perspective:

  1. Select the already imported (or newly created) development configuration.

  2. Open the context menu and choose Export as File.. .

  3. Point to the location where you want to store the development configuration and complete the dialog.

Updating a development configuration

If something is modified within the development configuration, you have to update the configuration to refer to the changes. Choose either of the two ways:

  • automatic - from the menu path choose Start of the navigation path Window Next navigation step Preferences...  End of the navigation path. Select Start of the navigation path Development Infrastructure  Next navigation step Development Component Infrastructure  End of the navigation path and then select Update Development Configuration automatically.

  • manual - in the context menu of the development configuration, choose Update .

Removing a development configuration

To remove a development configuration from the Developer Studio, all activities of its development components have to be checked in to the repository you are using. You cannot remove a development configuration if you still have open activities for this development configuration. You can view your open activities in the Open Activities view and choose whether to check in your changes or cancel the checkout.

  1. In the context menu of the development configuration, choose Remove .

  2. In the dialog that appears, choose Yes .

Ignore name reservation for a DC

With this option you can stop the DC's name check when copying a DC to another CMS track on which a DC with the same name already exists. In this way you can overwrite the content of the targeted DC. This option is active only until you restart the Developer Studio (that is, you end your current session). To enable the ignoring of the name reservation:

  1. Select the development configuration.

  2. Under the Component Properties view, in the Overview tab page, choose Ignore name reservation mode for the current session .

More Information

Defining Products in a Single Development Configuration

Configuring Development Configuration Build Options

Using CM Services