Development Configurations Browser 

You use the Development Configuration perspective of the SAP NetWeaver Developer Studio to manage development components. From there, you can load development components from central servers to your local computer, create new DCs and edit the properties of existing DCs.

TheDevelopment Configuration perspective is not used in scenario 1, because there no components are used for development.

DC Views

The Development Configuration Browser is located in the Development Configurations perspective.

It contains the views Active DCs and Local DCs:

Die...

·        Inactive DCs View: Used in these scenarios:

¡        Scenario 2+: Development with a Track

¡        Scenario 3: Layered Development.

 

·        Active DCs View: Used in these scenarios:

¡        Scenario 2: Development with Components

¡        Scenario 2+: Development with a Track

¡        Scenario 3: Layered Development.

·        Local DCs View: Used in all scenarios except in scenario 1. It shows the components located in your local file system. This can be:

¡        DCs synchronized from the DTR

¡        DCs stored as “local” DCs, but not (yet) submitted to the source administration in the DTR

¡        DCs pre-installed by SAP

The Local DCs view also contains a configuration named Local Development. This development 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”).

DCs are displayed “flat“ in the Local View, inner DCs are displayed on the same level as outer DCs.

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 software components (SCs) that exist in this configuration.

·        Below the SCs, you see the individual development components.

Scenario 2

In scenario 2, you do not use a Component Build Service. So, there is no activation of your source files. Therefore, the source files are always seen as active and can only be edited in the Active DCs and Local DCs views.

Scenarios 2+ and 3

The ”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. Usually, 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 debug the active state of a DC other that your own or if you want to inspect the active state of, for example, 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 files out for editing, delete or add them to the DTR.

In the Active DCs view, the DCs are displayed according to the child DC hierarchy.

The ”Inactive DCs“ View

In the Inactive DCs view, you see the inactive state of the development components. Developers can change only the inactive state. 

To change a development component, you must first create a project for the inactive state of the component.

For other than your own DCs, which are edited by other teams, you should never use the inactive, but always the active state. Keep in mind that the inactive state has not yet been released by the developers. You will frequently find that the inactive source codes cannot be compiled or that the inactive state contains 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, also in the Inactive DCs view the DCs are displayed according to the child DC hierarchy.

Advantage of the Distinction Between Inactive and Active DCs Views

The advantage of distinguishing between an inactive and an active state is that you can always use the inactive state to check in changes into 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 yet unfinished results with other developers in your team who use the same DCs.

Sync Mode of a Development Component

The property whether a development component was synchronized as an inactive source code, as an active source code or as an archive is called ”sync mode”. The sync mode is displayed in the Properties view after you selected the development component in one of the three DC views. You can also gather information on the sync mode from the decorator icons in the views:

·        : DC is synchronized in inactive state (archive or source)

·        : DC is synchronized in inactive state

·        No green triangle: DC does not exist locally

The 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 preinstalled by SAP (in configurations from scenario 2)

After you have set up your work environment and synchronized the required DCs from DTR and CBS, you will in the Development Configuration perspective usually work with the Local DCs view.

In contrast to 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.