Product:
Planning Analytics 2.0.2
Planning analytics workspace 2.0.25
Microsoft Windows 2016 standard server
Problem:
How install PAW with Microsoft 2016 Docker files?
Solution:
When using the Microsoft 2016 server with Docker EE, there is no need to have a Virtualize active in VMWARE, therefor is this a better solution. (If you not use Linux OS). Docker EE also does not cost anything extra, as it is part of the Microsoft 2016 licenses.
But to make this work you must:
– The Microsoft Windows 2016 server must be connected to Internet to download the Docker EE.
– Update Microsoft Windows 2016 standard server to the latest fix pack.
– You must use FQDN to access all servers.
– You must have 70 GB free disk space on the Microsoft Windows 2016 server.
– Turn off the Antivirus program on the Windows 2016 server where PAW is installed.
– After you start PAW you must always wait 10 minutes before you try to access it.
– Recommend that you only have ONE network card on the Microsoft Windows 2016 server for PAW.

Above only for your test server, on your laptop.
There is possible to download Docker EE and move it to a different server, according to this page,
https://docs.docker.com/engine/installation/windows/docker-ee/
I copy some of the information here:
Use the following steps when you want to install manually, script automated installs, or install on air-gapped systems.

• PS> Expand-Archive docker.zip -DestinationPath $Env:ProgramFiles
• # Extract the archive.
• Copy the zip file to the machine where you want to install Docker. In a PowerShell command prompt, use the following commands to extract the archive, register, and start the Docker service.
• https://download.docker.com/components/engine/windows-server/17.06/docker-17.06.2-ee-4.zip
• PS> invoke-webrequest -UseBasicparsing -Outfile docker.zip
• # On an online machine, download the zip file.
• In a PowerShell command prompt, download the installer archive on a machine that has a connection.
• # Clean up the zip file.
• PS> Remove-Item -Force docker.zip

• # Install Docker. This will require rebooting.
• $null = Install-WindowsFeature containers

• # Add Docker to the path for the current session.
• PS> $env:path += “;$env:ProgramFiles\docker”

• # Optionally, modify PATH to persist across sessions.
• PS> $newPath = “$env:ProgramFiles\docker;” +
• [Environment]::GetEnvironmentVariable(“PATH”,
• [EnvironmentVariableTarget]::Machine)

• PS> [Environment]::SetEnvironmentVariable(“PATH”, $newPath,
• [EnvironmentVariableTarget]::Machine)

• # Register the Docker daemon as a service.
• PS> dockerd –register-service

• PS> Start-Service docker
• # Start the Docker service.

• Test your Docker EE installation by running the hello-world container.
• PS> docker container run hello-world:nanoserver

But for this installation, we will have the Microsoft Windows 2016 server connected to Internet.

Download the latest PA Workspace file (ipa) from IBM Fix Central
http://www-01.ibm.com/support/docview.wss?uid=swg27049597

In these instructions we use the version 25. Note; take the WIN version, the other is for Linux (or Windows 2012).

• ipa_workspace_local_win_2.0.25.46.1.zip (6.27 GB)

Unzip the file and place it on the Microsoft Windows 2016 server in a folder, e.g. \install\paw

The Start.ps1 file indicate that you have downloaded the correct program for Windows 2016.

Check that Microsoft Windows 2016 is update in control panel

You can go to settings from Server Manager or enter Settings in the search box.

By the way, we have IE Enhanced Security Configuration and DEP off during the installation. Turn off the Windows firewall during installation and first testing. Start up the firewall later.

After the update you need to reboot your Microsoft Windows 2016 server.

How install Docker EE

https://github.com/docker/labs/blob/master/windows/windows-containers/Setup-Server2016.md

PowerShell Package Provider (recommended)

Microsoft maintains a PowerShell package provider that lets easily install Docker on Windows Server 2016.
Run the following in an Administrative PowerShell prompt:

Install-Module -Name DockerMsftProvider -Force
Install-Package -Name docker -ProviderName DockerMsftProvider -Force
Restart-Computer -Force

So, ensure the server is connected to internet, and right click on start, and select Windows PowerShell (Admin).

Enter the below commands:

Install-Module DockerProvider -Force

Install-Package Docker -ProviderName DockerProvider -Force

For the questions about update the NUTGET, press Yes.

Then the download is done as shown in above picture.

Restart the Microsoft Windows server

Above error comes when you run Start.ps1 and you have not downloaded docker compose.

Download docker compose from here https://github.com/docker/compose/releases/tag/1.16.1

Copy to the file to \program files\docker folder and rename the file to docker-compose.exe.

Install IBM Planning Analytics Workspace

The Microsoft Windows 2016 server will need at least

• 13308 MB of memory
• 4 CPUs
• 70,000 MB (70 GB) of storage

Here the official instructions
https://www.ibm.com/support/knowledgecenter/SSD29G_2.0.0/com.ibm.swg.ba.cognos.tm1_inst.2.0.0.doc/t_paw_install.html

Then go to the powershell admin and run ./start.ps1

Click Y to start the admin tool

Accept the licenses

You must accept both the license tabs

Click OK and you are into the setup dialog.

If you want CAM security (then you need to fill in all above)

But for our test we will use Native TM1 security, then we only need to fill in above values.

The HTTPPortNumber is found in the TM1S.CFG file for the TM1 application that you will use as Authority to the PAW program. Above we use the Planning Sample application.

All users that will use the PAW program must be part of that application, so the users must in most cases be part of TWO TM1 instances, the “login” TM1 instance and the “Application” instance – where they should work on their Budget solution.

Fill in the server name and port number and click on Validate.

If you get above error, this can be a DNS or Network problem, change to use FQDN, even do the ping to the server is working.

Now you see the HTTP ports number the different TM1 instances are using on your server.

Click on UPDATE to start the services.

Go to the Antivirus software, in above dialog it is Microsoft Defender, and click on Settings to turn it off.

Turn off Real-time protection.

Start Internet explorer and surf to you server to test the installation of PAW , surf to your IP address of your Windows server.

http://192.168.254.24/login/form

Login with the user and password for the planning sample application. Now you need to test the installation by creating a workbook.

https://www.ibm.com/support/knowledgecenter/en/SSD29G_2.0.0/com.ibm.swg.ba.cognos.tm1_prism_gs.2.0.0.doc/c_prism_books_views.html

To check the version of docker enter: docker version

Enter Docker stats to see what memory is used by the services

Press CTRL+C to exit the session.

How to backup the PAW database

To take a backup of the databases inside PAW, recommend to run every week the ./Backup.ps1 script from the scripts folder. This will stop and start the services, making the backup possible.

The backup files are placed in the backup folder.

How stop PAW in a secure way:

Start a powershell prompt in administrator mode and enter ./paw.ps1 stop

When that is finish – then you can shut down the Microsoft Windows 2016 server.

Docker stats should show an empty page, if all services are closed.

You can start the PAW from the PowerShell prompt with commando ./paw.ps1 start

How upgrade PAW to later version:

Depending on the version of PAW the steps are different, but in general for version 25.

You must first backup your existing PAW data by use of the backup_for_upgrade.ps1

Copy the zip backup files to a save location.

Procedure from IBM site;

Copy the <paw_install_location>/config/paw.env file from your current installation to the new installation location.

Copy the <paw_install_location>/config/certs directory from your current installation to the new installation location.

Perform Installing of new Planning Analytics Workspace.

Reply “y” when you are prompted to install the Docker images. Reply “y” when you are prompted to open the administration tool.

In the Planning Analytics Workspace administration tool, restart all the services.

After you got all up and running, run the new Restore.ps1 script, and point to your saved files to read that data into the PAWs databases.

https://www.ibm.com/support/knowledgecenter/en/SSD29G_2.0.0/com.ibm.swg.ba.cognos.tm1_inst.2.0.0.doc/t_paw_backup_restore.html

How do i see PAW

Docker is running as a service in Windows 2016, and you have the PAW solution inside the docker service. Check Windows Task Managers details, to see if the PAW parts are running.

