|
Siebel Analytics User Guide > Using Siebel Delivers >
Selecting Destinations for a Siebel Delivers iBot
Use the Destinations tab to specify a range of desired devices and destinations for iBots. This section contains the following topics:
For an overview of Siebel Delivers, see Overview of Siebel Delivers. To specify devices and destinations for the iBot
- Click on a check box next to a device or destination to select it for the iBot.
About User Destinations for the Siebel Delivers iBot
This section describes the user destinations available for the iBot.
- Intelligence Dashboard
Active iBots will appear in a Dashboard Alerts section as well as on the Alerts! page. A link to this summary appears together with the application navigation links when new iBots are delivered. After these are reviewed, the alert link is removed.
- Active Delivery Profile
iBots will be sent to specified devices in the active delivery profile. The active delivery profile is configured through the My Account page. For more information, see Configuring Your Siebel Delivers Devices and Delivery Profiles.
About Specific Devices for the Siebel Delivers iBot
If you select a specific device, your selection overrides the active delivery profile for a user. Devices specified here act as additions to the active delivery profile. An administrative iBot, for example, need not be dependent upon user configuration. It would, however, receive users' device information from their devices configured in My Devices. For more information about active delivery profiles and My Devices, see Configuring Your Siebel Delivers Devices and Delivery Profiles. These are the available devices:
- Email
- Pager
- Digital Phone
- Handheld Device
About System Services for the Siebel Delivers iBot
This section describes the system services available for the iBot.
- Siebel Analytics Server Cache
This is used for seeding cache.
Siebel Analytics administrators can create Analytics Server cache for individual users. The cache seeding operation allows administrators to run requests on dashboard pages or requests stored in the Web Catalog, and create an Analytics Server cache. This speeds up response time for users when they actually run the requests on the dashboards. If data already exists in the cache for a given request, the data is deleted and refreshed when the iBot runs.
The cache for the request or the dashboard page is created at the appropriate schedule for the indicated set of users.
NOTE: To have the cache created for each user, choose the Personalized option for data visibility at the General tab.
You would typically not select any other destination for this kind of request.
- Disconnected Application Cache
This setting is for organizations that have licensed Disconnected Siebel Analytics. It is related to the preprocessed synchronization mode in disconnected Analytics applications.
You can create server datasets for your mobile users, so that when they synchronize their applications, the data downloads are faster.
The preprocessed synchronization mode is the recommended data download mode for users. It avoids the potential overhead that can occur from running data creation requests in online mode during normal business hours and reduces wait time for the download. Preprocessed data is stored under each user's directory on the machine running Siebel Analytics Web. If you decide to use this mode to schedule data cache creation, make sure that adequate disk space is available. For more information about Siebel Disconnected Analytics, see Siebel Analytics Server Administration Guide.
NOTE: To have the disconnected application cache created for each user, choose the Personalized option for Data Visibility at the General tab. (Nonpersonalized data is not used for disconnected Analytics users.)
You would typically not select any other destination for this kind of request.
|
