Importing Development
Configurations 
Use
The development configuration (or simply configuration) is the entry point to the SAP Component Model within the SAP NetWeaver Developer Studio. By importing the development configuration you get all the environment settings needed for your development task.
Prerequisites
You are logged in to the development infrastructure.
Importing Configurations via Landscape Directory and CMS
...
1.
To login to
the development infrastructure choose the icon 
in
the tool bar, if necessary.
2. To open the Development Configurations Perspective in the menu choose Window ® Open Perspective ® Other.
To take a short cut you can press on icon 
(on
the left margin) alternatively.
3.
In the list
of perspectives choose the entry
Development Configurations.
The corresponding perspective appears. It provides several views like Team View and Local View.
If you have already imported one or more configurations you will see them in the Team View and Local View as top nodes. For more information, see Development Configuration Perspective.
4. You can use the configuration node to start navigation through the SC and DC hierarchies.
Assuming that you have not imported a configuration so far, the Team View and Local View will show No Configuration imported.
If you are not logged in, the Team View shows OFFLINE.
5. To import a configuration, move the mouse cursor into the team view and press the right mouse button.
A context menu appears that contains an entry labeled Import Configuration.
6. After you have selected this menu entry the import wizard appears.
Clicking on icon in the tool bar also launches the import
wizard. This icon only appears if the Development Components
perspective is active.
7. To import configurations via the Change Management Service from the Landscape Directory, in the upper part of Development Configuration Pool specify the connection parameters.
This is the normal mode in larger development teams.
8. At the bottom you can specify the local root directory under which all configurations are stored.
Besides the configurations itself all files that belong to a configuration are stored under this root directory. This includes all SC and DC files that are created locally or copied from DTR or CBS.
However you are allowed to specify this root directory only, if no configuration has been imported so far. Therefore, we recommend that you make the decision on the configuration root directory at the earliest possible stage.
9. Choose the build variant for each compartment of the configuration: If a selection is possible a list box appears, otherwise the default build variant is displayed. The build variant selection is not offered for each compartment. A build variant is a symbolic name for a number of settings, which are relevant for build or deployment process. This may include:
...
a. Generator/compiler options like optimized / debug
b. Platform switches like target operating system or target J2EE implementation
c. Locales to be included when packing the deployable archives (Java specific)
One variant can contain one set of locales, for example (EN, IT, FR, JP).
Importing Configurations via Local Configuration File
You can also import configurations via local configuration file.
...
1. To import configurations via local configuration file select the radio button local development configuration file in the window.
Provided that the Landscape Directory is available, all existing configurations will be displayed in the Configuration Import Wizard.
2. To get a configuration from the Landscape Directory select the radio button for local development configuration files.
In this case another window comes up, if the so-called Development Configuration Pool is not configured:
3. To open the Development Configuration Pool, in the menu choose Window ® Preferences ® Development Configuration Pool
Usually these entries will be done only once per IDE installation. They describe the entry point to the development landscape, which usually does not change.