The Web Services toolset is integrated in the SAP NetWeaver Developer Studio. Wizards and various tools enable you to create and consume Web services.
Providing Web Services on the SAP Web application server is supported in the following ways:
· Configuration with the help of Wizards
Enterprise JavaBeans (EJBs) and Java classes can be provided as Web services without additional programming effort. You create a Web service for an EJB using the Web Service Creation Wizard. In this case, the Web services properties are defined in a preset, selectable profile. If you wish to define the properties of the Web service yourself, that is, properties such as interface, security features, and so on, or if you wish to provide a Java class as a Web service, create a Virtual Interface, a Web Service Definition, and a Web Service Configuration.
· Virtual Interfaces
Using virtual interfaces, you can define several views of an implementation and publish these separately as a Web service. When you create virtual interfaces, you can rename or hide methods and parameters of the EJB. You can define standard values for parameters and convert parameter types. In addition, you can define the way the parameters are to be represented in the SOAP message (element or attribute, namespaces, and so on).
· Web Service Definition and Web Service Configuration
Features such as communication type or authentication level are assigned in the Web service in abstract form. The technical features are specified in the Web Service configuration. Therefore, a Web service definition can be used for various application servers that are different with regard to their technical setup. The proxy generation on the client side refers to the Web service definition. Technical details that are predefined in the Web service configuration are configured separately in the WS client runtime.
The SAP Web AS and the Web Service Proxy support the encryption of data that are transmitted using HTTP with the help of the Secure Socket Layer Protocol (SSL). Roles can be created for session beans and Java classes. The roles are assigned to users.
· Publication of Web Services in UDDI Registries
Web service definitions can be published as tModels and deployed Web services as business services.
The Web Service Framework supports the use of provided Web services in the following ways:
· Generating the Web Service client proxy configuration on the basis of a WSDL description and on the basis of executing client programming in the Developer Studio.
· UDDI browser for searching for suitable Web services
of the SOAP runtime on the client side through logical ports
Using logical ports, you can make settings such as authentication of the user, and so on. This makes calling services easier for the Web service client proxy.
The Web Service Homepage provides utilities for developing and using Web Services. A separate homepage is generated for each Web service. The homepage contains the documentation of the Web service. Standalone proxies can be created and Web services can be tested here.
Web services are fully integrated into the J2EE engine. Administrative tasks can be performed in the Visual Administrator of the J2EE engine. For example, you can publish deployed Web services as business services in the UDDI, or you can call the Web service homepage.
Web Services that were deployed on the local J2EE Engine can be displayed using a view in the SAP NetWeaver Developer Studio. You can call up the Web service homepage for each web service and deployable and standalone proxies can be generated from the Deployed Web Services View.