Introduction | Information Center

Using the IBM Alphablox Cube Manager page


The IBM Alphablox Cube Manager page specifies the maximum number of cubes that can be loaded and the location of the member cache directory. The initial number is established during installation.

Maximum Cubes

The Maximum Cubes value can be used to restrict the number of IBM Alphablox cubes that can be running simultaneously. By default, the Maximum Cubes setting is disabled and the number of IBM Alphablox cubes that can be loaded and running simultaneously is limited by the memory available on the server. When selected, the Maximum Cubes setting limits the maximum number of cubes to the value specified. The default value is 20.

Member Cache Directory Path

The Member Cache Directory Path value specifies the directory path for the disk storage of dimension data for each IBM Alphablox cube. By default, the directory path is alphablox_dir\analytics\repository\temp (for example, c:\alphablox\analytics\repository\temp). You can specify a different directory path location, based on performance or backup requirements.

For each dimension in a cube, two files are created in the member cache directory, one containing dimension data (named [cubeName].[dimensionName] and an associated index file (named [cubeName].[dimensionName].idx). The dimension file contains information about member names, member properties, member keys, and other member data. For each cube, there is also a cube index file (named [cubeName].idx).

When a cube is started or refreshed, the cube's member cache files are generated and any previous files are overwritten. As long as the cube is running, dimension members are dynamically read into memory from the dimension files on an as-needed basis. If the member cache grows larger than user-specified parameters, the space is managed according to the IBM Alphablox Cube Server's caching policies.

Related Topics: