Configuring the Web Dynpro Runtime Environment - Developing Jav...

http://help.sap.com/saphelp_nw73ehp1/helpdata/en/4c/2319ca352857...

Configuring the Web Dynpro Runtime Environment

Procedure
A number of settings allow you to influence the behavior of the Web Dynpro system configuration. This is done in the archive file WebDynpro.war. This file is part of EAR file sap.com/tc~wd~dispwda.ear and is automatically deployed on the SAP NetWeaver Application Server. To configure a number of basic settings of the Web Dynpro runtime environment in file default.properties , the system administrator defines system configuration properties using NetWeaver Administrator. 01. Log in to NetWeaver Administrator either by choosing NetWeaver Administrator on your engine's Start page or by entering the following URL: http://<your host name>:<port>/ nwa 02. In the top level navigation, select Configuration Management and in the second level navigation bar, select Infrastructure. 03. Select Application Modules, and in the Module List section enter tc~wd~dispwda (or parts of this string) into the filter row. The complete path name for the module is displayed: webdynpro/resources/sap.com/tc~wd~dispwda 04. In the Web Module Detailssection, select the Web Dynpro Properties tab and select default from the corresponding table. 05. In the Full Details section, navigate to the property you want to configure, and make the required entries. 06. To save your changes, select Save in the Web Module Detailssection. Parameter Description Parameter AccessibilityChecksEnabled ActivateURLParameters Description Specifies the whether accessibility checks are enabled. If set to false, the Web Dynpro runtime ignores some URL parameters that could be set. These URL parameters are, for instance, the sap.csf.* parameters and the sap.session.plugin parameter. It's recommended to keep parameter value false in order to deactivate URL parameters that might not be available in production mode. Enables the end user to implicitly configure the Web Dynpro interface, for example to adapt fields or tables. Specifies whether Web Dynpro is allowed to use an XMLHttpRequest object for IE6 user agents. In case ActiveX is not enabled for all such clients, you can use this switch in case of warnings or errors due to the use of an XMLHttpRequest object by Web Dynpro. Specifies the expiration time in seconds when no user interaction takes place. This default expiration time is used if an application does not specify its own expiration time explicitly. Valid values: Any positive integer number Specifies whether the Web Dynpro runtime environment runs in a development mode, or not. This can affect how error messages are displayed. For example, the error message page provides detailed information about product, version, protocol, and stack trace when the Web Dynpro runtime environment runs in a development session. Specifies the Web address of the Internet Graphics Service (IGS) valid for the application. This service supports the display of the UI elements BusinessGraphics and GeoMap. The URL of the IGS is specified according the following pattern: http://<server host name>< fully qualified path name>:4<server instance number>80. Example: http://localhost:40080 Specifies whether the Web Dynpro runtime performs the optimization of inline CSS rendering. This affects server-side HTML rendering only. Specifies whether the Web Dynpro runtime uses Unified Rendering's Lightspeed control framework (instead of classic UR). This affects server-side HTML rendering only. Specifies the security level of UI security checks. UI security means that the framework checks whether a UI event is allowed in the current state of the UI element. Per default the Web Dynpro runtime throws an exception, if such a situation occurs. Valid values: integer value = 0, 1, 2 0 No Exceptions are thrown, if UI security is violated, but the violations are traced. 1 Exceptions are thrown, if generic checks like enabled, isible and read only fail, other violations are traced. 2 Exceptions are thrown, if any security violation is recognized. Note: You should only change the default, if the security exception is caused by framework bugs or known temporary inconsistencies. Default false false

AllowUserPersonalization AllowXMLHttpRequestForIE6

true true

DefaultExpirationTime

3600

DevelopmentMode

true

IGSUrl

<empty>

InlineCSS Lightspeed UISecurityLevel

true true 2

1 of 6

1/23/2013 2:32 PM

Configuring the Web Dynpro Runtime Environment - Developing Jav...

http://help.sap.com/saphelp_nw73ehp1/helpdata/en/4c/2319ca352857...

ValidateByRendering

