Configuring Web Dynpro Applications
(ABAP)
Purpose
This process is part of the following IT scenario:
IT Scenario |
Scenario Variant |
Process Flow
The following process steps are performed as part of this process.
Provide Component Configurations
Components can be configured in two ways: firstly with implicit configuration options of UI elements, and secondly with explicitly developed configuration controllers that are used to control the behavior of the component. You can create special parameter sets that are designated as configurations. For example, a Web Dynpro component can have a configuration for execution in a complex expert mode, and another configuration for execution in a simple beginner's mode. The implicit configuration options can be used immediately and do not require any further adjustments in the source code.
More Information:
Personalization and
Configuration
Combining WD Components with WD Application Configurations
If multiple Web Dynpro components are brought together in one Web Dynpro application, you must specify which configuration of the individual components is to be used. The global settings are controlled by the application configuration. In particular, here you can configure the dynamic use of subcomponents. The Web Dynpro application allows the implementation of Web Dynpro components that can use other components for specific subtasks. There can be various implementations for these subtasks. The configuration may specify which subcomponents can be used at runtime. This allows various Web Dynpro components to be merged more flexibly with running applications simply by changing the configuration.
More Information:
Execute Functional Tests
You can test Web Dynpro applications and their associated components either individually in the workbench (menu option Test/Execute or function key F8), or by calling the URL for the Web Dynpro application in the client browser. The single test function is used more often in the development environment. With integration tests, quality assurance scenarios, and productive scenarios the test is either started by calling the URL in the browser or directly from the portal menu (usage type EP).
Merging of WD Applications into Portal iViews and Roles
Views of Web Dynpro for ABAP must be merged in the correct user roles so that they are available in the portal menu for user navigation. All Web Dynpro applications can be integrated easily into SAP NetWeaver Portal using the Web Dynpro iView assistant. These iViews can then be assigned to portal pages and portal roles. SAP NetWeaver Portal also provides a number of functions that help end users in their day-to-day work. These include portal event control, direct navigation between Web Dynpro applications or to other portal contents, and the work-protect mode. As with other applications that use portal services too, portal eventing and object-based navigation (OBN) are supported.
More Information: