ABAP Web Services (Enhanced)

Integration Scenario Definitions (New)

You can now define entire integration scenarios at design time. These scenarios are bundles of semantically related interaction patterns. The interacting parties are described semantically and only at configuration time are concrete business partners specified to replace them.

For more information, see Working with Integration Scenarios.

Consumer Mappings (New)

Consumer mappings are a mechanisms which enable consumer proxies to consume different service providers that are semantically similar.

For more information, see Working with Consumer Mappings.

Semantic Addressing (New)

You can now address business application entities directly, using Identifiable Business Contexts (IBCs). Each addressable business application entity is represented as an IBC in SAP NetWeaver. Until the concrete communication partners are known, abstract IBCs are used that only describe the communication partners semantically. At configuration time, they are replaced with the concrete communication partners.

For more information, see Semantic Addressing Using Identifiable Business Contexts (IBCs).

Web Service Persistency (New)

Web Services are now stored in a Web Service-specific persistency. All messages can still be displayed in the Web services message monitor.

For more information, see Configuring the Web Service Runtime.

SOAP Runtime (Deprecated)

The SOAP Processor 6.20 (ICF service/sap/bc/soap/) delivered with mySAP Technology Components 6.20 has been set to deprecated. With SAP NetWeaver 2004, it was replaced by the SAP NetWeaver AS for ABAP Web Services infrastructure. Within this infrastructure, the SOAP Processor 6.40 was introduced using LPConfig, WSConfig, WSAdmin, SOA Manager, SRT_TOOL, SRT_MONI, WS Adapter of PI, Enterprise Services Repository, and Services Registry.

The SOAP Processor 6.20 will be deactivated in the next release. The SOAP Processor 6.20 covering WSDL browser and WSDL generation was only used for a short period of time to access remotely enabled function modules via SOAP. It was never recommended to use the SOAP Processor 6.20 in production environment (see SAP Note 1728500 ). Since SAP NetWeaver 2004, SAP has recommended to use the new ABAP Web Service Infrastructure.

Note that the ABAP Web Services infrastructure is not affected by the SOAP processor.