Debugging and Identifying Cube Dependencies

Using TurboIntegrator to preset dependencies may be necessary.

To identify existing cube dependencies requires an in-depth understanding of an application so that you can analyze all of the rules for each cube including control cubes. Even when you have that level of knowledge about an application, it is important to turn on the following logging capability to identify cube dependencies as they are established.

For example, when the following command is added to the the tm1s-log.properties file:

log4j.logger.TM1.Cube.Dependency=DEBUG

the following information is returned that identifies dependencies:

INFO   2010-06-09 18:09:23.728   TM1.Cube.Dependency
  Adding cube dependency: cube 
"}ElementSecurity_}Cubes" depends on cube "}CubeSecurity"

The TurboIntegrator command for this would be:

AddCubeDependency('}CubeSecurity','}ElementSecurity_}Cubes');