Product:
Cognos TM1 10.2.2 (works also in PA 2.0 Local)
Microsoft Windows 2012 R2 server

Problem:
Setup logging of TI processes execution to a Tm1 cube.

Solution:
Create two dimensions and build a cube of them.
Then add an EPILOG script to all TI process that should log information in that cube.

Go into your application – in our text we use planning sample.
In Tm1 Architect select Dimensions – Create New Dimension
Select Insert Element from Edit menu
Enter the following as Element Name
Time
User
Comment
Click OK
Select save from dimension menu and name the dimension to be Sys.Event

In Tm1 Architect select Dimensions – Create New Dimension
Select Insert Element from Edit menu
Enter the following as Element Name
Temp
Click OK
Select save from dimension menu and name the dimension to be Sys.Log

Right click on cubes and select Create new cube
Mark the two dimensions and click on the arrow icon to move them over to the cube.
Enter Cube name to Sys.Log
Click on Create Cube button.

Now you have a cube to view the logging in.

Then you need to paste below code in EPILOG in all TM1 TI process that you need logging in.
It is important you update the sStatusText line in each TI process to explain what has happen.

#—————————————————————————–
# Logging
#
# set sStatusText to information on what file create or values updated
# if the TI process is run by a Chore then the TM1 user is R*+chore name
# otherwise set the sUserText to the user running the chore
# dimensionelementinsertdirect will add the TI process to the dim if it does not exist
# timSt(now, ‘\Y-\m-\d \h:\i’) will create the time in format 2017-05-16 12:43
#—————————————————————————–

sStatusText = ‘ This the comment written to log ‘;
sCubeName = ‘Sys.Log’;

if(SUBST(TM1User(),1,2) @= ‘R*’);
sUserText = ‘Scheduled’;
else;
sUserText = attrs(‘}clients’, TM1User(), ‘}TM1_DefaultDisplayValue’);
If (sUserText @= ”);
sUserText = TM1User();
endif;
endif;

dimensionelementinsertdirect( sCubeName , ”, getProcessName(),’S’);
cellputs(timSt(now, ‘\Y-\m-\d \h:\i’), sCubeName ,’Time’, getProcessName());
cellputs(sUserText , sCubeName ,’User’, getProcessName());
cellputs(sStatusText, sCubeName ,’Comment’, getProcessName());

To test the TI process, you can enter following code in PROLOG tab.
#—————————————————–
# DEBUG LINE ONLY
#——————————————————
V1 = TM1User();
ASCIIOutput(‘c:\temp\tm1logging.txt’, V1, ‘ this is a variable result’ ) ;

Please note that TI process that is run from a scheduled core in TM1 is executed as a special user that have admin rights and is not listed in the Security dialog. If you run same TI process from TM1 Architect – it is processed as the user who logged in to TM1 Architect.

## The below is the smart code that will take the user name and show the Friendly name of it instead of the CAMID(“AD:u:6f2c060820fb2341bbcfd6”)

sUserText = attrs(‘}clients’, TM1User(), ‘}TM1_DefaultDisplayValue’);

## This extra test if it is blank, is for the case there is not a DisplayValue (alias).

If (sUserText @= ”);
sUserText = TM1User();
endif;

Ensure the ‘ character is correct in your code.

More information:
https://www.ibm.com/support/knowledgecenter/en/SS9RXT_9.5.0/com.ibm.swg.im.cognos.tm1_ref.9.5.2.doc/tm1_ref_id13786tifun_asciioutput.html

Product:
Cognos TM1 10.2.2
Microsoft Windows 2008 R2 Server

Symptom:
[ ERROR ] The cryptography information was not generated – error when you try to save changes in Cognos Configuration for TM1.

Cause:
When you first save Cognos Configuration for TM1, after a new installation of TM1, the crypto keys are generated. If you at that time have the values for Content Manager URIs set to localhost, then the keys will be created with use of the Cognos TM1 services.
If you later change this value, IBM Cognos Configuration, Environment – Gateway URI or Content Manager URI, to a Cognos BI server host – then when you try to save the configuration it will contact that server to check the crypto files – because they are not generated from that BI server, the process will fail.

If you have set the values to localhost in Environment – the recommendation is to keep them that way later too. Then there is not a crypto demand with Cognos BI at this point.

If you have set the values to a Cognos BI server the first time, then you need to ensure the Cognos BI server is up, and that you can reach it from the TM1 server when you make the “save” in Cognos configuration.

Test by copy the URL from Gateway URI and paste it into Internet Explorer on your TM1 server – to see if you have network connection to that services.

If Cognos BI is stopped before the save – in TM1 Cognos configuration – then the save should work – because the local certificates should be used. But this is not always the case.

If you are going to use a BI services on the same Windows server as you have Cognos TM1 installed, then you must install the Cognos BI service first. Because if you use localhost and there is a Cognos BI service on the localhost server it (Cognos BI) will be used for the keys.

More information:
http://www-01.ibm.com/support/docview.wss?uid=swg21648832

http://www-01.ibm.com/support/docview.wss?uid=swg21694322

Product:

Cognos Tm1 10.2.2 fix pack 7

http://www-01.ibm.com/support/docview.wss?uid=swg24043388

Cognos BI 10.2.2 fix pack 8

