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.
A Service Group Configuration DC is created in the SAP NetWeaver Development Infrastructure.
More information:
An Enterprise Application DC is created in SAP NetWeaver Development Infrastructure.
The dependencies between the following components are set:
EJB Module DC and the corresponding Enterprise Application DC
OR
WEB Module DC and the corresponding Enterprise Application DC
More information: Defining Development Component Dependencies
The AS Java settings are configured in
.The application server and Web service runtime are set in SAP NetWeaver Developer Studio from . In the Server field, choose SAP Server , and in the Web service runtime , choose SAP NetWeaver .
SAP NetWeaver Developer Studio is configured to connect to the SR in .
More information: Connecting the SAP NetWeaver Developer Studio to the Services Registry
If you are using a proxy to access the Internet, the proxy settings of SAP NetWeaver Developer Studio are configured in .
Import the WSDL document of the Web service 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 and classify them using the deployment units and process components that are listed in the Service Registry (SR). When you use the Web service tools in SAP NetWeaver Developer Studio, you create classified Service Groups in Service Group Configuration, Web Module, or EJB Module development components (DCs).
The tools create the classified Service Group and the corresponding service references in the respective DCs.
As a next step, you can proceed with the following tasks:
Create a Web service proxy
More information: Creating Web Service Proxies
Create a 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 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, 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 Modeling framework.
Adaptive Web service models that are created with Web Dynpro framework.
Web service operations that are created with Visual Composer framework.