how to change the jboss schema name

[qbq]

Hi,

I'm following the Server Configuration documentation and came across:

We assume that you have already installed the external database server, and have it running. You should create an empty database named jboss, accessible via the username / password pair jbossuser / jbosspass. The jboss database is used to store JBoss AS internal data -- JBoss AS will automatically create tables and data in it.

Our DBA's standard is all caps and they created the database named slightly differently than above. Now before I requested a change on their side I was wondering if I could change this in the configuration somewhere to keep with their standards.

Thanks!

[peterj]

It would have helped if you provided contextual information on where that sentence was found. Since you did not, I will have to guess, so my answer is based on that guess.

I assume that you are configuring a database login module. You can use all uppercase names for the database, tables and columns. Then edit login module configuration within jboss-login.xml to use uppercase names in it's SQL statements (hmm, looks like the example one already does that). Then in the *-ds.xml file for the datasource use uppercase names in connection URL.

If my guess is incorrect, you can still use the above information to tackle your issue.

[qbq]

sorry, the documentation is from here: http://www.jboss.org/file-access/default/members/jbossas/freezone/docs/Administration_And_Configuration_Guide/5/html_single/index.html#d0e3980


Thanks for the response, I'll look into your suggestion.

[peterj]

If you are replacing HSQL with your database, and your DBAs require uppercase names, you are in for lots of fun. You'll have to find the SQL statements for Messaging and Quartz and convert them all to use uppercase. And I know I forgot a table or two...

But the *-ds.xml suggestion still holds.

[qbq]

thanks for the heads up, everything is all caps all the time...and the *-ds.xml suggestion looks good and I'm working on those changes now. I just had a moment of panic when the db was created.