Articolo web: "Transportability of Web services"

"Transportability of Web services
You want to transport a Web service (WS) configuration in an ABAP system, but notice that no option to do so is provided in transaction SOAMANAGER.
You also know that there is an optional transport connection for configurations in transactions WSCONFIG and LPCONFIG.
In addition, the selection of WS configurations and the Design Time (DT) objects (service definitions for WS provider and proxy definitions for WS consumer) underlying these configurations is not completely clear.
[...]
1. Transportability of WS consumer configurations
When transporting a WS consumer configuration from one SAP system to another, the connection information was transported exactly as it was set in the WS consumer configuration of the source system. As a result, both WS configurations pointed to the same target, which meant that the production environment and test environment had the same WS provider as the communication partner. You generally do not want this to occur. [...]  

2. Transportability of WS provider configurationsIt is also problematic for the provider to transport WS provider configurations. Generally, there are significant deviations between the security requirements of an SAP Customizing environment, development environment and production environment. [...]

3. Transportability of WS Design Time objects
The transporting of DT objects, which the WS provider (service definition) or the WS consumer (proxy definition) implement, as their own types of repository objects is still possible without restrictions.
After transporting, these objects are not automatically ready for use in the manner intended for the environment, since access to their implementation is only possible once the WS configurations are created.
The WS configuration is the entity that decides whether the transported ABAP source code of the Design Time objects can be actually used or not for a WS connection.
In more general terms, the use as WS cannot usefully be attached only to the transporting of the DT objects, but is based solely on the business scenarios to be implemented and their requirements regarding connectivity and security. The numerous service definitions or proxy definitions provided by SAP are also not intended for use in every SAP system landscape." 

Link utile: http://solveissue.com/note?id=1318499