Follow us on Twitter


48.1%United States United States
7.2%India India
7%United Kingdom United Kingdom
5.5%Canada Canada
5.4%Australia Australia


Today: 77
Yesterday: 226
This Week: 948
Last Week: 2039
This Month: 2987
Last Month: 4096
Total: 826577

How to install Data studio PDF Print E-mail
Written by Roger   
Wednesday, 16 September 2015 18:27


IBM Data Studio 4.11
Windows 2012 R2 Server
DB2 database

To save money the Cognos TM1 project does not want to use TOAD, and instead the free Data Studio - to allow the Developers have access to the data.

When run lanchpad.exe to install the DB2 Data Studio you get a installation screen without buttons. There are no links to select and install the product. Only a OK button to select language in the dialog exist in top right corner.
There should be buttons or menu options on the left side of the dialog, but there are none.
When you click on the OK button at the language, you are only brought back to the same dialog as before.

Instruction say to start LANCHPAD.EXE from the unzipped ibm_ds4110_win.zip file.
But that does not seem to work in some computer environments.

Run the INSTALL.EXE instead.
Go to the folder \ibm_ds4110_win\disk1\installerimage_win64\
Right click on INSTALL.EXE and select "Run as Administrator"
This will first install the IBM Installation Manager
When that is done it will automatically start installation of Data Studio.

More Information:


Error when I start the program Data Studio 4.1.1 Client PDF Print E-mail
Written by Roger   
Wednesday, 16 September 2015 18:25


IBM DB2 Data Studio 4.1.1
Windows 2012 R2 Server
DB2 database

Get a error when I start the program Data Studio 4.1.1 Client

Error Message:
Locking is not possible in the directory "D:\xxxx.... " A common reason is that the file system or Runtime Environment does not support file locking for that location. Please choose a different location, or disable file locking passing "-Dosgi.locking=none" as a VM argument. ....

Right click on the icon for Data Studio 4.1.1 Client and start the program "Run As Administrator".

During installation the Windows environment was not setup to run in a "multiuser environment".




FAP client can not login to the TM1 FAP instance PDF Print E-mail
Written by Roger   
Wednesday, 16 September 2015 18:20


Cognos TM1 10.2.2
Windows 2008 R2 Server
Cognos Controller 10.1.1 FAP service

Suddenly the FAP client can not login to the TM1 FAP instance, that have worked before.

Error message:
Could not login to TM1, host: servername.domain.com, server name: FAP user name: AD\Roger

If you restart the TM1 instance, then you need to restart the FAP service.
  1. Stop the FAP Service
  2. Stop the TM1Service
  3. Start the TM1Service
  4. Start the FAP Service

Make sure to pause between the startup of TM1 and FAP, to ensure that the TM1 is up complete and ready to accept calls from clients.

More Information:




How run TM1TOP on a windows 2012 server from a bat file? PDF Print E-mail
Written by Roger   
Wednesday, 16 September 2015 18:18


Cognos TM1 10.2.2
Windows 2012 R2

How run TM1TOP on a windows 2012 server from a bat file?

Create a new folder on you TM1 server, e.g. D:\TM1TOP

Copy the 3 files to a separate folder on your TM1 server.
Tm1top.exe file from a earlier version of TM1.
tm1top.ini should be updated to contain the values for you TM1 server, or as below.

# The possible fields which can be set in this file are listed below.  Note that the
# field names are not case sensitive.  For example AllowMultiModes and allowmultimodes
# are equivalent.
# adminhost - admin server, default is localhost
# servername - TM1 server name
# logfile - log the status line to a log file
# logperiod - time(sec) that the status lines are written to the log file
# logappend [T,F] - When a new session is started should the log data be
#        appended to the log file specified by logfile
# refresh - time(sec) that the display is refreshed. Default is 2 seconds
# adminsvrsslcertid - SSL admin certificate ID, default is tm1adminserver
# adminsvrsslcertauthority - SSL admin server certificate Authority file,
#        default is in the ssl directory
# adminsvrsslcertrevlist - SSL admin server certificate revocation file 
# exportadminsvrsslcert - export the admin server SSL certificate
# adminsvrsslexportkeyid - id used to export the admin server SSL certificate


# AllowMultiModes=[T,F]
# If AllowMultiModes is set to T, TM1Top supports additional display modes that show details of Sandbox
# and Job Queue operation.  The mode is selected when TM1Top is running by processing one
# of the following keys:  (N=Normal, S=Sandbox, Q=Job Queue)
# The default value if AllowMultiModes is not specified is T.

# DisplayMode (N=Normal, S=Sandbox, Q=Job Queue)
# DisplayMode selects the display mode that TM1Top that is in effect when TM1Top starts.
# The default value if this configuration entry doesn’t exist in the file is N for Normal mode.

Create a tm1topfap.bat file to start the session. It can contain values like this;
tm1top -servername "FAP" -refresh 1

