TM1 Forum

Hi
Questions to those who were lucky (?) enough to install PA local.
I try to insatll it on my Win8.1 laptop, so Workspace is installed on a VirtualBox VM.
I use TM1 native authentication, Mode 1.

What IP addresses should I use int he administration tool? 192.168.40.1, or my laptop's IP address? And then the workspace login should be simply http://192.168.40.1?

I tried with both IPs, faced various issues, sometimes 2-3 different random issues even with the same config.

Thanks for any help!
Matyas

It seems 192.168.40.1 can be used, my last issue is with the Windows Firewall
Can someone please point me in the right direction about what kind of firewall changes should I do?
The login page comes up from my browser: http://192.168.40.1 , but the login itself fails; when I disable the firewall, it works fine

Thanks for any help!

You will need to set an exception within your firewall (assuming you don't want to have it turned off all the time); I think it was port 443 and 80.

Hi
I tried with creating a custom Inbound rule, any protocol, any ports, using 192.168.56.1 as local (host, Virtualbox Host-only network) and 192.168.40.1 as remote IP address (vm, Virtualbox Host-only network#2), but this did not work.

Maybe I should also make some changes on the VM itself?

I followed the first advise here:
http://serverfault.com/questions/225155 ... s-internet

Thanks!

From digging through the scripts, the admin tool uses port 8888. Also, by default, it is only accessible from localhost. To deal with this you enter
before running the Start.sh script.
We are using the 'Docker on a Linux VM' approach so there may be some differences vs the 'Docker in VirtualBox on Windows' option.

Hi David,

I think the line that you show:

This task applies to IBM Planning Analytics Workspace installed on a Linux OS only.

according to the install guide.
I can access the admin tool from my laptop's browser. I can also access the PAw login page under http://192.168.40.1 from my laptop's browser. It is the login that does not work and blocked by the firewall.

Thanks!

To clarify how the networking works... (and this is a great article for further detail: https://blogs.oracle.com/fatbloke/entry ... irtualbox1)

The paw VM has two network adapters. It has a NAT adapter and the VirtualBox Host-Only Adapter.

The NAT adapter lets the VM talk to the outside world via your host Windows computer. It also permits inbound connections from the host to the VM via port forwarding (80 and 443).

The VirtualBox Host-Only Adapter is primarily for Docker tooling to interact with the VM. The Windows host has the address 192.168.40.1 on this network while the VM has 192.168.40.100.

It is convenient to reference TM1 instances running on the host via 192.168.40.1 since that address won't change whereas the host might (DHCP, VPN, and so on).

During logon a Docker container is making a REST API call to the TM1 Server you have specified as the authentication provider. So it is making an inbound connection to whatever port you have configured on 192.168.40.1. You may want to unblock any inbound connections to 192.168.40.1, or if you want to be more fine-grained open up the specific port for the REST API you have configured (and also 5895/5898 for the TM1 Admin Server)

Hi,

Thanks for all of your input guys, after many hours spent (in previous versions these nr of hours were enough to install the sw + test all new features, not that only install the sw...) I managed to make it work, I share details here, maybe it will help others:

1. In the Admin Tool, I am using my computer name (which is not in a domain) in the config settings, and do not use SSL (http://ComputerName:Port)
2. I added a custom Inbound rule to my Firewall, 192.168.40.1 as local, 192.168.40.100 as remote (all ports and protocols for now)
3. I login to PAw or CAFE via http://192.168.40.100

IBM Documentation on all of these are as if I had written it

Thanks again for all your help!