Restoring TM1 server files from Production to UAT environment breaks applications

[wigglyrat]

Hi:

I am encountering an issue when restoring files from our TM1 live server to our UAT server. Our practice for this is to copy out all files from the Live/Production server to UAT and then replace the .CFG file with one from a previous UAT backup. This seems to disturb TM1 applications - when this is accessed via the web we often see error messages stating that server password is invalid (although is is not).

When restoring data from one TM1 server to another are there additional files that should remain the same outside of the .CFG file?

Many thanks in advance.

[jim wood]

It's probably something to do with your log files. Really you should have your CFG in a directory, then your data in one sub folder and your log files in another. If you then make sure you complete a save before copying over the data folder you'll be good to go.

[Oratia623]

Assuming that your production and UAT instance have different names, you could get a number of problems:
1) Each application file would be hard-coded to a specific server name. Opening this file on a TM1web associated to a different TM1 instance name would not work.The servername within the file would need to be changed.
Our Solution: The server reference in each of our application files are in a single Excel named range.
When we flush back from prod to other environments we run a simple VBA macro that opens up each file in the Data\}Externals directory and replaces the contents of this named range to the new server name before saving the file.

2) If you have set home pages for each user, this is stored against the 'Web Home Page Object' element in the '}ClientSettings' cube. This entry contains the servername.
eg

TM1://,servername./blob/PUBLIC/.\}Externals\<ReportName>.xlsx_<datestamp>.xlsx

This needs to be updated when flushing to a server with a different name.
Our Solution: We have created a TI that cycles through the '}ClientSettings' cube and updates the string in these entries to the new servername.

Not sure if these are the cause of your issues, but it may be of assistance.