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.

Product:
Cognos TM1 10.2 64 bit
Cognos TM1 Architect 10.2 32 bit
Cognos TM1 package connector 10.1.1 32 bit
Microsoft Windows 2008 R2 server 64 bit
Oracle database server

Symptom:
Error when connecting from TM1 Architect to Oracle source through Cognos BI via TM1 Package Connector.
You have installed TM1 Package Connector on your TM1 server, and on your Terminal Server where you have installed TM1 Architect and Cognos Framework Manager.

You get a Data Source Sign on when you inside TM1 Architect are trying to Query the data with the IBM Cognos Package. This is because the client computer where TM1 Architect are trying to connect direct to the Oracle data source. You need to install Oracle 32 bit Drivers on the computer where TM1 Architect are installed. Also you need to update the tnsnames.ora file with the values needed for the database you try to connect to.

Error Message:
Error: MetaData procedure line (0): CCognosPackage::BuildDataSource Exception: (TR0324) Invalid logon.
– QE-DEF-0285 The logon failed.
– QE-DEF-0325 The logon failed for the following reason:
– RQP-DEF-0068 Unable to connect to at least one database during a multi-database attach to 1 database(s) in:
– CNSDW

– UDA-SQL-0432 Unable to locate the gateway “cogudaor”.
or
Error: MetaData procedure line (0): CCognosPackage::BuildDataSource Exception: (TR0324) Invalid logon.
– QE-DEF-0285 The logon failed.
– QE-DEF-0323 The DSN(ODBC)/ServiceName is invalid. Either the DSN is missing or the host is inaccessible.
– RQP-DEF-0068 Unable to connect to at least one database during a multi-database attach to 1 database(s) in:
– CNSDW

– UDA-SQL-0031 Unable to access the “CNSDW” database. Check that the connection parameters to the database are configured correctly. For example, ensure that the data source connection contains the signon information, such as a password, to connect to the database.
– UDA-SQL-0532 Data Source is not accessible: “data.test.domain.com”.
– ORA-12154: TNS:could not resolve the connect identifier specified

Solution:
Install the Oracle 32 bit drivers on the terminal server where TM1 architect and TM1 Package Connector are installed.
Update the tnsnames.ora file in folder \network\admin to include your data source.

Install the Oracle 32 bit drivers on the Windows server where TM1 Application and TM1 Package Connector are installed. This is the TM1 server where you have your TM1 data folder and you TM1 application.
Update the tnsnames.ora file in folder \network\admin to include your data source.

To get ODBC connections to work in TM1 Architect you need to also install the Oracle 64 bit drivers (in its own directory) on the Windows server where TM1 Application or TM1 Architect are installed. The ODBC connection is using the 64 bit parts of TM1 applications.
You need to start the ODBC Admin (odbcad32) and configure your odbc connection before start of TM1 Architect.

You must restart the TM1 application server, to make it be aware of your new installation of Oracle Drivers.

The Windows Path variable must include the path to the BIN folder of both the Oracle drivers installed.

More information:
Error:UDA-SQL-0432 Unable to locate the gateway “cogudaor”.
= missing 32 bit driver on TM1 server

Error: ORA-12154: TNS:could not resolve the connect identifier specified
= missing TNSNAMES.ORA file on the TM1 server

The TM1 server 64 bit version is using 32 bit drivers when access to data is made though the TM1 Package Connector (who is a 32 bit application). The TM1 architect also need direct connection to the Oracle datasource when developing, so you need 32 bit drivers on the TM1 Architect computer when using the TM1 package connector software.

The TM1 server 64 bit version is using 64 bit drivers when access to data is made through the ODBC connection on the server, here is the same on the terminal server where you have installed TM1 Architect. You must install the 64 bit database drivers on the TM1 servers and TM1 Architect clients.

Product:
Cognos TM1 10.2.2
Microsoft Windows 2008 R2

Problem:
How install TM1 clients to client computers at Enterprise Company?

