Does anyone have experience running TM1 and Planning analytics Workspace on the same server 2016 machine? We're experimenting with a new setup in azure and can't seem to get it to work like we are able to on our server 2008 environment with PAW running on a Linux virtual machine. The issue is that we can't seem to be able to find the correct URI's to get Workspace to be able to connect to TM1. On our 2008 environment, we are able to use localhost. IBM says this won't work in a server 2016 environment (can confirm it doesn't). Using the universal address of our sever that they are both running on doesn't seem to work either. They have some other IP's listed in support but nothing I can find on IBM's site seems to work.
Any insights here??
Thanks in advance.
TM1 and Planning Analytics Workspace on Same Server 2016 Machine
-
- Posts: 22
- Joined: Sun Mar 12, 2017 1:41 am
- OLAP Product: TM1
- Version: Planning Analytics 2.0.21, PAW
- Excel Version: Excel 2013
- Location: Los Angeles, Atlanta
Re: TM1 and Planning Analytics Workspace on Same Server 2016 Machine
Worked this one out. Ended up finding the internal IP that the containers were using and using that and things are all hooked up now.
-
- Posts: 40
- Joined: Tue Dec 21, 2010 12:43 am
- OLAP Product: Cognos Express
- Version: 10.2.1 FP3
- Excel Version: 2013
Re: TM1 and Planning Analytics Workspace on Same Server 2016 Machine
Hi codingCPA
I'm glad I found your post as I'm having the exact same issue with an installation of TM1 & PAW on the same MS Server 2016 vm.
I have all the sample TM1 servers installed on Planning Analytics 2.0.3, but only have the Planning Sample TM1 Server running, & using its HTTPPortNumber of 12354 for the Login Server URI.
The PAW IP is 172.22.171.138 & the gateway is 172.22.160.1, but when I try this in the PAW admin tool config, I get timeout errors. True IP of the vm is 192.168.75.74.
Does anyone have any idea where I'm going wrong?
Thanks in advance
Terri
I'm glad I found your post as I'm having the exact same issue with an installation of TM1 & PAW on the same MS Server 2016 vm.
I have all the sample TM1 servers installed on Planning Analytics 2.0.3, but only have the Planning Sample TM1 Server running, & using its HTTPPortNumber of 12354 for the Login Server URI.
The PAW IP is 172.22.171.138 & the gateway is 172.22.160.1, but when I try this in the PAW admin tool config, I get timeout errors. True IP of the vm is 192.168.75.74.
Does anyone have any idea where I'm going wrong?
Thanks in advance
Terri
-
- MVP
- Posts: 160
- Joined: Wed Aug 17, 2011 3:51 pm
- OLAP Product: TM1
- Version: 10.2.2
- Excel Version: Excel 2007
Re: TM1 and Planning Analytics Workspace on Same Server 2016 Machine
You may have to add firewall rules to permit it. Even communication on the same box can be blocked by the Windows firewall.
Try to temporarily disable it to see if that addresses the problem.
Try to temporarily disable it to see if that addresses the problem.
-
- Posts: 40
- Joined: Tue Dec 21, 2010 12:43 am
- OLAP Product: Cognos Express
- Version: 10.2.1 FP3
- Excel Version: 2013
Re: TM1 and Planning Analytics Workspace on Same Server 2016 Machine
Hi dr.nybble
Fantastic, thanks for that...it worked!
Cheers
Terri
Fantastic, thanks for that...it worked!
Cheers
Terri
-
- Posts: 11
- Joined: Tue Aug 20, 2013 6:28 am
- OLAP Product: TM1
- Version: 10.2.2
- Excel Version: Excel 2013
Re: TM1 and Planning Analytics Workspace on Same Server 2016 Machine
have you guys experienced any performance issues with them being on the same server?
-
- Posts: 72
- Joined: Wed Aug 15, 2018 3:18 pm
- OLAP Product: TM1
- Version: 10.3
- Excel Version: 2016
Re: TM1 and Planning Analytics Workspace on Same Server 2016 Machine
Hi,
I also received the same error. Anyone know how could i resolve this?
When i utilized FQDN in admin tool:
When i utilized PAW Gateway:
Please feel free if you require further information.
How to check whether internal port is blocked or not?
Thank You
Dharav
I also received the same error. Anyone know how could i resolve this?
When i utilized FQDN in admin tool:
When i utilized PAW Gateway:
Please feel free if you require further information.
How to check whether internal port is blocked or not?
Thank You
Dharav
- Attachments
-
- Error 3.PNG (49.81 KiB) Viewed 5928 times
-
- Error 2.PNG (50.28 KiB) Viewed 5928 times
-
- Posts: 72
- Joined: Wed Aug 15, 2018 3:18 pm
- OLAP Product: TM1
- Version: 10.3
- Excel Version: 2016
Re: TM1 and Planning Analytics Workspace on Same Server 2016 Machine
Hi, All
I found out the cause behind that error. As it was UAT server, i install Planning Analytics in non-production mode so that IBM Cognos TM1 services wont found and that was causing port 9510 to ping. I install to production type and admin tool got validated with HNS IP address.
Now when i am trying to execute PAW url http://abcd.de.webmd.net:9580 then i see blue authenticating screen then it throws error. While throwing the error URL changed to http://112.20.111.1:9300/bi/v1/disp. In cognos BI configuration window, external dispatcher configured with FQDN as follow:
http://abcd.de.webmd.net:9300/bi/v1/disp
It seems due to configuration of admin tool (where hns ip (112.20.111.1)address has been utilized instead of FQDN), PAW tries to authenticate on that url instead of FQDN url which is defined in the cognos configuration. How could we create a bridge so that HNS IP address url point to public ip adress?
Please Advise.
Thank You
Dharav
I found out the cause behind that error. As it was UAT server, i install Planning Analytics in non-production mode so that IBM Cognos TM1 services wont found and that was causing port 9510 to ping. I install to production type and admin tool got validated with HNS IP address.
Now when i am trying to execute PAW url http://abcd.de.webmd.net:9580 then i see blue authenticating screen then it throws error. While throwing the error URL changed to http://112.20.111.1:9300/bi/v1/disp. In cognos BI configuration window, external dispatcher configured with FQDN as follow:
http://abcd.de.webmd.net:9300/bi/v1/disp
It seems due to configuration of admin tool (where hns ip (112.20.111.1)address has been utilized instead of FQDN), PAW tries to authenticate on that url instead of FQDN url which is defined in the cognos configuration. How could we create a bridge so that HNS IP address url point to public ip adress?
Please Advise.
Thank You
Dharav