Well as the post name sais i'm trying to move from using the default internal database and run it independently of Jforum. I plan to use the accounts for other pages on my site.
Now i've gotten hsqldb to run with the JForum files no problem. I viewed the data with the the database manager swing. However I can't seem to find all the properties and configuration information to properly connect.
I've tried doing a search, but there was 300+ DB problems. And i'm not sure the exact term to use to narrow the search.
I'm not an HSQLDB expert but I think in order to use it across multiple applications you need to run it in one of it's server modes. I assume that's what you mean by external HSQLDB?
The default jforum access uses "In process mode" which can only be used by a single application.
Converting shouldn't be hard, just transfer the tables and data from the jForum Application DB to the HSQLDB server, and change the database.connection.string property to use the correct syntax. [originally posted on jforum.net by monroe]
" Now i've gotten hsqldb to run with the JForum files no problem. I viewed the data with the the database manager swing. However I can't seem to find all the properties and *configuration information to properly connect. "
The server mode was easy. it's the fact that jForum doesn't use it in server more that's the problem. It's already *configured for internal use. So it's not using it in server mode.
Any suggestions, I would greatly appreciate it. [originally posted on jforum.net by jaydryu]
You're making it harder than it is... the only application difference between using the server and the internal mode, is the JDBC URL. The HSQLDB driver is the same for both and it handles all the "magic".
The JDBC URL is set in your jforum-custom.conf file via the database.connection.string parameter. So the URL should change from something like:
Where database.connection.host and database.connection.dbname are defined by the properties setting in the config file.
Of course, you will also need the correct settings for the database.connection.username and database.connection.passwords properties as well. [originally posted on jforum.net by monroe]
We must storm this mad man's lab and destroy his villanous bomb! Are you with me tiny ad?