Challenges while Upgrading your BA server (Pentaho 6.0 to 7.1)

- Pentaho

Missing jars

Issue:

  • After upgrade, there is a possibility of certain jars missing in upgraded Pentaho server.

Tracking:

  • Once the Pentaho is started navigate to $pentaho_home/tomcat/logs/catalina.out and check for error due to missing jar.

Solution:

  • Download the missing jars found in catalina.out and place it in specified paths.

Customization of login page does not work

Issue:

  • Customized login and logout page does not work after upgrade.

Tracking:

  • Check in the Pentaho home browser, if customized login page does not work, navigate to $PENTAHO_HOME/server/biserver-ee/tomcat/webapps/pentaho/WEB-INF. Open web.xml to confirm the old customized web.xml is replaced.

Solution:

  • Need to manually customize the web.xml again as replacing the older web.xml does not work. With older web.xml as a reference, customize the current web.xml. Once completed, save the file and reload the Pentaho home browser. The customized login page will work fine.

Xaction files after migration does not work

Issue:

  • Xaction files after migration does not work.

Tracking:

  • If a Xaction file does not work, navigate to $Pentaho_home/tomcat/logs/catalina.out. Check if error is because of file is unavailable or plugin issue.

Solution:

  • If the issue is because of file unavailability, open the XML file in text editor and check the path of file. Either replace the path in the XML file or upload the file in the specified path.
  • If Plugin missing is the issue, then download the missing plugin to Pentaho in the required path.

PRPT files after migration does not work.

Issue:

  • PRPT files after migration does not work.

Tracking:

  • If a PRPT file does not work, navigate to $Pentaho_home/tomcat/logs/catalina.out. Check the reason for the cause of error. PRPT file error are caused due to database connection issue or datatype format issue.

Solution:

If the error is due to database connection,

  • In the report designer open data – JDBC connection, change the database connection to correct database. The report will work fine.

If the error is due to format issue,

  • In the report designer change the format of data and replace the file in Pentaho. The report will work fine.

SAML authentication:

Issue:

  • SAML authentication does not work in Pentaho after upgrade.

Tracking:

  • Check if the pentaho works https server. Navigate to Pentaho and check if ssl certificate, keystore.jks are migrated. Navigate to  $Pentaho_home/server/biserver-ee/tomcat/conf folder and open server.xml to see if SSL configuration are activated.

Solution:

  • Generate a new keystore.jks file and a SSL certificate. Configure SAML authentication again.