Show TOC

Re-importing Adaptive Web Service ModelsLocate this document in the navigation structure

Use

You re-import Adaptive Web Service (AWS) models to obtain the latest web services that need to be consumed by the composite or the application.

Procedure

Re-importing an AWS Model in a Service Group Configuration scenario

  1. In Web Dynpro Explorer , select the imported AWS model.

  2. To preview the changes in a model structure due to reimport, choose Reimport Preview using the right mouse button.

  3. Use the information provided in the ReimportPreview wizard such as, addition, deletion or modifications in model class relations or properties and decide if you wish to proceed with the model reimport.

  4. Using the secondary mouse button, choose Reimport Model and follow the steps in the Reimport Model wizard.

  5. Select the source of the WSDL and the WSDL to be imported (preferably the previously imported WSDL).

  6. In the Reimport Model window, you can select choose existing to select the existing service group. You can select Create new to create a new service group.

    Note

    Existing service group is selected if same WSDL is to be used else to consume a new WSDL a new service group is created.

  7. You can view and edit the model class names, if required. The model classes renamed during import are preserved.

    Note

    If name clashes occur, you need not manually rename the typed model classes; system resolves them automatically. However, system allows you to rename the system generated typed model classes.

    You can view and compare the model class name changes in the import log.

Re-importing an AWS Model in a non-Service Group Configuration scenario

  1. In Web Dynpro Explorer , select the imported AWS model.

  2. Using the secondary mouse button, choose Reimport Model .

  3. Select the source of the WSDL and the WSDL to be imported (preferably the previously imported WSDL).

  4. Define the logical destinations.

    If you have selected the Use destinations for metadata and execution the Default Metadata Destinations and Default Execution Destinations are pre-populated.

  5. You can view and edit the model class names, if required. The model classes renamed during import are preserved.

    Note

    If name clashes occur, you need not manually rename the typed model classes; system resolves them automatically. However, system allows you to rename the system generated typed model classes.

    You can view and compare the model class name changes in the import log.

  6. Optional: To configure the runtime destinations, choose the re-imported Model.

  7. Using the secondary mouse button, choose Configure Destination.

    For more information on how to configure destination, see: Destination Service