Transporting abap web services

[Former Member]

guys,

i am developing an abap web service from a bapi in my dev. environment. It works as expected. Now i want to export this service to our QA box but there seems to be a problem. The URL of this service in my dev box contains the sap-client=100 but the client number in my QA system that i want to test the service is 800. so, thats an issue. how can i prevent this from happening or resolve it ?? Also, is there anything else i need to carry out in this qa client after i import the service. Please advise.

[Former Member]

Hi,

Since Netweaver Abap 7.0 SP14, you can only transport the design time configuration of web services.

You have to set up the run time configuration of web services with transaction SOAMANAGER in each system.

The reason is simple, the security, the port or the client may be different in each system.

Regards,

Olivier

[Former Member]

Hello,

After transport the service needs to be activated in transaction SICF.

In SICF you can also configure a new target client per system (eg QA system or PRD system).

Wim

[former_member66264]

If you have a user and password defined (in logon data) , you will also have to add that again

described here:

Note 732218 - ICF: Logon data from SICF is not transported