!--a11y-->
Creating Development Components (DCs) 
This procedure is used in the following development scenarios:
· Scenario 2: Development with Components
· Scenario 2+: Development with a Track
· Scenario 3: Layered Development
The difference lies in the view you select to create the DCs.
You have already imported a development configuration and are logged on to the SAP NetWeaver Java Development Infrastructure.
...
1.
Open
the Development Configurationsperspective
under Window ®Open Perspective ® Development
Configurations.
The Development Configurations Browser appears.
2. To create DCs, choose according to the development scenario:
¡ Scenario 2: Choose one of the views Active DC or Local DC
The Inactive DCsview is not used in this scenario.
¡ Scenario 2+: Choose one of the views Inactive DC or Local DC
After a successful central build in the Component Build Service, the DC is automatically displayed in the Active DCs view.
¡ Scenario 3: Choose one of the views Inactive DC or Local DC
After a successful central build in the Component Build Service, the DC is automatically displayed in the Active DCsview.
...
...
1.
To
create a DC in the context menu of a
compartment,
choose Create New DC in the appropriate
view.
A wizard for a Development Component Project appears:
2. Specify the following attributes for the component:
a. Vendor of the DC
b.
Name of the DC. For information on names, see
Component
Names.

You cannot change the name of the DC at a later time. If you configured a name service, it now performs a name reservation.
c. Caption of the DC.
d. Language of the DC.
e. Specify whether the DC is local or not.

If the checkbox labeled Local development component is enabled, the DC will be created locally. In this case, the files of the DC are located only on the local disk; they are not shared with the development landscape. You can add local DCs later to the content of the DTR.
f.
Select
the
component
type.
3. Choose Next.
On the second page of the wizard, you can make other settings, depending on the selected component type. In most cases, you can simply accept the proposed settings.
4. To create the DC, choose Finish.
Creating a new component triggers changes in the DTR. Unless the DC is local, you must now add the created files to an activity.
A window showing open activities appears:

For a new component, create a new activity.
5. Enter name and description of the new activity (you can change these values before you check in the activity).
6. Select the created activity and confirm with OK.
You can now work with the new component.

For an overview of the files in this activity,
switch to the Open Activities
view. While you are editing the component, the development
environment automatically recognizes changed, deleted or newly added files and
folders and will ask you to assign them to an activity.

If you do not want to add certain changes to an activity or if you want to include a local component into the development infrastructure at a later time, you need detailed knowledge of which files and folders are actually submitted to version control and which exist only on the local file system.
As a general rule, you should not submit any files to version-control that are stored in folders named bin or carrying a name that starts with gen.
