You can cache the static contents that were accessed once, on the memory. By caching the once accessed static contents on the memory, and by returning a response from the cache to the browser when the static contents are accessed for second time and then onwards, you can shorten the response time of the static contents.

With a Web container, you can control the cache of the static contents by setting an upper limit for the memory size used for the cache in the Web application, and an upper limit for the file size of the static contents to be cached.

This section describes the static contents cache.

The following table describes the organization of this section.

Table 2-63 Organization of this section (static contents cache)

Category	Title	Reference
Description	Controlling the cache of static contents	2.21.1
Implementation	Definition in the DD (Settings for each Web application)	2.21.2
Settings	Execution environment settings	2.21.3

Note:

There is no specific description of Operations and Notes for this functionality.

Organization of this section

2.21.1 Controlling the cache of static contents

2.21.2 Definition in the DD (Settings for each Web application)

2.21.3 Execution environment settings