Show TOC

Procedure documentationMigrating Web Service Configurations Locate this document in the navigation structure

 

To use new functionality in SOA Manager, you can migrate Web service configurations from earlier SAP NetWeaver releases to the latest SAP NetWeaver release.

With earlier SAP NetWeaver releases, Web service configurations were normally created using transactions WSCONFIG and WSADMIN (for providers), and LPCONFIG (for consumers). Although these transactions are still supported, their functionality is now superseded by SOA Manager (for both providers and consumers).

Note Note

You do not need to migrate all the Web service configurations in a system at once. You can migrate individual configurations whenever it is convenient for you.

ABAP Web services with older configurations can be used concurrently with Web services configured using SOA Manager as long as the newly migrated configurations do not need to use configuration options that are specific to the newer SAP NetWeaver release.

End of the note.

Prerequisites

You must be assigned the following roles:

  • SAP_BC_WEBSERVICE_ADMIN

  • SAP_BC_WEBSERVICE_CONFIGURATOR

More information: Checking Roles

Procedure

Note Note

Web service configurations are client-specific, so you need to perform the steps described below in each ABAP client that has Web service configurations.

End of the note.

  1. Log on to the ABAP system where the Web service configurations reside.

  2. Start transaction WSMIGRATE.

  3. Choose whether to migrate the provider configurations or the consumer configurations.

  4. To check whether a migration is possible, select Simulation only.

    In simulation mode, the existing Web service configurations are not changed.

  5. Choose Execute.

    The tool displays an overview of the (provider or consumer) Web service configurations in the current client that were created in previous SAP NetWeaver releases.

  6. Select the configurations to migrate. You can also delete configurations here. For example, if there are already configurations in SAP NetWeaver 7.10 that replace older ones.

    Since you can use both old and new configurations at the same time, you do not have to migrate all the configurations at the same time. You can migrate individual configurations at different times.

    Recommendation Recommendation

    We recommend that you first migrate a small number of provider configurations and the related consumer configurations. You can then check whether the basic business scenarios that use the existing Web service configurations are still valid. After that, you can then migrate more or all of the remaining configurations.

    End of the recommendation.

  7. Choose Execute.

    When configurations are migrated, they are either converted or deleted. None of the old configurations are retained if the migration was successful.

    Once you have migrated the Web service configurations, you can manage the new Web service configurations using SOA Manager.

Note Note

The new Web service configurations cannot be transported. The reason is that the new connections must be managed using a (central) tool.

More information: Note 1318499

End of the note.

Note Note

You cannot perform a complete migration in the background. If a migration is performed in the background, it may fail for the following reasons:

  • The fixed URL of the new Web service provider has not been calculated and has already been assigned to a different Web service.

  • The external Internet Communication Framework (ICF) alias already exists.

  • A logical port with the same name already exists for a specific consumer proxy class.

End of the note.

More Information

SAP Note 1120273

What Migration Does