In new version of PAW you can set security better than in older versions, more information here
https://www.ibm.com/support/knowledgecenter/SSD29G_2.0.0/com.ibm.swg.ba.cognos.tm1_prism_gs.2.0.0.doc/c_paw_administration_top_level.html

In new version of PAW you can share a view, here more information on how
https://www.ibm.com/support/knowledgecenter/SSD29G_2.0.0/com.ibm.swg.ba.cognos.tm1_prism_gs.2.0.0.doc/t_prism_sharing.html

Note that version 25 of PAW does not support Single Sign On (SSO). That maybe will be accessible in a future version.

You cannot install more than one PAW on a server, due to network configuration issues.

All TM1 applications use SSL for communications between the programs, using their default certificates.

If you get error:

Unable to invoke ‘docker’. Ensure docker is installed and is on the PATH.

Then you have not reboot the server, after docker installation.

If you get error:

This error (HTTP 404 Not Found) means that Internet Explorer was able to connect to the website, but the page you wanted was not found. It’s possible that the webpage is temporarily unavailable. Alternatively, the website might have changed or removed the webpage.

For more information about HTTP errors, see Help.

Then the PAW is not started completely.

Above error show that the PAW underlying services are stopped. Check in Task Manager.

PAX (Planning Analysis for Excel) setup, is not covered in this article.

In the task manager you can see the processes that make up the Docker solution, under the details section;

MONGO database is running here.

REDIS database is running here.

The COUCH database is running here.

When all the services inside docker are stopped, there is no CPU activate or memory used.

More Information:

How setup SSO

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

How setup PAX

https://www.ibm.com/support/knowledgecenter/en/SSD29G_2.0.0/com.ibm.swg.ba.cognos.tm1_inst.2.0.0.doc/t_installingcognos8analysisformicrosoftexcel.html

The latest functions in the different PAW versions

https://www.ibm.com/support/knowledgecenter/SSD29G_2.0.0/com.ibm.swg.ba.cognos.tm1_prism_gs.2.0.0.doc/c_new_features_paw.html

Please note; that the PA 2.0 LOCAL PAW is released a few months later than the PA on cloud. Local is around 3 versions after.

Product:
Planning Analytics 2.0.2
Centos Linux to install PAW (ipa_workspace_local_2.0.22.832.2)
Microsoft Windows 2012 R2 server for the TM1 main install.
Docker version docker-1.12.6-32.git88a4867.el7.centos.x86_64
Operating System: CentOS Linux 7 (Core).

Problem:
How install Planning Analytics Workplace on Linux?

Solution:
This is a suggestion on how to do it in your lab – please follow official documentation in first place. You must have a Linux expert with you when you do the installation at a company production site.

Download products;
IBM Planning Analytics Workspace 2.0.22
with file ipa_workspace_local_2.0.22.832.2.zip (2.06 GB)
from here
https://www-945.ibm.com/support/fixcentral/swg/downloadFixes?parent=Cognos&product=ibm/Information+Management/IBM+Planning+Analytics+Local&release=All&platform=All&function=fixId&fixids=BA-PAWL-2.0.22&includeRequisites=1&includeSupersedes=0&downloadMethod=http&login=true

Download Linux Centos file CentOS-7-x86_64-DVD-1611.iso from here
http://isoredirect.centos.org/centos/7/isos/x86_64/CentOS-7-x86_64-DVD-1611.iso

Different versions of Linux and Docker can give you other issues.
Download PUTTY from here https://www.chiark.greenend.org.uk/~sgtatham/putty/latest.html
Download WINSCP from here https://winscp.net/eng/download.php

For TEST purpose you can setup a VMWARE image on your laptop, select New Virtual Machine Wizard. Point to your ISO file at Installer disc image file (iso) and click next.
Select Linux (version: Red Hat Enterprise Linux 7 64-bit) at Guest Operating System and click next.

Enter a name like CentOS and point to a empty folder on your harddisk and click next.
Set maximum disk size to 200 GB and mark “Store virtual disk as a single file” and click next.

Click on Customize hardware and set memory to 10088 MB, set Number of cores per processor to 2, Remove USB and Sound Card and Printer.
Leave network at NAT. Click close and Finish.

Click on “power on this virtual machine” in WMware Workstation.
Click in the black area with your mouse to get the focus inside the VMware session, go with arrow up to select Install CentOS Linux 7 and press ENTER.

This acpi error is nothing to be concern about – let the installation start.

Let English be your choice and click Continue.
Fill in date and time and keyboard for your country.


Then scroll down and click on Network.


Change the HOST name to something better – like centospaw.lab.domain and activate the network to see what ip you get from the DHCP. Enter the host name in small letters.

Note down the IP address, and click on the Configure button at lower right corner. Click on IPv4 Settings tab and select Method to Manual (you must use manual ip on your PAW server) and click on Add button to fill in the IP values.

Enter the ip address you had on the screen before.
address 192.168.254.11
Netmask 255.255.255.0
Gateway 192.168.254.2
Click Save and then click Done in the top left corner.

Click on Begin installation.
Click on ROOT Password to set it to Cognos17 (or something better)
Using this weak password will demand that you click on Done twice to move forward.


Click on USER Creator and enter your name. Mark “make this user administrator” (this will make it possible for him to use SUDO command in linux)
and set password to Cognos17 (or something better)
click Done twice.
Click on Finish Configuration.

Wait until it is complete installed and click on Reboot button.

Enter your name and your password, as you set it up before.
Now you are inside your Linux OS.

Linux is case sensitive – so enter all commands in lower case. They are only shown in capitals letters in this text to stand out.
Best is to add a text editor, so because this is CENTOS you need to enter YUM SEARCH NANO to see if the text editor NANO exist for installing. If this had been Ubuntu you have to enter APT-GET

Install NANO

http://ubuntu-for-humans.blogspot.se/2009/11/installing-and-using-terminal-editor.html

Enter SUDO YUM INSTALL NANO to install the editor. You need to provide your password for it to act on the command.

First it will list what it will download, so you must click Y to allow it to download and install your selected program.

Enter Y to other warnings.

Now the program is installed.

Now you have setup the VMWARE to have 10 GB of ram and 200 GB of hard disk and installed Linux CentOS version. You have also tested to install a program into Linux. This may require that you have access to Internet from your Linux machine.

Install DOCKER
Enter SUDO YUM INSTALL DOCKER to install docker into your machine.

Enter Y to install the DOCKER program.

Enter SUDO YUM UPDATE to update the Linux OS to latest fix pack.
(Note that Linux is case sensitive, you must enter program commands in lowercase).

After the installation it is best to reboot the Linux server, enter SUDO INIT 6 or REBOOT NOW.

Install Docker-Compose
Before you install Docker-Compose you need to create a folder to store it in.
Enter PWD  (in lower case) to see what folder you are in.
pwd

The Linux disk is build up of several folders, recommendation is to install all cognos to folder OPT. Change to folder with commando CD /OPT (the / tell it to start from the top).

Enter LS to see if there are any files in the folder.
Enter SUDO MKDIR COMP to create the folder comp.
Enter LS to see the folder now (in blue text).

Enter CD COMP
Enter LS
This is a new folder so it should not have any content.
Enter CD .. to go up one folder in the file structure.
Enter LS -L COMP to see the rights on the folder.
Enter SUDO CHMOD A+X COMP to set full rights for all users on folder COMP.

https://ss64.com/bash/syntax-permissions.html
https://help.ubuntu.com/community/FilePermissions

Now you need to enter this line to download Docker-Compose.
curl -L “https://github.com/docker/compose/releases/download/1.9.0/docker-compose -$(uname -s) -$(uname -m)” -o /opt/comp/docker-compose

https://docs.docker.com/compose/install/

Enter SUDO CHMOD A+X DOCKER-COMPOSE to make the file executable.

Sometimes the download of Docker-Compose only give you the HTML page — you can check your download by open it in your text editor, in our case NANO.

