#### Job sharing and page caching

This section provides a general description of how the Page Server caches and shares jobs.

When a client requests a report that has not been requested before, the following occurs:

- A new job is created. When this happens a cache is created. The cache holds the report pages as they are requested. A reference to the report job is also created. The reference has a unique ID (Request ID) that is used to access the job if it is requested again in the future.
- A refresh interval is associated with the report job. This is the time interval (Database Refresh setting in the Web Components Manager application) after which a new request for the same report results in accessing the database for updated information. In other words, if a new client requests the report after the refresh interval for the existing report job, then a new report job is created.
- If a client referencing an existing report job selects refresh, then a new report job is created and the client receives a reference to the new job.

##### Job sharing

Job sharing occurs when more than one person accesses the same instance of a report. A report job can be shared if:

- the report contains saved data and there are no selection formula (SF#) or group selection formula (GF#) commands
- the report does not have saved data and there are no selection formula (SF#) or group selection formula (GF#) commands
- the selection formula (SF#) or group selection formula (GF#) commands are identical to the formulae of an existing job.

The sharing of a report stops in the following situations:

- A client sharing an existing report job clicks refresh. In this case, a new report job is created and the client receives a reference to the new report job.
- A client sharing an existing report job submits a page request that includes one of the commands listed above. In this case, a new report job is created and the client receives a reference to the new report job.

##### Page caching

A cache, associated with each report job, stores requested pages. The pages are generated then passed to the client and stored in the cache. If another client who is sharing the same report job requests a page that is already cached, then that client receives the cached page. This can greatly reduce access time.

Seagate Software, Inc. http://www.seagatesoftware.com Please send comments to: techpubs@seagatesoftware.com