Solution:
Only supported way to install Cognos Program is by the provide software, manually or scripted. Cognos support is not valid if you create your own installation package.
You can run a silent installation of Cognos programs by supplying an ATS text file that contain the result from a previous installation.
On a workstation at the company, run the installation of your Cognos Client manually answering all questions, for example about folder to install to.
After installation there is an ATS file in folder C:\Program Files (x86)\ibm\cognos\c10\instlog. Copy that ATS file and the Cognos media to a separate folder on a share.
Open the ATS file and change the License from NO to YES, like this:
[Dialog2]
Title=IBM License Agreement
;Failure to accept the license agreement and non-IBM terms, if any, will abort the installation.
;Please return the software to the point of acquisition and obtain a refund, if applicable.
I Agree=y
[Dialog3]
Title=Non IBM License Agreement
;Failure to accept the license agreement and non-IBM terms, if any, will abort the installation.
;Please return the software to the point of acquisition and obtain a refund, if applicable.
I Agree=y
Save the ATS file.
To make the installation, create an install.cmd file. Create a folder c:\install on the client computer. Under the c:\install create a folder called media. Copy the ATS file and a install.cmd file to a folder called c:\install\media on your computer.
Then copy the media for the client you want install to a suitable folder, example c:\install\media\tm1_10.2.2\ga\tm1_clt_10.2.2_32b_ml. Create separate folders for each client software.
The name of the ATS file tell the version that is installed, you can change the name.
cd /D %~dp0 move the focus in windows to the current folder.
Place any extra needed files in the c:\install\media folder as listed below;

TM1 Architect
The install.cmd should contain this:
@echo off
cd /D %~dp0
call .\tm1_10.2.2\ga\tm1_clt_10.2.2_32b_ml\win32\issetup.exe -s 01-TM1CLIENT-10.2-5200.235.ats
copy /Y /V msmask32.ocx “C:\Windows\SysWOW64\”
regsvr32 /s C:\Windows\SysWOW64\msmask32.ocx
==========
The file msmask32.ocx is sometimes not there; therefore add it in the script.

TM1 Perspective
The install.cmd should contain this:
@echo off
cd /D %~dp0
call .\tm1_10.2.2\ga\tm1_clt_10.2.2_32b_ml\win32\issetup.exe -s 01-TM1CLIENT-10.2-5200.235.ats
regsvr32 /s /u C:\Windows\SysWOW64\mscomctl.ocx
regsvr32 /s C:\Windows\SysWOW64\mscomctl.ocx
===========
The file mscomctl.ocx is sometimes not registered, so we unregister it and register it again.
TM1 Performance Modeller
The install.cmd should contain this:
@echo off
cd /D %~dp0
call .\tm1_10.2.2\PerformanceModeler64.msi ALLUSERS=1 TARGETDIR=”C:\Program Files” NOUPDATE=Yes
==========
TM1 client media is found on the TM1 server you have installed in folder C:\Program Files\ibm\cognos\tm1_64\webapps\pmpsvc\rcp_installs, copy the MSI file to your folder c:\install\media\tm1_10.2.2\.
TM1 Cognos Insight
The install.cmd should contain this:
@echo off
cd /D %~dp0
call .\tm1_10.2.2\CognosInsight64.msi ALLUSERS=1 TARGETDIR=”C:\Program Files” NOUPDATE=Yes
==========
TM1 client media is found on the TM1 server you have installed in folder C:\Program Files\ibm\cognos\tm1_64\webapps\pmpsvc\rcp_installs, copy the MSI file to your folder c:\install\media\tm1_10.2.2\.
TM1 10.2.0 Package Connector
The install.cmd should contain this:
@echo off
cd /D %~dp0
call .\bi_10.2.1\ga\tm1pc_10.1.1_bi_10.2.1_win_ml\win32\issetup.exe -s 01-TM1PKGCTOR-10.2-5000.14.ats
==========
The Package connector is needed on both Tm1 server and the client using TM1 architect, if you need to import data thru Cognos BI framework manager package.
CAFE 10.2.2
The install.cmd should contain this:
@echo off
cd /D %~dp0
call .\anl_ms_xls_32b_10.2.2_win_ml\win32\issetup.exe -s 02-COR-10.2-5200.150.ats
==========
You can in Cognos Configuration on the TM1 server, turn off that Cognos Insight is automatic installed to clients from TM1 Application Web when they click on the icon.
Go to environment – TM1 application server – TM1 Clients – Allow provision installs – set to False.
TM1 Application Web (contributor) or TM1 Operations Console does not need a client installation.
You surf from client Internet Explorer to http://tm1server:9510/tm1web
You also need to install any database drivers e.g. oracle, at the client that run TM1 Architect.
More information:
http://www-01.ibm.com/support/knowledgecenter/?lang=en#!/SS9RXT_10.2.2/com.ibm.swg.ba.cognos.tm1_inst.10.2.2.doc/t_tm1_inst_settingupanunattendedinstallationandconfiguration.html

Product:
IBM Cognos TM1 10.1.1
Microsoft Windows 2008 R2 server

Problem:
How do I create a system cube, where I can store common values ( like file paths, database logins) and other things that can change when I move my TM1 application between Cognos Servers.

