Hi everyone, I realize this may be a fairly simple question, though I've never done anything like this before, so I'm unsure if this is expected behavior or not. I'm doing a test run installing the free evaluation version of rollbase on a private cloud and I've followed the installation guide in Chapter 18 of Rollbase in Action pretty much to the letter, except I have the tomcat server using port 80 instead of 8080 (there is no apache front-end). I've reached the "Finish Installation" section and started tomcat and everything works pretty much as excepted; I see tomcat at http://localhost/ and can log in to rollbase at http://localhost/router/login/login.jsp with no problems. However, when I try to access the application from a browser on another computer I am able to get to http://-ipaddress-/router/login/login.jsp but when I try to log in it simply says that the browser "cannot display the webpage". The shared file has these parameters: # Default host name HostName=localhost # URL of corp
Look into the components.xml in that same folder. It looks to me like it may have the answer you seek.
You pretty much answered the question already. External URLs are used for external access of Rollbase components. You cannot use "localhost" for these parameters if you plane to access the system from another computer.
The best solution: in shared.properties set your host name to your physical IP address. That would automatically update all External URLs. There should be no difference from which machine you loging.
It's OK to use "localhost" for Internal URLs if all components are on the same machine,
Yes of course. When I set the host name to the ip address I can log in fine from a different machine. However, when I then try to log onto the server locally through http://localhost/router/login/login.jsp it directs me to http://-ipaddress-/master/m/main.jsp?appId=2551&tabId=2530 (I figured out that I had to whitelist the server's own ip address for port 80, which is what caused my confusion beforehand, since it seems that is what blocked me from logging in).
I can log in now from the server, to http://-ipaddress-/master/m/main.jsp?appId=2551&tabId=2530, except some links and widgets do not work properly (setup and support tabs, log files in the master zone don't pop-up). Shouldn't log in be sending me to http://localhost/master/m/main.jsp?appId=2551&tabId=2530 or do I just need to whitelist more ports?
It is best to use consistent host name - IP address in your case.
Alright, thanks for the help.
Hi Mike,
To say it another way, Rollbase only supports external access from one host name and it is designed this way purposefully [I can explain why if this of interest, but this is a separate topic].
So this means if you set localhost as your HostName you can only access Rollbase with URLs of the form localhost. Similarly if you set an IP address as your HostName you can only access Rollbase with URLs that use that IP address.
Internal URLs that Pavel mentioned are used for a different purpose: for Rollbase components to communicate with each other when there is more than one server running Rollbase in your instance; these can use a different base URL than your HostName if needed because they are used to communicate with Rollbase components typically behind the firewall.
Hope this helps,
Matt