Troubleshooting Connections to the Business Analytics Repository
The most common problem when the Business Analytics Server server does not restart successfully after you move the Business Analytics Repository to a new database is that is cannot connect to the Business Analytics Repository. To verify that this is the problem:
1. Open the Business Analytics Server log file prestoserver.log in your web application server’s log directory. For TomEE, this is:
web-apps-home/logs/prestoserver.log
2. Check for a log entry for Cannot create PoolableConnectionFactory near the end of the file. This error indicates the Business Analytics Server could not successfully connect to the new database.
Common causes for this error include:
The database hosting the
Business Analytics Repository is not running.
If this is true, start the Business Analytics Repository and verify that it is up. Then restart the Business Analytics Server and confirm that this starts successfully.
There are one or more firewalls between the
Business Analytics Repository and the
Business Analytics Server that are not configured to allow this connection.
Note: | This can only happen when the database for the Business Analytics Repository is hosted on a different server than the Business Analytics Server. |
Update the firewall configuration to allow this connection. Then restart the Business Analytics Server and confirm that this starts successfully.
The URL or other connection configuration that you entered in
Business Analytics for the
Business Analytics Repository is incorrect.
To correct an error in this case, edit the resource properties for the Business Analytics Repository in the MashZoneNG-install/apache-tomee-jaxrs/conf/tomee.xml file.
Then restart the Business Analytics Server and confirm that this starts successfully.
Port or connection configuration for the database is not set up properly to allow connections from the
Business Analytics Server. See documentation for your database for more information.
