Bookshelf Home | Contents | Index | Search | PDF

Siebel Analytics Server Administration Guide > Query Caching > Cache Event Processing with an Event Polling Table >

Making the Event Polling Table Active

---

Once the table is created on the physical database, you can make it active in the Siebel Analytics Server.

To make the polling table active

Import the table to the Physical layer.
Include it in the group of Siebel Analytics Server event polling tables using the Tools > Utilities > Siebel Event Tables menu item, and set a polling interval.

To import the polling table into the Physical layer, perform the following steps from an open repository.

To import the table into the Physical layer

Select File > Import...
Select the data source containing the event table to import, and then click OK.

The Import dialog box appears.

Check the Tables option to import the table metadata.
Navigate to the event polling table, select the table and either click the Import button or drag and drop it into the Physical layer.

This imports the event table to the Physical layer. If you have multiple event polling tables, repeat this procedure for each event table.

NOTE:  Be sure the data source specified for the event table has read and write access to the event table. The repository will both read the table and delete rows from it, so it needs write permission. Event tables do not need to be exposed in the Business Model and Mapping layer.

Once one or more polling tables are present in the Physical layer, you need to include them in the group of event polling tables.

To mark the table object as an Event Polling Table

Click on the Tools > Utilities menu item.
Select the option Siebel Event Tables from the list of options.
Click Execute.
Select the table to register as an Event Table and click the >> button.
Specify the polling frequency in minutes, and click OK.

The default value is 60 minutes. Click OK.

NOTE:  You should not set the polling frequency to less than 10 minutes. If you want a very short polling interval, consider marking some or all of the tables noncachable.

When a table has been registered as a Siebel Analytics Server event table, the table properties change. Registration as an event table removes the option to make the table cachable, as there is no reason to cache results from an event polling table.

Bookshelf Home | Contents | Index | Search | PDF