Siebel Analytics Scheduler Guide > Using Siebel Analytics Scheduler > Setting Up Analytics Scheduler Jobs >

Modifying iBots


You can modify individual iBots using the Modify Job dialog box in the Job Manager, accessible from Siebel Analytics Administration Tool.

To modify an iBot

Table 15. iBot Properties
iBot Property
Description
Web Server
Specifies the Web server this iBot contacts when it runs.

Do not change this setting, because the iBot may not exist on a different Web Server. This feature was added for debugging purposes only.
Debug Log
Determines whether debugging information is written to a log.
Max Concurrent Subscribers
Specifies how many concurrent actions or unique requests are executed in parallel.

NOTE: This number represents the number of dedicated threads from the thread pool that this iBot uses. If you have many subscribers, and the iBot is personalized for each recipient, it may be beneficial to increase the number of threads for this iBot, because it can handle more subscribers concurrently. However, you should exercise caution, because if a subscriber receives multiple deliveries, threads can become blocked.

For example, if you have two subscribers, each with a delivery to an email device and to the Intelligence Dashboard, then two threads can execute concurrently while the other two wait for the results of the first two. If you have allocated five threads to this iBot, all deliveries try to execute, but two occupy threads that could be used by other iBots. The other iBots are not able to execute if one long-running iBot uses all of the threads.

If many iBots are scheduled to execute at the same time, the cumulative number of threads you dedicate (that is, the sum of all iBots' threads) should not be greater than the current thread pool. Otherwise, performance could be impeded.

 Siebel Analytics Scheduler Guide
 Published: 11 March 2004