One of the following DCs is created in SAP NetWeaver Development Infrastructure:
WEB Module DC.
The WEB Module DC in the project is version 2.5.
EJB Module DC.
The EJB Module DC in the project is version 3.
An enterprise application project DC is created in the SAP NetWeaver Development Infrastructure.
More information:
A dependency from the EAR project DC to the Web Module DC or the EJB Module DC is set. More information: Defining Development Component Dependencies
The AS Java settings are configured in
The application server and Web service runtime are set in the SAP NetWeaver Developer Studio from
In the Server field, choose SAP Server, and in the Web service runtime, choose SAP NetWeaver.
Import the WSDL document of the Web service that you want to consume in the Web Module DC.
More information: Importing WSDL Documents in the SAP NetWeaver Developer Studio
You can create Service Groups that are referred by multiple services in the same development component (DC) in which you create the consumer application. These Service Groups are private for the consumer and you cannot reuse them in other consumer applications.
The tools create the Service Group and the service references in the Web Module DC or the EJB Module DC.
As a next step, you can proceed with the following tasks:
Create a Web service proxy.
More information: Creating Web Service Proxies
Create the Web service client application.
More information: Creating Web Service Client Applications
Deploy the Web service client on the application server (for deployable proxies only).
More information: Building, Publishing and Removing Published Java EE Applications
Configure the Web service client in the SAP NetWeaver Administrator.
More information: Configuring Web Services and Web Service Clients in the SAP NetWeaver Administrator
When you deploy the application on the consumer system and there is an established connection from the consumer system to the Services Registry (SR), SOA configuration for connectivity checks the provider systems listed in the SR. If there is a system providing the Web services that you want to consume and a connection to this system is established, SOA configuration for connectivity automatically creates assignment to this system and creates configuration entities (logical ports).
Note that SOA configuration for connectivity checks only the names of the provider system and the consumed services. The connectivity settings in the communication profiles and the policies in the service endpoints are not taken into account at this stage. Even if the names of the provider system and the consumed services match, the automatic assignment may still fail if the policies in the profiles and service endpoints do not match.
In addition, the following entities may not be configured properly if the policies in the profiles and service endpoints do not match, even though the system displays them as successfully configured.
Callable objects that are created with Guided Procedures framework.
Automated activities and events that are created with Business Process Management framework.
Adaptive Web service models that are created with Web Dynpro framework.
Web service operations that are created with Visual Composer framework.