Running Web Dynpro Applications 

When you have finalized development of the complete Web Dynpro application with its components, views, backend references, and data flow definitions, you would next run the application in the chosen frontend. Generally, you would execute the following tasks in the sequence as they are listed below. In the case of test runs, or a number of them, you of course would switch between these.

Creating a Web Dynpro application

The unit which is the interface between the whole application logic and the frontend is the application unit. Application is the triggering element which is responsible for the application start itself. The application is directly bound to the application component containers and therefore with the logical units defined such as views and controllers.

More information: Creating applications

Making configuration settings for the Web Dynpro application

The Web Dynpro framework provides configuration features for runtime usage as well as for the design time logical application unit. Furthermore, you can use a range of URL parameters when using the browser as a frontend, and also some client parameters for Web Dynpro applications. In addition to the configuration options, you also can directly access a configuration service which is a runtime API.

More information: Configuring applications

Deploying a Web Dynpro application to the SAP NetWeaver Application Server

For deploy purposes, a tight integration of deployment functions and features is available within the WD Perspective. Archive creation as well as the deployment itself are started from the main Web Dynpro display view, the Web Dynpro Explorer. Server information and configuration settings of deployment popup appearance can be entered by the Web Dynpro developer. Additionally, a runtime service is available which is represented by a deployable object interface which you also can address for deploy purposes.

More information: Deploying applications

Executing a Web Dynpro application

When you start the Web Dynpro application you would distinguish between a standalone Web Dynpro application and an application which is integrated into the SAP NetWeaver Portal. Starting the Web Dynpro application means that it is executed after the development and deployment process, either for test or productive purposes, and then displayed on frontend side.

More information: Starting applications

Exiting a running application

When defining the exit point for the Web Dynpro application, you would mainly focus on the decision whether the end user shall be completely logged off, or not when leaving the application. You can also define a certain HTML page as target page after application exit.

More information: Stopping applications