If it show readable text, you have not downloaded the program.  Remove your download with the RM DOCKER-COMPOSE command.

Then you should try this URL instead;
curl -L “https://github.com/docker/compose/releases/download/1.9.0/docker-compose-Linux-x86_64cd” -o /opt/comp/docker-compose

Note the size of the received bytes, if to small then you did not download the correct file.

Now you need on your Windows laptop, install below program to access the Linux virtual machine
Install PUTTY
http://support.real-time.com/windows/web/putty.html
Install WINSCP
http://support.real-time.com/open-source/winscp/#installation

Install PAW
Create the folder /opt/apps/ibm/paw to store it in.
Enter SUDO MKDIR APPS APPS/IBM APPS/IBM/PAW

Enter CD APPS/IBM
Enter SUDO CHOWN ROGER: PAW to set owner on the folder paw

install unzip in your linux OS
Enter SUDO YUM INSTALL UNZIP

Enter Y to download and install the unzip program.

To check that you have access to Linux server from you laptop open a CMD prompt and enter PING 192.168.254.11, this should give a good reply.
Copy the PAW files to your linux server, start the WINSCP program.
Click New Site
Enter the Host name to the ip address and enter the user name to your name in linux and the password you have set there.

Click save and login

Click Yes to the question about adding the host key.
Navigate on the left side to the folder on your laptop where you have the ipa file you have downloaded.

Navigate on the right side on the linux box to your new created folder /opt/apps/ibm/paw.
Drag the ipa file from the left windows to the right window, and the copy starts. You can also click on UPLOAD.

When done exit WINSCP program.
In CentOS linux go to the /opt/apps/ibm/paw folder.
Enter CD /OPT/APPS/IBM/PAW
Enter SUDO UNZIP ipa_workspace_local_2.0.22.832.2.zip


Remove the large ipa file with commando SUDO RM -F filename

Start Notepad++ and enter below in a new file.
###### begin of file ##########
#!/bin/bash

# This script exports required environment variables needed
# set to autostart docker program with linux os
systemctl enable docker

# set ip address – change to address of your server
export ADMINTOOL_IP=192.168.254.11

# set area to path where docker-compose is
export PATH=$PATH:/opt/comp

# create docker group
groupadd docker
usermod -a -G docker roger
usermod -a -G docker root

#create folder
mkdir /root/bin

# set rights on the folder to be able to run files
chmod -R a+x /root/bin

# map (link) docker to the a root area
ln -s /opt/comp/docker-compose /root/bin/docker-compose

# lower security
setenforce permissive

# open port in firewall
firewall-cmd –add-port=8888/tcp
firewall-cmd –add-port=8888/tcp –permanent

###### end of file #######
Save the file as startbeforepaw.sh on your laptop.
Use WINSCP to copy the file to your linux paw folder.

Start putty on you laptop.
Enter the ip address at Host Name, and enter a name at Saved Sessions and click on Save.

Click on Open to connect.

Click on Yes to add the server key to your local machine.
Enter your username and password
Enter PWD to see where you are.
Enter CD /opt/apps/ibm/paw to change to the paw folder.

Change so you can run the files in the paw folder by enter SUDO CHMOD A+X *

Enter SUDO ./startbeforepaw.sh to run the startbeforepaw.sh script
Run it as Root will work best.

Let your Linux expert validate your steps before you run them.

Above when you run the script without correct user permissions.

Set execute rights on the script files with command SUDO CHMOD A+X *

If the script does not work, then you have to enter this values manually before you run the Start.sh script.

Or better is to add this lines to start of the Start.sh script;
#!/bin/bash
export ADMINTOOL_IP=192.168.254.11
export PATH=$PATH:/opt/comp

..then when start.sh is run this is executed as the correct user.

Check if they are set with command ENV.

Above when the folder where docker-compose file is not part of the PATH.

Run paw
Go to the paw folder on your CentOS linux server
Enter SUDO ./Start.sh
(Note that linux are case sensitive, you must enter Start.sh)

Press Y

The second run will ask if you want to update the images.

DOCKER PS -A will list the running services. Here only the admintool.

Start a Internet Explorer and surf to http://192.168.254.11:8888

Scroll down and press Accept

Press OK, and select the other tab

Scroll down and press Accept and OK.

Change the servername to point to your TM1 server.

In our example we use the IP address of the TM1 server.

The TM1 Login Server URI port number is to the TM1 instance that will control the access to the PAW (in native mode).

The port number is found in the TM1S.CFG file.

Press validate – this will also show the TM1 applications on that server.
Click on Update button to start the PAW services.

Click on Status tab to see the process start. Press Refresh to get a update of the status. When the CPU% is low the PAW is started. Then you should be able to browse to it on address http://192.168.254.11:80

Enter Admin and apple to login to your sample application.

If you have a terminal to the linux server, you can there enter DOCKER PS -A to see a similar list of status on how the PAW all services are working.

Now you are in PAW. If you are missing options in PAW, please try a different browser – like Chrome instead.
https://www.ibm.com/support/knowledgecenter/en/SSD29G_2.0.0/com.ibm.swg.ba.cognos.tm1_prism_gs.2.0.0.doc/c_paw_modeling.html

Command to see the running docker images;

DOCKER PS  -A

Command to see list of installed images;

DOCKER IMAGES

Command to see content of file;

MORE ADMINTOOL/UP.LOG

If you enter ctrl-c here, you only stop the AdminTool – the paw will still run.

How run a backup of the instance

From a terminal windows – check that the process are running by enter DOCKER PS -A

Then move to the script folder of your PAW start folder.

CD /opt/apps/ibm/paw/script

Here you can run the SUDO ./backup.sh command to create the backup of the databases in folder /opt/apps/ibm/paw/backup

Backup.sh will stop the services, take a backup and start the services again. Recommended to run this every week at least.

Please check the other scripts files in Notepad++ to learn more.

Error

/opt/comp/docker-compose: line 1: syntax error near unexpected token `newline’
/opt/comp/docker-compose: line 1: `<!DOCTYPE html>’

Solution
Download Docker-Compose again, you did not get the right file.

Error
ERROR: for admintool  Cannot start service admintool: driver failed programming external connectivity on endpoint admintool (81344b5025415739036ed6be09366f4f76076d1ce835733547889d727cc77a5c): exec: “docker-proxy”: executable file not found in $PATH
Encountered errors while bringing up the project.

Solution
The docker file does not exist, in this version of docker it have a different name. Make a link in the folder from the new name to the old name, so the program can find the file. Enter a command like this:

ln -s docker-proxy-current docker-proxy

Error
ERROR: for admintool  Cannot start service admintool: driver failed programming external connectivity on endpoint admintool (52dcfb86a67c6f953074c223aefe27e5a85aca9b250df6e5c5d2fa34acb4ce7f): Bind for 192.168.254.11:8888 failed: port is already allocated

Solution
Restart the server, the last try made the ports to be allocated, but no service started.

To ensure you get a new log file, you can erase the old log file with the commando;

rm admintool/up.log

Error
Error response from daemon: Container 81344b5025415739036ed6be09366f4f76076d1ce835733547889d727cc77a5c is not running.

The user that run the service (root) does not have docker files in its path.

