Show TOC Start of Content Area

Procedure documentation Migrating to the Adaptive Web Service Model Type  Locate the document in its SAP Library structure

Use

Web Dynpro applications that were developed using the non-adaptive Web Service Model type still run with NetWeaver Support Packages that support the Adaptive Web Service (AWS) Model.

Prerequisites

The Web Service model that you want to migrate is bound to a Web Dynpro component controller context.

Procedure

To run an existing non-adaptive model within the Web Dynpro runtime that supports Adaptive Web Service Models, work through the following steps in the specified order.

       1.      In the model import wizard, select the Import Adaptive Web Service Model option and follow the instructions given by the wizard: For the model package, enter a new one, for example com.sap.migration.demo.model. Choose a WSDL file or URL to be imported.

       2.      Identify the Web Dynpro component including its component controller and views which have to be adapted to the new model type.

       3.      Add the usage reference for the Adaptive Web Service model by choosing Add Existing Model under the Used Models node in the logical hierarchy of the Web Dynpro component in the Web Dynpro Explorer view.

       4.      Open the Data Modeler tool for the Web Dynpro component in question. Create a data link between the component controller and the Adaptive Web Service Model. Start the graphical link definition on the controller unit. The model binding wizard now appears.

       5.      Drag and drop the request model classes from the model context on the left to the controller context on the right. Select the model class property and the related model class according to the requirements on the views. The Edit Context Mapping wizard now appears.

       6.      Check all the attributes under the request and response classes, and rename the context node.

       7.      Assign the relevant request classes and response classes from one context structure to the other, using drag and drop.

       8.      Create another context structure in parallel to the existing context structure. For each view dealing with the model, either adapt the existing mapping as described above, or remove the model context mapping and map via the component controller context. Now create a context mapped to the model nodes in the controller context.

       9.      In the Data Modeler tool, display the component and double-click on the link between the view and the component controller. In the Edit Context Mapping wizard, you drag and drop the request class from the new model to the context on the left. Check all the class attributes.

   10.      Similarly, drag and drop all other request classes for mapping, if needed. Save the project.

   11.      You need to adapt the UI element properties to the context bindings. Double-click on view to start View Designer, and select the Layout tab. Click on the field for which you want to define the mapping, for example an input field, and map the value to the corresponding context value. Do the same for all UI elements which you need the mapping for in this view. In the next step, perform the same steps for all other views.

   12.      Save all metadata and carry out a rebuild on the Web Dynpro project. Finally, deploy and run the application as usual.

End of Content Area