Configuring a Web Dynpro Application
(Java)
Purpose
This process introduces the different configuration possibilities for Web Dynpro applications.
Use of the Process
This process is part of the following IT scenario:
IT Scenario |
Scenario Variant |
Prerequisites
The Web Dynpro application has already been developed and the configuration options can be used.
Process Flow
1. Configuring the Application Entity Application
At design time, you can declare several configuration properties for your Web Dynpro application. Examples of this are the specification of an expiration time for the application (ExpirationTime) or the definition of the HTML page to be used as the logoff page (LogoffURL). The configuration property Authentication, which describes the Boolean value for the use of the authentication, is also included in the configuration options.
You set the properties of the application configuration in the SAP NetWeaver Developer Studio. For some properties, the values of the Web Dynpro system configuration are adopted if you have not already set them explicitly in the application configuration. For example, the value of the DefaultExpirationTime parameter of the Web Dynpro system configuration is used if you have not assigned a value to the ExpirationTime property of the application configuration.
2. Using the Configuration Service
The configuration service can be used for accessing configuration files that are deployed with a Web Dynpro application. The configuration data is available in the form of name/value pairs in the properties files. The IWDConfiguration interface provides methods for accessing this configuration data as typed objects. Web Dynpro offers a range of configuration properties files, and a Web Dynpro application can define its own configuration properties files. This can be done either at the level of a deployable object or at the level of a deployable object part. The IWDConfiguration interface also provides methods for accessing the properties files defined by the developer and using these properties files to read data.
To define
application-specific properties files yourself, you must use an editor to
create a properties file containing the relevant name/value pairs. You then
import this file into the corresponding directory structure in the Package
Explorer. If you want to use the properties file at the level of the
deployable object (interface IWDDeployableObject), you must import the file into the directory
/src/configurations in your Web Dynpro project. If you want to
use the properties file at the level of the deployable object part (interface
IWDDeployableObjectPart), you must import the file into the directory
/src/configurations/<type
of deployable object part>/<name of deployable object
part> in your Web Dynpro project.
Types for deployable object parts are Application, Component, or ComponentInterface. You can find a complete list of types in the
enumeration class com.sap.tc.webdynpro.services.sal.deployment.WDDeployableObjectPartType. When you deploy a Web Dynpro application
that contains properties files either at the level of the deployable objects
or at the level of the deployable object part, these property files are
deployed as properties sheets in the Configuration
Adapter of the J2EE
Engine. To change these properties files, you can use the Configuration
Adapter Service of the Visual Administrator of the J2EE Engine. You then do
not need to modify the source text or perform another deployment. If you edit
a properties file, you must restart the server for the changes to take effect.
Note that redeploying the development component overwrites any changes made to
the properties files with the Configuration Adapter.
3. Mapping Logical Systems
Mapping logical systems allows you to use functions from different back-end systems in a Java Web Dynpro application that is integrated in the SAP Enterprise Portal. You configure the logical target system name in the Web Dynpro Content Administrator. With the configuration of the Portal page, you pass the following URL parameters along with the Web Dynpro application; these parameters are then taken into account when the application is started.
sap-wd-arfc-useSys =<DEFAULT_SYSTEM>:<SUFFIX_OF_MAPPED_SYSTEM> |
There are naming conventions for the old and the new system name. If several systems are to be mapped, the parameter sap-wd-arfc-useSys can be repeated any number of times within a URL entry. One parameter entry is made for each logical system. The URL parameters for the Portal page are maintained as described in the Administration Guide of the SAP Enterprise Portal.
Example: You have developed a Web Dynpro self-service application ESSApp that uses the functions of a back-end system XYZ. The logical system names of the application are WD_MODELDATA_DEST and WD_RFC_METADATA_DEST. The application is now also to have access to the functions of a second system ABC. The targets for the logical systems are to be named correspondingly – that is, WD_MODELDATA_DESTABC and WD_RFC_METADATA_DESTABC. In the browser URL, the application call with the parameters is then as follows:
http://<hostname>:<port>/webdynpro/dispatcher/local/ESSProject/ESSApp? |
Result
Depending on the configuration options selected, the settings for the application entity application are now completed and, if necessary, logical systems have been mapped.