Developing Java Applications Using Web Dynpro 

Complete descriptions of the IT processes, which are part of this scenario variant, can be found under Developing Java Applications Using Web Dynpro in the documentation section IT Scenarios At a Glance.

Steps

The current scenario variant comprises the following phases, which you process in the context of Web Dynpro application development:

       1.      Model the complete Java Web Dynpro application, including the back end to be used.

                            a.      Plan the back end to be called, which obtains the data for your Web Dynpro application. The back end is specified by means of the Web Dynpro model definition and use access.

                            b.      Arrange the Web Dynpro application into development components, which are infrastructure entities. This step is carried out in the context of the Web Dynpro project to be set up.

                            c.      The navigation within the Web Dynpro application and the Portal Navigation must be taken into account during the modeling. You will usually first plan the navigation between the views of the application. However, you should already consider at an early stage what function your application is to have within the SAP Enterprise Portal (EP).

       2.      Develop the Java Web Dynpro application using the design time tools in the development environment, the SAP NetWeaver Developer Studio. All Java Web Dynpro tools are available in the Web Dynpro perspective.

                            a.      Implement the back-end model, such as the Adaptive Remote Function Call (Adaptive RFC) model, using the Web Dynpro Model Tools.

                            b.      Define the data binding. The term data binding refers to the data flow between a UI element and the controller context or between the controller context and a back-end model. For this reason, SAP has added Web Dynpro-specific properties to the standard Eclipse Properties view, which enable direct navigation to the controller context for definition purposes.

                            c.      Implement the view layout in the graphical View Designer tool. Choose the required UI elements from the range provided. There is also a Favorites category, which lists the most frequently use elements.

                            d.      Deploy the application on the Java engine of the SAP Web Application Server. During Web Dynpro development, you can query the current status of your engine using the J2EE view.

                            e.      Debug and test the Web Dynpro application, including functional application tests. A separate perspective is available for the debugging process.

                              f.      Manage the lifecycle of the Web Dynpro application: The SAP NetWeaver Development Infrastructure NWDI is used for the management and versioning of Web Dynpro applications. Explicit integration via context menu entries is available for the check-in and check-out process for the individual application entities.

                            g.      In the NW Developer Studio, choose Window ® Preferences ® SAP J2EE Engine and enter the server settings for the Java engine of the SAP Web Application Server.

                            h.      If necessary, you can use the Configuration Service provided by Web Dynpro for application settings. Furthermore, a Web Dynpro application can also define files for the configuration.

                              i.      If you have used the Adaptive RFC model, you can map the logical systems. This enables you to use functions from different SAP back-end systems in a Web Dynpro application integrated in the EP.

       3.      Adapt the Java Web Dynpro application for the end user, or enable the end user to adjust the application to suit his or her requirements.

                            a.      Internationalize the user interface to ensure that the application is multilingual. SAP supports the Java standard and creates resource files, but also provides an input form. Developers are thus able to send users detailed information electronically.

                            b.      Personalize the Web Dynpro application using the corresponding functions of the Portal, as described under User Guide ® Personalization.

                            c.      If necessary, carry out an implicit configuration of the Web Dynpro application to adapt the user interface accordingly. Examples of implicit configurations are the role-specific altering of labels or changing the visibility of fields.