Migrating Projects to the Development
Infrastructure
Use
When you work with the SAP NetWeaver Development Infrastructure (NWDI), you must structure your development in accordance with the SAP component model. The procedures described here allow you to migrate projects that do not correspond to the component model to the component model and the NWDI. The component model does not make changes to the development objects such as classes; therefore, the source files can usually be copied using Copy & Paste.
The migration discussed here is the migration on the source file level. For information about the procedure for functions that are available only as archives (binaries), see External Library DC.
Prerequisites
You work in the SAP NetWeaver Developer Studio.
Procedure
...
1. Create development components (DCs) with the appropriate name and type for the existing projects. See Creating Development Components.
A DC in this case corresponds to an Eclipse project. For more information about naming DCs, see tips for naming components and Structuring Development Components.
2. Open the Package Explorer view to see both the DC projects and the non-DC projects.
3. Copy the objects/packages from the non-DC projects to the appropriate folders of the DC projects.
4. Identify the objects that are used by other DCs and add them to the public parts of the DC. See Changing Public Parts.
5. Add the use dependency to the new DCs to the metadata of the using DCs. See Changing Public Parts.
6. Adapt the descriptors if required.
See also: