DISABLE LOCAL TM1 PERSPECTIVES
-
- Posts: 3
- Joined: Mon Feb 20, 2012 4:11 pm
- OLAP Product: TM1
- Version: 9.5 9.5.2 10.2 PA 11.8
- Excel Version: 2003 2007 2010 2016
DISABLE LOCAL TM1 PERSPECTIVES
how do we disable a client's local perspective application. we are moving to PAFE and Paw. Don't want perspective clients to use their local perspectives but instead use pafe and paw connections. is there a way to disable perspectives on user's computer without manually uninstalling it? is there a config or file that can be removed to prevent client's from using perspectives?
- gtonkin
- MVP
- Posts: 1198
- Joined: Thu May 06, 2010 3:03 pm
- OLAP Product: TM1
- Version: Latest and greatest
- Excel Version: Office 365 64-bit
- Location: JHB, South Africa
- Contact:
Re: DISABLE LOCAL TM1 PERSPECTIVES
Could try set ClientVersionMaximum in the TM1s.cfg - obviously impacts everyone.
Possibly firewall the port the instance is linked to but allow the PAW server through. Cannot remember right now if you need it anyway as it should connect via the REST API
Possibly firewall the port the instance is linked to but allow the PAW server through. Cannot remember right now if you need it anyway as it should connect via the REST API
-
- Posts: 3
- Joined: Mon Feb 20, 2012 4:11 pm
- OLAP Product: TM1
- Version: 9.5 9.5.2 10.2 PA 11.8
- Excel Version: 2003 2007 2010 2016
Re: DISABLE LOCAL TM1 PERSPECTIVES
Thanks gtonkin. However, since the perspective version is the same as pafe, i'm not sure setting ClientVersionMaximum in config will work. But thank you for your response.
-
- Regular Participant
- Posts: 197
- Joined: Wed May 06, 2020 2:58 pm
- OLAP Product: Planning Analytics
- Version: 2.0.9
- Excel Version: 2016
Re: DISABLE LOCAL TM1 PERSPECTIVES
As gtonkin alluded to you can block access to legacy apps through the firewall block ports 5495 and 5498 for clients but allow access from the server running paw.
All legacy tools, architect, perspectives, performance modeler use these ports. The new client pax, however doesn't as this goes through paw so uses whatever port you have the pa-gateway (paw) using.
Once you've blocked the ports, users will no longer see the tm1 instance in architect/perspectives and so can't log in using those tools.
All legacy tools, architect, perspectives, performance modeler use these ports. The new client pax, however doesn't as this goes through paw so uses whatever port you have the pa-gateway (paw) using.
Once you've blocked the ports, users will no longer see the tm1 instance in architect/perspectives and so can't log in using those tools.