Storing Temporary Output Objects Outside the Content Store

The reportService, batchReportService, and powerPlayService services can now store temporary output objects, such as interactive report data, in the server file system. Previously, temporary output objects were always stored in the content store. This feature improves overall system throughput and performance by reducing the number of content store queries. Applications that frequently run reports interactively will likely benefit most from this change.

Administrators can change the default location using the new bibus » configuration » temporaryObjectLocation property, or using IBM® Cognos® Administration. IBM Cognos dispatcher deletes the temporary objects after the duration specified in the bibus » configuration » temporaryObjectLifetime property. It is important to specify a duration that ensures interactive report data remain accessible, yet not excessively long such that disk space becomes an issue. The default duration is four hours.

As objects stored in the file system are not available using the SDK, applications should continue to store temporary output objects in the content store by not specifying the bibus » runOptionEnum » outputLocation value option for reportService objects or the bibus » powerPlay8OptionEnum » outputLocation value option for powerPlayService objects. This uses the default storage location (content store), thereby allowing SDK applications to retrieve temporary outputs, as in previous releases.

For information on configuration and encryption options, refer to the IBM Cognos Analytics Installation and Configuration Guide.

This change affects: