Start of Content Area

Procedure documentation Creating a Web Service and a Web Service Configuration  Locate the document in its SAP Library structure


A Web service configuration (WS Configuration) defines the properties of the Web service at runtime. One or more Web service configurations are assigned to a Web service.

Whenever you generate a client proxy for the Web service, a logical port is generated for each Web service configuration (see: Configure Logical Ports).

The Web service configurator knows the system landscape and the technical requirements of the application server where the Web service is to be called. In the configuration editor, he or she assigns attributes to features selected in the WSD.


You have created a VI and a WSD.



       1.      Select the EJB Module project. In the context menu, choose New  Web Service Deployment Descriptor. A deployment descriptor is an XML file in which the options you use to deploy an application are described. In the dialog box that appears, confirm this by pressing Finish.On the right, you see the WS Deployment Descriptor Editor.

       2.      Select the node for the deployment descriptor and choose Add. Choose the EJB reference and WSD. Assign the name to the Web service and choose Finish. 

       3.      Add a WS configuration. Select the generated node for the Web service (under Web Service Configurations) and choose Add.

This graphic is explained in the accompanying text

       4.      In the dialog box that appears, enter the required data. Choose the appropriate transport binding. The following transport bindings are available: HTTP SOAP, HTTP GET, HTTP POST, and SOAP with attachments. For information on the transport binding Soap with Attachments, see Creating a Web Service with Attachments.

This graphic is explained in the accompanying text

The transport binding is the same for all configurations of a Web service. Only when you create the first configuration do you have the option of choosing a SOAP or HTTP binding.

       5.      Define the WS configuration. Click the subnode of the WS configuration and make the appropriate settings.

This graphic is explained in the accompanying text





The URL suffix in the Path field is set automatically. You can change the relative path specification, if required.

The system displays information on the WSD and the EJB that are the basis for the Web service configuration.


Choose the required Authentication Type for the Web service. Only options that do not conflict with the authentication defined already in the WSD are allowed. (See also Creating a Web Service Definition.)

If the Authorization option was selected at design time, roles are assigned for the operations of the Web service. You can change the assignment by choosing Use Authorization (see also: Web Services Security).


You can enter the WSDL port name, the WSDL binding name and the address of the target server. 

       6.      Save your entries.

       7.      Create a JAR file. A JAR file is a platform-independent file format in which different files can be grouped together. Choose Build JAR File in the context menu of the module project node.

       8.      Create an enterprise application project. Choose File New Project J2EE Enterprise Assembly Project. In the subsequent dialog, select the JAR file that is to be included in the EAR project.

       9.      Select this EAR project and choose Build EAR File from the context menu. An EAR file is a JAR archive that contains a J2EE application.

   10.      Deploy the EAR file. Select it, and then choose Deploy to J2EE Engine in the context menu.

This graphic is explained in the accompanying text


Publish the Web service in the UDDI. For more information, see Publishing a Web Service as a Business Service.



You have defined the runtime properties of the Web service, deployed it, and published it in the UDDI if appropriate. The Web service is available for proxy generation on the client side. 


End of Content Area