Installation Trouble Shooting
From jVantage
Q: I tried to install jVantage on a fresh jboss 4.0.4 installation. jVantage setup procedure completes well and creates MySQL 44 tables, but when I try to access the login page I always obtain the follwing message: "An unrecoverable internal error has occurred. Please contact your system administrator for assistance."
Note: This issue has been corrected and will not surface on new downloads.
A: jVantage allows a URL to be defined that specifies the location of user interface (UI) themes. This allows themes to be created and hosted on the same server that hosts jVantage itself, or on a different host entirely.
On a typical installation, jVantage assumes that the UI themes are installed on the same server as itself. This means that the Template Server URL refers to the localhost as shown below.
Unfortunately, if this URL is incorrect it can render the jVantage development environment completely unavailable, since jVantage becomes unable to find a UI theme for its own use. This condition can be verified by the following entries in your Servlet_Main.log file, which can be found in the <jvantage-config-dir>/logs directory.
2006/09/26 00:09:29 INFO : SID(1111569) TRX(10000004) No such template
[http://localhost/jvtheme-jvantage/defaultviewrecord.html].
2006/09/26 00:09:29 ERROR: SID(1111569) TRX(10000004) The specified UI
template could not be found. Verify that the template exists in
UI Theme [jvtheme-jvantage], which is designated for this request.
For now, correcting this issue requires a manual update of the URL value directly in the database.
To correct the value, you must first determine what the correct value should be. By default, JBoss applications are available on port 8080. If this value has not been changed, jVantage will be accessible at http://<host-name>:8080/jvantage after installation. In this case, the Template Server URL should be http://<host-name>:8080. If the default JBoss port has been changed to 80, then the port number is not required on the URL at all, since in the absence of an explicit port, 80 is assumed, meaning the URL would be http://<host-name>.
Note that in most cases the hostname can be localhost. The only requirement is that localhost must be resolvable by the server hosting jVantage.
A good way of verifying the Template Server URL prior to updating the database is to enter the following URL on the server where jVantage has been installed: http://<host-name>:<port>/jvtheme-jvantage/about.html. For instance, on our development server, the URL looks like this, since we do use port 80: http://abt01/jvtheme-jvantage/about.html. When you enter this URL (with substituted host and port), you should see a screen similar to the following:
Once you are able to see this screen, the Template Server URL will be equal to the protocol, host and port (if applicable). Which means, that given our test URL of http://abt01/jvtheme-jvantage/about.html, our Template Server URL will equal http://abt01.
To update the value in the database, perform the following using the command-line mysql application or a graphical database client.
# mysql mysql> use jvantage Reading table information for completion of table and column names You can turn off this feature to get a quicker startup with -A Database changed mysql> UPDATE ROOTCONTEXT SET TEMPLATEURL = 'http://localhost:8080'; Query OK, 0 rows affected (0.00 sec) Rows matched: 1 Changed: 0 Warnings: 0 mysql> quit Bye #
Once these steps are complete, restart the JBoss application server.
Q: I checked Enable SSL on the Root Context and now jVantage won't let me back in.
A: Be aware that before updating the jVantage Root Context to Enable SSL, your application server must already be configured to support SSL. If it is not, then jVantage may become inaccessible, since it will immediately attempt to use SSL for all logins. To correct this, you must uncheck the Enable SSL field directly in the database, by performing the following steps.
# mysql mysql> use jvantage Reading table information for completion of table and column names You can turn off this feature to get a quicker startup with -A Database changed mysql> UPDATE ROOTCONTEXT SET ENABLESSL = 'No'; Query OK, 0 rows affected (0.00 sec) Rows matched: 1 Changed: 0 Warnings: 0 mysql> quit Bye #
