Development Configurations
Perspective
You use the Development Configurations perspective of the SAP NetWeaver Developer Studio to manage development components (DCs). From there, you can load DCs from central servers to your local computer, create new DCs and edit the properties of existing DCs.
The Development Configurations perspective is used for component development (including also layered development) with the SAP NetWeaver Development Infrastructure (NWDI). It is used for a component-based development.
DC Views
The Development Configurations perspective contains the following views:
● Inactive DCs – shows all compartments and all DCs that can be changed in this development configuration. You can create new DCs in this view.
● Active DCs – shows all DCs from software components (SCs) that have been imported in this development configuration in the archive state, and therefore cannot be changed. All activated DCs, and those DCs that have been built successfully in the CBS (triggering the build process is called activate) are also displayed here.
Advantages of the Distinction Between Inactive and Active DC Views
There are many advantages of distinguishing between an inactive and an active state. You can always use the inactive state to check changes in to the DTR without endangering the work of other teams or the functionality of central systems by possible errors. By checking changes into the DTR, you can use the advantage of the central storage. Your changes are versioned and you can exchange the as yet unfinished results with other developers in your team who are using the same DCs.
● Local DCs – shows the components located in your local file system. DCs are displayed “flat“ in the Local View, inner DCs are displayed on the same level as outer DCs.
The Local DCs view also contains a configuration named Local Development. This configuration contains a compartment named MyComponents, in which you can create private components. These components are located only on your local file system. Other developers cannot access them. In addition, the configuration contains compartments with the most important SAP technology components and build tools (build plug-ins).
The DC views offer a hierarchically-structured overview of the compartments and components of the imported development configurations:
● The top hierarchy level contains the imported development configurations.
● Below, you see the compartments for the SCs that exist in this configuration.
● Below the SCs, you see the individual development components.
Active DCs View
In the Active DCs view, you see the active state of the development components. Use the Active DCs view to find the reusable DCs. You should always use DCs of other developers in an active state.
The DCs displayed here have been built centrally by the Component Build Service (CBS). You can download the central build results by selecting a DC in the Active DCs view and choosing Sync Archives in the context menu. The active DCs are synchronized as completed archives.
The Active DCs view also allows you to create projects for the active state of a DC or to synchronize active DCs as source code from the DTR. This can be useful if you are debugging the active state of a DC other than your own. Or for example, you can inspect the active state of a Web Dynpro DC by using the tools of the SAP NetWeaver Developer Studio.
The active state of a DC cannot be changed directly by the developer. You can only change the inactive state and then activate the change. For this reason, in projects that contain the active state, you cannot check out files for editing, delete them or add them to the DTR.
In the Active DCs view, the DCs are displayed according to the child DC hierarchy.
Inactive DCs
In the Inactive DCs view, you see the inactive state of the development components. Developers can only change the inactive state.
To change a development component, you must first create a project for the inactive state of the component.
For DCs other than your own that are edited by other teams, you should always use the active state. Remember that the inactive state means that the change has not yet been released by the other developer(s). The inactive source code cannot be compiled or the inactive state can contain some functional errors.
Newly created development components only appear in the Inactive DCs view. Only after a successful activation (that is, a successful build in the CBS), can they be seen in the Active DCs view as well. The same applies for the selection dialog used to select used DCs when creating use dependencies.
Similar to the Active DCs view, the DCs are displayed also in the Inactive DCs view according to the child DC hierarchy.
Local DCs View
The Local DCs view shows the DCs located in your local file system.
This can be:
● DCs synchronized from the DTR or CBS.
● Newly created DCs that have not yet been checked in.
● Local DCs not submitted to the source file administration in the DTR.
● DCs that were preinstalled by SAP.
After you have set up your work environment and synchronized the required DCs from DTR and CBS, you usually work with the Local DCs view in the Development Configuration perspective.
In contrast to the Active DCs and Inactive DCs view, in the Local DCs view all locally existing DCs are not displayed hierarchically but on the same level.
In the Local DCs view, decorators also display the following:
● Whether the DC must be built again (because its own content or a used DC was changed).
● Whether in the last local build errors occurred.
Sync Mode of a DC
The sync mode property specifies if a DC has to be synchronized as:
● inactive source code
● active source code
● an archive.
The sync mode is displayed in the Propertiesview if you have selected the DC in one of the three DC views. You can also gather information about the sync mode from the icons in the views:
●
(green triangle): DC is synchronized in active
state (archive or source).
●
(gray
triangle): DC is synchronized in inactive state.
● No triangle: DC does not exist locally.
See also:
Working with the Development Configurations Perspective
Working with Development Configurations