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.

Product:
Cognos TM1 10.1.1
Windows 2008 R2 server

Problem:
How can I to simple log, when process have been run. Best into a cube, as a status log?

Solution:
Log into TM1 Architect
Create first a dimension SYS.EVENTS
Right click on dimensions and select “create new dimension”
Right click and select “insert element”
Enter 1
Select “string” for Element type.
Click Add.
Click OK
Click OK in the top right of the dialog.
Enter the name Sys.Events.

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

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

Now you have created a cube to store the values from the logging.
Then in each process you have in your application, you add this lines to get a logging going for when the process was run.

In the PROLOG tab enter this line of code last;
#—————————————————————————
# Logging
#—————————————————————————
currentEvent = dimnm(‘sys.events’,dimsiz(‘sys.events’));
currentEvent = numbertoString(stringToNumber(currentEvent)+1);
DimensionElementInsert(‘sys.events’, ”, currentEvent,’N’);

Above code will update the sys.events dimension with one value, so it is ready to accept more values.

In the EPILOG tab enter this lines of code last, update the text with valid text describing the process that have happened.

#—————————————————————————
# Logging
#—————————————————————————
cellputs(‘Moved data for =’|pCompany |’ ‘ |pPeriod, ‘Sys.Log’,currentEvent, ‘event’);
cellputs(timSt(now, ‘\Y-\m-\d \h:\i’), ‘Sys.Log’,currentEvent, ‘time’);
cellputs(‘Name of the process that was run’,’Sys.Log’,currentEvent, ‘type’);

Replace the italic text with your function for that process, this is the text that is stored in the sys.log cube.

‘| is concatenation and will bring text ‘ ‘ together with the value of the variable pCompany.
So it will in the log show Moved data for= Office1 201401, in the case pCompany contains the value Office1.
timSt(now, ‘\Y-\m-\d \h:\i’) will give you the date and time in format YYYY-MM-DD HH:MM.
You need to ensure that all parameters you use are in STRING format when they are called here;
cellputs(‘Moved data for =’|pCompany |’ ‘ |pPeriod, ‘Sys.Log’,currentEvent, ‘event’);
Cellputs function sends a string value to a cube cell. Use the format;
Cellputs( ‘string to enter’, The name of the cube to which you want to send the string, Dimension element names that define the intersection of the cube to receive the string in our case the number, and the dimension name.)
DIMNM returns the element of a dimension that corresponds to the Index argument.
DIMSIZ returns the number of elements within a specified dimension.
Will give that dimnm(‘sys.events’,dimsiz(‘sys.events’)); returns the last element in the dimension.
DimensionElementInsert function adds an element to a dimension.
You can use this function to add numeric, string, or consolidated elements. Note that you cannot use this function in the Data or Epilog procedures of a TurboIntegrator process.
DimensionElementInsert(‘sys.events’, ”, currentEvent,’N’);
will increase the dimension sys.events with one more row.
Save and run your process, then you will se that the Sys.Log cube is updated with valid information.

This can be used as a simple time stamp log for when processes have been run, and can be easy accessed by the end-user from a TM1 view.

Product:
Cognos TM1 10.2
Windows 2008 R2 Server

Symptom:
TM1 application web is slow and it is resolved by restarting the TM1 Application service (tomcat).

Possible Solution:
1) In IBM Cognos Configuration of TM1, select Environment >TM1 Application Server, and increase “Maximum Memory in MB” from 768 to 1024 or 1536. The maximum that it can be set from this GUI is 4096 (in version 10.1x) – if set that high, be sure that the server has enough memory available to accommodate it. Restart the TM1 Application Server.

NOTE: In versions 10.2x the memory can be set higher than 4096 through the Cognos Configuration GUI – but, again, make sure there is enough RAM on the machine to accommodate it.

