Adaptive Web Service Model 

If you plan to reuse a Web Service which is either locally available or from a UDDI then the Adaptive Web Service Model is the interface you would use for your Java Web Dynpro application. The Adaptive Web Service Model supports both a generic and a typed usage. Generic usage includes the creation of model metadata plus Web Service invocation at runtime and is needed for example for frameworks like Web Dynpro for Visual Composer (WD4VC). Typed usage addresses the model import into the Integrated Development Environment (IDE) as well as the metadata and code generation on top of the generic model. The following picture shows the architecture of the typed use case which would be the usual case for a Web Dynpro developer.

For this Adaptive Web Service Model type, the Web Service runtime was enhanced by dynamic proxies. Another new feature is the integration with the Semantical Integration Model (SIM) for retrieving the logical ports from the Web Service destination.

The Web Dynpro runtime which is part of the JEE Engine of the SAP Web Application Server now comes with a Common Model Interface (CMI)-based metadata generation where generic Web Service model classes implement the WS-R Object Access API standard.

On Developer Studio side, an adaptation import wizard supports the developer when using the Web Services. Also new is the importer for a typed proxy generation which is executed from the Web Dynpro runtime.

Within the Visual Administrator tool, a maintenance user interface for the logical ports in the API for accessing logical ports is provided; this is relevant for destination and security settings. Additionally, the adaptive model type comes with advanced security settings: Adding a non-SAP SSO authentication ticket to the Web Service SOAP header is possible so that a cookie-based authentication for Web Services within Web Dynpro projects is possible.

Functions and Features

The new Adaptive Web Service model type comes with a range of new features and functions, in comparison to the former Web Service model type. Some of the main new features are, for example, the possible adoption of changed metadata, or the configurable Web Service destination settings which makes the availability of logical ports within the design time environment superfluous.

The table below lists the news for the Adaptive Web Service model to provide an overview of the benefits the user will get using this service.

Features and Functions	Adaptive Web Service Model
CMI (Common Model Interface) implementation	CMI implementation, generic and typed model
Adoption to changed metadata	Metadata is read at runtime, this allows adoption (in limited sense) to changed metadata
Configurable Web Service destination settings	Model uses WS runtime settings which are configurable at runtime through WS destinations and proxy settings (Visual Administrator tool); mapping of logical ports to destinations; logical ports therefore not available at design time any longer
Renaming model classes	Renaming model classes possible
URL support	Allows importing Web Service Description Language (WSDL) through URL which requires authentication; Requirement: Web Service provider system supports WSIL
Support of nested structures	Direct support of nested structure, no manual binding required
XML schema support	Improved support for XML schema type constructs in WSDL (Full support for anonymous/local types, complex types / multi-dimensional arrays)
Typed proxies	Typed wrapper on top of model; no standalone Web Service proxy class generation required. Typed model classes based on generic base and/or delegation classes; bug fixes possible without new code generation
Support of data types	Improved support for data types at runtime
Model instances	Creation and management of model instance(s) to which model objects are assigned are handled in application code
Security settings	Advanced security settings supported via WS-R Service Extension Interfaces; accessing the extension interfaces allows modifying HTTP, SOAP, and security settings (e.g. set non-SAP SSO authentication ticket)
Logging and tracing enhancements	Intervention on log level: Output HTTP request/response (including SOAP in body); Tracing of model content / SOAP traffic for problem analysis