cancel
Showing results for 
Search instead for 
Did you mean: 

how to import and export dc's form nwds to nwdi

Former Member
0 Kudos

how to import and export dc's form nwds to nwdi and what are the activities to be activited,so that the dc objects will reuse in another dc.

thanks for your valuable suggestion.

Accepted Solutions (0)

Answers (2)

Answers (2)

snehal_kendre
Active Contributor
0 Kudos

HI,

Above is clear explaination.

Just when you want to reuse any DC in other DC then you need to create public parts.

there are two types of public parts. one is API, which is used to get reference only. and another on is SDA, where you can use it as a building block(similer to add external jar files).

and when you activate any activity dont use force activation.

Former Member
0 Kudos

Hi Subba,

NWDS is a tool where you develop sap web dynpro applications. NWDS provides different perspectives to develop various applications. Once you installed your NWDS, now you import a development configuration to configure your development environment. As a developer, you cannot change a configuration.

you can open development configrations Perspective from:

Windows>>Open Perspective and choose Development Configurations.

You use the Development Configurations perspective of the SAP NetWeaver Developer Studio to manage development components (DCs). This perspective only used for Development Components but not individual web dynpro projects.

So, the The Development Configurations perspective contains the following views:

Inactive DCs u2013 this view you use only to cahnge the existing dc's are creating new DC's.

Active DCs u2013 shows all DCs from software components (SCs) that have been imported in this development configuration in the archive state, and therefore cannot be changed here.

Now select the DC on which you want to work on and from the DC context menu you see a property called Sync. The sync mode property specifies if a DC has to be synchronized as: inactive source code, active source code ,an archive.

1.Import a development configuration.

The first step for you as a developer is to import an appropriate development configuration. The development configuration is your connection to the NWDI. By importing a development configuration, you get access to all resources relevant for your work without having to search for the right sources, libraries and servers.

2.Select the components you want to develop.

In the Development Configurations perspective, you can create projects for existing components to add them to your development list, The development environment automatically loads the required source files and archives into your local file system and tries to build the selected components locally

3. Create new components.

You can use the Development Configurations perspective also to create new components .Create the new component directly in the DTR. The development environment may propose a change list ("activity") or prompt you to create a new activity to be used to record the creation of the component.

4.Synchronize the source files and libraries.

From time to time, you should resynchronize your local sources and libraries with the NWDI to receive the most up-to-date changes of other developers.

5.Change the component sources.

Before you can change a source file, you must make the intended change known to the DTR (to check out the file) and agree on an activity to record the change. You can create a new activity or use an existing one.

6.Edit components.

Depending on the type of the component you develop, you can perform components development using the Java, J2EE, WebDynpro, Dictionary or any other suitable perspective.

7. Release the changes for the central build.

After checking the changes in, you can pass them to the Component Build Service (CBS), that is, you perform the activation process.

8.Release the changes in the development landscape.

After a successful activation, pass your changes to the Change Management Service (CMS) of the NWDI, which transports your changes within the development landscape, for example, between a development system and a consolidation system.

Thanks

Krishna