1. Install and configure IBM Cognos 8.4 on your system.


2. Install IBM Cognos TM1.


3. Install C8_TM1_Portlets_win32_8.4.28.4 to your Cognos 8.4 Directory

1. Turn anonymous access "off"



2. Add the TM1 server name to the valid domain list (CAF)


3. Enable the share of session information for IBM Cognos 8



4. remember your internal dispatcher URI and gateway URI

1. Locate your TM1 Instance which you want to get work with IBM CAM Security (for example (\TM1\Custom\TM1Data\PlanSamp)


2. Locate and open the file tm1s.cfg

Add the following lines (comment existing entries out):
ServerCAMURI=your internal dispatcher URI
dispatchClientCAMURI=your IBM Cognos 8 Gateway URI
ClientPingCAMPassport=900
CAMPortalVariableFile = portal\variables_TM1.xml

3. Change the IntegratedSecurityMode to 4

(IBM documentation says you should change it to 2 but thats wrong!)


4. Locate and open the variables_TM1.xml file

(can be usually found within your_cognos_8_installation_directory\templates\ps\portal)

Add the following lines (comment existing - similar - entries out)

<urls>
<url>http://your_tm1_server/TM1Web/TM1WebLoginHandler.aspx</url>
<url>http://your_tm1_server/TM1Web/TM1WebMain.aspx</url>
</urls>


5. Restart your TM1 Server and test the login.

You shoud be able to login by Web and with Architect.
Attention: You may need to assign appropiate rights to administer the server.
You can do this by changing the parameter IntegratedSecurityMode back to its default (1) and assigning appropiate rights in Architect. (Syntax for the username is namespace_name\username)

64 Bit Version
same Hardware
Windows 2008 Server Standard Edition (64 Bit)
SQL Server 2005 Developer Edition with SP3 (64 Bit)
Cognos 8.4 (64 Bit)

The test:

• 3 new Report Studio reports based on MSAS 2005 and the Cognos sample package GOSalesFact_EN_MSAS2005
• 2 new Report Studio reports based on SQL Server 2005 and the Cognos sample package GO Data Warehouse (query)

were run in at least a minimum of 70 to 100 iterations. The fastest report ran in 37 seconds, the most time consuming report completed after 9 minutes for one execution.

All values are based on averages given from the No. of iterations.

To get an reproducable test case by avoiding any caching or other side effects I decided to use the rstest utiltiy which inherits the main logic of report processing. This tool is often used internally by IBM Cognos Information Management people and has some interesting features. You can find this tool in the Cognos 8.4 bin directory.

The results of rstest may not be comparable to an execution within Cognos Connection, since the bibustkservermain process caches a lot of data. In other words the test results should reflect a "first time execution in Cognos Connection" and therefore the maximum processing time a report may need. As already pointed out, the rstest and bibustkserver processes are both 32 bit programs.



Looking at the result table above, you may raise the question why the elapsed time for the 64 bit tests were always lower then the 32 bit values?
Answer: The database server and olap server (both 64 bit) were able to return the results faster back to the IBM Cognos report engine, this caused a faster execution.

The last column which is calculated from the rstest cpu time vs total elapsed shows clearly that the time the IBM Cognos process needed to finish was even higher than on the 32 bit system.
One reason for that could be the emulation for the 32 bit processes on a 64 bit system. Those emulations cost surely some time.

Alternativ kann man natürlich auch gleich ein Batch schreiben, welches einem die Adminitrative Tätigkeit des Bereinigens der wichtigesten Temp Verzeichnisse erledigt.

Wichtige Temp Verzeichnisse sind z.b. \data\cqe\RTModels und \temp (das \temp Verzeichnis kann auch in IBM® Cognos® Configuration auf einen anderen Ort definiert werden). Diese sollten aber nur bereinigt (die Verzeichnisse selbst dürfen nicht gelöscht werden!) werden, wenn der Dienst heruntergefahren wurde.