At design time, you can declaratively specify several predefined or self-defined configuration properties that you want to use to configure your WD application. The configuration parameters are are assigned to the logical Application unit. The available pre-defined configuration properties include:
The configuration property Authentication describes a Boolean value (true orfalse) that specifies whether or not a WD application requires authentication when started. If you assigned the value true to this parameter, the application requires a user authentication. Default setting isfalse, no authentication is required.
The configuration property LogoffURL specifies the Web address of a Web page that is displayed when the user terminates the application. If you do not assign a value to this configuration property, a default logoff page is used. Any valid, absolute Web address can be used for logoff. Note that the HTML file that describes the logoff template can be referenced like any other resource – for example,html/myLogoff.htm. The htm logoff page is contained in thewebdynpro.wda archive file.
The configuration property ExpirationTime describes the lifetime (in seconds) of a WD application on the server before the application is terminated by the server. A valid value for this setting is any positive integer where the value assigned to the DefaultExpirationTime parameter in the system configuration is used as the default value. Therefore, the expiration time configuration setting within the Developer Studio is an optional one for the application.
The configuration property Locale specifies the language key locale, which is used for the WD application. The value of this property is used if the user does not explicitly specify a property. The default language key locale is specified in the system configuration by the sap.systemLocale parameter. Valid values for language keys comply with the ISO standard 639. An ID is made up of two lower-case letters – for example, de for German or en for English.
As a content administrator, you can create individual iViews from each view in an application, in order to rearrange the layout of the application and to incorporate non-Web Dynpro iViews among the Web Dynpro iViews. To do this, the application must be developed to be split up into different iViews. The iView splitting itself is done within NetWeaver Portal; by assigning the iViewSplitting parameter to the Web Dynpro application unit, you would prepare the whole application, or the user interface units respectively, for this splitting process.
The application unit has been created and is displayed in the Web Dynpro Explorer. Alternatively, you can configure the unit within the same wizard that you would use for creation of the application.
1. Start the edit mode for the application to be configured in the Web Dynpro Explorer in the Applications folder: Choose Open from the context menu.
2. Select New in the application properties view to select one of the pre-defined application configurations DefaultLocale, ExpirationTime, LogoffURL, SuspendExpirationTime, iViewSplitting, or DomainRelaxation.
For some properties, the values of the WD runtime configuration are adopted if you have not already set them explicitly with the application configuration. For example, the value of the DefaultExpirationTime parameter of the WD system configuration is used if you have not assigned a value to the ExpirationTime property of the application configuration (see Configuring the Web Dynpro Runtime Environment).
3. Redeploy the application if the configuration settings have been done after the initial deploy process. The redeployment makes the values become valid.
You can also create your own application properties as name/value pairs by selecting User defined. Also in this case, you would redeploy the application if the configuration settings have been done within an edit step after initial deployment.
More Information: Configuration Service