2) Launch the Apache Tomcat manager GUI from the cmd line (run the command prompt by using Run as Administrator) and navigate to the install directory for TM1 and the Tomcat bin folder (eg: C:\Program Files\ibm\cognos\tm1_64\tomcat\bin).
Type this:
tomcat6w.exe //ES//pmpsvc
Navigate to the Java tab, and in the Java Options window, navigate to the bottom of the options list and add in the following:
-Xgcpolicy:gencon
(the default garbage collector policy is “optthruput”)
Validate and close the window and restart TM1 Application Server.

Below is the list of default values for the TM1 Tomcat java:
-Dcatalina.base=C:\Program Files\ibm\cognos\tm1_64\tomcat
-Dcatalina.home=C:\Program Files\ibm\cognos\tm1_64\tomcat
-Djava.endorsed.dirs=C:\Program Files\ibm\cognos\tm1_64\tomcat\common\endorsed
-Djava.io.tmpdir=C:\Program Files\ibm\cognos\tm1_64\tomcat\temp
-Dorg.apache.tomcat.util.buf.UDecoder.ALLOW_ENCODED_SLASH=true
-Xmx768m
-XX:MaxNewSize=384m
-XX:NewSize=192m
-XX:MaxPermSize=128m
-Dcom.sun.management.jmxremote.port=7999
-Dcom.sun.management.jmxremote.authenticate=false
-Dcom.sun.management.jmxremote.ssl=true
-Dcom.sun.management.jmxremote.password=false
-Djmx.remote.x.server.connection.timeout=1000

NOTE: If you set the properties using the Apache Tomcat administration tab, start the TM1 Application Server using the Component Services option–do not use Cognos Configuration in that case as Cognos Configuration then resets the properties back to the shipped defaults.

3) If the server is a Virtual Machine (VMWare, ESXi) then go to Windows Control Panel, System and Security, Power Options, and change the power plan from “Balanced” to “High performance”.

4) Add exclusions to the antivirus to prevent “C:\Program Files\ibm\cognos\tm1_64\tomcat” and “C:\Program Files\ibm\cognos\tm1_64\webapps” from being scanned. Skipping scanning of all TM1 files is preferred – see below link.

5) Verify DEP is set to “Essential Windows programs and services only”. To do this : Right-click the”Computer” icon on your desktop, select “Properties”, select “Advanced System Settings”, select “Advanced” tab, under “Performances”, “Settings” button, “Data Execution Prevention” tab.

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

Product:
Cognos TM1 10.2.2
Microsoft Windows 2008 R2 server

Problem:
When users surf to TM1 Application Web and login they do not see the icons needed to start Performance Modeller nor do administration work. If some other user surf and login they see the icons needed.
http://tm1applicationservername.domain.com:9510/pmpsvc/
Possible Solution:
The user is not ADMIN in the published TM1 applications in TM1 application web.
When you login to TM1 application Web at address http://servername.domain.com:9510/pmpsvc/applications.jsp, you are assumed to be Administrator and also be administration inside the TM1 applications connected to the portal.
Normal end users that report values to TM1 applications should start the TM1 Application Web client from clicking on the link in Cognos Connection under IBM Cognos TM1 Application – My Applications folder.
Solve by make the Planning Sample a CAM used application.
Stop Planning Sample service.
Change to IntegratedSecurityMode=2 in C:\Program Files\ibm\cognos\tm1_64\samples\tm1\PlanSamp\TM1S.CFG file
Add the values that point to your BI servers in your TM1S.CFG file.
# CAMURI parameters have to be set to correct BI environment
ServerCAMURI=http://BIdispatcherservername.domain.com:9300/p2pd/servlet/dispatch
ClientCAMURI=http://BIgatewayservername.domain.com/ibmcognos/cgi-bin/cognosisapi.dll
ClientPingCAMPassport=900
Save the file and start the Planning Sample service.
You also need to make some changes on the BI servers to get TM1 CAM to work.
http://public.dhe.ibm.com/software/data/cognos/documentation/docs/en/10.2.2/tm1_inst.pdf

