The HTML DB engine actually uses two logs to track user activity. At any given time, one log is designated as current. For each rendered page view, the HTML DB engine inserts one row into the log file. A log switch occurs at the interval listed on the Manage Activity Logs page. At that point, the HTML DB engine removes all entries in the noncurrent log and designates it as current.

To truncate the activity logs manually:

Click Truncate Logs.

Click either Truncate Log 1 or Truncate Log 2.

Managing Session State

A session is a logical construct that establishes persistence (or stateful behavior) across page views. Each session is assigned a unique ID which the HTML DB engine uses to store and retrieve an application's working set of data (or session state) before and after each page view. Sessions persist in the database until purged by an administrator.

An Oracle HTML DB administrator can view session state statistics and purge session state on the Session State Management page.

Purging Sessions by Age

Using the Purge Session page, administrators can purge sessions by age.

To view specific session details:

Log in to Oracle HTML DB Administration Services.

Select the Service Administration tab.

Select Purge old sessions by age.

On the Purge Session page, specify:

The maximum number of sessions to be purged

The age of session to be purged

To view a report of session statistics, click Count Sessions.

To purge the selected sessions, click Purge Sessions.

Viewing Session Details Before Purging

Before purging sessions, administrators can use the Recent Sessions page to first view a listing of recent sessions and then drill down on session details.

To purge sessions by age:

Log in to Oracle HTML DB Administration Services.

Select the Service Administration tab.

Select Report recent sessions with drill down to session details.

On the Recent Sessions page, you can:

Click a session ID to view additional details.

Click Purge Session to delete the displayed sessions.

Viewing Session Statistics Before Purging

On the Session State Statistics page, administrators can view statistics about current sessions prior to purging.

To view session state statistics:

Log in to Oracle HTML DB Administration Services.

Select the Service Administration tab.

Select Report session counts.

Click Purge Sessions to delete the current sessions.

Monitoring Activities

Oracle HTML DB administrators can monitor user activity by accessing a number of charts and reports on the Monitoring page.

To monitor user activity:

Log in to Oracle HTML DB Administration Services.

Select the Monitoring tab.

The Monitoring page appears.

Select a chart or report to review.

Managing Engine Settings

HTML DB engine settings are named substitution value pairs defined by an Oracle HTML DB administrator. Engine setting are used internally by the HTML DB engine to determine a provisioning mode and to configure the HTML DB engine to send mail.

SERVICE_REQUEST_FLOW determines whether Oracle HTML DB is in manual provision mode or request provision mode. When in request provision mode, users can use a link on the login page to request a workspace.

When an administrator logs into Oracle HTML DB Administration Services, they can create and delete this engine setting by selecting Toggle Provisioning Mode. Clicking this link and selecting Request creates a preference named SERVICE_REQUEST_FLOW that has a value of 4700. Reversely, selecting Manual removes this engine setting.

If you enable request provision mode or enable users to reset their passwords using a link on the login page, your must configure Oracle HTML DB to send mail. In order to enable Oracle HTML DB to send mail, you must configure the following engine settings.

DEVELOPMENT_SERVICE_URL - If you are running in request provisioning mode, the value of this setting is used in the e-mail when the request is approved. This setting defines the URL for the service. If this setting is not present, the URL will be derived from your environment.

SMTP_HOST_ADDRESS - Defines the server address of the SMTP server. On installation, this will be set to localhost. If you are using another server for SMTP relaying, change localhost to that server's address.

SMTP_HOST_PORT - Defines the port the SMTP server listens to for mail requests. By default, this setting will be set to 25 at the time of installation.

SMTP_FROM - Defines the "from" address when an administrative tasks such as approving a provision request, or resetting a password generates an e-mail.