In iServer Release 9, the Encyclopedia volume can cache data using a single cache connection to a database. In iServer Release 10 and later, you can set up multiple cache connections to multiple databases.

In iServer Release 9, you run SQL scripts to create an information cache definition (ICD) file. In iServer Release 10 and later, an information architect creates an information cache definition file using Actuate Information Object Designer. For each ICD, the information architect specifies the name of its cache data table, the names of the columns of that table, and any table indexes.

From Configuration Console, you configure properties on Server Configuration Templates—Settings—NetOSI File Types—ICD to communicate between the information object and Actuate Caching service (ACS) using SOAP. From Management Console, you activate the cache when scheduling a job. iHub executes the ICD schedule and populates the cache table. When you run a query against the information object, iHub retrieves data from the cache table.

You need to provide the information architect with the location and connection properties to use for caching, so the information architect can publish either information objects or designs that contain them to iHub. The information objects become available in the Encyclopedia volume, and designs can use them as data sources.