Added all TM1 developers, for all existing and new TM1 applications, to the Planning Sample application.
First update the C:\Users\%username%\AppData\Roaming\Applix\TM1\TM1P.INI file with the value to the BI servers.
AdvancedRulesEditor = T
AllowImportCAMClients = T
CognosGatewayURI = http://BIgatewayservername.domain.com/ibmcognos/cgi-bin/cognosisapi.dll
Save the file.
Start TM1 Architect and click on Planning sample to login as Admin.
Right click on planning sample and select security – clients/groups.
Click on Clients – add new clients.
You should get the Cognos Connection security page up so you can search your AD/LDAP domain for the users you want to add.
Click on your Active Directory folder.
Click on search in top right corner.
Enter the name of the user (this must be correct spelled)
Select Find text in Name and Description field.
Click search.
Mark the user and click arrow to add the users.
Click OK.
The users are added last in the Clients/groups on planning sample dialog.
Mark the user as ADMIN with a X in the column for ADMIN.
Click OK.
Select save data from menu and exit TM1 Architect.
Now you need to stop the TM1 service for Planning sample.
Change the TM1S.CFG file to IntegratedSecurityMode=5
Start the TM1 service for Planning sample.
Add planning sample to the IBM Cognos TM1 Applications site.
Add these values to TM1S.CFG file to make it work good in TM1 applications web;
DistributedPlanningOutputDir=tunit
PersistentFeeders=T
ForceReevaluationOfFeedersForFedCellsOnDataChange=T
AllowSeparateNandCRules = T
ParallelInteraction=T
ProportionSpreadToZeroCells=T
AllRuleCalcStargateOptimization=T
Surf to http://tm1servername.domain.com:9510/pmpsvc
Login as a person who already is administrator in TM1 applications there.
Click on the icon far to the right, Administer IBM Cognos TM1 Applications.
In the new page, under Server Names: click ADD
Enter the name of the TM1 host server as admin host.
Select Planning Sample from the drop down list and click OK.
Exit Internet Explorer.
Surf to applications web, click on the icon for performance modeller and now you should be able to select Planning Sample in the dropdown menu when performance modeller starts.

Then next time a user logins – he is an administrator in planning sample application and can start to create the IBM Cognos TM1 Applications for Web.

Product:

LICENSE_TM1-AW64-ML-RTM-10.2.5200.2-0

SWTAG_TM1-AW64-ML-RTM-10.2.5200.1-0

PLANANALYTICS-AW64-ML-RTM-10.2.5200.234-0

IBM Cognos TM1 10.2.2

Symptom:

When log in to TM1 application Web the session loops in Internet Explorer 8.

Error message:

No error message.

The URL in Internet Explorer is something like this;

http://ServerName3002.CompanyDomainName.com/ibmcognos/cgi-bin/cognosisapi.dll?b_action=xts.run&m=portal/bridge.xts&c_env=portal/variables_plan.xml&c_cmd=../planning.html&ps=http%3A%2F%2FServerName0015.CompanyDomainName.com%3A9510&pg=%2Fapplications.jsp

http://ServerName3002.CompanyDomainName.com/ibmcognos/planning.html?cam_passport=MTsxMDE6MThkODU1N2EtZGQ4ZS05YzVkLTUxZTktNDZlMmZjOGUxZDEzOjIyMjgwMjg1ODU7MDszOzA7&CRN=contentLocale%3Den%26columnsPerPage%3D3%26http%3A%2F%2Fdeveloper.cognos.com%2Fceba%2Fconstants%2FbiDirectionalOptionEnum%23biDirectionalFeaturesEnabled%3Dfalse%26productLocale%3Den%26showOptionSummary%3Dtrue%26showWelcomePage%3Dtrue%26skin%3Dcorporate%26linesPerPage%3D15%26http%3A%2F%2Fdeveloper.cognos.com%2Fceba%2Fconstants%2FsystemOptionEnum%23accessibilityFeatures%3Dfalse%26listViewSeparator%3Dbackground%26displayMode%3Dlist%26timeZoneID%3DEurope%252FStockholm%26format%3DHTML%26showHiddenObjects%3Dfalse%26useAccessibilityFeatures%3Dfalse%26automaticPageRefresh%3D30%26&pg=%2fapplications.jsp&ps=http%3a%2f%2fServerName0015.CompanyDomainName.com%3a9510

