Cognos Controller 10.3.1
Microsoft Windows 2012 R2 (Windows NT 6.2)
What are the recommended settings for IIS Application Pools?
For cognos controller and ICAPool that are used with Cognos Controller, recommended timeout is 600 minutes.
Login to the Cognos Controller Server.
Open Internet Information Services (IIS) Manager
Click on Applications Pools
Click on NET v4.5 or the one created for Controller.
Change Idle Time-Out (minutes) to 600.
Do the same for the other Applications Pool used by Cognos.
Cognos Controller Applications Pool should use the local system account.
Set the Cognos BI timeout value to same, open Cognos Configuration, and go to Security – Authentication, and change to 36000 seconds.
Save and restart your Cognos services in correct order. Cognos Content Manager service first.
Then you should change recycling of Application Pool for Cognos Controller to be at a defined time, and not after 29 hours.
Change this to it to be recycled at 1 AM at night, like below.
Also ensure that the logging of the recycling is active, this is not default in Windows 2012, see below to have it active.
Planning Analytics 2.0.5
Microsoft Windows server 2016
When open the tm1server.log file, the time is 2 hour off the local time or so. This is because default all tm1 logging is done in GMT time.
Create a tm1s-log.properties file with below content and place it in same folder as your tm1s.cfg file.
# Enable INFO level logging through the shared memory appender, by default. The server # will write informational messages, as well as errors and warnings to the log file.
# S1 is set to be a SharedMemoryAppender
# Specify the size of the shared memory segment
# Specify the max filesize
# Specify the max backup index
# Specify GMT or Local timezone
# adds info about process locks to the tm1 server log file
Planning Analytics 2.0.5
Microsoft Windows 2016 Server
How move NTFS and File Share security to a new server? We have shared a MANUALINPUT folder on the TM1 server, where selected users can update text files with data. This csv file are read into the TM1 application with use of a TI process. Now we setup a bigger Windows server and want to move over the windows security setup.
Test this steps in a test server first, to ensure they work in your environment.
You have created the folder d:\tm1app\manualinput
Login on your old TM1 server and open a command prompt as administrator.
Enter this command to save the security:
icacls d:\tm1app\manualinput /save ntfspermissions.txt /c
Copy the txt file over to the new PAL server
Enter this to restore the security:
icacls d:\tm1app /restore ntfspermissions.txt /c
/t parameter to icacls will include all subfolders in the security file.
The user that have access to the file share is stored in the registry, so on your old TM1 server you need to open REGEDIT.
Expand Regedit to the following location:
Right-click the Shares registry key and select Export. Enter a file name like sharepermissions.reg.
Copy the reg file to the new PAL server.
Open the reg file in notepad, to ensure you only got the SHARES you want to be there.
If there are extra shares you do not want on the new server, erase this lines and save the file.
Open Regedit and go to HKLM\SYSTEM\CurrentControlSet\Services\LanmanServer\Shares
Right-click the Shares registry key and select Export. Enter a file name like backuppermissions.reg. This to have a backup of the settings in registry before you apply the new values.
Double click on the reg file from the other server, to import the values.
After the file is imported, you have to reboot the windows server to make the change take affect.
Note that the servers need to be in the same domain, for this to work, so the users are the same in both servers.