Save the bat file and run it - if it works you should have a white dos dialog that show tm1top: -adminhost localhost -servername FAP -refresh 1

The different commands in TM1TOP window:
N = Displays TM1 Top normal (thread status) mode.
S = Displays TM1 Top sandbox mode.
Q = Displays TM1 Top queue mode.
W = Writes the current TM1 Top information to a file.
X = Exits the TM1 Top utility.
H = Displays help text.
V  = Verifies a TM1 Top administrator session.
Displays a user name and password prompt so the TM1 administrator can log into the current session of TM1 Top and enter commands to cancel processing in other threads.
C = Cancels processing in another thread.
Note: Before using the Cancel command, an administrator must first log into the current session of TM1 Top by using the V (Verify) command.
K = Cancels a sandbox submission in the job queue for a specific job ID number.
Requires administrator login with the V (Verify) command

More information:


How to setup SSO against Active Directory with TM1 and CAM security? PDF Print E-mail
Written by Roger   
Wednesday, 16 September 2015 18:15
Cognos TM1 10.2.2
Cognos Controller 10.2.1
Windows 2012 R2 Server
Microsoft SQL database server

How to setup SSO against Active Directory with TM1 and CAM security?

Possible Solution:
This describe the steps to setup for SSO in the Cognos BI and TM1 world.

Install the IIS on the Windows 2012 server to support Windows authentication.
Start server manager - go to local server - scroll down to roles and features, select add roles and features. Click next until you can expand Web Server - Security and select Windows Authentication.

Next you need to setup a connection to Active Directory inside Cognos Configuration.
Go to Security - authentication and right click new resource - namespace.
Enter name same as your domain e.g. AD and select type Active Directory.
Enter Namespace ID to same as domain, e.g. AD, keep all letters the same, this field is case sensitive.
Enter host and port to a DC server in your domain, e.g. domain.com:389
if you enter only the domain, the BI server will random contact on DC server and talk to for validate the user login.

At advance properties , for your namespace , you enter the key singleSignOnOption with the value IdentityMapping.
More information at http://www.ibm.com/developerworks/data/library/cognos/page64.html

Set authentication inside Cognos Configuration to not allow anonymous login. Save and restart Bi server.
If you are using Cognos Controller then you need to add users to the groups Controller Administrator and Controller users inside Cognos Connection. Click on "more" and "set members".

Then in Cognos Controller configuration you need to switch security to CAM authentication from Native.
Restart Cognos Controller server, and let only the ADMIN person login first and add the other users from inside Cognos Controller client.

On the TM1 server there is a file you need to copy to your BI or Cognos Controller server. Check folder C:\Program Files\IBM\cognos\tm1_64\bi_interop for the new bi_interop.zip file.
Extract and merge the content of the bi_interop.zip file into the root directory of your existing Cognos BI installation: For example: C:\Program Files\IBM\cognos\c10_64\
Note: The bi_interop.zip file contains a directory structure that merges files into the \templates and \webcontent subdirectories.
Follow these steps to configure IBM® Cognos® TM1® Web to use IBM Cognos authentication security:
You need to copy and unzip the files from c:\Program Files\ibm\cognos\tm1_64\webapps\tm1web\bi_files folder on the TM1 server, to the BI server.
The unzipped templates directory must be copied into the root of each Cognos BI Server application tier install. Merge with the existing ..\c10_64\templates directory.
The unzipped webcontent directory must be copied into the root of each Cognos BI gateway install. Merge with the existing ..\c10_64\webcontent directory.
Unzip ..tm1_64\webapps\tm1web\gateway_files\tm1web_gateway.zip in the TM1 install directory. This file should unzip into a templates and webcontent directory.
In newer versions of Cognos TM1 the above 3 steps may not be needed. The last step is needed if there is a Cognos Controller 10.2.1 installation of Cognos BI.
This file is contained inside the compressed file tm1web_app.zip.
This file is contained inside the compressed file tm1web_gateway.zip.
Rename the variables_TM1.xml.sample file to variables_TM1.xml.
Rename the tm1web.html.new file to tm1web.html.

Copy variables_TM1.xml file to <Cognos location>\templates\ps\portal on your Cognos BI system.
The variables_TM1.xml file should not be edit as of TM1 version 10.2.2

Copy tm1web.html file to <Cognos location>\webcontent\tm1\web on your Cognos BI system.
Edit the tm1web.html file to point to the server where Cognos TM1 Web is running.
var tm1webServices = ["http://SystemName:PortNumber"];
// Update the following to point to the location of the TM1Web service(s)
var tm1webServices = ["http://localhost:8080","http://localhost:9510"];
change to var tm1webServices = ["http://tm1server.domain.com:9510"];

These files are also installed with newer Cognos BI installations. If the files exist on your Cognos BI server, then you only need to edit them.
Open the C:\Program Files\ibm\cognos\ccr_64\webcontent\planning.html file and locate the following lines:
// Update the following to point to the location of the planning service(s)
var planningServices = ["http://machine.company.com:9510"];
Replace web_server_address with the fully qualified domain name (FQDN) for the computer where the Cognos TM1 Application Server is running. For example, myhost.example.com
var planningServices = ["http://web_server_address:9510"];

