[COGNOS TM1 10.2.2 Training]
Cognos TM1 Its an enterprise planning software platform that can transform your entire planning life cycle
From target setting and Budget to reportingScorecardingAnalysis and forecasting
TM1 Deploys: A distributed and client server architectureThat consists of IBM Cognos TM1 ServerTo which a different combination of clients can connect
Cognos TM1 Provides TM1 Architect TM1 PerspectivesTM1 Web ClientTM1 Application PortalPerformance ModelerCognos Insight11/5/20153
TM1 Client Server Architecture
TM1 Web Architecture11/5/20155
Setting up TM1 ServerThere are 3 ways to run TM1 Serveri) As a serviceii) As a desktop applicationiii) As a local server11/5/201511
12Server componentsYou can install the following server components on separate dedicated computers:Cognos TM1 Admin Server and Cognos TM1 ServerCognos TM1 WebCognos TM1 Application Server
Client componentsYou can install the following client components on multiple computers:Cognos TM1 PerspectivesCognos TM1 ArchitectCognos TM1 Performance ModelerCognos InsightTM1 10.2.2 Deployment11/5/2015
Cognos TM1 - Worksheets11/5/2015
23When the TM1 server is started, all TM1 data is loaded from the TM1 data directory into RAM on the server machine.While the TM1 server is running, all cube data resides in RAM. All edits received from TM1 clients are stored in a transaction log file named Tm1s.log.TM1 clients retrieve cube values from the server. Clients also send edits to cube values to the TM1 server.When the TM1 server is shut down, or when an explicit Save Data command is issued, any changes to cube values are written from the transactional log file to the data directory.On startup, the remote server loads dimensions and cubes from the data directory into the server machine RAM. At the same time, the server opens a new transactional log file called Tm1s.log in the data directory. After the cubes are loaded, the remote server is available.The remoteTM1server registers itself with one or more Admin Servers so that clients can connect to the remoteTM1server.Client applications contact Admin Servers to locate availableTM1servers. The clients log into theTM1servers whose data they want to access.Clients edit the cube data, sending the values back to theTM1server.As new values are received from clients, theTM1server writes the records to the Tm1s.log file, keeping track of every data change, including the date and time the edit occurred, and the ID of the client who made the edit.As the server calculates new values in response to client requests, the server stores them in memory, increasing the amount of memory used by the server.When the server shuts down, all records in the Tm1s.log file are saved to disk, and the transaction log file is renamed by appending a date/time stamp to it. The Tm1s.log file is saved in the server's data directory to back out data transactionsIf the server is intentionally shut down without saving the changes, the log file is saved with a time/date stamp and the extension is changed to .rej. You can process the Tm1syyyymmddhhmmss.rej file through TurboIntegrator to recover the transactions.
To save all changes to the data on aTM1server at any time without shutting down the server, right-click a server in Server Explorer and ClickSave Data. All records in the Tm1s.log file are immediately written to disk, the transaction log file is renamed by appending a date/time stamp to it, and a new Tm1s.log file is created to accept any subsequent edits to cube values. Any changes to the metadata, such as dimension definitions and cube definitions, are immediately saved to disk. The changes to the metadata are not written to the transaction log file.
COGNOS TM1 Files Overview11/5/2015