Ansicht
Dokumentation
icm/HTTP/file_access_ - Static file access specification
rdisp/max_wprun_time - Maximum work process run time
rdisp/max_wprun_time - Maximum work process run time
This documentation is copyright by SAP AG.
------------------------------------------------------------------------
| Parameter : icm/HTTP/file_access_<xx> |
------------------------------------------------------------------------
------------------------------------------------------------------------
| Short Description : Static file access specification |
------------------------------------------------------------------------
------------------------------------------------------------------------
| Parameter description : |
| ----------------------- |
| This parameter determines for which URL prefixes static file |
| accesses should be made, and in which directory the |
| static files are kept. |
| If a page or file underneath the "virtual_root" is accessed, the |
| "virtual_root" is replaced by the "document_root" and the handler |
| attempts to read the file from the file system and to send it back |
| to the client. |
| |
| Display Contents of Directory |
| ========================== |
| You can also define a directory index with this parameter. Use the |
| following options to do this: |
| - BROWSEDIR: Use this to determine the level of detail of the list. |
| The following values are possible: |
| 0: Function is deactivated, the contents of the directory |
| are not displayed |
| 1: Only the file names are displayed |
| 2: File names are displayed with size and last change date |
| |
| - DIRINDEX: Name of a file that is to be displayed instead of the |
| contents of the directory. |
| - IGNORE: You can use this to restrict the display of the contents |
| of the directory. Files that match the pattern are not lsited. |
| |
| |
| Caching in the ICM Server Cache |
| =========================== |
| You can use the option CACHECTRL to specify the cache period in |
| seconds. This is the length of time for which the ICM temporarily |
| stores the data after it has sent it to the client. If the same |
| request comes again during this length of time, it is met from the |
| cache. For possible values, see below. |
| |
| Caching of Objects in Client/Browser |
| ====================================== |
| You can use the option MAXAGE to specify in seconds the period for |
| which objects are cached in the client/browser cache. |
| This value is set in the HTTP response with the HTTP header field |
| Cache-Control: max-age=<duration in seconds> |
| Information is provided below about possible values. |
------------------------------------------------------------------------
------------------------------------------------------------------------
| Application area: Internet Communication Manager |
------------------------------------------------------------------------
------------------------------------------------------------------------
| Unit : Special character string (see below) |
------------------------------------------------------------------------
------------------------------------------------------------------------
| Default Value : Not Activated |
------------------------------------------------------------------------
------------------------------------------------------------------------
| Who is permitted to make changes: The customer |
------------------------------------------------------------------------
------------------------------------------------------------------------
| Limitations for Operating Systems: None |
------------------------------------------------------------------------
------------------------------------------------------------------------
| Limitations for Database Systems: None |
------------------------------------------------------------------------
------------------------------------------------------------------------
| Are other parameters affected or dependent: No |
------------------------------------------------------------------------
------------------------------------------------------------------------
| Valid Input, Formats, Areas: |
| icm/file_access_<xx> = PREFIX=<URL-Prefix>, DOCROOT=<Root
| directory of the files>,BROWSEDIR=<n>,
| DIRINDEX=<file>,IGNORE=<pattern>,
| CACHECTRL=<caching period in seconds>, |
| MAXAGE=<duration in seconds>, |
| ARCHIVE=<SAR archive> |
| <xx> must be entered, ascending from "0".
| If you want to deactivate the caching of file objects in the ICM |
| server cache, set the value of CACHECTRL to 0 or -1. If you want to |
| cache objects, set CACHECTRL to a positive numerical value in |
| in seconds. For example, CACHECTRL=+7200 means that file objects are |
| to be cached for two hours. |
| Default Value: +3600 |
| If you want to activate the caching of objects in the client/ |
| browser, set the value of MAXAGE to a positive numerical value in |
| seconds, such as MAXAGE=+3600. |
| Always explicitly specify the plus sign for these options. |
| This means that the client/browser can then load the object from the |
| browser cache for a maximum of one hour. |
| The default value for MAXAGE is not set; that is, no objects are |
| cached in the client/browser. |
| You can use the argument ARCHIVE to specify an SAR archive that is |
| to be extracted in the directory of DOCROOT when starting. So that |
| this is not done every time, the system checks whether the archive's |
| time stamp is older than the one in the file last_update.txt. |
| |
| Examples: |
| |
| icm/HTTP/file_access_0 = PREFIX=/docs/, DOCROOT=/tmp/documents, |
| MAXAGE=+3600 |
| icm/HTTP/file_access_0 = PREFIX=/doc/, DOCROOT=/documents, |
| DIRINDEX=index.htm,BROWSEDIR=2, |
| IGNORE=core . *.dll *.info *.bak #* ~* |
------------------------------------------------------------------------
------------------------------------------------------------------------
| Short Description : Static file access specification
------------------------------------------------------------------------
------------------------------------------------------------------------
| Applications Area : ICM
------------------------------------------------------------------------
------------------------------------------------------------------------
| Parameter Type : S
------------------------------------------------------------------------
------------------------------------------------------------------------
| Changes allowed : X
------------------------------------------------------------------------
------------------------------------------------------------------------
| Valid for Operating System : *
------------------------------------------------------------------------
------------------------------------------------------------------------
| Dynamic switchable :
------------------------------------------------------------------------
------------------------------------------------------------------------
| Same on all Servers :
------------------------------------------------------------------------
Vendor Master (General Section) SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up
This documentation is copyright by SAP AG.
Length: 9809 Date: 20240425 Time: 152646 sap01-206 ( 7 ms )