http://www-01.ibm.com/support/docview.wss?uid=swg24043468

Microsoft Windows 2012 R2 server

Microsoft SQL server 2014

Symptom:

Cannot login to TM1 application web when surf to http://tm1test:9510/pmpsvc

Error message

“The planning service parameter was not specified or is not one of the configured locations”

Cause:

The value you use in fpmsvc_config.xml file for <external uri=”http://tm1test:9510″/>

Must exist in file E:\Program Files\ibm\cognos\c10_64\webcontent\planning.html

At

// Update the following to point to the location of the planning service(s)

var planningServices = [“http://tm1test:9510″,”http://tm1serversnames:9510”];

Below from other website;

Solution, the steps to setup cam authentication:

To configure TM1 Web and Performance Modeller / Planning Service to use CAM Authentication and Single Signon.

Configuring TM1 Web

By default the URL for TM1Web is http://mytm1server:9510/tm1web.

This works by default with the default installation, however, if your TM1 Server is configured to use CAM Security (IntegratedSecurityMode 5) rather than Native (IntegratedSecurityMode 1) then you will hit issues trying to access it.

To configure TM1Web to use CAM Secured Servers do the following:

STEP 1 – Create the variables_tm1.xml file

This file links BI to the TM1Web Interface using CAM Authentication. Simply make a copy of the file variables_tm1.xml.sample in the BI Server installation directory …\templates\ps\portal and call it variables_tm1.xml. Edit the file to include your tm1server. The file can contain a NETBIOS and FQDN value to ensure it works in all circumstances.

<?xml version=”1.0″ encoding=”UTF-8″?>

<!–

IBM Confidential

 

OCO Source Materials

 

BI and PM: tm1fragments

 

(C) Copyright IBM Corp. 2008, 2017

 

The source code for this program is not published or otherwise

divested of its trade secrets, irrespective of what has been

deposited with the U.S. Copyright Office.

–>

<!–

This file is referenced by the tm1s.cfg file when using CAM authentication.  The “localhost” string should be replaced with the name of the server running TM1Web. For java tm1web, the tm1web.html is accessed when the standalone tm1web uses cam authentication.

–>

 

<CRNenv>

<urls>

<url is-regex=”true”>http://tm1test/TM1Web(/\([aAsS]\([A-Za-z0-9]+\)\))?/TM1WebLogin.aspx</url>

<url is-regex=”true”>http://tm1test/TM1Web(/\([aAsS]\([A-Za-z0-9]+\)\))?/TM1WebLoginHandler.aspx</url>

<url is-regex=”true”>http://tm1test/TM1Web(/\([aAsS]\([A-Za-z0-9]+\)\))?/TM1WebMain.aspx</url>

<url is-regex=”true”>http://tm1test:9510/TM1Web(/\([aAsS]\([A-Za-z0-9]+\)\))?/UrlApi.jsp(\?.*)?(#.*)?</url>

 

<url>../tm1/web/tm1web.html</url>

</urls>

<cookies>

<param name=”cam_passport”/>

</cookies>

</CRNenv>

 

STEP 2 – Add CAMPortalVariableFile to tm1s.cfg

Next you need to add the reference to the variables_tm1.xml file into your TM1 Server and connect BI authentication if it is is not already in place.

Open your TM1 Servers tm1s.cfg file and add/amend the following lines to it.

IntegratedSecurityMode=5

ServerCAMURI=http://mybiserver:9300/p2pd/servlet/dispatch

ClientCAMURI=http://mybiserver/ibmcognos/cgi-bin/cognosisapi.dll

ClientPingCAMPassport=900

CAMPortalVariableFile=portal\variables_TM1.xml

Remember, if your BI Gateway is using CGI and not ISAPI then use cognos.cgi not cognosisapi.dll.

STEP 3 – Configuring TM1Web Main Page

The next step is to configure TM1Web and to avoid service errors when accessing TM1Web. To do this you edit the tm1web.html file in the BI Install Location\webcontent\tm1\web directory.

Open file E:\Program Files\ibm\cognos\c10_64\webcontent\tm1\web\tm1web.html in notepad.

The following change need to be made:

Change the var tm1webServices variable to use references to your TM1 Server as below.

// Update the following to point to the location of the TM1Web service(s)

var tm1webServices = [“http://tm1test:9510”];

STEP 4 – Modify the TM1Web Configuration to choose Admin Server

To modify the TM1Web front page to automatically select an admin server and TM1 Server modify the file tm1web_config.xml in directory

TM1 install location\webapps\tm1web\WEB-INF\configuration.

Change the following arguments to select defaults:

<!– If set, users will not be asked to enter Admin Host during login. –>

<add key=”AdminHostName” value=”mytm1server” />

and optionally

<!– If set, users will not be asked to select a TM1 Server to connect to during login. –>

<add key=”TM1ServerName” value=”GO_New_Stores” />

When complete, save the file and restart the ‘TM1 Application Server’ windows service for the changes to take effect.

Testing TM1Web

To test TM1Web simply go to http://mytm1server:9510/tm1web and you should be prompted to select from a list of available TM1 Servers. Once you have selected the TM1 Server you will be prompted for appropriate Native or CAM Security before being presented with the TM1 Cube View screen.

TM1 Architect

Before you start TM1 Architect the first time adjust this file E:\Program Files\ibm\cognos\tm1_64\bin64\tm1p.ini to have values for CAM.

[TM1]

DataBaseDirectory = ..\samples\tm1\PData

AdminHost =

ConnectLocalAtStartup = F

LocalServerNetworkProtocol = tcp

IntegratedLogin = F

AdvancedRulesEditor = F

AllowImportCAMClients = T

CognosGatewayURI = http://myBIserver/ibmcognos/cgi-bin/cognosisapi.dll

Language=eng

This file is copied to your windows user’s profile when you start TM1 architect the first time – the file cannot be changed in the user profile when the TM1 Architect program is running.

C:\Users\%username%\AppData\Roaming\Applix\TM1\

Steps to configure TM1 Performance Modeller

In order to configure Performance Modeller to function correctly with CAM secured TM1 Servers we need to perform some configuration work.

The steps required are as follows:

STEP 1 – Add required parameters to support Performance Modeller models.

These parameters and settings need to be added or modified in the TM1 Server tm1s.cfg file and the TM1 Server windows service restarted.

ServerCAMURI=http://mybiserver:9300/p2pd/servlet/dispatch

ClientCAMURI=http://mubiserver/ibmcognos/cgi-bin/cognosisapi.dll

ClientPingCAMPassport=900

CAMPortalVariableFile=portal\variables_TM1.xml

DistributedPlanningOutputDir=tunit

ForceReevaluationOfFeedersForFedCellsOnDataChange=T

AllowSeparateNandCRules=T

Some of the above will already have been added to the configuration file if you have previous configured TM1Web.

STEP 2 – Modify the Service Configuration file

Modify the fpm_svc.config file on the TM1 Server. The file resides in the TM1 installation location webapps\pmpsvc\WEB-INF\configuration directory. Stop the TM1 Application server service BEFORE editing this file.

Only the marked arguments need to be completed / corrected:

<?xml version=”1.0″ encoding=”UTF-8″?><fpm_config xmlns:xsi=”http://www.w3.org/2001/XMLSchema-instance” xsi:noNamespaceSchemaLocation=”fpmsvc_config.xsd”>

<service forceQualifiedPaths=”true”>

<businessViewpoint enabled=”false” uri=”http://localhost:9655/bv/main.jsp”/>

<scorecarding enabled=”true”/>

 

<provisioning allowInstalls=”true” allowUpdates=”true” uri=””/>

<resource path=””/>

<users path=””/>

<external uri=”http://tm1test:9510″/>

<session timeout=”60″/>

</service>

<tm1>

<gateway uri=”http://mybiserver/ibmcognos/cgi-bin/cognosisapi.dll”/>

<alternate_gateway_uris>

<alternate_gateway uri=”*”/>

</alternate_gateway_uris>

<dispatcher uri=”http://mybiserver:9300/p2pd/servlet/dispatch”/>

<admin_host name=”mytm1server”>

<servers>

<server name=”proven_techniques”/>

</servers>

</admin_host>

</tm1>

<!–

The Cognos Insight publish feature enforces a set of minimum system requirements that are required to perform a publish. These are requirements on the system running the TM1 Applications service where the new TM1 servers will be created. To change these system requirement settings add the <insight_publish> element.

maximumCDDDataMB – The maximum amount of TM1 data that can be sent in a publish request

maximumTM1ServersAllowed – The maximum number of servers that can run on this machine. This is the maximum number of servers that are registered with the tm1Admin service.

minimumFreeDiskSpaceMbRequired – The amount of disk space that must be available on the drive where the Tm1 data is published.

minimumFreeDiskSpaceMbRequired – The amount of free memory that must be available on the publish server.

–>

<!–

<insight_publish enabled=”true” maximumCDDDataMB=”100″>

<system_requirements maximumTM1ServersAllowed=”10″ minimumFreeDiskSpaceMbRequired=”5000″ minimumFreeMemoryMbRequired=”500″/>

</insight_publish>

–>

<!– If low on disk space you can set a different drive for the published TM1 server data as an alternative to reducing minimumFreeDiskSpaceMbRequired –>

<!–

<insight_publish enabled=”true” maximumCDDDataMB=”100″>

<tm1Data path=”E:\PublishedServers”/>

<system_requirements maximumTM1ServersAllowed=”10″ minimumFreeDiskSpaceMbRequired=”5000″ minimumFreeMemoryMbRequired=”500″/>

</insight_publish>

–>

 

 

<insight pmpsvcPingTime=”30″/>

<insight_publish enabled=”true”/>

</fpm_config>

 

By default, they will be pointing to localhost, you can also change these in Cognos Configuration IF you have NEVER configured TM1 Application Server to run with a Native secured TM1 Server.  Inside Cognos Configuration at TM1 Applications Server at Component Properties you find the External Server URI to change.

By checking this file and adding your Gateway and Dispatcher URI’s you will guarantee the correct settings are in place.

Changes in Cognos Configuration can overwrite any manual updates to the config file.

 

STEP 3 – Install and modify the BI Interoperability software

You have a single ZIP file called bi_interop.zip that resides in a bi_interop directory of the TM1 installation directory (E:\Program Files\ibm\cognos\tm1_64\bi_interop).

Copy this file and expand it into the BI installation directory. This places files in the following directories within the BI installation:

• Variables_plan.xml in \templates\ps\portal
• Planning.html in webcontent
• Pmhub.html in webcontent
• Icon_active_application.gif in webcontent\icd\feeds\images
• Icon_active_application.gif in webcontent\ps\portal\images

STEP 4 – Modify the BI Interoperability HTML Files

The two html files extracted into the Webcontent directory need to be modified as follows:

Change in E:\Program Files\ibm\cognos\c10_64\webcontent\planning.html

// Update the following to point to the location of the planning service(s)

var planningServices = [“http://mytm1server.domain.com:9510″,”http://tm1test:9510”];

 

Change in E:\Program Files\ibm\cognos\c10_64\webcontent\pmhub.html

// Update the following to point to the location of the pmhub service(s)

var pmhubURLs = [“http://tm1test:9510″,”http://mytm1server.domain.com:9510”];

Testing Performance Modeller

Now the configuration is complete, restart the TM1 application server service to read all the new parameters and test access to the application through the URL http://mytm1server:9510/pmpsvc

If successful your browser will return a blank applications window.

Click the Open Performance Modeller button on the toolbar. This can take some time to open first time, PM will look for TM1 Servers that have the correct security and parameters. If more than one are found you will be prompted to choose and then Performance Modeller opens.

 

Firewall

In some cases, you need to open following ports in the local Windows Firewall on the server to make it Cognos Tm1 work:

80,9300,9510,5495,5498,12345,12346

Plus ports for your TM1 applications instances.

Memory

In Cognos BI Configuration it is recommended to adjust the memory for java to the function of the BI server

Maximum memory for WebSphere Liberty Profile in MB 1024 change to 4096.

Cognos Configuration TM1 Applications server – component properties – Maximum memory in MB 768 change to 4096.

http://www-01.ibm.com/support/docview.wss?uid=swg21669247

https://www.ibm.com/support/knowledgecenter/SSEP7J_10.2.2/com.ibm.swg.ba.cognos.c8pp_inst.10.2.2.doc/c_installs_verify_ram.html

 

The values depend on your server hardware and what the users will do and how many they are.

Timeout

When using IBM® Cognos® TM1® Applications with IBM Cognos Business Intelligence security, set the pmpsvc session timeout to a value higher than the CAM session timeout to ensure the proper timeout detection. If the Cognos TM1 Applications (pmpsvc) session timeout is set to a value lower than the Cognos BI security (CAM) session timeout, then Cognos TM1 Applications will not properly detect a CAM session termination and will not timeout.

The timeout for TM1 default is 60 minutes in Cognos Configuration – TM1 Applications server – components properties at session timeout (min). Set to a good value calculated to fulfill the requirements.

Can also be changed in the file, Navigate to the fpmsvc_config.xml file in the following location: TM1_install_location\webapps\pmpsvc\WEB-INF\configuration.

Update the default value to a desired time, default is, <session timeout=”60″/>.

Inside tm1s.cfg you can adjust the value of ClientPingCAMPassport, default is

ClientPingCAMPassport=900. Change ClientPingCAMPassport to a good value.

On your Cognos BI system, configure the CAM session timeout using IBM Cognos Configuration.

Enter a value in the Inactivity timeout in seconds’ field in the Security/Authentication section of Cognos Configuration. Set to 10800 seconds to get 3 hours or other good value.

Click BI Configuration > Servlet Gateway > IBM Cognos Servlet Gateway.

Notice the Ping timeout in seconds value. Default 240 seconds is 4 minutes.

Verify that the Ping timeout in seconds and Inactivity timeout in seconds settings in BI Configuration are set the same, and that they are lower than the session timeout setting in the fpmsvc_config.xml file and twice as much as the ClientPingCAMPassport value in the tm1s.cfg file.

Adjust the IIS to have the same value in all timeout positions.

I am Not sure if above is correct about timeout values – please test in your dev Cognos environment first.

Cognos BI DUMP files

If you prefer you can disable the creation of these files by amending a configuration file as below:

1. On the server where IBM Cognos BI is installed, open the cclWinSEHConfig.xml file from the c10_location\configuration directory.
2. In the configuration element, change the value of the environment variable setting to 0 (zero) so that it reads <env_var name=”CCL_HWE_ABORT” value=”0″/>

III. Save the file.

1. Repeat the above steps for any other server(s) that could potentially run reports.

 

Text copied from this sites:

https://allthingscognos.wordpress.com/

https://www.ibm.com/support/knowledgecenter/en/SSMR4U_10.2.2/com.ibm.swg.ba.cognos.express_migration.10.2.2.doc/c_express_inst_mig_trouble_tm1_timeout.html

http://www-01.ibm.com/support/docview.wss?uid=swg21637849

Product:
Cognos Tm1 10.2.2
Microsoft Windows 2012 R2 server

Problem:
Can not connect to TM1 server from other computer, but it works fine direct on the TM1 server to connect from TM1 architect.

Possible Solution:
The Windows firewall is blocking the connection.
This looks like TM1 architect is not responding for a long time and then you are not seeing a list of TM1 applications.

You need port 5498 open to get contact with the TM1 admin service from the TM1 architect client.
You need the TM1 applications port (e.g. 12345) to connect to the application from TM1 architect client.

Go to control panel on the TM1 windows server
Click on Windows firewall
Click on Advance settings
Select inbound rules and click on New Rule on the left
Select Port and click next
Enter list of ports at Specific local ports
(e.g. 80,9300,9080,9510,5495,5498,12345,12346)
ensure you use comma between the port numbers.
click Next
Select Allow the connection and click next
Keep all marked for where the rule apply and click next
Set a name (e.g. cognos) and click finish

Now test again from you remote computer where TM1 architect are installed.

Cognos Controller 10.3 need this ports;
80,9300,9080
Cognos BI 10.2.2 need this ports;
80,9300,9362 ,25,389,1433
Cognos Tm1 10.2.2 need this ports;
80,9510,9513,5495,5498,12345,12346 + your TM1 applications ports.

If you have all products, then you need to open all this ports between the Cognos Servers.
You need also open port for database connections, like 1433 for Microsoft SQL server and 389 for Active Directory contact.
Port 25 is used for sending mail from Cognos BI.

No port over 65535 is allowed to be configured in Windows firewall.
TM1 sample application Proven_techniques uses port 83333 as default and need therefor to be changed to port 13333.
PortNumber=12345 is for planning sample application.
PortNumber=12346 is for SDATA app, that you use for opsconsole as default login.
PortNumber=9510 is used by CAFE and PM.

You can in TM1S.CFG set a client port number for each tm1 application. Should be used if you have firewalls between server and client computer, or client is a citrix server. This number need also to be open in the firewall.
# Note: Be sure to assign unique port numbers for the server and client message ports. If you have two servers running on the same machine with the same port number, the message activity may cause a system failure.
ClientMessagePortNumber=32345

Best is if you keep a notepad txt file on your server where you enter each TM1 PortNumber and ClientMessagePortNumber, so you easy can see that you not by mistake reuse the same number.

More information:
http://www-01.ibm.com/support/docview.wss?uid=swg21459257

Product:
Cognos TM1 architect 10.2.2
Microsoft Windows 2012 R2 standard server

Problem:
Login dialog when you start TM1 architect, and you have configured it to be SSO to the Cognos BI Cognos Connection.
If you surf to http://cognosBIserver.domain.com/ibmcognos you are automatically logged in.

Login dialog titled : Windows Security

tm1a.exe connecting to biservername.domain.com

User name

Password

…

Solution:
On the computer where you start TM1 architect, go to control panel and internet options.
Go to Security tab.
Select Local Intranet and click on sites button.
Click on advance button.
Enter the URL to the Cognos BI server;
http://biservername.domain.com
Click on Add button.
Click Close.
Click OK.

Restart TM1 architect, and see if the SSO are working.

For SSO to work with TM1 clients and Cognos BI the CAM authentication Bi server must be in local intranet or trusted intranet zone of Internet Explorer on client computer.

Product:
Cognos TM1 10.2.2
Microsoft Windows 2012 R2 standard server

Problem:
When inside TM1 architect try to add a new user (clients – add new client) you get a error message about the CAM. The dialog will not show up.

Possible solution:
The value in the file tm1p.ini for that user is not updated with a URL to the cognos bi server.

You update the TM1S.CFG file for the TM1 server – but this change is not copied to the TM1 architect users.

IntegratedSecurityMode=2
ServerCAMURI=http://biservername:9300/p2pd/servlet/dispatch
ClientCAMURI=http://biservername.domain.com:80/ibmcognos/cgi-bin/cognosisapi.dll
ClientPingCAMPassport=900
CAMPortalVariableFile=portal\variables_TM1.xml

Only new TM1 architect users will get value from file E:\Program Files\ibm\cognos\tm1_64\bin64\tm1p.ini.

You need to close TM1 architect and update this file
C:\Users\%username%\AppData\Roaming\Applix\TM1\tm1p.ini in notepad.

Add values for
AllowImportCAMClients = T
CognosGatewayURI = http://biservername.domain.com:80/ibmcognos/cgi-bin/cognosisapi.dll

save the tm1p.ini file and start the TM1 architect program again.

Product:

Cognos TM1 10.2.2 Fix Pack 6

Microsoft Windows 2008 R2 server

Problem:

What is a recommended starting point for settings in the TM1S.CFG file?

Solution:

In the TM1S.CFG file that you use for new TM1 applications instances, the settings vary with the server capacity and the need of the application. Please note that the TM1S.CFG values change with different version of TM1. You need to consult the manual for the valid values for your version of TM1. Here is a suggestion:  (do not use values you do not need).

MTQ=4

If you have Microsoft Windows server with 8 CPU cores, and on that server, you run other TM1 instances or the TM1 Application web, you should not utilize all cores. I would recommend to start with MTQ=4 and then adjust it to MTQ=6 if the load allows it.

Query caching behavior is configured per cube via the VMM value in the }CubeProperties cube, where the VMM value defines the maximum amount of memory to be used for caching per cube. If memory permits on server a new start value could be 512 kb.

If VMM cache is set too low, even queries that were cached without MTQ use may not be cached anymore once MTQ is enabled. In such cases – to avoid unnecessary re-execution of MTQs – increase the VMM value until repeated query execution will not trigger MTQ activity anymore (indicating the cache is used).

 

To enable multi-threaded start-up, a configuration parameter must be added to tm1s.cfg file: MaximumCubeLoadThreads=<#ofThreads>.

IBM recommends starting with 50% of the number of available processor cores for your server and testing the trade-off of additional memory consumption and start-up time to determine the optimal setting for this configuration parameter.

When MaximumCubeLoadThreads is set to 0, cube loading and feeder processing is NOT multi-threaded. This is the default behavior when MaximumCubeLoadThreads is not explicitly set in the Tm1s.cfg file.

If your Cognos TM1 model uses conditional feeders where the condition clause contains a fed value, you should set MaximumCubeLoadThreads=0 or exclude the parameter from the Tm1s.cfg file to disable the use of multiple threads at load time.

 

PersistentFeeders=T

To improve reload time of cubes with feeders, set the PersistentFeeders configuration parameter to true (T) to store the calculated feeders to a .feeders file. The feeders will be saved to a *.feeders file (per cube) when the data is saved or rules are edited. On Startup and with PersistentFeeders=T, TM1 will load feeders from the saved feeders file which reduces the time normally taken to recalculate those feeders.

 

ViewConsolidationOptimizationMethod=TREE

the tm1s.cfg parameter ViewConsolidationOptimizationMethod defines the method used to achieve view consolidation optimization. Recommended to have it to TREE.  For example, in the uncommon circumstance when dimensions have just a few leaf elements rolling up to many consolidations, ViewConsolidationOptimizationMethod should be set to ARRAY .

 

Recommend to have a ClientMessagePortNumber set to ensure good performance on TM1 Architect in Citrix environments.  If you are running more than one TM1 server on a machine, each must have a unique port number noted.

ClientMessagePortNumber=<your port number>

RuleStatusIncludeConditionalCheck=F , can improve performance in TM1 10.2.2

LockPagesInMemory= F (False to allow windows to handled memory)

In rare circumstances, should this be set to T. Recommendation is to set it at F.

If a Cognos TM1 server running on a Windows 64-bit operating system is idle for a long period of time, physical memory taken up by the Cognos TM1 server will page out to disk. This is a function of the Windows 64-bit operating system and not Cognos TM1 . This can cause performance degradation in large Cognos TM1 databases when trying to access data after an idle period.

To maximize performance when running a large Cognos TM1 database on 64-bit Windows, set LockPagesInMemory=T in the Tm1s.cfg file.

When this parameter is enabled, Windows still trims pages from the Cognos TM1 process space, but does not page them to disk. This benefits Cognos TM1 server performance because objects are no longer placed in virtual memory, but instead remain in physical RAM.

 

For Performance Modeler to work you need:

AllowSeparateNandCRules = T

DistributedPlanningOutputDir=tunit

ForceReevaluationOfFeedersForFedCellsOnDataChange=T

 

For SSO with CAM you need:

ServerCAMURI=http://biservername:9300/p2pd/servlet/dispatch

ClientCAMURI=http://biservername/ibmcognos/cgi-bin/cognosisapi.dll

ClientPingCAMPassport=900

Indicates the interval, in seconds, that a client should ping the CAM server to keep their passport alive. If an error occurs or the passport expires the user will be disconnected from the Cognos® TM1® server.

 

CAMPortalVariableFile=portal\variables_TM1.xml

CAMPortalVariableFile parameter needed only when variables_tm1.xml file name changes.

https://www.ibm.com/support/knowledgecenter/en/SS9RXT_10.2.2/com.ibm.swg.ba.cognos.tm1_inst.10.2.2.3.doc/c_camportalvariablefile_1.html#CAMPortalVariableFile_1

 

How to setup Cognos Access Manager authentication

https://allthingscognos.wordpress.com/2014/08/26/configuring-performance-modeller-and-tm1-web-with-cam-security-for-tm1-10-2-n/

 

Other information:

The IBM® Cognos® TM1® server may crash when Parallel Interaction is turned on and Bulk Load mode is used. In version 10.2.0 of Cognos TM1, Parallel Interaction is turned on by default.

http://www-01.ibm.com/support/docview.wss?uid=swg21646056

Text is copied from different guidelines by IBM

https://www.ibm.com/support/knowledgecenter/SS9RXT_10.2.0/com.ibm.swg.ba.cognos.tm1_inst.10.2.0.doc/c_parametersinthetm1s.cfgfile_n1503fe.html

Product:

Cognos Tm1 10.2.2 fix pack 6

Microsoft Windows 2008 R2 Server

Symptom:

When new updated express TM1 instance start, it is named = CXMD

Cause:

In the TM1S.CFG file the servername is as Servername = CXMD, but in TM1 you need to not have a space – it should be Servername=CXMD.

 

Uninstall the TM1 instance, change the TM1S.CFG to not use space at = , then start the service again from Cognos Configuration for TM1.

If you not have uninstalled Cognos Express – then the new start of TM1 instance with same name as a existing one will make it look like the new one is installed in Cognos Configuration, but in Windows services if you check on properties on the TM1 instance CXMD it will show it use the old Cognos express engine under \program files (x86)\ that make it not work.

You notice something is wrong if no log files are created in the new folder you have setup for the new TM1 instance – then there is a different folder in use, probably the old one.

 

Solution:

How to move a Cognos Express application to a TM1 10.2.2 application.

 

Make a backup of all excel sheets used in the TM1WEB part.

You need to login to Cognos Express with Tm1 architect and do savedataall step and take a backup of the data folder, mostly there exist a TI process already written for this.

Then copy the Cognos express folder c:\program files (x86)\IBM\cognos express\xcelerator\custom\tm1data\cxmd\ to your new folder for tm1 that in most cases are c:\program files\ibm\cognos\tm1_64\samples\tm1\cxmd\.

Recommend to create a separate folder for log files like this c:\program files\ibm\cognos\tm1_64\samples\tm1\cxmd_logs.

 

To get Cognos Express BI security you need to take screen shoots how it is setup in Cognos Express and then manually add the same AD groups to Cognos BI groups inside the New Cognos Connection on the new installation.

 

Download fix pack for TM1 and Cognos BI

https://www-945.ibm.com/support/fixcentral/swg/downloadFixes?parent=Cognos&product=ibm/Information+Management/Cognos+8+Business+Intelligence&release=10.2.2&platform=All&function=fixId&fixids=10.2.2-BA-CBI-Win64-FP007&includeRequisites=1&includeSupersedes=0&downloadMethod=http

Uninstall Cognos Express program from the server.

 

Install Cognos BI and setup IIS as show here:

http://www.ibm.com/developerworks/data/library/cognos/infrastructure/web_servers/page599.html

Active SSO for Cognos BI with this steps

http://www.ibm.com/support/knowledgecenter/SSEP7J_10.2.2/com.ibm.swg.ba.cognos.c8pp_inst.10.2.2.doc/t_stp_sso_active_drctry_remote_user.html

The connection to customers Active Directory must have the namespace id to be “CognosExpressActiveDirectoryID” set, to allow the users that before was setup in Cognos Express come in as the same user in the new TM1 solution.

Inside Cognos Configuration for BI,  under Security – Authentication, select New Resource – Namespace.

Set Name to domain.com and select Type to Active Directory.

Set the Namespace ID to CognosExpressActiveDirectoryID.

Set host and port to;  customer´s Domain.com:389

 

The name that you show in left for the authentication is what is shown inside Cognos Connection as the name of the namespace, the namespace ID is the Cognos BI internal ID and that should be the same as used in Cognos Express to ensure the users end up in the same rows inside TM1 security table.

Best Practices is to have this two field the same, that should mean namespace id is CognosExpressActiveDirectoryID in this case.

Install Cognos Tm1 10.2.2 and set it up as show here:

http://www.ibm.com/support/knowledgecenter/en/SSMR4U_10.2.2/com.ibm.swg.ba.cognos.express_migration.10.2.2.doc/t_express_inst_mig_install_tm1_start_servers.html

 

Install Cognos TM1 10.2.2 fix pack 6 new certs as of this page

http://www-01.ibm.com/support/docview.wss?uid=swg21991545

http://www-01.ibm.com/support/docview.wss?uid=swg21992411

 

Install SSO for TM1 applications by following this steps:

https://allthingscognos.wordpress.com/2014/08/26/configuring-performance-modeller-and-tm1-web-with-cam-security-for-tm1-10-2-n/

 

In the new CXMD data folder – remove the tm1s.cfg and TM1.lic files.

Create a new TM1S.CFG file with content like this:

[TM1S]

 CAMPortalVariableFile=portal/variables_TM1.xml

Language=ENG

IntegratedSecurityMode=5

ClientMessagePortNumber=12307

DataBaseDirectory=C:\Program Files\ibm\cognos\tm1_64\samples\tm1\CXMD

UseSSL=T

PortNumber=12306

ClientPingCAMPassport=900

LoggingDirectory=C:\Program Files\ibm\cognos\tm1_64\samples\tm1\CXMD_logs

ServerName=CXMD

 

AdminHost=

ForceReevaluationOfFeedersForFedCellsOnDataChange=T

DistributedPlanningOutputDir=.\tunit

AllowSeparateNandCRules=T

ServerCAMIPVersion=ipv4

IPVersion=ipv4

 

ClientCAMURI=http://BISERVER.domain.com/ibmcognos/cgi-bin/cognosisapi.dll

ServerCAMURI=http://BISERVER.domain.com:9300/p2pd/servlet/dispatch

##ServerCAMURI=http://EXPRESSSERVER.domain.com:9300/p2pd/servlet/dispatch

##ClientCAMURI=http://EXPRESSSERVER.domain.com:9300/p2pd/servlet/dispatch

ParallelInteraction=T

SupportPreTLSv12Clients=T

Update the BISERVER values with your server and domain name in above file.

Inside Cognos Configuration for TM1 click on TM1 server – New Resource – TM1 server instances.  Enter CXMD as name.  then browse to the folder where the tm1s.cfg file are in our example that is in c:\program files\ibm\cognos\tm1_64\samples\tm1\cxmd.

Save and start the CXMD instance from Configuration program.

 

Start TM1 architect on the Server to see if you can access the CXMD application.

 

To get TM1 perspective to work after you have used Cognos Express the end user must do a few things;

Ensure the new Cognos BI/TM1 servers are in Internet Options local intranet zone.

Uninstall the previous Cognos Express client.

Install the new TM1 perspective from setup files you place on a share (\\TM1server\clientsetup$).

(select default options during install)

 

first run setup from

\\TM1server\clientsetup$\tm1_clt_10.2.2_32b_ml.tar\win32\iisetup.exe

 

second run setup from

\\TM1server\clientsetup$\up_tm1client_win32_10.2.5260.168_ml.tar\win32\iisetup.exe

 

Then copy all files from folder

\\TM1server\clientsetup$\NewSSLCerts\*.*

 

to this folders on your computer

C:\Program Files (x86)\ibm\cognos\tm1\bin\ssl\*.*

 

Inside Microsoft Excel 2010 add the new folder for TM1\bin to trusted locations.

Go to File – Options in Excel.

Click on Trust Center

Click on Trust Center Settings button

Click on Trusted Locations

Click on Add new location button

Browse to the folder for TM1 that is c:\program files (x86)\ibm\cognos\tm1\bin

Click OK all the way out of Microsoft Excel

Now it should work to start TM1 Perspective from icon on start menu.

 

Excel sheet you have published in TM1WEB, you may need to republish from TM1 Perspective again.

If you get the error message “STOP Failed to open the target workbook. Please make sure the file has not been renamed or deleted.”  when you open a xlsx file in Tm1web applications, then the solution is to create the xlsx-page in new Excel Workbook files and publish them again to the TM1WEB application. Hopefully you can copy the layout and code from the old xls file. The xls files previous used in Cognos Express can in many case not be working in the new Cognos TM1 10.2.2.

 

More Information:

http://www.ibm.com/support/knowledgecenter/SSMR4U_10.2.2/com.ibm.swg.ba.cognos.express_migration.10.2.2.doc/t_express_inst_mig_migrate_tm1_migrate_cxmd.html

To test and see error better set it up like this

https://tm1help.wordpress.com/2011/06/19/how-to-set-up-a-new-tm1-model/

Ensure that you have uninstall Cognos Express before you install TM1 otherwise this can help

http://www-01.ibm.com/support/docview.wss?uid=swg21635821

To active sso in Cognos BI do this steps

http://www.ibm.com/support/knowledgecenter/SSEP7J_10.2.2/com.ibm.swg.ba.cognos.c8pp_inst.10.2.2.doc/t_stp_sso_active_drctry_remote_user.html

Product:
Cognos TM1 10.2.2
Windows Server 2008 R2 64 bit

Problem:
After change to use DNS alias to surf to the Cognos servers there is an error message after you try to login that says;
The TM1Web service parameter was not specified or is not one of the configured locations
You can login if you enter the TM1 server direct like this;
http://servername.domain.com:9510/tm1web/

Possible solution:
You need to update the TM1WEB.HTML file with the DNS alias.
Open the TM1WEB.HTML file from your Cognos BI gateway server in folder
C:\Program Files\ibm\cognos\c10_64\webcontent\tm1\web\tm1web.html

Update the value below by adding the DNS alias for the TM1 server.
// Update the following to point to the location of the TM1Web service(s)
var tm1webServices = [“http://servername.domain.com:9510″,”http://dnsalias.domain.com:9510”];

Save the file, and start Internet Explorer to test again.

Product:
IBM Cognos TM1 10.2 server (version 10.2.5000.367-0)
IBM Cognos TM1 package connector (version 10.2.5000.14-0)
IBM Cognos BI 10.2.1 Fix Pack 1 (version 10.2.5001.156-0)
IBM Cognos BI 10.2.1 Fix Pack 2 (version 10.2.5002.78-0)
Windows 2008 R2 server

Symptom:
After installation of TM1 Package Connector (tm1pc_10.1.1_bi_10.2.1_win_ml.tar) on the same computer where you have TM1 Architect and Framework Manager installed, the option inside TI Turbo Integrator dialog for “IBM Cognos Package” is greyed out and not select-able.

You only get this issue on the Developer computer where you have also installed frame work manager for Cognos BI 10.2.1 fix pack 1.
If there is only TM1 installed or there is not a Cognos BI fix pack installed, it will work.

Solution:
Uninstall TM1 package connector from your computer.
Leave the Framework Manager and other software still installed.
Run installation of TM1 Package Connector again, but
Select a new folder, like:
C:\program files (x86)\ibm\cognos\c10pack
And also remember to set a new shortcut folder name to “IBM Cognos 10 Package Connector”
Finish the installation.
Then go to start menu and open Cognos configuration from “IBM Cognos 10 Package Connector”.
Update the environment tab with values for you Cognos Gateway server;
http://BIgatewayname.domain.com:80/ibmcognos/cgi-bin/cognosisapi.dll
And for you Dispatcher URI for external applications set it to;
http://BIservername.domain.com:9300/p2pd/servlet/dispatch
Save the settings.
Exit Cognos Configuration.
Start TM1 Architect
Click on a TM1 application to login.
Inside a TM1 application right click on “processes” and select “create new process”
Try to click on “IBM Cognos Package” – if it works, then you have succeeded.

TM1 architect use the windows variable TM1_PACKAGE_CONNECTOR to find the installation files its needs, so this variable should be a system variable. You can type SET in the command prompt on the server to check its current value, it should be
TM1_PACKAGE_CONNECTOR=c:\program files (x86)\ibm\cognos\c10pack\bin

You need to replace the URL/PATHS with the correct values for your servers.

Note: This will only work with 32 bit version of TM1 Architect.

And you must REBOOT the server after installation of the Package Connector.