For the Web Dynpro application to be able to handle the errors caused during data retrieval, the Web Dynpro runtime executes the request for each data set before the call of the wdDoPostProcessing() method. In this context, the request process is referred to as validation (IWDNode.validate() method), while the response to the client is referred to as rendering. The default behavior during the validation phase requires all nodes in all visible views to be validated. Specifies whether to send the data to the client zipped or unzipped. If this parameter is already defined in the http service in J2EE Engine, this parameter should be set to false . Enabling this property, node elements activate an extended sanity check on attribute access, for example regarding destruction of an element via eventing. Property used for memory report: If set to true , the memory report is written into the defaultTrace.trc file under location com.sap.tc.webdynpro.session.report, severity level INFO . Property used for memory report: Granularity level. Specifies whether the memory analyzer is activated, or not. 0 is indicating that it is not activated. Choose value 1 to activate memory reporting. Property used for serialization report: Write report into trace. If set to true, the serialization report is written into the defaultTrace.trc file under location com.sap.tc.webdynpro.session.report , severity level INFO . Specifies the problem filter which the monitor should take into account. Bit mask encoding: 1 Class uses custom serialization (i.e. class is NOT shareable) 2 Class loader is not shareable 4 Class uses non trivial finalizer 8 Class has serial persistent field 16 Class has transient fields 32 Super class does not implement serializable 64 Object is not shareable due to a complex reason 128 Class does not implement serializable (i.e. class is NOT serializable) 256 Object is not serializable due to a complex reason Specifies if the monitor is activated and if so, in which granularity information should be gathered. Valid values: 0 serialization monitor is disabled 1 serialization monitor creates a short summary report 2 serialization monitor creates a report on class level, considering only application classes 3 serialization monitor creates a report on class level, considering all classes 4 serialization monitor creates a report on object level, considering objects of all types Specifies which ActiveX version is required for Adobe Interactive-Forms. Value d efault uses the version specified by default for the current stack. Any other value: May be needed to automatically upgrade the front-end components without a server upgrade Specifies the time a Web Dynpro application waits for the zciReady message from the Acrobat Reader in milliseconds. The default value is enough for small and medium sized forms to be loaded in the browser. Applicable only for ZCI (Zero Client Install - native) based interactive forms in Web Dynpro for Java. Specifies whether a predefined popup window (Confirmation Dialog, EVS, OVS or TechnicalInfo) is displayed with the new wave line design. Messages being reported via an ICMIMessageProvider. can contain a short or a long message text. If you set this property to true you can achieve that the long message text is taken if available. Specifies whether all Web Dynpro application require authentication per default. If set to true, authentication will be required for all applications. If set to false, only those applications require authentication which have set the authentication flag in the application properties. Specifies the duration of the connection (in msec) Specifies the maximum permitted number of valid JCo destinations Specifies the maximum pool size, i.e. maximum number of simultaneously used JCo connections. Specifies the maximum wait time when calling the system (in msec). If the request fails after this time interval, it will be ended with a LockException. Specifies the blacklist of applications for which domain relaxation is not allowed. This property is only taken into account if the configuration parameter sap.domain.relaxation.enabled is set to true. Valid values: Comma-separated list of Web Dynpro applications, containing the DC name and the

true

ZipResponse

false

context.extended.validation sap-mem-report-filetrc

true false

sap-mem-report-level

sap-ser-report-filetrc

false

sap-ser-report-filter

384

sap-ser-report-level

sap.acf.adobe.CABFileVersion

default

sap.adobe.zciReady.timeout.limit

1000

sap.corecomp.useWavelineDesign sap.cmi.useLongTexts

true false

sap.default.authentication

false

sap.defaultConnectionTimeOut sap.defaultMaxNumberOfConnections sap.defaultMaxPoolSize sap.defaultMaxWaitTime sap.domain.relaxation.blacklist

30000 10 5 10000 <empty>

2 of 6

1/23/2013 2:32 PM

Configuring the Web Dynpro Runtime Environment - Developing Jav...

http://help.sap.com/saphelp_nw73ehp1/helpdata/en/4c/2319ca352857...