Solution
Make symbolic links to the folder for all files, from the USR/BIN folder, that normally is in the ROOTs path.
cd /usr/bin
ln -s /usr/libexec/docker/* .

More info about setup of CAM with PAW:

#CognosAnalytics and #PlanningAnalytics Integration – Walkthrough – Part 3

More Information about PAW versions:
https://www.ibm.com/support/knowledgecenter/SSD29G_2.0.0/com.ibm.swg.ba.cognos.tm1_prism_gs.2.0.0.doc/c_new_features_paw.html

How to install DOCKER CE for Centos on a RED HAT Linux

https://stackoverflow.com/questions/42981114/install-docker-ce-17-03-on-rhel7

Recommendation is to only use supported environments.
https://www.ibm.com/software/reports/compatibility/clarity-reports/report/html/osForProduct?deliverableId=6745CB200D5411E69DCADF455C6AF151

Product:
Cognos TM1 10.2.2 Fix Pack 7 (or Planning Analytics 2.0.2)
TM1_version=TM1-AW64-ML-RTM-11.0.0.612-0
TM1_name=IBM Cognos TM1
Microsoft Windows 2012 R2 server

Problem:
How write and debug TI code more easy?

Solution:
Use the free TI debugger tool.
You download it from here
https://www.ibm.com/developerworks/community/groups/service/html/communityview?communityUuid=51f0ea6b-1c8b-4e4d-9042-74d69ad84fe3#fullpageWidgetId=W8f78e5b97b1c_4f90_8fcb_de8eb32c26ad&file=f78f0f40-bbe8-48a7-acfc-2e6c68c1e8ce

On your TM1 server create a empty folder c:\debugger
Save the 20161214_TurboDebugger [v6].zip file in that folder.
Unzip it in this folder so you get 3 files.
Open TurboDebugger.bat file in notepad.
Add the path to your java folder to the first line, then it can look like this;
start “TM1 Turbo Integrator Debugger” “C:\Program Files\ibm\cognos\tm1_64\bin64\jre\7.0\bin\javaw.exe” -Djavax.net.ssl.keyStore=cacerts -Djavax.net.ssl.trustStore=cacerts -jar TurboDebugger.jar
Save the file.
Create a Shortcut on the desktop to your TurboDebugger.bat file.

In your TM1S.CFG file you need to add EnableTIDebugging=True and then restart the TM1 instance.
For Planning Sample you find the file in folder C:\Program Files\ibm\cognos\tm1_64\samples\tm1\PlanSamp.
# TM1 Server HTTP Port
# Sets the server port number for HTTP access. Like PortNumber above, it is used to distinguish between multiple servers running on the same computer. When multiple TM1 servers are installed on a single computer, each server must use unique values for port number and HTTP port number.
# Type: Optional, Static
# When you install a TM1 server, the default HTTP port number is 12354. Valid port values are between 5000 and 49151
#
# If the Tm1s.cfg file does not contain the HTTPPortNumber parameter, then you can not use the OData v4 Compliant REST API.
HTTPPortNumber=12354
EnableTIDebugging=True

Click on the bat file in Windows explorer to start the debugger.
At the login enter the TM1 windows server name and the HTTPportnumber for the application you want to connect to.
You find the HTTPS port number in the TM1S.CFG file for your TM1 application.
https://localhost:12354/api/v1/

Enter the username and password to connect to your TM1 application.

This give you a improved TI editor.
You can search and replace text, and more easy update the TI processes.
On the right side you will see the TM1 variables values when you step though the TI process.

Changes you make to the code can be save with the save button on the top right side.

More Information:
http://www-01.ibm.com/support/docview.wss?uid=swg27049516
http://ecapitaladvisors.com/blog/ibm-planning-analytics-turbointegrator-debugger-tool-is-now-available/

Product:
Planning Analytics 2.0 Local (TM1)
Microsoft Windows 2012 R2 Server
Microsoft SQL 2014 database server

Problem:
How setup PA 2.0 Local?

Background:
This will describe the steps to setup PA 2.0 local with Security mode 5 connected to Cognos Analytics 11 (CA) and install of Toolbox docker and PAW. This doc will not cover SSO or how-to setup a reverse proxy for CA 11.

https://www.ibm.com/support/knowledgecenter/SSD29G_2.0.0/com.ibm.swg.ba.cognos.tm1_inst.2.0.0.doc/c_tm1_inst_singlecomputerinstallations.html

Newer versions of Planning Analytics use a different setup, please check the official documentation.

Solution:
Ensure that you have a big virtual Microsoft Windows 2012 R2 server, with at least 4 CPU cores, 16 Gb ram and 200 Gb hard disk space. Recommended is to have more RAM – like 64 GB ram.

Download software from IBM web site (easiest is to search for the PART NUMBER)

IBM TM1 2.0 Microsoft Windows Multilingual (download also the latest version from the links below)	CNG5RML
IBM Planning Analytics Workspace 2.0 Multilingual	CNG5UML
IBM Planning Analytics for Microsoft Excel 64-bit 2.0 Microsoft Windows Multilingual	CNG5WML
IBM TM1 Client 64-bit 2.0 Microsoft Windows Multilingual  (TM1 Perspective)	CNG5TML
IBM Cognos Analytics Server 11.0.5 Microsoft Windows Multilingual (for cam security) You should download the latest version – at least version 11.0.6 from link below.	CNG1XML
IBM Cognos Framework Manager 11.0.5 Microsoft Windows Multilingual	CNG25ML
IBM TM1 Client 32-bit 2.0 Microsoft Windows Multilingual (if you have 32 bit Excel)	CNG5SML
IBM Planning Analytics for Microsoft Excel 32-bit 2.0 Microsoft Windows Multilingual (if you have 32 bit Excel 2010)	CNG5VML

RTM versions are listed here http://www-01.ibm.com/support/docview.wss?uid=swg24042732

Download IBM Cognos Analytics 11.0.6.0 from here (ca_srv_win64_11.0.6.17031315.exe) http://www-01.ibm.com/support/docview.wss?uid=swg24043412

IBM Planning Analytics Local 2.0.2 is now available on Fix Central (tm1_winx64h_2.0.2.138_ml.tar.gz)

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

IBM Planning Analytics Workspace 2.0.20  (ipa_workspace_local_2.0.20.770.4.zip)

https://www-945.ibm.com/support/fixcentral/swg/downloadFixes?parent=ibm%7EInformation%20Management&product=ibm/Information+Management/IBM+Planning+Analytics+Local&release=All&platform=All&function=fixId&fixids=BA-PAWL-2.0.20&includeRequisites=1&includeSupersedes=0&downloadMethod=http&login=true

IBM Planning Analytics for Microsoft Excel 2.0.20  (cor_win32_2.0.20.17_ml.tar.gz)

https://www-945.ibm.com/support/fixcentral/swg/downloadFixes?parent=ibm%7EInformation%20Management&product=ibm/Information+Management/IBM+Planning+Analytics+Local&release=All&platform=All&function=fixId&fixids=BA-PAXL-2.0.20&includeRequisites=1&includeSupersedes=0&downloadMethod=http

Fix pack information can be found here

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

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

To get the fix list info in mail

https://www.ibm.com/communities/analytics/planning-analytics-blog/subscribe-to-fix-list-updates-for-planning-analytics-workspace-and-planning-analytics-for-microsoft-excel/

This is only a suggestion for the setup of PA 2.0 Local – you should follow the instructions that come from IBM in the first hand.

If you install to Microsoft Windows 2016 – you should use version 2.0.21

https://www-01.ibm.com/support/docview.wss?uid=swg24043782

Download Docker Toolbox https://www.docker.com/products/docker-toolbox  if PAW is going to be installed on Windows 2012 server.

Check that on the Windows 2012 R2 server, you have installed:

• NET Framework 4.6.1
• C++ 2010 x64 redistributable (vcredist_x64.exe)
• 7zip (to unpack the media files) http://www.7-zip.org/download.html
• Telnet client (for testing of access to ports)
• SQL drivers (sqlncli_x64.msi and sqljdbc4.jar files)

Turn off DEP

1. Log on to the server.
2. Open Windows Explorer.
3. Right-click Computer > Properties.
4. In the System Properties window, click Advanced System Settings.
5. On the Advanced tab, under the Performance heading, click Settings.
6. In the Performance Options window, click the Data Execution Prevention tab, and then select Turn on DEP for essential Windows programs and services only.
7. Click OK and then restart your system to enable the change.

DEP – Data Execution Prevention, can also be changed like this;
To do this from the Start menu select All Programs, then go to Accessories and then finally right-click on Command Prompt and click Run as Administrator.
Once the command prompt is open, you can now disable the DEP by entering the following command line.
bcdedit.exe /set nx AlwaysOff

Now restart the server
To reverse the action, simply type this command line to enable DEP back on again.
bcdedit.exe /set nx AlwaysOn

Turn off IE enhanced security

To disable IE enhanced security in windows server 2012 R2, launch the Server Manager, on the left hand side click on Local Server. On the right hand side click on the On link next to IE Enhanced Security Configuration.

You will now see the Internet Explorer Enhanced Security Configuration box. Click on Off to turn off the IE ESC for both users and administrators.

Switch to the High Performance power profile

To configure this using a GUI, go to the Start Menu, search for “Choose a Power Plan” under Settings, then select the “High Performance” option. To configure this from a command line, use “POWERCFG.EXE /S SCHEME_MIN”.

By default, hidden files and folders are not visible, change this to make the work easier.

1. Start Control panel.
2. Click Folder options.
3. Click Folder and search options.
4. Click the View tab.
5. Check show hidden files, folders and drives.
6. Scroll down until you notice Hide extensions for known file types, un-check this line by clicking the check box.
   Note; To hide file name extensions, check this line.
7. Click OK

If you are going to install CA11 and PA 2.0 Local on the same Windows server you must install CA11 first. If they are not on the same server (it is recommended to have them on separate servers) you can install PA 2.0 Local first and set it up with “localhost” in Cognos Configuration Environment tab.

Copy all media files to a folder on the Windows server, like D:\install

Unzip all gz media files to different folders, and remove the .tar files to save space.

SETUP CA 11

Create an empty database on your SQL server, name the database to “contentstore”.

Create a SQL login named cognos with the password Cognos202.

Ensure the SQL login cognos is DB_OWNER on the database “contentstore”.

Turn off On-Access-Scan in the server’s Anti-virus software before installing.

Right click on ca_srv_win64_11.0.6.17031315.exe file and select “run as administrator”.

Click next to run the installation in English.

Select IBM Cognos Analytics, and click Next.

Select to Accept the license agreement, and click Next.

Enter the installation directory to d:\program files\ibm\cognos\analytics and click Next.

Select the Custom installation type, and click Next.

Select the First Install option and click Next.

Select all components and click Next.

Click on Install.

If you get a warning from the Windows firewall, check all and click on Allow access to continue the program installation.

When finish, click on Done.

 

Start up Cognos Configuration by right click and select “run as administrator”.

Check to ensure the Windows server name is under Environment instead of localhost for the important URLs. Should be same server name everywhere instead of localhost.

The Content store need to be change from IBM DB2 to a SQL Server database.  Under Data Access – Content manager, right click ‘Content Store’.  Select ‘Delete’.

Right-click New Resources -Database.  Name the database ‘Content Store’ and select the type ‘Microsoft SQL Server database’.

In the right-hand pane at ‘Resource Properties’, fill in;

Database server name with port number (the sql servernamn:1433)

User ID and password (in our example cognos and Cognos202)

Database name (in our example contentstore)

Click on save icon and wait.

To enable login to Active Directory, you need under Security –  Authentication,

Right-click New Resource – Namespace.  Provide a name of the domain ‘AD’ and select ‘Active Directory’.  Click OK.

Enter the Namespace ID to be the same as the Authentication name like ‘AD’.

Enter the host and port to the domain:  domain.com:389

Click the save icon. You must change domain.com and the server-name to meet your environments need.

Right click and test to see that the AD connection works, you must provide an AD users name and password for the test.

Click save and click on start (triangle) to start the CA 11 service.

Surf to ‘http://servername:9300/bi/v1/disp’ to test the program.

You should get to the page without the need to login.

 

To test the network speed to the AD server, open a DOS prompt, and enter

PING  DOMAIN.COM  -T

This should give you how far it is to the DC server, if Time value is above 50ms you need to talk to IT department.

Change allow anonymous access to ‘False’ under the cognos namespace in Cognos Configuration.

Save the change and restart the Cognos services from the restart icon.

Test to surf again to http://servername:9300/bi, this time you should get a login dialog up.

Login to ensure the connection to Active Directory (AD) is working.

 

SETUP PA 2.0 Local

Turn off the anti-virus program on the server before installing.

Go to the folder where you have unzipped the PA media files.

Right click on file D:\install\pa 2.0.1\pa_2.0.1_win_ml.tar\winx64h\iisetup.exe and select ‘run as administrator’.

Click Next to get English as installation language.

Click I agree to the IBM License Agreement, and click Next.

Enter the path to the installations folder and set the server use type to Production (if this is the production server) and click Next. Server use type can be used by ILMT software to list the server as production or not.

Select all components and click Next.

Mark ‘Make the shortcuts visible to all users’ and click Next.

Click next to start the installation.

It should finish without any errors.

Go to the folder for the latest version of the PA 2.0 Local media and run the setup again in same folder. Ensure you install to the same folder as before. (maybe it is possible to run the setup direct with this refresh media file tm1_winx64h_2.0.2.138_ml.tar.gz)

 

Right-click IBM Cognos Configuration for IBM Cognos TM1 – 64. and select Run as Administrator.

Go to Environment and enter the server name of the BI (CA11) server (if BI is not on same server as PA, then some fields should point to PA) instead of localhost.

Click on save icon.  If you get message from Windows Firewall , click on Allow access.

Right click on TM1 Admin server and select start.

Go to TM1 applications and enter the server name of the TM1 server you are configure instead of localhost. Click on the save icon.

Right click on IBM Cognos TM1 under IBM Cognos TM1 services and select start.

Go down to TM1 servers, and start the SData and Proven_Techniques sample TM1 data models.

SData is default used by Opsconsole as the holder of user’s login.

We use Proven_Techniques to test the CAM security later.

Close Cognos Configuration.

 

Start TM1 Architect and test that you can login to Sdata.

User name is Admin and password is apple.

FIREWALL

To access the PA 2.0 Local from other computers, you need to open some ports on the Microsoft Windows firewall on the 2012 server.

On the Start menu, click Run, type WF.msc, and then click OK.

In the Windows Firewall with Advanced Security, in the left pane, right-click Inbound Rules, and then click New Rule in the action pane (upper right corner).

Select Port and click next.

Specify the local ports to: 80,443,9300,9510,9513,5495,5498, 5895,5898,9362,9580,9543
(ports 80,443,9510 are for End Users, the rest is for TM1 developers)

Click Next.

Ensure ‘allow the connection’ is select and click next.

Mark all options for the rule to apply and click next.

Enter a name, like “Cognos Tm1” and click on Finish.

Repeat the above for a new rule for the TM1 applications ports.

Here is best to open a series of ports – can be this suggested range;

PortNumber	Range 12340 -12350
HTTPPortNumber	Range 12540 -12550
ClientMessagePortNumber	Range 12440 -12450

We may have missed some needed ports, like 1433, that you also need to open in the Windows firewall on the server.

If there exist router firewalls between the servers, then you also need to open the ports in there.

TEST TM1WEB

Ensure the PA 2.0 LOCAL server is in the Trusted Zone in your Internet Options for your IE browser. Add both the server name and the *.domain.com

Surf to http://PAservername:9510/tm1web to test tm1web.

for IBM Cognos Performance Management Hub use:
http://PAservername:9510/pmhub/pm/admin

for TM1 Operations Console use:
http://PAservername:9510/pmhub/pm/opsconsole

TM1 applications should you not setup yet, if you are going to use CAM security.

http://PAservername:9510/pmpsvc

SETUP CAM SECURITY

Start Cognos Configuration for CA 11, and change to not allow anonymous login.

Save and restart the CA 11 windows service (IBM Cognos).

Open Cognos Configuration for PA 2.0 and in Environment section copy the URL for gateway and internal dispatcher to notepad. This should be used in your TM1S.CFG file.

Close TM1 architect, if it is open.

Click start and select Command Prompt (admin).

From the cmd dialog enter notepad and press enter.

This will start a notepad in admin mode that can write to \program files\ folder.

From inside Notepad select open and find tm1s.cfg in folder d:\Program Files\ibm\cognos\tm1_64\samples\tm1\Proven_Techniques\.

You need to change notepad to show all files and not only .txt.

 

Add this values to the tm1s.cfg file

IntegratedSecurityMode=2

ClientCAMURI=http://biservername:9300/bi/v1/disp

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

ClientPingCAMPassport=900

 

Update the values for ports to this

PortNumber=12345

HTTPPortNumber=12545

ClientMessagePortNumber=12445

 

Add these values

IPaddress=T

AllowSeparateNandCRules=T

DistributedPlanningOutputDir=.\tunit

ForceReevaluationOfFeedersForFedCellsOnDataChange=T

EnableNewHierarchyCreation=T

ParallelInteraction=T

MTQ=2

 

See here for more values to tm1s.cfg

https://www.ibm.com/support/knowledgecenter/en/SS9RXT_10.2.2/com.ibm.swg.ba.cognos.tm1_inst.10.2.2.3.doc/c_parametersinthetm1s.cfgfile_n1503fe.html

Save the tm1s.cfg file for Proven_Techniques

From inside Notepad (in administrator mode) open the tm1p.ini file for your user.

You will find it in folder C:\Users\%username%\AppData\Roaming\Applix\TM1

Change AllowImportCAMClients = F to AllowImportCAMClients = T.

Add CognosGatewayURI = http://biservername:9300/bi/v1/disp

 

Save the file and close notepad.

Check that Cognos BI service ‘IBM Cognos’ is running.

Restart your TM1 services, like IBM Cognos TM1 Server – proven_techniques.

 

Start TM1 Architect and login to proven_techniques.

Use the native login of Admin and password apple.

When inside, select the application and right click and select security – clients/groups.

From menu clients, select add new member.

At the login prompt enter the AD username and password you have.

You should get to Cognos Connections add users dialog where you can select Cognos and your AD namespace.

Go to you AD namespace, and search for the Windows users you want to be able to work in your application. In this test, only add one user (you).

You can also click on TYPE in upper right corner and enter the username like this;

AD/roos

Where first is your AD namespace name and after the slash is the NT user name.

Click on the arrow to add the user, and it should resolve to display name.

Click OK to add the user to your TM1 application.

Mark ADMIN for that user before you exist TM1 architect.

Close TM1 Architect.

 

Start NOTEPAD from Admin command prompt.

Open the tm1s.cfg file from d:\Program Files\ibm\cognos\tm1_64\samples\tm1\Proven_Techniques folder.

Change to IntegratedSecurityMode=5

Save the tm1s.cfg file and exit notepad.

Restart the TM1 windows service proven_techniques.

 

Wait a long time to allow the services to start.

Start TM1 Architect and login to proven_techniques, you should be prompted with the CA 11 login page, and come in as the user you have just added.

 

You need to repeat above step of adding users for your TM1 applications, so you get the first CAM user to be Admin inside the TM1 application.

 

To get TM1WEB and PMPSVC to work with CAM security you need to update some file in your Cognos BI (CA 11) server.

On your PA 2.0 Local (TM1) server unzip the file d:\program files\ibm\cognos\tm1_64\bi_interop\bi_interop.zip to a new folder.

Stop the Cognos Analytices service (IBM Cognos)

Copy the webcontent to the folder d:\program files\ibm\cognos\analytics\webcontent to merge the content.

Copy the templates to the folder d:\program files\ibm\cognos\analytics\templates to merge the content.

Start Notepad from a admin command prompt, to be able to save the files later.

From inside notepad open the file d:\program files\ibm\cognos\analytics\webcontent\planning.html

Change

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

var planningServices = [“http://machine.company.com:9510”];

to point to the new PA (TM1) server

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

var planningServices = [“http://PAservername.domain.com:9510”];

Save the file.

 

From inside notepad open the file d:\program files\ibm\cognos\analytics\webcontent\pmhub.html

Change

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

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

to point to the new PA (TM1) server and to the PAW server, like this

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

var pmhubURLs = [“http://PAservername.domain.com:9510″,”http://PAWservername.domain.com:9580”];

Save the file.

 

From inside notepad open the file d:\program files\ibm\cognos\analytics\webcontent\tm1\web\tm1web.html

Change

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

var tm1webServices = [“http://localhost:8080”, “http://localhost:9510”];

to point to the new PA (TM1) server

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

var tm1webServices = [“http://PAservername.domain.com:9510”];

Save the file.

Start the CA 11 ( IBM  Cognos) service. Wait until it is started.

Startup PMPSVC for the first time, now when you have cam security in your application and support for it setup in the cognos bi (CA 11) server.

Surf to http://PAservername.domain.com:9510/pmpsvc/

Ensure you can select your TM1 application in the dropdown list

(if the list is missing – please try a different web browser)

All url should be correct populated.

If you are missing information – check the TM1 Cognos Configuration section. You may have a localhost line there.

Mark the Cognos BI dispatcher and click OK to save the settings (they are save to the file d:\Program Files\ibm\cognos\tm1_64\webapps\pmpsvc\WEB-INF\configuration\ fpmsvc_config.xml).

Now only applications with the same security (IntegratedSecurityMode=5) will work in TM1 application portal (pmpsvc).

User who need to access the admin functions in pmpsvc, can need to be part of the first TM1 application you added to the list of PMPSVC TM1 applications (instances).

The new Planning Analytics Workspace (PAW) in IntegratedSecurityMode=1 point to ONE TM1 instance, that must contain the admin users who can change the PAW settings.

PAW only work with IntegratedSecurityMode=1 applications or IntegratedSecurityMode=5 applications, you cannot mix IntegratedSecurityMode for applications that interact with the PAW.

Simplest is to use IntegratedSecurityMode=1 in your application, but then the TM1 super user need to handle the name and password administration.

With IntegratedSecurityMode=5 you can use the Active Directory (or LDAP) functions, and user and password administration can be handled by your IT department.

 

Before installing docker;

Check that VTX are enable on the Microsoft Windows 2012 server, by download and install the Intel processor identifier. Download it from here:

https://downloadcenter.intel.com/download/7838/Intel-Processor-Identification-Utility-Windows-Version
Run the utility, and go to the cpu technologies tab. The Intel VT-x with EPT must read a value of Yes. If No, you must active VTx in your system before we start installing PA 2.0 Local PAW.

This mean your VMWARE guru need to change in HOST BIOS, enable VT-X support in the HOST VMware console, and for change VT-x support for the image you plan to run PAW in.

Note; that some versions of Hyper-V or VMWARE does not support VT-x, here can you not install PAW.

Best is to create a folder, d:\vbox, for the virtual machines on your server.

Go to Control Panel \System and Security\System.

Click on Change Settings.

Go to “Advance” tab.

Click on Environment Variables.

Set the “MACHINE_STORAGE_PATH” system variable to point to folder d:\vbox

 

Go to CMD prompt and enter SET to see a list of all variables in use.

Check that the MACHINE_STORAGE_PATH is listed correct.

 

SETUP DOCKER

For Microsoft Windows 2012 you must download the “docker toolbox” installation program.

Right click on DockerToolbox.exe and select “run as administrator”.

Untick ‘help Docker improve Toolbox’ and click Next.

Enter the path for the program (d:\program files\docker toolbox) and click Next.

Choose Full Installation and click Next.

Uncheck ‘Install VirtualBox with NDISS driver’ and click Next, at additional tasks.

Click Install.

If you get the question to install ‘Oracle Corporation Universal Serial Bus’, click Install.

Uncheck ‘View Shortcuts in File Explorer’ and click Finish.

This should give you some new icons on the desktop for Oracle VM VirtualBox.

To get VBOX to run as a service you need to download VBoxVmService-5.1-Plum.exe from  https://sourceforge.net/projects/vboxvmservice

This will only work with VirtualBox Version 5.1.

The Only help I found was here;

https://forums.virtualbox.org/viewtopic.php?f=6&t=4762&start=390

 

SETUP PAW

Important to reboot the Windows server before installing the PAW program.

You need to download the latest PAW installation file from IBM Fix Central.

Unzip the ipa_workspace_local_2.0.20.770.4.zip file to a folder on the server.

Place the files in an easy accessible folder, because you will check the log files here.

The start.bat file contain values you can change.

Open it in Notepad before installation, to change the memory the PAW image will use and the Ports the program will use. If it is run one its own server, then leave the default ports at 80 and 443.

In the case we install it on the same server where we have Cognos BI or IIS installed, then change the ports to 9580 and 9543 (so they will not collide with IIS port 80).

You should not change the CPU COUNT to less than 4 CPU, then it will become slow.

But your host server must have at least the same amount of CPU, and best if it have 2-4 Gb ram more than the PAW will use.

If your VMware host use the network 192.168.40.x you should change the Networks values to a different not used network.

 

Example of START.BAT shown below:

@echo off

REM Start up a bash shell and run the Windows start script for IBM Planning Analytics Workspace

SET PAW_DIR=%~dp0

 

SET DOCKER_MACHINE_NAME=paw

SET VM_MEMORY=6144

SET VM_CPU_COUNT=4

SET VM_DISK_SIZE=20000

SET HOSTONLY_CIDR=192.168.40.1/24

SET STATIC_IP=192.168.40.100

SET NETMASK=255.255.255.0

SET BROADCAST_IP=192.168.40.255

SET HTTP_PORT=9580

SET HTTPS_PORT=9543

 

REM Avoid a breaking change in Docker Compose 1.9

SET COMPOSE_CONVERT_WINDOWS_PATHS=1

 

REM Share the parent directory with the Virtual Machine

cd %PAW_DIR%/..

SET HOST_SHARED_FOLDER=%CD%

cd %PAW_DIR%

 

SETLOCAL ENABLEEXTENSIONS

SET KEY_NAME=”HKEY_LOCAL_MACHINE\SOFTWARE\GitForWindows”

SET VALUE_NAME=”InstallPath”

 

FOR /F “tokens=2*” %%A IN (‘REG.exe query “%KEY_NAME%” /v “%VALUE_NAME%”‘) DO (set GIT_PATH=%%B)

 

IF NOT “%GIT_PATH%”==”” (

SET BASH_PATH=%GIT_PATH%\bin\bash.exe

) ELSE (

SET BASH_PATH=C:\Program Files\Git\bin\bash.exe

)

 

if exist “%BASH_PATH%” (

SET TERM=

start “IBM Planning Analytics Workspace Administration” “%BASH_PATH%” –login -i “scripts\winstart.sh”

) else (

@echo on

echo Install Docker Toolbox for Windows and try again.

explorer “https://www.docker.com/products/docker-toolbox”

pause

)

 

On the Windows server right click on start and select ‘command prompt (admin)’.

In the CMD window, CD to the folder where you have your Start.bat.

Enter START.BAT to start the PAW installation.

You must enter START.BAT, if you enter only START it will fail.

The program will check the ports,

and give you an option to change the memory and cpu usage.

Creating the virtual machine “paw” takes a very long time.

Press Y when you get the question about starting the Administration Tool.

This will start a IE Browser one your host accessing the Admin page, accept both license before you can move on.

In the Configuration tab you should enter your TM1 servers name.

TM1 Admin server URI = https://PAservername.domain.com:5898

TM1 Application Server Gateway URI = http://PAservername.domain.com:9510

Under Authentication Mode when using TM1 you should point to the Window server where you have your TM1 instance using a specific port, that will be your TM1 application to control who will have access to the Administration tool.

TM1 Login Server URI=https://PAservername.domain.com:12545

(Note: that all new functions use the new HTTPport for access)

Click on validate button, to check the values you entered are working.

If you get an Error: Request timed out after 10010ms, you maybe  have entered the wrong port number.

Click UPDATE when you get the Validate to work.

The start of PAW will take some time, click on STATUS and then on REFRESH to see the progress.

When CPU usage is low like 1%, then it is ready and you can surf to the PAW (Planning Analytics Workspace).

Surf to http://PAwservername:9580/

Login with the user and password you have in your TM1 application.

In our test, click on a new book and expand and drag some view of the cube onto the canvas.

Click on Save icon up at the left side to save your designs.

 

Here some Error messages you may get when installing PAW

(The log files are found in folder d:\install\ipa_workspace_local_2.0.20.770.4\log\admintool)

Error:

Docker Machine is not installed. Please re-run Toolbox Installer and try again.

Solution:

Reboot your Windows server.

Error:

Creating CA: D:\vbox\certs\ca.pem

Creating client certificate: D:\vbox\certs\cert.pem

Running pre-create checks…

(paw) Image cache directory does not exist, creating it at D:\vbox\cache…

(paw) No default Boot2Docker ISO found locally, downloading the latest release…

(paw) Latest release for github.com/boot2docker/boot2docker is v17.05.0-ce

(paw) Downloading D:\vbox\cache\boot2docker.iso from https://github.com/boot2docker/boot2docker/releases/download/v17.05.0-ce/boot2docker.iso…

(paw)

Solution:

Good you had internet connection, so it could download the file.

Error:

Running pre-create checks…

Error with pre-create check: “This computer doesn’t have VT-X/AMD-v enabled. Enabling it in the BIOS is mandatory”

Solution:

Change the VMWARE host to support VTX.

Error:

Invalid command line. Found extra arguments [–virtualbox-no-share –virtualbox-hostonly-cidr 192.168.40.1/24 –virtualbox-memory 6144 –virtualbox-cpu-count 4 –virtualbox-disk-size 20000 paw]

Solution:

You have been changing the file \scripts\winstart.sh in attempt to get past the VTX issue.

Check that you have not missed a space.

Error:

Running pre-create checks…

(paw) Image cache directory does not exist, creating it at C:\machine\cache…

(paw) No default Boot2Docker ISO found locally, downloading the latest release…

Error with pre-create check: “Get https://api.github.com/repos/boot2docker/boot2docker/releases/latest: dial tcp: lookup api.github.com: getaddrinfow: No such host is known.”

Solution:

Place the file boot2docker.iso in correct folder, d:\vbox\cache

Try again to run the Start.bat file

 

TO SETUP PAW TO USE CAM

If not already started, run START.BAT, and select NO on update PAW, instead say YES to start the Admin configuration.

Here at the Configuration tab click on CAM button and fill in the values for the BI server.

IBM Cognos BI Gateway URI = http://CAservername.domain.com:9300/bi/v1/disp

IBM Cognos BI Dispatcher URI = http://CAservername.domain.com:9300/p2pd/servlet/dispatch

IBM Cognos BI Authentication Namespace ID = Exact the same Namespace ID you entered in Cognos Configuration for CA11 (this is case sensitive).

Click on validate and OK.

Go to status tab and click on the RESTART button to make the changes take effect.

 

Error you may see when working in PAW;

Error:
Cannot get the data.

Cannot create the session for server SDATA.

Solution:
The SDATA application use Native security and you have setup PAW to use CAM security.

Only use CAM security enabled TM1 applications with your PAW installation.

Error:
The server it temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.

Solution:
Wait or reboot the services.

SETUP TO RUN AS A SERVICE

Important to reboot the windows server before configuring PAW to be run as a service.

Rigth click on VBoxVmService-5.1-Plum.exe and select run as administrator.

Mark “I accept the agreement” and click next.

Click install.

Click finish.

Open the file d:\vms\VBoxVmService.ini in notepad.

Looks like this;

[Settings]

VBOX_USER_HOME=C:\Users\admin\.VirtualBox

RunWebService=no

PauseShutdown=5000

 

[Vm0]

VmName=ubuntu

ShutdownMethod=savestate

AutoStart=yes

 

[Vm1]

VmName=winxp

ShutdownMethod=savestate

AutoStart=no

 

Change it to point out your location for images that is d:\vbox\machines

Change it to handle the paw image and take away the last image.

Should look like this now

[Settings]

VBOX_USER_HOME=D:\VBOX\machines

RunWebService=no

PauseShutdown=5000

[Vm0]

VmName=paw

ShutdownMethod=acpipowerbutton

AutoStart=yes

Save the file.

Restart the server.

The log file will be written to d:\vms\VBoxVmService.log

Check the log file to ensure the service start up correct.

You must test reboot of the Windows server to find the best settings for this vbox service settings to work with PAW.

Example of Error you can get:

Error:
Callee RC  E_FAIL (0x80004005)

Solution:
You have too little memory free, the last shutdown of the vbox did not work.

Reboot the Windows server.

HOW TO BACKUP THE PAW

Run the START.BAT from a command prompt to get to a java prompt.

Enter scripts/paw.sh stop to stop the server

 

Enter scripts/backup.sh to stop paw services and make a backup and start them again

All the example scripts you can use, are in this folder, d:\install\ipa_workspace_local_2.0.20.770.4\scripts

Explore and create better scripts for your use.

The backup files are stored in a folder under d:\install\ipa_workspace_local_2.0.20.770.4\backup.

 

The TM1 application, can you backup with a bat file that contain this lines (you need to adjust the paths for your environment);

REM execute the backup command on data folder

“d:\program files\7-zip\7z” a d:\pal\planning\work\backup\tm1backup.zip -r d:\pal\planning\datafiles\*.*

TM1 reboot

Stop these WINDOWS services before you reboot your server with PA 2.0 Local

NET STOP VBOXVMSERVICE

NET STOP “IBM COGNOS”

NET STOP “IBM COGNOS TM1”

NET STOP SDATA

NET STOP PROVEN_TECHNIQUES

NET STOP PLANNING

NET STOP TM1ADMSDX64

 

When TM1 instance is down, you can also make a backup of the log files folder.

More information:

https://www.ibm.com/communities/analytics/planning-analytics/blog/

Note: in code you need to replace “ with ” to make it work.

How  install new PAW on new Windows version: https://www.youtube.com/watch?v=6REUFVQD-xA

Product:

Cognos Analytics 11.0.6

Information:

Cognos Analytics 11.0.6 adds support for Planning Analytics Local. Here are the new integration highlights in version 11.0.6.

Dashboard support for packages with TM1 and Planning Analytics cubes

As of version 11.0.6, you can make Cognos Analytics dashboards using packages from TM1 or Planning Analytics cubes. As always you create the packages in the Cognos Administration console or with Framework Manager. See Dashboard Enhancements in Cognos Analytics 11.0.6 for information on the OLAP support now available in dashboards.

REST connectivity to Planning Analytics

Cognos Analytics connects to TM1 data sources using TM1 client software which needs to be installed on the Cognos Analytics server. Cognos Analytics connects to Planning Analytics using the TM1 REST API which doesn’t require any additional software to be installed. You create a connection to Planning Analytics from the Cognos Administration console by selecting the IBM Planning Analytics data source connection type.

If you are upgrading from TM1 to Planning Analytics, within the Cognos Administration data source you can replace the TM1 connection with a Planning Analytics connection. Subsequently you need to re-publish any packages that refer to that data source, but no need to make any changes to the associated reports.

Support for Planning Analytics hierarchies

Sometimes referred to as “attribute hierarchies” and “named alternate hierarchies”, they are commonly known as simply “PA hierarchies” and are arguably the most important new TM1 server feature in Planning Analytics Local. Here’s a 3 min video on them.

Planning Analytics hierarchies appear and behave no differently than any other OLAP hierarchy in Cognos Analytics, but now you can have a TM1 dimension that has multiple hierarchies.

You need to use a Planning Analytics data source connection to see multiple TM1 hierarchies within a dimension; if you try to use a TM1 data source connection only the first or default hierarchy will appear within each dimension.

Support for localized Planning Analytics cubes

TM1 10.2.2 introduced the ability to localize objects in a cube without needing alias tables as documented here. This is supported in Cognos Analytics via a Planning Analytics REST connection only.

Cognos Analytics users can see a localized Planning Analytics cube in their language by either setting the Content Language in their user preferences or by setting the report language in the report properties. Note that you do not need to use the language settings that appear when creating a package for Planning Analytics cubes as those are for the legacy alias table localization functionality only.

Link to the CA 11 versions  http://www-01.ibm.com/support/docview.wss?uid=swg24043412

Above text from:

Cognos Analytics 11.0.6 support for Planning Analytics

 

Product:
Planning Analytics 2.0 local
Microsoft Windows 2016 server Version 10.9.14393

Problem:
Can I install PAW on Windows 2016 server with the native docker that come with Windows 2016?

Solution:
No. PAW does not support native docker on windows 2016. PAW in current state, need that you install the “docker toolbox” on your windows server.  The new version Planning Analytics Workspace 21 includes a native install for Windows Server 2016.
https://www-01.ibm.com/support/docview.wss?uid=swg24043782
https://community.watsonanalytics.com/discussions/questions/30105/does-planning-analytics-workspace-server-run-on-wi.html

More Information:
This is the steps to install the docker that is part of Microsoft Windows 2016. But this does not work with PA 2.0 Local.

Install Microsoft Windows 2016 server.
Ensure that Windows is connected to the internet.
Update the Windows 2016 server to latest fix pack version.
Start a power shell session as a administrator.
Right click on the power shell icon and select run as administrator.
Paste this line to install DOCKER
Install-Module -Name DockerMsftProvider -Force

Windows PowerShell
Copyright (C) 2016 Microsoft Corporation. All rights reserved.

PS C:\Windows\system32> Install-Module -Name DockerMsftProvider -Force

NuGet provider is required to continue
PowerShellGet requires NuGet provider version ‘2.8.5.201’ or newer to interact with NuGet-based repositories. The NuGet
provider must be available in ‘C:\Program Files\PackageManagement\ProviderAssemblies’ or
‘C:\Users\admin\AppData\Local\PackageManagement\ProviderAssemblies’. You can also install the NuGet provider by running
‘Install-PackageProvider -Name NuGet -MinimumVersion 2.8.5.201 -Force’. Do you want PowerShellGet to install and
import the NuGet provider now?
[Y] Yes [N] No [S] Suspend [?] Help (default is “Y”): y
WARNING: Unable to download from URI ‘https://go.microsoft.com/fwlink/?LinkID=627338&clcid=0x409’ to ”.
WARNING: Unable to download the list of available providers. Check your internet connection.
PackageManagement\Install-PackageProvider : No match was found for the specified search criteria for the provider ‘NuGe

You will be asked to update NUGET – above error happens when you do not have internet connection from your Windows 2016 server.
Ensure you have internet connection from your Windows server.

Run the command again in Power Shell:
Install-Module -Name DockerMsftProvider -Force

Then run this:
Install-Package -Name docker -ProviderName DockerMsftProvider -Force

This text will be the response:
WARNING: A restart is required to start docker service. Please restart you machine.
Name: Version: Source: Summary:
—-
Docker 17.03.1-ee DockerDefault Contains Docker EE for use with Windows Server 2016…

Restart the Windows server with this command in power shell:
Restart-Computer -Force

You will now have a windows service called Docker that is running. There will also be a new network adapter called vEthernet (HNS Internal NIC).

To test you can enter this in power shell:
docker run hello-world:nanoserver

It will start by download the container and then run it.

Give above if it works.

If you in CMD enter:
docker version
you will get the version like this
C:\Windows\system32>docker version
Client:
Version: 17.03.1-ee-3
API version: 1.27
Go version: go1.7.5
Git commit: 3fcee33
Built: Thu Mar 30 19:31:22 2017
OS/Arch: windows/amd64

Server:
Version: 17.03.1-ee-3
API version: 1.27 (minimum version 1.24)
Go version: go1.7.5
Git commit: 3fcee33
Built: Thu Mar 30 19:31:22 2017
OS/Arch: windows/amd64
Experimental: false

Here to download Docker Toolbox
https://www.docker.com/products/docker-toolbox?cm_mc_uid=80072513057014906872494&cm_mc_sid_50200000=1496826036

Here to understand Docker

https://store.docker.com/editions/enterprise/docker-ee-server-windows

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