TM1Web works, Application Web doesn't over WAN

[Ogram]

I have a client who needs to test a TM1 PoC solution I made but we've run into some technical problems with him connecting over WAN to our server.

TM1Web works fine, he can log in and sees all the content there is on the TM1 POC server. Using the same address but replacing TM1web with PMPSVC he can see the application portal login. He's able to login and can see the applications but when he selects a workflow node, a new window pops up but instead of opening the application as one would expect, it only displays the standard 'Web page could not be displayed' error message.

I have added exceptions for both the TM1 server ports (server and client messages) and for the admin server - am I still missing something?

I have added the IPAddress-parameter to the tm1s.cfg-file with both the WAN and local IPs but to no avail.

Running the latest TM1 10.2.2.1.

[whitej_d]

There's a config file, whih cshould be somewhere like

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

In it there's a parameter <service forceQualifiedPaths="true">. If you change it to false, then reconfigure the admin part of Applications portal to point to the machine name, not the FQDN for all entries (TM1 servers and web client address) then it seems to behave itself much bettter, particularly if it's a POC on a machine which keeps changing networks and IP addresses.

I would be a little wary of doing this in production though as I don't believe it is documented anywhere by IBM.

[Ogram]

Thanks, I'll give it a try!

[Ogram]

I eventually managed to find the source of the problem. In Application Web settings (accessible through the portal) the Contributor client's address was still referring to an internal address. Changing this to the WAN ip of the host machine seems to have fixed the problem.