Agent editor: Destinations tab

Use this tab of the "Agent editor" to specify where content is to be delivered.

For more information, see:

• "What Are Agents?"

• "How Agents Work"

• "What Are Alerts?"

• "Creating Agents"

Components

Home Page and Dashboard

Use this box to specify whether content is to be delivered to the Home page and dashboard pages. (For how content is delivered as an alert to the Home page and dashboard, see "What Are Alerts?".)

Devices

Use this option to specify whether content is to be delivered to specified devices. If you select this option, then you must select one of the following options:

• Active Delivery Profile — Use this option to specify that content is to be delivered to the devices specified in the active delivery profile.

  The active delivery profile is configured through the "My Account dialog: Delivery Options tab".

• Specific Devices — Use this option to specify that content is to be delivered to specific devices and then select one or more of the following device options:

  • Email

  • Pager

  • Digital Phone

  • Handheld Device

  If you select a specific device here, then the default device selected in the My Account dialog: Delivery Options tab overrides the devices that are set in the active delivery profile for a user. Devices that are specified here are used instead of the devices specified in the active delivery profile. An agent, for example, need not be dependent upon a user's configuration. The agent can be configured to use device information from default devices in the Devices area in the My Account dialog: Delivery Options tab.

  For more information about active delivery profiles and devices, see "Configuring Your Devices and Delivery Profiles".

Oracle BI Server Cache (For seeding cache)

This option is available only for administrators who have been granted the Manage Catalog Groups privilege.

Use this option to specify whether to seed the cache.

Administrators can create Server cache for individual users. The cache seeding operation enables administrators to run analyses on dashboard pages or analyses that are stored in the catalog, and to create a Server cache. This speeds up response time for users when they actually run the analyses on the dashboards. If data exists in the cache for a given analysis, then the data is deleted and refreshed when the agent runs.

The cache for the analysis or the dashboard page is created at the appropriate schedule for the indicated set of users.

Generally, if you are using the analysis that you have specified as the content for this agent to seed the cache, then you do not select any other user destinations (such as Email).