Show TOC

 Migrating Web Dynpro Development ComponentsLocate this document in the navigation structure

Use

Use this procedure to reuse the DCs available in the SAP NetWeaver 2004 and SAP NetWeaver 7.0 environment in the latest SAP NetWeaver CE 7.1 or higher.

The migration task includes a few subtasks that are mandatory for building the Web Dynpro DCs. The remaining optional subtasks need to be performed if you want to make use of the new functionality provided by the higher SAP NetWeaver CE 7.1 or higher.

You can find details related to migration considerations and other noteworthy information from the following topics:

Procedure

1. Migrating DC dependencies

For more information, see Running the Application Projects Migration Wizard .

2. Migrating Internal APIs to Public APIs

Note

We recommend you do not use internal APIs as they are subject to change at any time and also can undergo semantic changes without warning. For more information, see SAP Note 928485.

  1. Choose the project that needs API migration.
  2. Using the secondary mouse button, choose Repair → Internal Web Dynpro APIs usage.

3. Optional: Migrating Component Interface Definitions

Note

An existing Web Dynpro Component Interface Definition (CID) should only be migrated to the new component model in specific cases.

For more information, see Decision to Migrate a Component Interface Definition .

  1. Select the CID to be migrated in the SAP NetWeaver Developer Studio.
  2. Using the secondary mouse button, choose Migrate.

4. Optional: Migrating Components

Note

An existing Web Dynpro Component should only be migrated to the new component model in specific cases.

For more information, see Decision to Migrate a Component .

  1. The WD components which have not been migrated are displayed in gray. Select the gray-colored Web Dynpro component to be migrated in the Developer Studio.
  2. Using the secondary mouse button, choose Migrate.

    The tool opens a cheat sheet which guides you with a list of instructions to migrate the components.

    For more information, see Cheat Sheet .

5. Optional: Migrating Model

  1. Migrating Adaptive RFC Model to Adaptive RFC 2 Model
  2. Migrating to the Adaptive Web Service Model Type

6. Optional: Migrating Fusion

  1. Start the console by <instance-dir>\SYS\global\com.sap.dtr.console\run.bat.
  2. Connect to the Design Time Repository (DTR) containing the source track with the unmodified Web Dynpro project using the connect command (help connect).
  3. Connect to the DTR containing the target track which should contain the migrated Web Dynpro project.
  4. Call copyAsFusion -targetSession <targetDtrSession> -r .*\.wdmodel,.*\.wdcomponent /ws/<sourceTrackname>/<SCName>/dev/inactive/DCs /ws/<targetTrackname>/<SCName>/dev/inactive/DCs <activityname>.
    Note

    You need to rebuild your project after you have completed the above migration steps.