!--a11y-->
Creating a New Library
DC 
A library DC is required as a container for other Java DCs or even other library DCs.
|
|
|
|
...
1. If you have not already done so, open the Development Configurations perspective by choosing Window ® Open Perspective ® Other... ® Development Configurations.
2. Open the Inactive DCs view and select the relevant software component.
3. From the context menu for the software component, choose Create New DC.

A wizard appears in which you can define the general attributes of the DC project.
4. Specify the DC project to be created.
Attribute |
Description |
Vendor |
Globally unique vendor ID. It is recommended that you derive this name from the Internet domain of the provider (for example, sap.com). |
Name |
Unique component
name. For more information, refer to |
Caption |
Name with which the DC is referred to in visual tools. |
Language |
Original language of the DC project. |
Local Development Component |
Flags the DC as a local DC. You should only activate this option if the DC is not to be checked in to the DTR, but only to be created locally. In this case, no assignment is made to a DTR activity. However, you can assign the local DC to an activity at a later stage in the project processing. |
Sync Used Archives |
Select this if you want to add a standard set of DCs to be used to the DC to be created. The relevant DCs are then synchronized from the DTR and listed individually in the new DC project under Used DCs. |
Type |
Choose J2EE Server Component / Library. |
5. Choose Next.
As you have not yet assigned a DTR activity, the dialog box Select Activity appears.
6. In the dialog box, choose New…
7. Enter a meaningful name for the new activity in the Display name field and add a Description.

8. Choose OK to confirm your entries.
9. If necessary, select the newly created activity and choose Next.
10. In the wizard that appears, confirm the project attributes by choosing Finish.
The wizard generates an initial project structure for the new DC. After the generation routines have been completed, the system automatically opens the J2EE Perspective and displays the logical project structure in the J2EE DC Explorer.
The generated project name is derived from the DC name as follows: <Development Configuration>~<Development Component>~<Vendor>.
In contrast to a
local library project,
DC
MetaData is generated as an additional node in this case. Here you make
all specifications that are relevant to the handling of DCs.
Furthermore, unlike a library project, the library DC only contains the XML file sda-dd.xml. The file provider.xml is missing, since the relevant specifications (dependencies) are implemented by the component model. provider.xml will be generated automatically when you execute a build for the DC at a later stage.
A public part with the name defLib was already created.
|
|
