Show TOC

Integrating ServicesLocate this document in the navigation structure

Web Dynpro technology is based on the Model View Controller paradigm. Within this concept, the model retrieves the application data from the back-end system.

Context

The Java Web Dynpro developer always will - in addition to the user interface definition itself - either define new persistent application logic for the application, or reuse application parts, where possible. The Web Dynpro model which is a mandatory logical application unit which receives the application data from a back-end system where the data for the Web Dynpro application can originate from various sources: Either Java or ABAP application coding can be chosen to be the backend at design time, developers usually would come to the decision about the addressed back-end platform at the beginning of the project setup. In some cases, it also might be useful to first create the user interface units and then choose the back-end form, but in most cases it will be vice versa. Even defining more than one model entity for a Web Dynpro DC is possible, at any time developers then simply create a component reference for the runtime-relevant model where the Web Dynpro component is the application container unit which provides the interfaces for the data flow between the backend and the front end.

Procedure

  1. Make a decision for an available backend type.
  2. Start the model importer in Developer Studio.
  3. Select the corresponding model type in the wizard screen.

    1. Adaptive RFC Model (deprecated)

      If you have been using the ABAP platform in the past and want to provide a Java Web Dynpro user interface, then the Adaptive Remote Function Call (RFC) Model will be the right choice to start with Web Dynpro since the reuse factor is high, and development time is shortened. The Web Dynpro model importer generates Java classes out of the Business API (BAPI) or function module application data. This encapsulated data can be SAP data, or an application part which customers have developed themselves. Adaptive RFC model makes use of JCo 2.x for backend connection and as JCo 2.x is now deprecated, Adaptive RFC model is also deprecated.

    2. Adaptive RFC 2 Model

      Adaptive RFC 2 model provides a similar functionality as that of Adaptive RFC model. In addition, the model classes can be renamed during import of the model and the connection layer to backend systems uses JCo 3.0. JCo 3.0 has advantages over JCo 2.x like efficient connection handling, lesser memory requirement and faster performance. In the SAP NetWeaver Developer Studio, ARFC models can be migrated to ARFC 2.

    3. Adaptive Web Service Model

      If you plan to reuse a Web Service which is either locally available or from a Universal Description, Discovery and Integration(UDDI), then the Adaptive Web Service model is the interface you would use for your Java Web Dynpro application. The Web Services used for the Web Dynpro application can also be services that were defined in the Web Service perspective as custom development. The Adaptive Web Service Model type provides enhanced features such as renaming of Model Classes, configurable Web Service destination settings, cookie-based authentication, improved support for XML schema type constructs in WSDL, support for nested structures, advanced security settings supported via WS-R Service Extension Interfaces etc.

    4. Java Bean Model

      Web Dynpro offers support for using Java Beans for a Web Dynpro application using the Java Bean Model. The Java Bean model provides support for Java interfaces, inheriting Java Bean classes, abstract Java Bean classes and support for using Java Bean from multiple sources such as project, local jar file and public parts of used Development Components.

    5. Enterprise JavaBean Model

      In addition to the JavaBean Model, you can use the Enterprise JavaBean (EJB) Model for the Session beans. The Enterprise JavaBean Model supports you during the call of one or several EJBs to be used in the Web Dynpro application. Enterprise JavaBean Model uses Enterprise JavaBeans 3.0 and Java Persistence API (JPA )1.0. Providing an abstraction of the application business logic into the Web Dynpro components reduces the manual coding done by the Web Dynpro application developer thus allowing to concentrate on the user interface part of the application.

  4. Finish import to generate the model classes which can then be reused for model binding purposes.

Next Steps

Migrate Adaptive RFC model to Adaptive RFC 2 model