Solution:
Log into TM1 Architect
Create first a dimension Sys.Environment variables, like this:
Right click on dimensions and select “create new dimension”
Right click and select “insert element”
Enter “fileshare_to_TM1”
Select “string” for Element type.
Click Add.
Enter “ODBC connection”
Select “string” for Element type.
Click Add.
Click OK
Click OK in the top right of the dialog.
Enter the name Sys.Environment variables.
Click OK

Right click on dimensions and select “create new dimension”
Right click and select “insert element”
Enter Value
Select “string” for Element type.
Click Add.
Enter Number
Select “simple” for Element type.
Click Add.
Click OK
Click OK in the top right of the dialog.
Enter the name Sys.Measures
Click OK

Right click on cubes and select “create new cube”
Enter cube name: Sys.Settings
Move the two dimensions to the right side column by mark sys.measures and sys.environment variables and click on the arrow button to move them over.
Click create cube.

Now you can use this for your application.
Double click on the cube Sys.Settings to get into Cube Viewer.
Click on Recalculate icon to show content.
Under the value column for the row of fileshare_to_tm1 enter the path your application will use to get csv files to import, in format \\servername\sharename\foldername , e.g. \\srv001\common\budgetimport.

In the same manner can you enter the name of the ODBC connection you are going to use in the Microsoft Windows server where TM1 is installed, e.g. DATA42 ( if you have named your ODBC connection to that).
To create a ODBC connection you start program c:\windows\system32\odbcad32.exe.

This value can you then use in your TI process code.
In your PROLOG tab you enter;
ODBC_Connection = cellgets (‘sys.settings’,’ODBC Connection’, ‘Value’);
This will populate variable ODBC_Connection with the value DATA42 that you have stored in the cube.
So when you set the source for the data source programmatically in your prolog tab with the value DataSourceNameForClient=ODBC_Connection; The “Data Source Name” will be DATA42.
If you move your TM1 application to some other TM1 server, then the TM1 administrator easy can update the Sys.Settings cube only. And then does not need to search your TI process code for references to the ODBC connection.

In similar manner you can get the path to your code by in PROLOG tab enter code like this;
sPath = cellgets(‘sys.settings’,’fileshare_to_tm1′,’value’);
This will set the variable sPath with the share you need, so when you need it you can use it in cases like;

DataSourceNameForServer= sFilePath;
or
Asciioutput ( sPath | ‘\’ | sFilename, vA_Value, vB_Value);

The best is if the sFilename also come from a stored value in Sys.Settings.
Right click on dimension Sys.Environments variables and select Edit Dimension Structure to get into Subset Editor.
Right click and select Insert Element
Enter “Filename”
Select “string” as element type
Click Add
Click OK
Click OK to close the Dimension Editor
One question about saving changes to dimension you select Yes.

Double click on the cube Sys.Settings to get into Cube Viewer.
Click on Recalculate icon to show content.
At Filename you under Value enter the name of the csv file you want to import, can be SapExport.csv.
Now use this code to get the value;
sFilename = cellgets (‘sys.settings’,’Filename’, ‘Value’);
Then you can create the sFilePath with this code;
sFilePath = sPath | ‘\’ | sFilename;

This will add value of sPath together with value of sFilename with a \ in-between.
The value of sFilePath will then in our example be \\srv001\common\budgetimport\SapExport.csv.

By using this technique for any environment value, like paths or database connections, it is easy to support the application when moved between DEV or PROD environments.

Product:

Cognos TM1 10.1.1 (version in cmplst.txt file is RTM-10.1.7000.91-0)

Update TM1 version is RTM-10.1.7101.108-0

Windows 2008 R2 Datacenter server, Service Pack 1

Problem:

Get the last day in each month to a value. You have in a dimension data, that only contain year and month, but you need to export it as year-month-day. And you want to have the day to be the last day in the each month. How do you find the last day in a month?

Solution:

You have a dimension called S2.PeriodMonthly that contains the hierarchies of the year – quarters – months.  Below the structure of the Dimension.

2011
2011Q1
201101
201102
201103
2011Q2
201104
201105
201106

 

Add to this is an alias called S2.Name where we want the information to be in this format

 

2011
2011Q1
2011-01-31
2011-02-28
2011-03-30

 

Select Display Control Objects from the VIEW menu in TM1 Architect.

Open the control cube for }ElementsAttributes_S2.PeriodMonthly and right click and select edit rule.

Enter below code text to create the rule, which will update the Alias with the Correct Day in the month for the values entered into the dimension.  This rule is automatic processed when values are entered into the dimension.

 

#———————————————————————————

#   RULE 1

#   Set the last day in the month

#———————————————————————————

 

[‘S2.Name’] = s:

