Managing Development
Configurations
No matter which development scenario you follow (with SAP NetWeaver Development Infrastructure (NWDI), with your own development infrastructure tools, or without development infrastructure support), you use a development configuration to configure the development environment.
These development configurations can be distributed among developers using a landscape directory. In small development landscapes, for example, 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.
This implies that you have already prepared a development configuration and it is downloaded locally on your PC. You only have to import it in your Developer Studio.
...
1. Choose New/Import Development Configuration icon. In the dialog that appears, decide what you want to do and choose the appropriate option.
2. Select the option from Development Configuration file.
3. In the Configuration File field that appears, browse to the location of the development configuration file and complete the dialog.
This option is valid if you are using a system with NWDI and System Landscape Directory (SLD) installed on it.
...
1. Configure the access to the development configurations in the SLD.
Set the Landscape Directory in the Developer Studio:
a. From the menu path, choose Window → Preferences.
b. Open Development Infrastructure →Landscape Directory.
c. In URL, enter the address of the SLD server. For example, http://my_server:8080.
d. Choose OK.
2. Set the proxy connection, if required:
a. From the menu path, choose Windows →Preferences.
b. Choose General→Network Connections.
c. Specify the proxy settings.
3. From the menu path, choose Window → Open Perspective → Other. Choose the Development Infrastructure perspective.

If you have imported one or more development configurations before, each of these views contains one entry for every imported development configuration.
4. To import a development configuration from the SLD, choose the New/Import Development Configuration icon.
5. (Optional) In the dialog that appears, log on to the NWDI.
6. Choose from System Landscape Directory (SLD).
7. Load the development configuration from the SLD and complete the dialog.
With this option, you create and configure a new development configuration file. In this case, you have to choose an archive provider to use. 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 what 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), 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.

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 from scratch to create the development configuration manually.
3. Specify a name for the developmentconfiguration.
4. Select the Archive Provider Type.
○ arcpool – 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.
○ fs - 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).

The file system share must have read permissions for everyone.
○ local only
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.
○ sca - 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.
To export the development configuration to distribute it, in the Development Infrastructure perspective, select the already imported (or newly created) development configuration.
Open the context menu and choose Export as File. Point to the location where you want to store the development configuration and complete the dialog.
If something is modified within the development configuration, you have to update the configuration to refer to the changes. Choose either of the both ways:
● automatic – choose Window → Preferences → Development Infrastructure → Development Component Infrastructure and select Update Development Configuration automatically.
● manual – in the context menu of the development configuration, choose Update. In the dialog that appears, select the location from where you want to update the development configuration.
To remove a development configuration, 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. More information: Managing Activities.
...
1. In the context menu of the development configuration, choose Remove.
2. In the dialog that appears, choose Yes.