You create a Web service so that users can access the functions available in an Enterprise JavaBean or Java class that is stored in a different system.
Two roles are provided for creating Web services:
· Web Service Developer
The Web service developer defines the Web service at design time. He or she knows the application logic as well as the resulting condition for the communication type (for example, stateless/stateful), and the required security level. He or she defines these properties at an abstract level. Specific details, such as the transport binding or security concept to be used, are not defined until later, during Web service configuration.
· Web Service Configurator
The Web service configurator defines the behavior of the Web service at runtime. He or she knows the system landscape and the technical requirements of the application server where the Web service is to be called. On the basis of the abstract definition of the Web service, the configurator can decide during configuration which specific attributes should be assigned to the features defined at design time.
You must execute the following steps to create a Web service:
· Creating a Virtual Interface
· Creating a Web Service Definition
· Creating a Web Service and a Web Service Configuration
If you wish, you can then publish the Web service in the UDDI.
If you want to aggregate the steps for creating a Web service, using profiles that contain standard features, use the Web Service Creation Wizard.
To improve flexibility and reusability, you can create several virtual interfaces for each endpoint, several Web service definitions for each virtual interface, and several Web services for each Web service definition. You then provide the appropriate Web service configurations for each Web service.
To create a Web service for an EJB, see Creating a Web Service for an Enterprise JavaBean.
To create a Web service for a Java class, see Creating a Web Service for a Java Class.
See also:
Web Service Invocation (Server-Side)