Solution:

Erase values in file fpmsvc_config.xml to start over again. It points to wrong BI server.

fpmsvc_config.xml file is found in folder C:\Program Files\ibm\cognos\tm1_64\webapps\pmpsvc\WEB-INF\configuration on the server where IBM Cognos TM1 Application Server (TM1WEB) is installed.

You must only point to the BI Content Manager as <dispatcher uri=.

When setting up TM1 10.2.2 with Cognos BI 10.2.1 security you need to have this files updated;

TM1 server C:\Program Files\ibm\cognos\tm1_64\webapps\pmpsvc\WEB-INF\configuration\ fpmsvc_config.xml

TM1 server C:\Program Files\ibm\cognos\tm1_64\webapps\pmpsvc\WEB-INF\configuration\ pmpsvc_config.xml

Cognos BI Gateway server C:\Program Files\ibm\cognos\c10_64\webcontent\ planning.html

Cognos BI Gateway server C:\Program Files\ibm\cognos\c10_64\webcontent\ pmhub.html

Cognos BI Gateway server C:\Program Files\ibm\cognos\c10_64\webcontent\tm1\web tm1web.html

Cognos BI report server C:\Program Files\ibm\cognos\c10_64\templates\ps\portal variables_TM1.xml

Cognos BI report server C:\Program Files\ibm\cognos\c10_64\templates\ps\portal variables_plan.xml

On Cognos BI report server open tm1_contribution.atom file in notepad from folder C:\Program Files\ibm\cognos\c10_64\configuration\icd\contributions\contrib\ tm1_contribution.atom to add the TM1 application.

On Cognos BI report server open tm1_en.properties file in notepad from folder C:\Program Files\ibm\cognos\c10_64\configuration\icd\contributions\contrib\ tm1_en.properties to add the Title of TM1 application to show in Cognos Workspace tool.

 

The files are updated with values like this;

In tm1web.html you need to add the TM1 Application Web server.

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

var tm1webServices = [“http://ServerName0015.CompanyDomainName.com:9510″];

In variables_TM1.xml you need to add the TM1 Application Web server.

<urls>

<url is-regex=”true”>http://ServerName0015.CompanyDomainName.com:9510/TM1Web/TM1WebLogin.aspx</url>

<url is-regex=”true”>http://ServerName0015.CompanyDomainName.com:9510/TM1Web/TM1WebLoginHandler.aspx</url>

<url is-regex=”true”>http://ServerName0015.CompanyDomainName.com:9510/TM1Web/TM1WebMain.aspx</url>

 

 

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

</urls>

In variables_plan.xml is not changed by you, but it is different than previous TM1 version.

In pmhub.html you need to add the TM1 Application Web server.

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

var pmhubURLs = [“http://ServerName0015:9510″,”http://ServerName0015.CompanyDomainName.com:9510”];

In planning.html you need to add the TM1 Application Web server.

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

var planningServices = [“http://ServerName0015.CompanyDomainName.com:9510”];

 

In fpmsvc_config.xml you normal not need to add anything as it is updated the first time you surf to http://tm1webservername:9510/pmpsvc, but it can look like this;

 

<?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://ServerName0015.CompanyDomainName.com:9410/bv”/>

 

<scorecarding enabled=”true”/>

 

 

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

 

<resource path=””/>

 

<users path=””/>

 

<external uri=”http://ServerName0015.CompanyDomainName.com:9510″/>

<session timeout=”65″/>

</service>

<tm1>

 

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

 

<alternate_gateway_uris>

<alternate_gateway uri=”*”/>

</alternate_gateway_uris>

<dispatcher uri=”http://ServerName0014.CompanyDomainName.com:9300/p2pd/servlet/dispatch”/>

<admin_host name=”SERVERNAME0020.CompanyDomainName.com”>

<servers>

<server name=”Tm1 application name …”/>

</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=”false”/>

</fpm_config>

You should only change <session timeout=”65″/> to a higher value than the timeout in Cognos BI server.