Adding WD-Specific Parameters to URL (SAP Library - SAP NetWeaver Composition Environment Library)

Adding WD-Specific Parameters to URL

The URL of the WD application is provided by deploying the WD application on the NetWeaver Application Server. The URL for a locally deployed WD application looks as follows:

http://<HostName>:<PortNumber>/webdynpro/resources/local/<WD DC>/<WDApp>

The URL for an application which was deployed to the SAP NetWeaver Development Infrastructure and therefore uses a development component as container consists of:

http://<HostName>:<PortNumber>/webdynpro/resources/<Vendor>/<DC>/<WDApp>

Available URL Parameters

With the URL parameters described below, you can influence how the WD application is launched from the URL. You simply would add the required parameter in the URL address field.

· sap-accessibility

¡ This parameter can be used to activate the unrestricted mode. For value true or X, the settings for the user master record are overwritten and unrestricted mode is activated. We recommend that you maintain the settings for the unrestricted mode using the SAP User Management Engine (UME) in the user master record.

· sap-cssurl

¡ You can use this parameter to determine the Cascading Style Sheet (CSS) to be used and thus to display the WD application in a design that meets your company requirements. The value to be assigned is a URL. Therefore, the CSS to be used has to be stored in a JEE Engine directory. The default themes that are provided by SAP are located in the following URL:
sap-cssurl=http://<Host-Name>:<Port-Nummer>/webdynpro/resources/
sap.com/tc~wd~dispwda/global/SSR/themes/sap_chrome/ur/ur_ie5.css.

¡ We recommend that you save your company-specific CSS in this directory as well.

· sap-locale

¡ You use this parameter to overwrite your language preference settings in the user master record, which is maintained using the User Management Engine (UME). The value to be assigned corresponds to the language ID for the language with which the settings should be overwritten. If the WD application does not require user authentication, you can use it to set the required language preference. The value to be assigned contains a character string with two lowercase letters, which indicate the language, optionally followed by a hyphen or underscore and two uppercase letters, which indicate the country. The abbreviations of language and country in this character string correspond to the default language ID according to ISO standard 639. For example, if you want to display the WD application currently displayed in English in German instead, you have to assign the value de_DE or de-DE.

¡ The required language can only be displayed if the corresponding resource bundle is available. Otherwise, the WD framework follows a given search mechanism to find the most suitable resource bundle.

¡ The language preference is usually specified by the Web browser’s language setting.

· sap-rtl

¡ You would use this parameter to determine whether the WD application is displayed from right to left. The WD application is displayed from right to left for the value true or X.

¡ As the WD application does not automatically display from right to left, even if the user logged on in Hebrew, for example, you would have to pass this parameter to the application then.

· sap-wd-arfc-useSys

¡ You use the parameter to map an existing logical system name to another logical system name. You can use this mapping function with a single Adaptive RFC Model to access different backend systems using a single JEE installation. This mapping is valid for the current application instance only.

¡ Note that mapping definitions can only be changed when WD application is not in running mode.

· sap-wd-client

¡ The parameter allows specifying the protocol between the server and the client. You can assign the following values to this parameter:

§ HtmlClient: The server provides the WD application in HTML format to the client.

§ XmlClient: The server provides the WD application in XML format to the client.

§ WmlClient: The server provides the WD application in WML format to the client. The server automatically transfers the WD application in this protocol to the mobile end device using the device detection mechanism, which is why this value is only relevant if you want to force displaying the application in a Web browser on an ordinary desktop PC when you develop mobile WD applications.

§ PieClient: The server provides the WD application in a special protocol for displaying the application on mobile devices that support a Pocket Internet Explorer (PIE). The server automatically transfers the WD application in this protocol to the mobile end device using the device detection mechanism, which is why this value is only relevant if you want to force displaying the application in a Web browser on an ordinary desktop PC when you develop mobile WD applications.

§ NokiaS80Client: The server provides the WD application in a special protocol for displaying the application on Nokia Series 80 devices (Opera browser) and Nokia Series 60 devices (S60 OSS browser). The server automatically transfers the WD application in this protocol to the mobile end device using the device detection mechanism, which is why this value is only relevant if you want to force displaying the application in a Web browser on an ordinary desktop PC when you develop mobile WD applications.

· sap-wd-clienttrace

¡ You can use tracing to find out information about the processing steps during execution of a WD application. If runtime errors occur, you would trace this process and assess it to find the error. The information is displayed in a popup directly in the user interface.
Using the parameter sap-wd-clienttrace you can determine the appropriate trace level. The chosen trace level determines how detailed the runtime information should be displayed:

§ 0 = Switches tracing off

§ 1 = Displays serious errors, which means that the application cannot be continued, and that there are errors that may affect the application

§ 2 = As level 1, additionally providing warning

§ 3 = As level 2, including additional notes for users

§ 4 = As level 3 with enhanced information; this level should be used for debugging purposes

§ 5 = As level 4 and also displays the current view assembly, its window, user interface elements and so on

These URL parameters can also be configured from Preferences using Web Dynpro àProject Handling. The parameters are appended to the URL for launching a Web Dynpro application from NWDS.

Procedure

...

1. Open Windows à Preferences.

2. Navigate to Web Dynpro àProject Handling.

3. Configure URL properties and choose OK.