To ensure that Cognos TM1 Applications can properly detect a CAM session termination, set the pmpsvc session timeout to a value higher than the CAM session timeout.
The pmpsvc session timeout is the number of minutes of inactivity after which Cognos TM1 Applications terminates a user session. The default value is 60 minutes (1 hour).
The CAM session timeout is the number of seconds of inactivity after which Cognos security terminates a user session. The default value is 3600 seconds (1 hour).
When Cognos TM1 Applications is deployed with the Apache Tomcat that is provided with the Cognos TM1 installation, the fpmsvc_config.xml file is here:
C:\Program Files\ibm\cognos\tm1_64\webapps\pmpsvc\WEB-INF\configuration
open the fpmsvc_config.xml file in notepad to edit it.
Enter a value for the timeout attribute of the service / session element.
Use the format for the service / session / timeout attribute as defined in the XML schema definition file fpmsvc_config.xsd located in the same directory.

<session timeout="65"/>

On your Cognos BI system, configure the CAM session timeout using IBM Cognos Configuration.
Leave the value to 3600 in the Inactivity timeout in seconds field in the Security/Authentication section of Cognos Configuration.

Configure Cognos TM1 Applications with values for the IBM Cognos Gateway URI and IBM Cognos Dispatcher URI . Open Cognos TM1 Applications using the format of the following link:
Log in and open the Cognos TM1 Applications Configuration page:
If you are running Cognos TM1 Applications for the first time, the Configuration page opens after you log in.

If you already configured Cognos TM1 Applications, open the Configuration page by clicking the Administer IBM Cognos TM1 Applications (the icon to the right) on the toolbar of the TM1 Applications portal page.

In some case you do not see the fields, this can be because we have already used a TM1 application with Native security, this has to be removed first before you can add a TM1 application with CAM security and setup this values.
To make a TM1 application use CAM security, you need to update there TM1S.CFG file with this values.

Save tm1s.cfg and restart the TM1 instance.
You need to add users to the TM1 instance from inside TM1 Architect.

Open IBM Cognos Configuration for TM1 and check that the Environment properties for Gateway URI and Content Manager URI point to the BI server.
If you are using Cognos Controller FAP, then you need to change that to also use CAM security.
Open C:\Program Files\ibm\cognos\ccr_64\Server\FAP\FAPservice.properties in notepad and unmark the clientcamuri value, update it to point to the Cognos BI Gateway URL.

Save and restart the FAP service. Then you need to update the login values inside Controller FAP manager for the TM1 data mart to be using AD\username instead of the native logins used before.

On the Cognos BI Gateway installation, that you point out in Cognos Analysis for Excel installation, navigate to Cognos_root\templates\ps\portal\ folder, where Cognos_root is the directory that Cognos Controller BI has been installed to.
Open the file C:\Program Files\ibm\cognos\ccr_64\templates\ps\portal\variables_plan.xml.
Verify that the <url>../pmhub.html</url> tag exists below <url>../planning.html</url>. The following text is an example of the variables_plan.xml file:

<?xml version="1.0" encoding="UTF-8"?>
<param name="cam_passport"/>
<param name="CRN"/>

Close the file.
Open C:\Program Files\ibm\cognos\ccr_64\webcontent\pmhub.html in notepad to edit it.
Edit this file to include all possible pmhub locations to the pmhubURL variable (see line 51). This enables SSO to operate.
// Update the following to point to the location of the pmhub service(s)
var pmhubURLs = ["http://mypmhubserver1:9510","http://mypmhubserver1.domain.com:9510"];

Make sure that the user account that is running the web server has permission to access pmhub.html. If you cannot access the pmhub.html in a web browser, check the pmhub.html file properties.
Edit the PMHub configuration screen.
In Internet Explorer, enter http://servername:port number/pmhub/pm/admin to open the configuration screen.
For example: http://tm1servername.domain.com:9510/pmhub/pm/admin
Expand the node for configurations > com.ibm.ba.pm.resource.security.dictionary and enter values for the following properties (you find the values to use inside Cognos Configuration):
CAMBIURL = http://biservername.domain.com:9300/p2pd/servlet/dispatch
CAMGatewayURL = http://biservername.domain.com:80/ibmcognos/cgi-bin/cognosisapi.dll

The values in PMHUB is saved automatic after a few seconds.
Then you need to test and ensure that Cognos Controller and Tm1web and FAP are working after this changes.
If you see the error "The planning service parameter was not specified or is not one of the configured locations", review your settings for the planningServices parameter in the planning.html file on the Cognos BI server.

More information:






CogKnowHow Newsletter

Please register to the site before you can sign for a list.
No account yet? Register


Do you use an additional administration tool for Cognos?