if( ellev(‘S2.PeriodMonthly’,!S2.PeriodMonthly) = 0,

#——-   31 DAYS —————————#

if(

subst(!S2.PeriodMonthly,5,2)@=’01’ %

subst(!S2.PeriodMonthly,5,2)@=’03’ %

subst(!S2.PeriodMonthly,5,2)@=’05’ %

subst(!S2.PeriodMonthly,5,2)@=’07’ %

subst(!S2.PeriodMonthly,5,2)@=’08’ %

subst(!S2.PeriodMonthly,5,2)@=’10’ %

subst(!S2.PeriodMonthly,5,2)@=’12’,

subst(!S2.PeriodMonthly,1,4)|’-‘|subst(!S2.PeriodMonthly,5,2) |’-31′,

#——-   30 DAYS —————————#

if(

subst(!S2.PeriodMonthly,5,2)@=’04’ %

subst(!S2.PeriodMonthly,5,2)@=’06’ %

subst(!S2.PeriodMonthly,5,2)@=’09’ %

subst(!S2.PeriodMonthly,5,2)@=’11’,

subst(!S2.PeriodMonthly,1,4)|’-‘|subst(!S2.PeriodMonthly,5,2) |’-30′,

#——-   28-29 DAYS —————————#

if(subst(!S2.PeriodMonthly,5,2)@=’02’,

if( mod (numbr(subst(!S2.PeriodMonthly,1,4)),4)=0,

subst(!S2.PeriodMonthly,1,4)|’-‘|subst(!S2.PeriodMonthly,5,2) |’-29′,

subst(!S2.PeriodMonthly,1,4)|’-‘|subst(!S2.PeriodMonthly,5,2) |’-28′

),

STET

)

)

),

STET

)

[‘S2.Name’] = s:

if( ellev(‘S2.PeriodMonthly’,!S2.PeriodMonthly) = 0,

 

Above will set the alias S2.Name to have this new value only if it is the lowest dimension, and not a consolidated value. ELLEV returns the level of an element within a dimension.

If S2.PeriodMonthly have a value at the lowest level (=0) then it will do the coming commands.

#——-   31 DAYS —————————#

if(

subst(!S2.PeriodMonthly,5,2)@=’01’ %

 

Above will check if the value for dimension S2.PeriodMonthly has the letters 01 in the last part.

So it will check 201101 that the 2 characters with start of character 5 in the word are equal to string 01. In that case it will move to next step.

subst(!S2.PeriodMonthly,1,4)|’-‘|subst(!S2.PeriodMonthly,5,2) |’-31′,

Above will create the value 2011-01-31 for the alias S2.Name.

Subst takes value from dimension and from start position and then number of characters, so this subst(!S2.PeriodMonthly,1,4)| will give ‘2011’. The pipe sign is the add function to add the next string – in this case ‘-‘ that will give the result ‘2011-‘. The next subst(!S2.PeriodMonthly,5,2) will add the characters from position fifth and two characters, in our example that is ‘01’.

Then |’-31′ will add ‘-31’ to the end of the string value that we put inside S2.Alias.

#——-   28-29 DAYS —————————#

if(subst(!S2.PeriodMonthly,5,2)@=’02’,

if( mod (numbr(subst(!S2.PeriodMonthly,1,4)),4)=0,

subst(!S2.PeriodMonthly,1,4)|’-‘|subst(!S2.PeriodMonthly,5,2) |’-29′,

subst(!S2.PeriodMonthly,1,4)|’-‘|subst(!S2.PeriodMonthly,5,2) |’-28′

 

Above part will check if the year is a leap year, by function mod 4 that will give every forth year.
MOD returns the remainder of dividing a number by a divisor.

(This function will not work for the year 3000, but otherwise be correct.)

subst(!S2.PeriodMonthly,1,4)|’-‘|subst(!S2.PeriodMonthly,5,2) |’-29′,
subst(!S2.PeriodMonthly,1,4)|’-‘|subst(!S2.PeriodMonthly,5,2) |’-28′

In TM1 Rules, the else command is the comma, so in case it is a leap year we will set the value ‘29’ and if there is not a leap year ‘28’.

 

You can use it like this, test on a values lenght, and if to long replace it with this value.

 

v23 =  pPeriod;

if (long (v23) = 6);

v23 =  attrs ( ‘S2.PeriodMonthly’, v23, ‘S2.Name’) ;

endif;

Above place input parameter pPerid in variable v23, then we test if it is exact  6 characters long, and in that case we use the value for  S2.PeriodMonthly alias S2.Name when the v23 variable match the dimension content in S2.PeriodMonthly.  ATTRS returns a string attribute for a specified element of a dimension.  Gives that the v23 contain the value in S2.Name if the v23 is exact 6 characters long.