}CubeProperties

[rsulsona]

As a production shop using TM1, how do we automate the process of getting this cube to update.
We have "copied" a new cube from our DEV environment to our UAT environment. However, the contents
of this cube is not part of that copy for rather obvious reasons.

How do othe shops handle this when the IT staff is not suppose to "update" at UAT or Production?

Do you have a special person in your user community that is responsible for this function?
The same issues exist with the }HierarchyProperties cube.

Thanks

Robin Sulsona

[cycleman83]

Once you copy the .cub file, you need to bounce the instance.

After bouncing the instance the }CubeProperties cube and more specifically, the }Cubes dimension will be updated and now contain the new cube.

[rsulsona]

We bounce all of our instances every night. However, in our DEV instance I had set the properties to know that
Measure was the Measures dimension.

This did not get populated in our UAT environment and I had to go into the cube and set the properties manually.
Is there some automated process that would have done this. What do we do now.....

[Alan Kirk]

We bounce all of our instances every night. However, in our DEV instance I had set the properties to know that
Measure was the Measures dimension.

This did not get populated in our UAT environment and I had to go into the cube and set the properties manually.
Is there some automated process that would have done this. What do we do now.....

The Measures dimension is meaningless to TM1; it only exists for compatibility with other applications that may be querying it, which is why it has to be set manually. The other option that you have is to create a housekeeping chore which runs some time after your server reboot and updates cube and dimension properties.