Publishing Powercubes - IBM Cognos User Manual

cube is not a multilingual cube; it is a unilingual cube in the UTF-8 code page.
IBM Cognos Series 7 products are unable to read PowerCubes that use the UTF-8
code page. To build PowerCubes in a code page that is different than the current
code page, you can change the Cube code page setting on the Model properties
sheet. For example, you can build a windows-1252 code page PowerCube on Linux
so that IBM Cognos Series 7 products can use the cube.
Cognos Transformer supports Unicode data sources, including Framework
Manager packages, IBM Cognos reports, and exported .csv files from IBM Cognos
reports. Cognos Transformer converts the Unicode data to the code page of the
current locale for processing and display, and will also convert the data to a cube
code page if one is specified. You must use compatible code pages, otherwise
character loss may occur. For example, you should not process Japanese text data
when Cognos Transformer is running in an English locale.

Publishing PowerCubes

PowerCubes must be published to IBM Cognos Connection before they can be
used as data sources by IBM Cognos components to create reports and analysis.
When your IBM Cognos environment is properly configured, you can publish any
PowerCube from Cognos Transformer directly to IBM Cognos Connection. You
must specify the Windows , UNIX or Linux location from where the IBM Cognos
server accesses each PowerCube and, if user authentication is enabled, the
configured namespace to use.
Some of the other settings that you may need to specify while publishing a
PowerCube include:
v
v
162
IBM Cognos Transformer Version 10.1.1: User Guide
Null suppression options
You can set suppression options for the package published with the PowerCube.
These options determine whether IBM Cognos studio users can choose to hide
empty rows only, empty columns only, or both empty rows and columns.
Options also determine the types of empty values that can be suppressed, such
as zero or missing values. Types of empty values that users can choose to
suppress depend on the studio.
Read cache size
The default read cache size for published PowerCubes is 80 MB. You can set this
parameter to a value between 1 MB and 1 GB, as required for optimal query
performance.
The optimal read cache size may be higher or lower than the default value of 80
MB. This is to be expected, as PowerCubes in production vary widely in type
and query characteristics.
Note that the read cache size has no effect on the initial time required to open a
cube.
The typical profile for query performance, or processing time, follows a pattern
whereby performance increases with the read cache size and then levels off
beyond the optimal setting. To determine the optimal setting, we recommend
that you lower the default by 10 MB (or 5 MB, or 1 MB, depending on the level
of fine tuning desired) and use the resulting query performance results as a
guide for establishing whether further reductions, or increases, are required.
The optimal read cache size will change as the cube grows and changes in the
production environment. As a result, you should review the optimal read cache
size when changes to the user's query performance pattern, or changes in the
PowerCube characteristics, occur.