application short name (i.e. it is equal to the part of the application URL that follows /webdynpro/dispatcher ). Examples: sap.com/tc~wd~tools/Explorer sap.com/tc~wd~tools /WebDynproConsole sap.domain.relaxation.enabled Specifies whether domain relaxation is enabled or not. Using the parameters sap.domain.relaxation.whitelist and sap.domain.relaxation.blacklist , it is possible to specify a list of applications which are allowed to use domain relaxation, or for which domain relaxation is forbidden. false : the sap.domain.relaxation.whitelist is checked whether it contains applications for which domain relaxation should be allowed anyway. true : the sap.domain.relaxation.blacklist is checked whether it contains applications for which domain relaxation should not be allowed, although it is generally allowed. Specifies comma-separated whitelist of applications for which domain relaxation is allowed. This property is only taken into account if the configuration parameter sap.domain.relaxation.enabled is set to false, i.e. if domain relaxation is generally not allowed. Valid values: Comma-separated list of Web Dynpro applications, containing the DC name and the application short name (i.e. it is equal to the part of the application URL that follows /webdynpro/dispatcher ). Examples: sap.com/tc~wd~tools/Explorer sap.com/tc~wd~tools/WebDynproConsole Defines interoperability mode between Adaptive RFC 1 and Adaptive RFC 2 model types as for connection management: ARFC1 and ARFC2 model use same stateful backend connection in order to allow applications using different model types to interoperate. Values (all others interpreted as off): off: no connection sharing filterDestinationName: use list of destination names specified in sap.interoperability_arfc1_arfc2.filter property filterModelName: use list of qualified Java model names specified in sap.interoperability_arfc1_arfc2.filter property on: use connection sharing for all models and destinations In general, connection sharing should be restricted as far as possible as this means quite some overhead on the JCO side; That means that you should only activate it for a destination if all applications using this destination should run in interoperability mode with ARFC2. General activation should only be set for test purposes. Interoperability Adaptive RFC 1 / 2 by stateful connection sharing. General activation is only recommended for test purposes. Valid values: Off (default), filterDestinationName, filterModelName, on Defines the Web address of the HTLM page to be displayed if the application is terminated due to an invalid status of the corresponding deployable object. Web page address: /webdynpro/resources/sap.com/tc~wd~dispwda/global/deployment.htm Further possible values: Any valid absolute URL. Specifies the maximum wait interval in seconds in the Web Dynpro locking system; needed for long-runners. This is especially needed for long-runners, for which request processing takes longer than 100 seconds. This property is usually not needed and should only be modified if long-runner applications are really used. Specifies the Web address of the standard logoff page displayed when the user terminates the application. Default Web page is /webdynpro/resources/sap.com/tc~wd~dispwda/global/logoff.htm Possible entries: Any valid absolute URLs Defines the maximum number of Web Dynpro page builder sessions and Web Dynpro standalone application sessions that are allowed per security session. Valid values: values > 0 value < 0 deactivates the check value = 0 produces an exception Maximal size that an uploaded file may have (in kB, 0 for unlimited) Maximal total upload in one session (in kB, 0 for unlimited) Specifies when the workaround for a problem with Microsoft IE and https will be activated. Reason: Web Dynpro always adds the header "Pragma: no-cache" to every file transfer during download or file exchange with Adobe or office integration. IE refuses to accept a file if it is accessed via https and this header is present (http://support.microsoft.com/kb/812935). The workaround is not to add this header if the client is MSIE6. The Web Dynpro configuration parameter decides when to activate it. With default value auto the workaround will be activated if the request arrived via https. Administrators can true

sap.domain.relaxation.whitelist

<empty>

sap.interoperability_arfc1_arfc2.filter

<empty>

sap.interoperability_arfc1_arfc2.mode

off

sap.invalid.DeploymentStateURL

required

sap.locking.maxWaitInterval

100

sap.logoffURL

required

sap.max.session.limit

sap.maxUpload.file sap.maxUpload.session sap.msie.no-cache.workaround

0 0 auto

3 of 6

1/23/2013 2:32 PM

Configuring the Web Dynpro Runtime Environment - Developing Jav...

http://help.sap.com/saphelp_nw73ehp1/helpdata/en/4c/2319ca352857...

set it to yes if there is a reverse proxy between browser and server that accesses the server via http, so that the server cannot see that the browser used https. sap.noClientURL If no clients are specified in Web Dynpro configuration file clients.properties, you can use this property to configure the displayed error page. Web page address: /webdynpro/resources/sap.com/tc~wd~dispwda/global/noclient.htm Further possible values: Any valid absolute URL Specifies the default value for used portal URL. The Portal's iView runtime application is a runtime environment for processing the iViews. This function is assigned to the component iView Runtime Java (IRJ) application. How this function is used depends on the configuration of the deployed portal. The runtime ID appears in the URL after http://<hostname>:<port>/ The preview mode enables features which where implemented as an outlook for upcoming functionalities. The use of those features is allowed for demo applications only. There is no support and no guarantee that these features will be available in later versions. Specifies which port the Web service client addresses: ConfigPort_Document for http calls or SecConfigPort_Document for https calls. If the property has value request , the protocol with which the Web Dynpro application was started is used. An http setting forces the http protocol, even if Web Dynpro was called using https. Exception: There are methods in the Adobe Document Service that force https. Examples of these are suppressPrint, digital signatures, or certification. In this case, Web Dynpro switches to the https protocol itself. Summary valid values: request: same protocol scheme as current httpRequest from client http: always http (as long as no secure function of ADS is used) https: always https Defines the time span (in secs) after which a cached resource is removed from the cache. If no value is set, the time span is 30 mins. Defines whether the resources will be encrypted when dumped to a file. Defines the time span after which a cached resource is stored in the cache. Defines the time interval (in secs) in which the cache is refreshed. If no value is set, the time interval is 60 secs. Defines the directory in which the cache stores its data. Defines the expiration time (in seconds) of an SLD object that is stored in the cache. Defines the invalidation time of cached SLD objects in seconds. If an unavailable SLD should always trigger an exception, this value must be set equally to the configuration parameter sap.sld.cacheExpirationTime . Valid values: Any positive integer number. Specifies the standard language key that is used when no language key is provided by the user authentication or no value is set for the Locale configuration property of the application configuration. Therefore, a valid ISO Language code is needed. These codes are the lower-case two-letter codes as defined by ISO-639. You can find a full list of these codes at a number of sites, such as: http://www.ics.uci.edu/pub/ietf/http/related/iso639.txt Valid values: A valid ISO language code (ISO-639) Specifies whether the Technical Info and its system menu entry are permanently enabled. Valid Values: default : The value is automatically determined by the Web Dynpro runtime true: permanently enabled onRequest : disabled until the user activates it for the duration of the current application by pressing both the CTRL and ALT keys while opening the context menu (right mouse click) false : permanently disabled Currently the resulting value for default is onRequest for all system types. Specifies whether Technical Info allows to modify the set of active extensions within a running session. Requires that the Extensions tab is visible. If set to default , the resulting value is automatically determined by the Web Dynpro runtime. Currently, only the System Type as specified in the licensing is taken into account. For Development systems the set of extensions can be modified, for other system (Test, Productive), it is not shown. Valid Values: default , true , false Comma separated list of predefined Technical Info extensions. All specified extensions are activated when the Technical Info is opened for the first time in a session. There are no further checks, esp. the other configuration entries showExtensions , manageExtensions are not checked. The purpose of this Yes (required)

sap.portalURL

irj

sap.previewMode.enabled

false

sap.protocolSchemeForADSCall

request

sap.resourceCache.deletionTime sap.resourceCache.encryption sap.resourceCache.persistenceTime sap.resourceCache.pollingTime sap.resourcePool.directory sap.sld.cacheExpirationTime sap.sld.cacheInvalidationTime

<empty> <empty> <empty> <empty> <empty> 3600 86400

sap.systemLocale

<Locale of server VM>

sap.techinfo.enabled

default

sap.techinfo.manageExtensions

default

sap.techinfo.predefinedExtensions

default

4 of 6

1/23/2013 2:32 PM

Configuring the Web Dynpro Runtime Environment - Developing Jav...

http://help.sap.com/saphelp_nw73ehp1/helpdata/en/4c/2319ca352857...

configuration is to allow the extensions of the Technical Info with a set of trusted extensions that should be available in every Web Dynpro session. Be careful when extending this list. Only add trusted components. Default Value is not defined, might vary from release to release. Valid Values: no fixed value set Format of Entries: QualifiedNameOfExtensionComponent '@' EngineApplicationName The QualifiedNameOfExtensionComponent is a Java qualified name, the EngineApplicationName is the name of a deployment unit in the format as shown in the NetWeaver Administrator. If the configured list starts with a ' + ', then the configured extensions are added to the SAP defined list of extensions, otherwise the SAP defined list is replaced by the configured list. Example: co m.mycompany.TechnicalInfoAddOn@ mycompany.com/techinfo~plugin sap.techinfo.showExtensions sap.textMapping.enable sap.textMapping.objectName sap.textMapping.separators sap.textMapping.systemName sap.textMapping.systemNumber sap.textMapping.webModule sap.theme.default Specifies whether the list of Technical Info extensions is displayed in its own tab. If set to default, visibility is determined by the Web Dynpro runtime automatically. Defines whether or not text mapping is used. Specifies the name of the deployable object (=EAR file) in which the text mapping is defined. Defines a list of separators used for text mappings of a message. Defines the system name of the J2EE Engine used for text mapping. Defines the system number of the J2EE Engine used for text mapping. Specifies the name of the Web module (= name of the Web module's context root) containing the defined text mappings. Defines the URL of the Unified Rendering style sheet themes used. This value is not used if a) the Web Dynpro application runs in SAP NetWeaver Portal, or b) URL parameter stylesheet_theme is set Specifies the valid hosts for CSS URLs. Comma-separated list of hosts which are valid provider for theme URLs. The usage of placeholders is possible (the syntax may be compatible with the syntax of the regular expression). If the property is empty or missing, all hosts are allowed to provide theme URLs (this is the default setting). If a host is used that is not included in this list, the Look-and-Feel service will throw an exception. Specifies the used default theme name. Determines the maximum count of rows which can be displayed in a table. Valid values: any positive integer Comma-separated list of protocols used by the Web Dynpro URL generator as whitelist of allowed protocols. If the property is empty, the supported default protocols are http and https. If a protocol is used that is not included in this list, the URL generator throws an exception. After changing this property, the server needs to be restarted. If running in the SAP NetWeaver Portal, this flag specifies whether or not the Portal style sheets shall be used. They are used if the parameter is set to false (default). If set to true, the Web Dynpro style sheets are used also when running in the Portal. Defines the maximum size of a simple type value set which is displayed as a Simple Value Selector (DropDownByKey UI element with dropdown list). When the value set size exceeds the configured sap.valuesetlimit.maxondemand value the dropdown list is replaced by an Extended Value Selector (EVS) popup dialog. Specifies whether input validation is disabled. If set to false, the validation of data in input fields bound to numeric simple types is automatically done while the user enters data. Disables the additional validation of user input via a defined IWDOVSSuggester implementation.. To deactivate this new validation, set this property to true . More information: Providing Search Result Value Lists (OVS) Specifies whether an input field bound to a CctCode with presentation mode description is rendered as ComboBox or as DropDown UI element. If configuration is set to true the input field is rendered as a ComboBox. More information: Displaying and Formatting Core Data Types Web dispatcher host must no longer be configured but is determined automatically by Web Dynpro. Web Dynpro runtime determines a used Web Dispatcher automatically. If an explicit configuration is defined, the explicitly configured Web Dispatcher is used to create balanced application URLs. Web dispatcher port must no longer be configured but is determined automatically by Web Dynpro. default false local/ TextMappings !;,:-_+=)([]? ${SYSTEM_ NAME} ${INSTANCE_ NUMBER} <empty> <empty>

sap.theme.hosts

<empty>

sap.theme.name.default sap.ui.table.maxVisibleRowCount

<empty> 200

sap.url.protocols

http,https, ftp,mailto, file,sapacp false

sap.useWebDynproStyleSheet

sap.valuesetlimit.maxondemand

50

sap.wd.disableAsyncInputValidation

false

sap.wd.disableInputValidationUsingOVSSuggester sap.wd.showPresentationModeDescriptionAsComboBox

false

true

sap.webdispatcher.host - deprecated -

<empty>

sap.webdispatcher.port - deprecated -

<empty>

5 of 6

1/23/2013 2:32 PM

Configuring the Web Dynpro Runtime Environment - Developing Jav...

http://help.sap.com/saphelp_nw73ehp1/helpdata/en/4c/2319ca352857...

sap.webdispatcher.protocol deprecated -

Web dispatcher protocol must no longer be configured but is determined automatically by Web Dynpro.

<empty>

6 of 6

1/23/2013 2:32 PM