Entering content frame

Procedure documentation Importing Development Configurations Locate the document in its SAP Library structure

Use

For you as a developer, the Structure linkdevelopment configuration defines the contents of the development infrastructure for your work on a particular software project and configures your Developer Studio for the connection with the relevant elements of the infrastructure.

Your very first step, therefore, even before you begin to develop, is to import the appropriate development configuration.

Prerequisites

You have started the SAP NetWeaver Developer Studio.

Opening the Development Configurations Perspective

...

...

...

       1.      To open the Development Configurations Perspective, in the menu choose Window ® Open Perspective ® Other.

       2.      In the list of perspectives, choose the entry This graphic is explained in the accompanying text Development Configurations.

This graphic is explained in the accompanying text

Or you can choose the symbol This graphic is explained in the accompanying text in the quickstart bar on the left margin of your working window and, from the context menu, choose Development Configurations.

The corresponding perspective appears. It offers several views, such as Active DCs, Inactive DCs and Local DCs. If you imported one or more development configurations before, each of these views contains one entry for every imported development configuration.

       3.      The import is done differently depending on the used development scenario:

                            a.      Scenario 2: Import from the local file system

                            b.      Scenarios 2+ and 3: Import from the System Landscape Directory

Importing a Development Configuration from the Local File System

You use this option in Scenario 2: Development with Components. Development configurations are created with a tool, can be stored as files and imported from a local file system into the SAP NetWeaver Developer Studio. This procedure usually suffices for smaller development teams. Development configurations in file form can easily be spread by e-mail or be offered for download on a central Web server.

...

...

You are in the Development Configurations perspective.

       1.      To import a development configuration, open the context menu in the Local View and choose Import Configuration... 

The development configuration import wizard appears.

Note

In this window, 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.

       2.      Select local development configuration file.

       3.      To navigate to the directory of the development configuration file, choose Browse.

Note

You can also enter the path and file name of the development configuration in the input field next to the switch.

       4.      Navigate to the development configuration file and choose Open.

The window Development Configuration Import appears.

       5.      Choose Next.

The Build Variants dialog window appears.

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

Example

To test locally, select, for example, dbg from the list.

       7.      Choose Finish.

This graphic is explained in the accompanying text

If you are not yet logged on to the development infrastructure, you are now prompted to log on. Enter your user ID and password.

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

This graphic is explained in the accompanying text

You can import more than one codevelopment nfiguration, if necessary.

Importing a Development Configuration from the System Landscape Directory

You use this option in Scenario 2+: Development with a Track and in Scenario 3: Layered Development.Development configurations are created in the Change Management Service(CMS), stored in the System Landscape Directory (SLD), and imported from there into the SAP NetWeaver Developer Studio.

You are in the Development Configurations perspective.

Configure Access to the System landscape Directory (SLD)

...

       1.      To have access to the development configurations in the SLD, set the Development Configuration Pool in the SAP NetWeaver Developer Studio:

                            a.      In the menu chose Window  ® Preferences.

A dialog window appears.

                            b.      Open Java Development Infrastructure ® Development Configuration Pool.

                            c.      Und URL, enter the host name and the port of the SLD server.

                            d.      Confirm with OK.

       2.      Set the proxy connection:

                            a.      In the menu, choose Windows ® Preferences ® Workbench ® Proxy Settings.

                            b.      Adapt the proxy settings or deselect the option Use a Proxy Server.

Import a Development Configuration

...

       1.      To import a development configuration, open the context menu in the Local View and choose Import Configuration... 

An import wizard appears.

       2.      Select the option remote.

A dialog window for logging on to the SAP NetWeaver Java Development Infrastructure appears.

       3.      Log on.

The development configuration import wizard appears.

Note

In this window, 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.

A list of the development components available in the SLD appears.

       4.      Select the required development configuration and confirm your selection.

The window Development Configuration Import appears.

       5.      Choose Next.

The Build Variants dialog window appears.

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

Example

To test locally, select, for example, dbg from the list.

       7.      Choose Finish.

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.

This graphic is explained in the accompanying text

You can import more than one codevelopment nfiguration, if necessary.

 

 

 

Leaving content frame