TM1 Control Cubes

While TM1 is a great tool, it is not the easiest to migrate from development to test or production environment. This process usually involves a tedious manual work in which the developer is required to identify every file that make up a complete dimension or cube to be migrated and to moved only these files. Typically, for dimensions, you should move your “.dim” files and the Element control cubes (which we will look at below) while for cubes, you should move all the “.dim”, Element control cubes, along with your “.cub” and “.rux” files. In this post, we’ll examine some of the Control Cubes – those cubes that start with a curly bracket (“}”).

Client and Group Management TM1 Control Cubes

These control cubes are used to manage clients and group connection to a particular TM1 server.

Control CubeFunctionsFiles
}ClientGroupsUsed to store assigned clients into groups}ClientGroups.cub
}Clients.dim
}Groups.dim
}ClientPropertiesUsed to store specific client information such as password, password expiration days no, max port connections, etc}ClientProperties.cub
}Clients.dim
}ClientProperties.dim

Security TM1 Control Cubes

These control cubes as used to manage TM1 security.

Note: You may or may not have the .rux files in your model depending on the approach your developers have taken to applying cell security.

Control CubeFunctionsFiles
}CellSecurityUsed to store cell level security accessAll dimensions in the cube (.dim files)
}CellSecurity_.cub
}CellSecurity_.RUX
}Groups.dim
}ElementSecurityUsed to store element level security accessDimension (.dim file)
}ElementSecurity_Cost Centre.cub
}ElementSecurity_Cost Centre.RUX
}Groups.dim
}DimensionSecurityUsed to store dimension level security access. Note that the }Dimensions.dim will include all list of the dimensions that currently exist in the TM1 server}DimensionSecurity.cub
}Dimensions.dim
}DimensionSecurity.RUX (if applicable)
}Groups.dim
}CubeSecurityUsed to store cube level security access. Note that the }Cubes.dim will include all list of the cubes that currently exist in the TM1 server}CubeSecurity.cub
}Cubes.dim
}CubeSecurity.RUX (if applicable)
}Groups.dim
}ProcessSecurityUsed to store processes security. Note that the }Processes.dim will include all list of the processes that currently exist in the TM1 server}ProcessSecurity.cub
}Processes.dim
}Groups.dim
}ChoreSecurityUsed to store processes security. Note that the }Chores.dim will include all list of the chores that currently exist in the TM1 server}ChoreSecurity.cub
}Chores.dim
}Groups.dim

For more information on migration from Dev to Test to Prod, please see this post.

If you like this post, please spread the love…

This site uses Akismet to reduce spam. Learn how your comment data is processed.

/* THIS WAS THE CODE USED FOR EMBEDDING A SURVEYMONKEY POPUP */