Hitachi Vantara Pentaho Community Forums
Results 1 to 3 of 3

Thread: Change the BA Server Fully Qualified URL in Release 5.2.0.0.209

  1. #1
    Join Date
    Feb 2013
    Posts
    3

    Default Change the BA Server Fully Qualified URL in Release 5.2.0.0.209

    Hi,

    I'm trying to redirect Pentaho BA Server 5.2 to my domain. So, I have changed the following:

    <context-param>
    <param-name>fully-qualified-server-url</param-name>
    <param-value>http://localhost:8080/pentaho/</param-value>
    </context-param>

    By this

    <context-param>
    <param-name>fully-qualified-server-url</param-name>
    <param-value>https://mydomain/pentaho/</param-value>
    </context-param>

    in the biserver-ce/tomcat/webapps/pentaho/WEB-INF/web.xml file.
    Then, I restart the BA Server. However, this doesn't go and when I log in Pentaho I'm redirected to http://localhost:8080/pentaho/index.jsp
    I tried with other params values (e.g. http://127.0.0.0:8080/pentaho/ , http://otherdomain/pentaho/, .....), but always I have the same result. I think that maybe Tomcat ignore this parameter and I don't know why it's happen.

    Can anyone help me?

    Thanks in advance,
    Roberto Tardío

  2. #2
    Join Date
    Feb 2013
    Posts
    3

    Default

    I have found a workaround to this issue. In file penjaho\biserver-ce\tomcat\webapps\pentaho\jsp\PUCLogin.jsp , I have modified the function

    function bounceToReturnLocation() {
    // pass
    var locale = document.login.locale.options[document.login.locale.selectedIndex].value;

    var returnLocation = '<%=ESAPI.encoder().encodeForJavaScript(requestedURL)%>';

    // Add this new line at this point for change http://localhost:8080 to https://mydomain.com

    returnLocation = returnLocation.replace("http://localhost:8080", "https://mydomain.com");

    Regards,
    Roberto

  3. #3
    Join Date
    Apr 2008
    Posts
    146

    Default

    There are a few things here that you are picking up on, but perhaps this little extra information helps. web.xml tells certain parts of Pentaho what constitutes the full base URL of the server. Think about content generators like Pentaho Reports (prpt) and CDE dashboards etc. Those things pick up the hint, including port number 8080 by default when a url is dynamically generated. The PUCLogin.jsp file is the login screen, and yes depending on successful authentication or a failure some kind of redirect has to happen. There is also one more place that is interesting to look at, and that is in tomcat/webapps/ROOT, where you'll find a file that redirects to tomcat/webapps/pentaho by default. That has the functionality of if someone just puts in http://mydomain:8080 and not /pentaho after it, that it will redirect over to http://mydomain:8080/pentaho. Then within the webapps/pentaho directory you'll see an index file that handles detecting if you're using a mobile browser etc and redirects eventually to PUCLogin.jsp.

    Knowing all the tie ups can let you go from login page to dashboard instead of to the Pentaho User Console. You might find things like that good for making a mobile ready version of Pentaho.

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Privacy Policy | Legal Notices | Safe Harbor Privacy Policy

Copyright © 2005 - 2019 Hitachi Vantara Corporation. All Rights Reserved.