TM1 Server Setup
Creating a new TM1 Server
To create a new server you must first create a data directory, this directory must have at very least:
The configuration file (tm1s.cfg) should specify:
- Server Name
- Server Admin-host
- Data Directory
- Logging Directory
- Server Port
- Any Additional Configurations (Max Login Attempt)
The typical directory structure of an Application Server is as follows:
- Server Name (No Spaces)
- Data (tm1s.cfg,tm1s.lic and other files)
- Logging/Logfiles (tm1s.log, tm1server.log)
- DataSources (Shared Directory)
- DataOutputs (Shared Directory)
Loading a Server as an Application
To load a server as an application we run the application ‘tm1s.exe’ found in the IBM Cognos TM1 bin Directory. We also provide this executable with a command line reference to the data directory.
The easiest way to do this is by creating a shortcut to ‘tm1s.exe’ and changing the launch field to have an additional ‘ –Z “DataDirectoryHere”.
Exercise – Start a server as an Application
Loading a Server as a Service
To load a server as a service we must first install it as one.
This is done through the same application that is installed as a service.
To create a new service, in a command prompt write:
“C:*pathtoTM1bin* tm1sd.exe –install *servername* “*datadir*”
Replacing items enclosed within a ‘*’ with the corresponding text.
The service can then be set to run as a specific user and the start method can be changed in the Computer Management Services Section
Exercise – Install a Server as a Service
Loading a backup
Starting up a Backup is relatively simple. As the server will most likely be temporarily up its best to start the server as an application instead of a service.
- Does the server have enough RAM to support another server in memory?
- What level of impact will this have (by using one or more CPU cores to load) on the rest of the system?
- Do not run the Server on the same port as the existing one (see configurations).
- Do not use the same name for the server if registering it on the same admin host as Production.
- Would it be beneficial to run the backup on the same admin host as Production? (Exposing the point in time backup to end-users)
Exercise – Load a Backup as an Application
TM1 Servers are stored in files on the server when the server Saves or Shuts down. When saving the server is translating the Application server objects from Memory onto the Computers Hard drives.
The following table highlights the object type and it’s saved file equivalent:
Query to a Data Store
Set of Measures for storing data against
Custom Selection of Measures
Style & Formats of a View
Logs of all activity in TM1
Logs of all TI Process Errors
When saving TM1 produces files one by one each time appending a ‘$’ to the filename until the output of that file is complete, at which point the server deletes the original and renames the file (removing the appended ‘$’).
Moving Cubes/Dimensions Around
Since cubes are saved to the hard disk as ‘.cub’ files its easier to move these between servers as opposed to exporting and re-importing data. Unfortunately in order for TM1 to recognize new Cubes the TM1 server needs to be restarted.
Note: When moving a cube between servers make sure the new server has all the dimensions used by the cube.
Shutting Down the server
Service Shutdown vs. TM1 Shut Down
How to do a Native TM1 Shutdown
- Within Server Explorer right click on the server
- Server Manager
- Chose the ‘Shutdown Server’ Option
- Press Ok to initiate
- When prompted to save the server first select yes