Importing Development Configurations 

Use

The development configuration defines the contents of the development infrastructure that you use for your work on a particular software project. The development configuration file configures your SAP NetWeaver Developer Studio connections with a central infrastructure. Before you begin the development itself, you have to import the appropriate development configuration.

Development configurations are created either by the CM Services triggered by TMS or by the Change Management Service (CMS) track. Regardless of their origin, the development configurations are stored in the System Landscape Directory (SLD),and you import them from the SLD into the Developer Studio.

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 using the Permissions view. To solve that 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.

Prerequisites

●      You are working in the SAP NetWeaver Developer Studio.

●      You have a user account for the SLD.

●      At least one non-ABAP system with the corresponding development configuration was created in the CTS or at least one track was created in the CMS.

Procedure

...

       1.      From the menu path, choose Window → Open Perspective → Other.

       2.      From the list of perspectives, choose the entry  Development Configurations.

The Development Configurations perspective appears. It offers several views, such as ActiveDCs, Inactive DCs andLocal DCs. If you imported one or more development configurations before, each of these views contains one entry for every imported development configuration.

       3.      To configure the access to the development configurations in the SLD, set the Development Configuration Pool in the Developer Studio:

                            a.      From the menu path, choose Window  → Preferences.

                            b.      Open Java Development Infrastructure →Development Configuration Pool.

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

                            d.      Choose OK.

You can set the storage location (the root folder) for the files created in this development configuration. To be able to change this setting, you must first remove all development configurations. For more information, see Removing Development Configurations.

       4.      Set the proxy connection:

                            a.      From the menu path, choose Windows →Preferences.

                            b.      Choose Workbench→Proxy Settings.

                            c.      Specify the proxy settings.

       5.      To import a development configuration, in the Local DCs view open the context menu and choose Import Configuration... 

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

       7.      Choose the option remote. If the development configuration is available locally on your PC, choose the entry local development configuration file.

       8.      Select a development configuration from the list of development configurations. Choose Next.

The Build Variants dialog window appears.

       9.      If appropriate, select a build variant for every compartment that you want to use for the local component build. (You can make a selection only if a compartment defines more than one variant.)

   10.      Choose Finish.

Later on if there are changes made to an already imported development configuration, you have to reload this development configuration. To do that in the context menu of the development configuration choose Update Configuration.

Result

The system reads the development configuration settings and sets up your development environment. The views Active DCs,Inactive DCs, and Local DCs now contain a new entry with the name of the imported development configuration.

You can now import another development configuration, if necessary.