15 Managing Services

This section provides information about managing Oracle HTML DB services. Oracle HTML DB administrators can use the Manage HTML DB Services application to manage log files, purge session state, monitor developer activities, and manage engine settings.

This section contains the following topics:

• Managing Logs

• Managing Session State

• Monitoring Activities

• Managing Engine Settings

See Also: "About the Oracle HTML DB Administrator" for more information on different administrator roles

Managing Logs

Oracle HTML DB administrators can manage the following log files on the Manage Logs and Files page:

• Developer activity logs

• External click counting log

• SQL Workshop logs

• Page View Activity logs

To manage log files:

1. Log in to Oracle HTML DB Administration Services. (See "About the Oracle HTML DB Administrator".)

2. Under Manage HTML DB Service, select Manage Logs.

   The Manage Logs page appears.

3. Select one of the following:

   • Developer activity logs, review with option to delete entries

   • External click counting log, review with option to truncate

   • Review SQL Workshop logs

   • Review page view activity log, with option to truncate

Deleting Developer Activity Log Entries

Clicking Developer activity logs, review with option to delete entries links you to the Developer Activity Log.

To delete a specific number of log entries:

1. Click Manage.

2. Specify the age of the entries to be deleted and click Delete Entries.

Deleting Click Counting Log Entries

Clicking External click counting log, review with option to truncate links you to the Click Counting Log.

To delete a specified number of log entries:

1. Click Manage.

2. Specify the age of the entries to be deleted and click Delete Entries.

Deleting SQL Workshop Logs

Clicking Review SQL Workshop logs links you to SQL Workshop logs. These logs maintain a history of recent commands and scripts run in the SQL Command Processor.

To delete or truncate log files entries:

1. Select one of the following:

   • Script File executions log entries

   • Control File execution log entries

   • SQL Command Processor history log entries

   • SQL Archives entries

2. To delete entries by age:

   • Specify the age of the entries to deleted

   • Click Delete Entries

3. To delete all entries, click Truncate Log.

See Also: "Accessing the SQL Command History"

Deleting User Activity Log Entries

Clicking Review page view activity log, with option to truncate links you to the Manage Activity Logs page. Activity logs track user activity for an application. Developers enable logging within their application on the Edit Application Attributes page.

See Also: "About Application Definition" for more information on enabling logging on an application

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:

1. Click Truncate Logs.

2. 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.

Topics in this section include:

• Purging Sessions by Age

• Viewing Session Details Before Purging

• Viewing Session Statistics Before Purging

See Also: "Understanding Session State Management"

Purging Sessions by Age

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

To view specific session details:

1. Log in to Oracle HTML DB Administration Services.

2. Select the Service Administration tab.

3. Select Purge old sessions by age.

4. On the Purge Session page, specify:

   • The maximum number of sessions to be purged

   • The age of session to be purged

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

6. 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:

1. Log in to Oracle HTML DB Administration Services.

2. Select the Service Administration tab.

3. Select Report recent sessions with drill down to session details.

4. 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:

1. Log in to Oracle HTML DB Administration Services.

2. Select the Service Administration tab.

3. Select Report session counts.

4. 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:

1. Log in to Oracle HTML DB Administration Services.

2. Select the Monitoring tab.

   The Monitoring page appears.

3. 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.