[jboss-cvs] jboss-docs/adminguide/docbook/en/modules ...
Sam Griffith
sam.griffith at jboss.com
Mon Mar 26 12:12:02 EDT 2007
User: sgriffith
Date: 07/03/26 12:12:02
Modified: adminguide/docbook/en/modules appendix-alternative_DBs.xml
Log:
Cleaned up more of the code to get it to show in the boxes correctly. Fixed CDATA tags.
Revision Changes Path
1.7 +280 -269 jboss-docs/adminguide/docbook/en/modules/appendix-alternative_DBs.xml
(In the diff below, changes in quantity of whitespace are not shown.)
Index: appendix-alternative_DBs.xml
===================================================================
RCS file: /cvsroot/jboss/jboss-docs/adminguide/docbook/en/modules/appendix-alternative_DBs.xml,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -b -r1.6 -r1.7
--- appendix-alternative_DBs.xml 26 Mar 2007 15:14:04 -0000 1.6
+++ appendix-alternative_DBs.xml 26 Mar 2007 16:12:02 -0000 1.7
@@ -18,59 +18,59 @@
<para>
MySQL is interacted with and administered by using the <literal>mysql</literal> command. On Mac OS X it is found in <literal>/usr/local/mysql/bin/mysql</literal>. To work with the <literal>mysql</literal> client you will most likely want to do it as a root user. To do so, use the<literal>-u</literal> or <literal>-user</literal> option. This allows you to specify the user name used when connecting to the database.
<programlisting>
- $ mysql -u root
- Welcome to the MySQL monitor. Commands end with ; or \g.
- Your MySQL connection id is 4 to server version: 5.0.27-standard
+$ mysql -u root
+Welcome to the MySQL monitor. Commands end with ; or \g.
+Your MySQL connection id is 4 to server version: 5.0.27-standard
- Type 'help;' or '\h' for help. Type '\c' to clear the buffer.
+Type 'help;' or '\h' for help. Type '\c' to clear the buffer.
- mysql>
+mysql>
</programlisting>
</para>
<para>
After you've logged into MySQL you'll need to create a database with the name <literal>jboss</literal>. To do so, use the <literal>create database</literal> command like so:
<programlisting>
- mysql> create database jboss;
- Query OK, 1 row affected (0.01 sec)
+mysql> create database jboss;
+Query OK, 1 row affected (0.01 sec)
</programlisting>
</para>
<para>
Now that you've created a database we need to create a user for it so that we don't have to be root to access it. To do so, use the <literal>grant</literal> command like so:
<programlisting>
- mysql> grant all privileges on jboss.* to sam at localhost identified by 'password';
- Query OK, 0 rows affected (0.00 sec)
+mysql> grant all privileges on jboss.* to sam at localhost identified by 'password';
+Query OK, 0 rows affected (0.00 sec)
</programlisting>
With that grant command we created a user <literal>sam</literal> with a password <literal>password</literal>. User <literal>sam</literal> has access to everything in the <literal>jboss</literal> database.
</para>
<para>
We can look at the MySQL user table to see that <literal>sam</literal> has been added.
<programlisting>
- mysql> select user, host, password from mysql.user;
- +------+-------------------+-------------------------------------------+
- | user | host | password |
- +------+-------------------+-------------------------------------------+
- | root | localhost | |
- | root | sam-griffiths.sme | |
- | | sam-griffiths.sme | |
- | | localhost | |
- | sam | localhost | *2470C0C06DEE42FD1618BB99005ADCA2EC9D1E19 |
- +------+-------------------+-------------------------------------------+
- 5 rows in set (0.01 sec)
+mysql> select user, host, password from mysql.user;
++------+-------------------+-------------------------------------------+
+| user | host | password |
++------+-------------------+-------------------------------------------+
+| root | localhost | |
+| root | sam-griffiths.sme | |
+| | sam-griffiths.sme | |
+| | localhost | |
+| sam | localhost | *2470C0C06DEE42FD1618BB99005ADCA2EC9D1E19 |
++------+-------------------+-------------------------------------------+
+5 rows in set (0.01 sec)
</programlisting>
We can now login to the database as <literal>sam</literal> instead of <literal>root</literal>. Let's see that work. Make sure if your still logged into the MySQL client, that you exit by typing in <literal>exit</literal> at the MySQL prompt like so:
<programlisting>
- mysql> exit
- Bye
+mysql> exit
+Bye
</programlisting>
Now you can login as the new user you created (in our case <literal>sam</literal>), like so:
<programlisting>
- $ mysql -u sam --password=password
- Welcome to the MySQL monitor. Commands end with ; or \g.
- Your MySQL connection id is 8 to server version: 5.0.27-standard
+$ mysql -u sam --password=password
+Welcome to the MySQL monitor. Commands end with ; or \g.
+Your MySQL connection id is 8 to server version: 5.0.27-standard
- Type 'help;' or '\h' for help. Type '\c' to clear the buffer.
+Type 'help;' or '\h' for help. Type '\c' to clear the buffer.
- mysql>
+mysql>
</programlisting>
One thing to note is that we did not create our user with remote access permissions, so if you try to login from a remote machine to mysql with user <literal>sam</literal>, you will not be able too. See the MySQL documentation for further information on creating users with remote users.
</para>
@@ -87,124 +87,129 @@
<para>
How can we tell if JBoss found that new MySQL driver? The quickest way is to look at our JMX console to see check which JDBC driver is loaded. Open your browser and go to: <literal>http://localhost:8080/jmx-console</literal>. Towards the top of the page you'll see the JMImplementation domain. Choose the <literal>name=Default,service=LoaderRepository</literal> MBean. On the screen for the LoaderRepository MBean you'll see a MBean operation for <literal>displayClassInfo()</literal>. In it's parameterValue text field put in <literal> com.mysql.jdbc.Driver</literal> and click the "Invoke" button. you should see something like this:
<programlisting>
- com.mysql.jdbc.Driver Information
- Not loaded in repository cache
+com.mysql.jdbc.Driver Information
+Not loaded in repository cache
- ### Instance0 found in UCL:
+### Instance0 found in UCL:
org.jboss.mx.loading.UnifiedClassLoader3 at 592141{ url=null ,addedOrder=2}
</programlisting>
While we haven't used the instance yet which would have caused the class to be loaded into the repository cache, we do have an instance, so JBoss knows about the driver and can see it. If we had used the class already we'd get much more information and it would look like this:
<programlisting>
- com.mysql.jdbc.Driver Information
- Repository cache version:
- com.mysql.jdbc.Driver(634bac).ClassLoader=
- org.jboss.mx.loading.UnifiedClassLoader3 at 3fa2d5{ url=null ,addedOrder=2}
- ..org.jboss.mx.loading.UnifiedClassLoader3 at 3fa2d5{ url=null ,addedOrder=2}
- ....file:/Users/sgriffith/jboss-4.2.0.CR1/server/default/lib/.DS_Store
- ....file:/Users/sgriffith/jboss-4.2.0.CR1/server/default/lib/activation.jar
- ....file:/Users/sgriffith/jboss-4.2.0.CR1/server/default/lib/antlr.jar
- ....file:/Users/sgriffith/jboss-4.2.0.CR1/server/default/lib/autonumber-plugin.jar
- ....file:/Users/sgriffith/jboss-4.2.0.CR1/server/default/lib/bcel.jar
- ....file:/Users/sgriffith/jboss-4.2.0.CR1/server/default/lib/bindingservice-plugin.jar
- ....file:/Users/sgriffith/jboss-4.2.0.CR1/server/default/lib/bsf.jar
- ....file:/Users/sgriffith/jboss-4.2.0.CR1/server/default/lib/bsh-deployer.jar
- ....file:/Users/sgriffith/jboss-4.2.0.CR1/server/default/lib/bsh.jar
- ....file:/Users/sgriffith/jboss-4.2.0.CR1/server/default/lib/cglib.jar
- ....file:/Users/sgriffith/jboss-4.2.0.CR1/server/default/lib/commons-codec.jar
- ....file:/Users/sgriffith/jboss-4.2.0.CR1/server/default/lib/commons-collections.jar
- ....file:/Users/sgriffith/jboss-4.2.0.CR1/server/default/lib/commons-httpclient.jar
- ....file:/Users/sgriffith/jboss-4.2.0.CR1/server/default/lib/commons-logging.jar
- ....file:/Users/sgriffith/jboss-4.2.0.CR1/server/default/lib/dom4j.jar
- ....file:/Users/sgriffith/jboss-4.2.0.CR1/server/default/lib/hibernate3.jar
- ....file:/Users/sgriffith/jboss-4.2.0.CR1/server/default/lib/hsqldb-plugin.jar
- ....file:/Users/sgriffith/jboss-4.2.0.CR1/server/default/lib/hsqldb.jar
- ....file:/Users/sgriffith/jboss-4.2.0.CR1/server/default/lib/javassist.jar
- ....file:/Users/sgriffith/jboss-4.2.0.CR1/server/default/lib/javax.el.jar
- ....file:/Users/sgriffith/jboss-4.2.0.CR1/server/default/lib/javax.servlet.jar
- ....file:/Users/sgriffith/jboss-4.2.0.CR1/server/default/lib/javax.servlet.jsp.jar
- ....file:/Users/sgriffith/jboss-4.2.0.CR1/server/default/lib/jaxen.jar
- ....file:/Users/sgriffith/jboss-4.2.0.CR1/server/default/lib/jboss-backport-concurrent.jar
- ....file:/Users/sgriffith/jboss-4.2.0.CR1/server/default/lib/jboss-common-jdbc-wrapper.jar
- ....file:/Users/sgriffith/jboss-4.2.0.CR1/server/default/lib/jboss-hibernate.jar
- ....file:/Users/sgriffith/jboss-4.2.0.CR1/server/default/lib/jboss-j2ee.jar
- ....file:/Users/sgriffith/jboss-4.2.0.CR1/server/default/lib/jboss-jaxrpc.jar
- ....file:/Users/sgriffith/jboss-4.2.0.CR1/server/default/lib/jboss-jca.jar
- ....file:/Users/sgriffith/jboss-4.2.0.CR1/server/default/lib/jboss-jsr77.jar
- ....file:/Users/sgriffith/jboss-4.2.0.CR1/server/default/lib/jboss-jsr88.jar
- ....file:/Users/sgriffith/jboss-4.2.0.CR1/server/default/lib/jboss-management.jar
- ....file:/Users/sgriffith/jboss-4.2.0.CR1/server/default/lib/jboss-monitoring.jar
- ....file:/Users/sgriffith/jboss-4.2.0.CR1/server/default/lib/jboss-remoting-int.jar
- ....file:/Users/sgriffith/jboss-4.2.0.CR1/server/default/lib/jboss-remoting.jar
- ....file:/Users/sgriffith/jboss-4.2.0.CR1/server/default/lib/jboss-saaj.jar
- ....file:/Users/sgriffith/jboss-4.2.0.CR1/server/default/lib/jboss-serialization.jar
- ....file:/Users/sgriffith/jboss-4.2.0.CR1/server/default/lib/jboss-srp.jar
- ....file:/Users/sgriffith/jboss-4.2.0.CR1/server/default/lib/jboss-transaction.jar
- ....file:/Users/sgriffith/jboss-4.2.0.CR1/server/default/lib/jboss.jar
- ....file:/Users/sgriffith/jboss-4.2.0.CR1/server/default/lib/jbossjta-integration.jar
- ....file:/Users/sgriffith/jboss-4.2.0.CR1/server/default/lib/jbossjta.jar
- ....file:/Users/sgriffith/jboss-4.2.0.CR1/server/default/lib/jbossmq.jar
- ....file:/Users/sgriffith/jboss-4.2.0.CR1/server/default/lib/jbossretro-rt.jar
- ....file:/Users/sgriffith/jboss-4.2.0.CR1/server/default/lib/jbosssx.jar
- ....file:/Users/sgriffith/jboss-4.2.0.CR1/server/default/lib/jbossts-common.jar
- ....file:/Users/sgriffith/jboss-4.2.0.CR1/server/default/lib/jmx-adaptor-plugin.jar
- ....file:/Users/sgriffith/jboss-4.2.0.CR1/server/default/lib/jnpserver.jar
- ....file:/Users/sgriffith/jboss-4.2.0.CR1/server/default/lib/joesnmp.jar
- ....file:/Users/sgriffith/jboss-4.2.0.CR1/server/default/lib/jpl-pattern.jar
- ....file:/Users/sgriffith/jboss-4.2.0.CR1/server/default/lib/jpl-util.jar
- ....file:/Users/sgriffith/jboss-4.2.0.CR1/server/default/lib/log4j-snmp-appender.jar
- ....file:/Users/sgriffith/jboss-4.2.0.CR1/server/default/lib/log4j.jar
- ....file:/Users/sgriffith/jboss-4.2.0.CR1/server/default/lib/mail-plugin.jar
- ....file:/Users/sgriffith/jboss-4.2.0.CR1/server/default/lib/mail.jar
- ....file:/Users/sgriffith/jboss-4.2.0.CR1/server/default/lib/mysql-connector-java-5.0.4-bin.jar
- ....file:/Users/sgriffith/jboss-4.2.0.CR1/server/default/lib/properties-plugin.jar
- ....file:/Users/sgriffith/jboss-4.2.0.CR1/server/default/lib/scheduler-plugin-example.jar
- ....file:/Users/sgriffith/jboss-4.2.0.CR1/server/default/lib/scheduler-plugin.jar
- ....file:/Users/sgriffith/jboss-4.2.0.CR1/server/default/lib/wsdl4j.jar
- ....file:/Users/sgriffith/jboss-4.2.0.CR1/server/default/lib/xmlentitymgr.jar
- ..org.jboss.system.server.NoAnnotationURLClassLoader at 7471e0
- ..sun.misc.Launcher$AppClassLoader at e39a3e
- ....file:/Users/sgriffith/jboss-4.2.0.CR1/bin/run.jar
- ....file:/lib/tools.jar
- ....file:/System/Library/Frameworks/JavaVM.framework/
- Versions/1.5.0/Classes/.compatibility/14compatibility.jar
- ..sun.misc.Launcher$ExtClassLoader at 92e78c
- ....file:/Library/Java/Extensions/.DS_Store
- ....file:/Library/Java/Extensions/junit-4.1.jar
- ....file:/usr/local/lib/libsvnjavahl-1.0.0.0.dylib
- ....file:/Library/Java/Extensions/OpenBaseJDBC.jar
- ....file:/System/Library/Java/Extensions/CoreAudio.jar
- ....file:/System/Library/Java/Extensions/dns_sd.jar
- ....file:/System/Library/Java/Extensions/j3daudio.jar
- ....file:/System/Library/Java/Extensions/j3dcore.jar
- ....file:/System/Library/Java/Extensions/j3dutils.jar
- ....file:/System/Library/Java/Extensions/jai_codec.jar
- ....file:/System/Library/Java/Extensions/jai_core.jar
- ....file:/System/Library/Java/Extensions/libJ3D.jnilib
- ....file:/System/Library/Java/Extensions/libJ3DAudio.jnilib
- ....file:/System/Library/Java/Extensions/libJ3DUtils.jnilib
- ....file:/System/Library/Java/Extensions/libmlib_jai.jnilib
- ....file:/System/Library/Java/Extensions/mlibwrapper_jai.jar
- ....file:/System/Library/Java/Extensions/MRJToolkit.jar
- ....file:/System/Library/Java/Extensions/QTJava.zip
- ....file:/System/Library/Java/Extensions/QTJSupport.jar
- ....file:/System/Library/Java/Extensions/vecmath.jar
- ....file:/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/lib/ext/
- apple_provider.jar
- ....file:/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/lib/ext/dnsns.jar
- ....file:/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/lib/ext/localedata.jar
- ....file:/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/lib/ext/
- sunjce_provider.jar
- ....file:/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/lib/ext/sunpkcs11.jar
- ++++CodeSource: (file:/Users/sgriffith/jboss-4.2.0.CR1/server/default/lib/
- mysql-connector-java-5.0.4-bin.jar )
- Implemented Interfaces:
- ++interface java.sql.Driver(e86394)
- ++++ClassLoader: null
- ++++Null CodeSource
+com.mysql.jdbc.Driver Information
+Repository cache version:
+com.mysql.jdbc.Driver(634bac).ClassLoader=
+org.jboss.mx.loading.UnifiedClassLoader3 at 3fa2d5{ url=null ,addedOrder=2}
+..org.jboss.mx.loading.UnifiedClassLoader3 at 3fa2d5{ url=null ,addedOrder=2}
+....file:/Users/sgriffith/jboss-4.2.0.CR1/server/default/lib/.DS_Store
+....file:/Users/sgriffith/jboss-4.2.0.CR1/server/default/lib/activation.jar
+....file:/Users/sgriffith/jboss-4.2.0.CR1/server/default/lib/antlr.jar
+....file:/Users/sgriffith/jboss-4.2.0.CR1/server/default/lib/autonumber-plugin.jar
+....file:/Users/sgriffith/jboss-4.2.0.CR1/server/default/lib/bcel.jar
+....file:/Users/sgriffith/jboss-4.2.0.CR1/server/default/lib/bindingservice-plugin.jar
+....file:/Users/sgriffith/jboss-4.2.0.CR1/server/default/lib/bsf.jar
+....file:/Users/sgriffith/jboss-4.2.0.CR1/server/default/lib/bsh-deployer.jar
+....file:/Users/sgriffith/jboss-4.2.0.CR1/server/default/lib/bsh.jar
+....file:/Users/sgriffith/jboss-4.2.0.CR1/server/default/lib/cglib.jar
+....file:/Users/sgriffith/jboss-4.2.0.CR1/server/default/lib/commons-codec.jar
+....file:/Users/sgriffith/jboss-4.2.0.CR1/server/default/lib/commons-collections.jar
+....file:/Users/sgriffith/jboss-4.2.0.CR1/server/default/lib/commons-httpclient.jar
+....file:/Users/sgriffith/jboss-4.2.0.CR1/server/default/lib/commons-logging.jar
+....file:/Users/sgriffith/jboss-4.2.0.CR1/server/default/lib/dom4j.jar
+....file:/Users/sgriffith/jboss-4.2.0.CR1/server/default/lib/hibernate3.jar
+....file:/Users/sgriffith/jboss-4.2.0.CR1/server/default/lib/hsqldb-plugin.jar
+....file:/Users/sgriffith/jboss-4.2.0.CR1/server/default/lib/hsqldb.jar
+....file:/Users/sgriffith/jboss-4.2.0.CR1/server/default/lib/javassist.jar
+....file:/Users/sgriffith/jboss-4.2.0.CR1/server/default/lib/javax.el.jar
+....file:/Users/sgriffith/jboss-4.2.0.CR1/server/default/lib/javax.servlet.jar
+....file:/Users/sgriffith/jboss-4.2.0.CR1/server/default/lib/javax.servlet.jsp.jar
+....file:/Users/sgriffith/jboss-4.2.0.CR1/server/default/lib/jaxen.jar
+....file:/Users/sgriffith/jboss-4.2.0.CR1/server/default/lib/jboss-backport-concurrent.jar
+....file:/Users/sgriffith/jboss-4.2.0.CR1/server/default/lib/jboss-common-jdbc-wrapper.jar
+....file:/Users/sgriffith/jboss-4.2.0.CR1/server/default/lib/jboss-hibernate.jar
+....file:/Users/sgriffith/jboss-4.2.0.CR1/server/default/lib/jboss-j2ee.jar
+....file:/Users/sgriffith/jboss-4.2.0.CR1/server/default/lib/jboss-jaxrpc.jar
+....file:/Users/sgriffith/jboss-4.2.0.CR1/server/default/lib/jboss-jca.jar
+....file:/Users/sgriffith/jboss-4.2.0.CR1/server/default/lib/jboss-jsr77.jar
+....file:/Users/sgriffith/jboss-4.2.0.CR1/server/default/lib/jboss-jsr88.jar
+....file:/Users/sgriffith/jboss-4.2.0.CR1/server/default/lib/jboss-management.jar
+....file:/Users/sgriffith/jboss-4.2.0.CR1/server/default/lib/jboss-monitoring.jar
+....file:/Users/sgriffith/jboss-4.2.0.CR1/server/default/lib/jboss-remoting-int.jar
+....file:/Users/sgriffith/jboss-4.2.0.CR1/server/default/lib/jboss-remoting.jar
+....file:/Users/sgriffith/jboss-4.2.0.CR1/server/default/lib/jboss-saaj.jar
+....file:/Users/sgriffith/jboss-4.2.0.CR1/server/default/lib/jboss-serialization.jar
+....file:/Users/sgriffith/jboss-4.2.0.CR1/server/default/lib/jboss-srp.jar
+....file:/Users/sgriffith/jboss-4.2.0.CR1/server/default/lib/jboss-transaction.jar
+....file:/Users/sgriffith/jboss-4.2.0.CR1/server/default/lib/jboss.jar
+....file:/Users/sgriffith/jboss-4.2.0.CR1/server/default/lib/jbossjta-integration.jar
+....file:/Users/sgriffith/jboss-4.2.0.CR1/server/default/lib/jbossjta.jar
+....file:/Users/sgriffith/jboss-4.2.0.CR1/server/default/lib/jbossmq.jar
+....file:/Users/sgriffith/jboss-4.2.0.CR1/server/default/lib/jbossretro-rt.jar
+....file:/Users/sgriffith/jboss-4.2.0.CR1/server/default/lib/jbosssx.jar
+....file:/Users/sgriffith/jboss-4.2.0.CR1/server/default/lib/jbossts-common.jar
+....file:/Users/sgriffith/jboss-4.2.0.CR1/server/default/lib/jmx-adaptor-plugin.jar
+....file:/Users/sgriffith/jboss-4.2.0.CR1/server/default/lib/jnpserver.jar
+....file:/Users/sgriffith/jboss-4.2.0.CR1/server/default/lib/joesnmp.jar
+....file:/Users/sgriffith/jboss-4.2.0.CR1/server/default/lib/jpl-pattern.jar
+....file:/Users/sgriffith/jboss-4.2.0.CR1/server/default/lib/jpl-util.jar
+....file:/Users/sgriffith/jboss-4.2.0.CR1/server/default/lib/log4j-snmp-appender.jar
+....file:/Users/sgriffith/jboss-4.2.0.CR1/server/default/lib/log4j.jar
+....file:/Users/sgriffith/jboss-4.2.0.CR1/server/default/lib/mail-plugin.jar
+....file:/Users/sgriffith/jboss-4.2.0.CR1/server/default/lib/mail.jar
+....file:/Users/sgriffith/jboss-4.2.0.CR1/server/default/lib/mysql-connector
+-java-5.0.4-bin.jar
+....file:/Users/sgriffith/jboss-4.2.0.CR1/server/default/lib/properties-plugin.jar
+....file:/Users/sgriffith/jboss-4.2.0.CR1/server/default/lib/scheduler-
+plugin-example.jar
+....file:/Users/sgriffith/jboss-4.2.0.CR1/server/default/lib/scheduler-plugin.jar
+....file:/Users/sgriffith/jboss-4.2.0.CR1/server/default/lib/wsdl4j.jar
+....file:/Users/sgriffith/jboss-4.2.0.CR1/server/default/lib/xmlentitymgr.jar
+..org.jboss.system.server.NoAnnotationURLClassLoader at 7471e0
+..sun.misc.Launcher$AppClassLoader at e39a3e
+....file:/Users/sgriffith/jboss-4.2.0.CR1/bin/run.jar
+....file:/lib/tools.jar
+....file:/System/Library/Frameworks/JavaVM.framework/
+Versions/1.5.0/Classes/.compatibility/14compatibility.jar
+..sun.misc.Launcher$ExtClassLoader at 92e78c
+....file:/Library/Java/Extensions/.DS_Store
+....file:/Library/Java/Extensions/junit-4.1.jar
+....file:/usr/local/lib/libsvnjavahl-1.0.0.0.dylib
+....file:/Library/Java/Extensions/OpenBaseJDBC.jar
+....file:/System/Library/Java/Extensions/CoreAudio.jar
+....file:/System/Library/Java/Extensions/dns_sd.jar
+....file:/System/Library/Java/Extensions/j3daudio.jar
+....file:/System/Library/Java/Extensions/j3dcore.jar
+....file:/System/Library/Java/Extensions/j3dutils.jar
+....file:/System/Library/Java/Extensions/jai_codec.jar
+....file:/System/Library/Java/Extensions/jai_core.jar
+....file:/System/Library/Java/Extensions/libJ3D.jnilib
+....file:/System/Library/Java/Extensions/libJ3DAudio.jnilib
+....file:/System/Library/Java/Extensions/libJ3DUtils.jnilib
+....file:/System/Library/Java/Extensions/libmlib_jai.jnilib
+....file:/System/Library/Java/Extensions/mlibwrapper_jai.jar
+....file:/System/Library/Java/Extensions/MRJToolkit.jar
+....file:/System/Library/Java/Extensions/QTJava.zip
+....file:/System/Library/Java/Extensions/QTJSupport.jar
+....file:/System/Library/Java/Extensions/vecmath.jar
+....file:/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/lib/ext/
+apple_provider.jar
+....file:/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/lib
+/ext/dnsns.jar
+....file:/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/lib
+/ext/localedata.jar
+....file:/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/lib/ext
+/sunjce_provider.jar
+....file:/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/lib
+/ext/sunpkcs11.jar
+++++CodeSource: (file:/Users/sgriffith/jboss-4.2.0.CR1/server/default/lib/
+mysql-connector-java-5.0.4-bin.jar )
+Implemented Interfaces:
+++interface java.sql.Driver(e86394)
+++++ClassLoader: null
+++++Null CodeSource
- ### Instance0 found in UCL:
- org.jboss.mx.loading.UnifiedClassLoader3 at 3fa2d5{ url=null ,addedOrder=2}
+### Instance0 found in UCL:
+org.jboss.mx.loading.UnifiedClassLoader3 at 3fa2d5{ url=null ,addedOrder=2}
</programlisting>
</para>
</section>
@@ -219,23 +224,27 @@
<para>
A MySQL datasource definition can be found in <literal>jboss-4.2.0.CR1/docs/examples/jca</literal>. If you look in there you'll find a file called <literal>mysql-ds.xml</literal>. It looks like this:
<programlisting>
- <![CDATA[
- <datasources>
+<![CDATA[
+<datasources>
<local-tx-datasource>
<jndi-name>MySqlDS</jndi-name>
<connection-url>jdbc:mysql://mysql-hostname:3306/jbossdb</connection-url>
<driver-class>com.mysql.jdbc.Driver</driver-class>
<user-name>x</user-name>
<password>y</password>
- <exception-sorter-class-name>org.jboss.resource.adapter.jdbc.vendor.MySQLExceptionSorter</exception-sorter-class-name>
+ <exception-sorter-class-name>
+ org.jboss.resource.adapter.jdbc.vendor.MySQLExceptionSorter
+ </exception-sorter-class-name>
<!-- should only be used on drivers after 3.22.1 with "ping" support
- <valid-connection-checker-class-name>org.jboss.resource.adapter.jdbc.vendor.MySQLValidConnectionChecker</valid-connection-checker-class-name>
+ <valid-connection-checker-class-name>
+ org.jboss.resource.adapter.jdbc.vendor.MySQLValidConnectionChecker
+ </valid-connection-checker-class-name>
-->
<!-- sql to call when connection is created
<new-connection-sql>some arbitrary sql</new-connection-sql>
-->
- <!-- sql to call on an existing pooled connection when it is obtained from pool - MySQLValidConnectionChecker is preferred for
- newer drivers
+ <!-- sql to call on an existing pooled connection when it is obtained from
+ pool - MySQLValidConnectionChecker is preferred for newer drivers
<check-valid-connection-sql>some arbitrary sql</check-valid-connection-sql>
-->
@@ -244,15 +253,15 @@
<type-mapping>mySQL</type-mapping>
</metadata>
</local-tx-datasource>
- </datasources>
- ]]>
+</datasources>
+]]>
</programlisting>
</para>
<para>
- We need to copy that file to the <literal>deploy</literal> directory for our server. (In our case "default"). Once we do that we need to change the <literal>connection-url</literal> to <literal>jdbc:postgresql://localhost:3306/jboss</literal>. For the username put <literal>sam</literal> and for the password put <literal>password</literal>.
+ We need to copy that file to the <literal>deploy</literal> directory for our server. (In our case "default"). Once we do that we need to change the <literal>connection-url</literal> to <literal>jdbc:mysql://localhost:3306/jboss</literal>. For the username put <literal>sam</literal> and for the password put <literal>password</literal>.
<programlisting>
<![CDATA[
- <datasources>
+<datasources>
<local-tx-datasource>
<jndi-name>MySqlDS</jndi-name>
<connection-url>jdbc:mysql://localhost:3306/jboss</connection-url>
@@ -263,12 +272,15 @@
org.jboss.resource.adapter.jdbc.vendor.MySQLExceptionSorter
</exception-sorter-class-name>
<!-- should only be used on drivers after 3.22.1 with "ping" support
- <valid-connection-checker-class-name>org.jboss.resource.adapter.jdbc.vendor.MySQLValidConnectionChecker</valid-connection-checker-class-name>
+ <valid-connection-checker-class-name>
+ org.jboss.resource.adapter.jdbc.vendor.MySQLValidConnectionChecker
+ </valid-connection-checker-class-name>
-->
<!-- sql to call when connection is created
<new-connection-sql>some arbitrary sql</new-connection-sql>
-->
- <!-- sql to call on an existing pooled connection when it is obtained from pool - MySQLValidConnectionChecker is preferred for newer drivers
+ <!-- sql to call on an existing pooled connection when it is obtained from pool -
+ MySQLValidConnectionChecker is preferred for newer drivers
<check-valid-connection-sql>some arbitrary sql</check-valid-connection-sql>
-->
@@ -278,14 +290,14 @@
</metadata>
</local-tx-datasource>
- </datasources>
- ]]>
+</datasources>
+]]>
</programlisting>
</para>
<para>When you save the file you should see the datasource be bound by JBoss in the console output like below. Each time you save the file the datasource will be bound and unbound, so you may see multiple entries like below.
<programlisting>
- 15:57:26,891 INFO [WrapperDataSourceService] Bound ConnectionManager
- 'jboss.jca:service=DataSourceBinding,name=MySqlDS' to JNDI name 'java:MySqlDS'
+15:57:26,891 INFO [WrapperDataSourceService] Bound ConnectionManager
+'jboss.jca:service=DataSourceBinding,name=MySqlDS' to JNDI name 'java:MySqlDS'
</programlisting>
</para>
<para>
@@ -298,19 +310,19 @@
<para>
For individual applications JBoss looks for a <literal>jbosscmp-jdbc.xml</literal> file in your applications deployment. To configure your application to use MySQL, look for a jbosscmp-jdbc.xml deployment descriptor in your applications jars files and then make sure the jbosscmp-jdbc settings are like so:
<programlisting>
- <![CDATA[
- <jbosscmp-jdbc>
+<![CDATA[
+<jbosscmp-jdbc>
<defaults>
<datasource>java:/MySqlDS</datasource>
<!-- optional since 4.0 <datasource-mapping>Hypersonic SQL</datasource-mapping> -->
<datasource-mapping>mySQL</datasource-mapping>
</defaults>
- </jbosscmp-jdbc>
- ]]>
+</jbosscmp-jdbc>
+]]>
</programlisting>
Although the <literal>datasource-mapping</literal> is optional, it is nice to know the type of the datasource, as this ties directly back to the type-mapping of the data-source.
</para>
- <para>For a full set of default datasource mappings look in <literal>jboss-4.2.0.CR1/server/default/conf/standardjbosscmp-jdbc.xml</literal>. In that file you can look for the <literal>mySQL</literal> type mapping.
+ <para>For a full set of default datasource mappings look in <literal>.../server/default/conf/standardjbosscmp-jdbc.xml</literal>. In that file you can look for the <literal>mySQL</literal> type mapping.
</para>
<para>
If you need to change any of the type mappings for mySQL you can put your own custom <literal>jbosscmp-jdbc.xml</literal> file right in your META-INF directory of your EJB JAR with the <literal>ejb-jar.xml</literal> and <literal>jboss.xml</literal> deployment descriptor files. Then you need to add a <literal>-Doptonal.dd=mysql</literal> to your <literal>ant</literal> build commands. When you've done that, your application will now be talking to MySQL. Now when you look at the tables for your MySQL database, you should see some tables that your application deployment created. You can see the tables in a MySQL database by typing <literal>show tables;</literal>.
@@ -343,13 +355,19 @@
<driver-class>com.mysql.jdbc.Driver</driver-class>
<user-name>root</user-name>
<password></password>
- <exception-sorter-class-name>org.jboss.resource.adapter.jdbc.vendor.MySQLExceptionSorter</exception-sorter-class-name>
- <!-- should only be used on drivers after 3.22.1 with "ping" support <valid-connection-checker-class-name>org.jboss.resource.adapter.jdbc.vendor.MySQLValidConnectionChecker</valid-connection-checker-class-name>
+ <exception-sorter-class-name>
+ org.jboss.resource.adapter.jdbc.vendor.MySQLExceptionSorter
+ </exception-sorter-class-name>
+ <!-- should only be used on drivers after 3.22.1 with "ping" support
+ <valid-connection-checker-class-name>
+ org.jboss.resource.adapter.jdbc.vendor.MySQLValidConnectionChecker
+ </valid-connection-checker-class-name>
-->
<!-- sql to call when connection is created
<new-connection-sql>some arbitrary sql</new-connection-sql>
-->
- <!-- sql to call on an existing pooled connection when it is obtained from pool - MySQLValidConnectionChecker is preferred for newer drivers
+ <!-- sql to call on an existing pooled connection when it is obtained from pool -
+ MySQLValidConnectionChecker is preferred for newer drivers
<check-valid-connection-sql>some arbitrary sql</check-valid-connection-sql>
-->
<!-- Use the security domain defined in conf/login-config.xml -->
@@ -375,31 +393,13 @@
Now we need to go change the <literal>.../server/default/conf/standardjbosscmp-jdbc.xml file so that the following elements have the correct values.</literal>
<programlisting>
-
<datasource>java:/DefaultDS</datasource>
<datasource-mapping>mySQL</datasource-mapping>
<fk-constraint>true</fk-constraint>
-
</programlisting>
</para>
-<!-- This was recommended by some articles I read, but did not work so I took it out. Need to look into why?
- <para>
- Add the following <literal>application-policy</literal> to login-config.xml.
- <programlisting>
- <application-policy name="MySqlDbRealm">
- <authentication>
- <login-module code = "org.jboss.resource.security.ConfiguredIdentityLoginModule" flag = "required" >
- <module-option name = "principal">root</module-option>
- <module-option name = "userName">root</module-option>
- <module-option name = "password"></module-option>
- <module-option name = "managedConnectionFactoryName">jboss.jca:service=LocalTxCM, name=DefaultDS</module-option>
- </login-module>
- </authentication>
- </application-policy>
- </programlisting>
- </para>
--->
+
<para>
Now we change and replace two files in <literal>.../server/default/deploy/jms</literal>. First we need to replace the file <literal>hsqldb-jdbc2-service.xml</literal> with <literal>.../docs/examples/jms/mysql-jdbc2-service.xml</literal>. In the hsql-jdbc2-service.xml file change the <literal>MySqlDS</literal> to <literal>DefaultDS</literal>. Next rename <literal>hsqldb-jdbc-state-service.xml</literal> to <literal>mysql-jdbc-state-service.xml</literal> . It's in the <literal>depends</literal> tag for the PersistenceManagers MBean.
</para>
@@ -530,13 +530,13 @@
<para>
Now we'll add our jboss user as well and set his password to <literal>password</literal>.
<programlisting>
-jboss=# create user jboss encrypted password 'password' createrole createdb;
+jboss=# create user jboss encrypted password 'password' createrole createdb superuser;
CREATE ROLE
jboss=# \du
List of roles
Role name | Superuser | Create role | Create DB | Connections | Member of
-----------+-----------+-------------+-----------+-------------+-----------
- jboss | no | yes | yes | no limit |
+ jboss | yes | yes | yes | no limit |
postgres | yes | yes | yes | no limit |
(2 rows)
</programlisting>
@@ -553,7 +553,6 @@
<programlisting>
org.postgresql.Driver Information
Not loaded in repository cache
-
</programlisting>
While we haven't used the instance yet which would have caused the class to be loaded into the repository cache, we do have an instance, so JBoss knows about the driver and can see it. If we had used the class already we'd get much more information and it would look like this:
<programlisting>
@@ -629,7 +628,8 @@
..org.jboss.system.server.NoAnnotationURLClassLoader at 7471e0
..sun.misc.Launcher$AppClassLoader at e39a3e
....file:/Users/sgriffith/jboss-4.2.0.GA/bin/run.jar
-....file:/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Classes/.compatibility/14compatibility.jar
+....file:/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Classes
+/.compatibility/14compatibility.jar
..sun.misc.Launcher$ExtClassLoader at 92e78c
....file:/Library/Java/Extensions/.DS_Store
....file:/Library/Java/Extensions/junit-4.1.jar
@@ -651,12 +651,18 @@
....file:/System/Library/Java/Extensions/QTJava.zip
....file:/System/Library/Java/Extensions/QTJSupport.jar
....file:/System/Library/Java/Extensions/vecmath.jar
-....file:/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/lib/ext/apple_provider.jar
-....file:/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/lib/ext/dnsns.jar
-....file:/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/lib/ext/localedata.jar
-....file:/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/lib/ext/sunjce_provider.jar
-....file:/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/lib/ext/sunpkcs11.jar
-++++CodeSource: (file:/Users/sgriffith/jboss-4.2.0.GA/server/default/lib/postgresql-8.2-504.jdbc3.jar )
+....file:/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/lib/ext
+/apple_provider.jar
+....file:/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/lib/ext
+/dnsns.jar
+....file:/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/lib/ext
+/localedata.jar
+....file:/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/lib/ext
+/sunjce_provider.jar
+....file:/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/lib/ext
+/sunpkcs11.jar
+++++CodeSource: (file:/Users/sgriffith/jboss-4.2.0.GA/server/default/lib
+/postgresql-8.2-504.jdbc3.jar )
Implemented Interfaces:
++interface java.sql.Driver(30c6cd)
++++ClassLoader: null
@@ -676,7 +682,7 @@
<para>
A PostgreSQL datasource definition can be found in <literal>jboss-4.2.0.CR1/docs/examples/jca</literal>. If you look in there you'll find a file called <literal>postgres-ds.xml</literal>. It looks like this:
<programlisting>
- ![CDATA[
+<![CDATA[
<datasources>
<local-tx-datasource>
<jndi-name>PostgresDS</jndi-name>
@@ -699,13 +705,13 @@
</local-tx-datasource>
</datasources>
- ]]
+]]>
</programlisting>
</para>
<para>
We need to copy that file to the <literal>deploy</literal> directory for our server. (In our case "default"). Once we do that we need to change the <literal>connection-url</literal> to <literal>jdbc:postgresql://localhost:5432/jboss</literal>. For the username put <literal>jboss</literal> and for the password put <literal>password</literal>.
<programlisting>
- ![CDATA[
+<![CDATA[
<datasources>
<local-tx-datasource>
<jndi-name>PostgresDS</jndi-name>
@@ -713,11 +719,13 @@
<driver-class>org.postgresql.Driver</driver-class>
<user-name>jboss</user-name>
<password>password</password>
- <!-- sql to call when connection is created. Can be anything, select 1 is valid for PostgreSQL
+ <!-- sql to call when connection is created. Can be anything, select 1 is valid
+ for PostgreSQL
<new-connection-sql>select 1</new-connection-sql>
-->
- <!-- sql to call on an existing pooled connection when it is obtained from pool. Can be anything, select 1 is valid for PostgreSQL
+ <!-- sql to call on an existing pooled connection when it is obtained from pool.
+ Can be anything, select 1 is valid for PostgreSQL
<check-valid-connection-sql>select 1</check-valid-connection-sql>
-->
@@ -728,7 +736,7 @@
</local-tx-datasource>
</datasources>
- ]]
+]]>
</programlisting>
</para>
<para>When you save the file you should see the datasource be bound by JBoss in the console output like below. Each time you save the file the datasource will be bound and unbound, so you may see multiple entries like below.
@@ -747,15 +755,15 @@
<para>
For individual applications JBoss looks for a <literal>jbosscmp-jdbc.xml</literal> file in your applications deployment. To configure your application to use PostgreSQL, look for a jbosscmp-jdbc.xml deployment descriptor in your applications jars files and then make sure the jbosscmp-jdbc settings are like so:
<programlisting>
- ![CDATA[
- <jbosscmp-jdbc>
+<![CDATA[
+<jbosscmp-jdbc>
<defaults>
<datasource>java:/MyPostgreSQL</datasource>
<!-- optional since 4.0 <datasource-mapping>Hypersonic SQL</datasource-mapping> -->
<datasource-mapping>PostgreSQL</datasource-mapping>
</defaults>
- </jbosscmp-jdbc>
- ]]
+</jbosscmp-jdbc>
+]]>
</programlisting>
Although the <literal>datasource-mapping</literal> is optional, it is nice to know the type of the datasource, as this ties directly back to the type-mapping of the data-source.
@@ -775,7 +783,7 @@
<para>
Now we need to change the <literal>.../server/default/deploy/postgres-ds.xml</literal> file to look like include the following datasource definition:
<programlisting>
- ![CDATA[
+<![CDATA[
<datasources>
<local-tx-datasource>
<jndi-name>PostgresDS</jndi-name>
@@ -783,11 +791,13 @@
<driver-class>org.postgresql.Driver</driver-class>
<user-name>jboss</user-name>
<password>password</password>
- <!-- sql to call when connection is created. Can be anything, select 1 is valid for PostgreSQL
+ <!-- sql to call when connection is created. Can be anything, select 1 is
+ valid for PostgreSQL
<new-connection-sql>select 1</new-connection-sql>
-->
- <!-- sql to call on an existing pooled connection when it is obtained from pool. Can be anything, select 1 is valid for PostgreSQL
+ <!-- sql to call on an existing pooled connection when it is obtained from pool.
+ Can be anything, select 1 is valid for PostgreSQL
<check-valid-connection-sql>select 1</check-valid-connection-sql>
-->
@@ -798,14 +808,14 @@
</local-tx-datasource>
</datasources>
- ]]
+]]>
</programlisting>
</para>
<para>
Now we need to go change the <literal>.../server/default/conf/standardjaws.xml</literal> file so that the following elements have the correct values.
<programlisting>
- <datasource>java:/DefaultDB</datasource>
- <type-mapping>PostgreSQL</type-mapping>
+<datasource>java:/DefaultDS</datasource>
+<type-mapping>PostgreSQL</type-mapping>
</programlisting>
</para>
<para>
@@ -831,7 +841,7 @@
<programlisting>
- ![CDATA[
+<![CDATA[
sgriffith$ run.sh
=========================================================================
@@ -915,9 +925,9 @@
08:09:31,086 WARN [JARDeployer] Failed to add deployable jar: file:/Users/sgriffith/jboss-4.2.0.GA/server/default/tmp/deploy/tmp64444jmsclear
java.util.zip.ZipException: error in opening zip file
at java.util.zip.ZipFile.open(Native Method)
- at java.util.zip.ZipFile.init(ZipFile.java:203)
- at java.util.jar.JarFile.init(JarFile.java:132)
- at java.util.jar.JarFile.init(JarFile.java:70)
+ at java.util.zip.ZipFile.<init>(ZipFile.java:203)
+ at java.util.jar.JarFile.<init>(JarFile.java:132)
+ at java.util.jar.JarFile.<init>(JarFile.java:70)
at org.jboss.deployment.SubDeployerSupport.processNestedDeployments(SubDeployerSupport.java:377)
at org.jboss.deployment.SubDeployerSupport.init(SubDeployerSupport.java:284)
at org.jboss.deployment.MainDeployer.init(MainDeployer.java:872)
@@ -990,6 +1000,7 @@
08:09:31,482 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-127.0.0.1-8080
08:09:31,623 INFO [AjpProtocol] Starting Coyote AJP/1.3 on ajp-127.0.0.1-8009
08:09:31,651 INFO [Server] JBoss (MX MicroKernel) [4.2.0.CR1 (build: SVNTag=JBoss_4_2_0_CR1 date=200701180935)] Started in 51s:920ms
+]]>
</programlisting>
Now we have JBoss using PostgreSQL as it's default datasource and starting up with no errors.
</para>
More information about the jboss-cvs-commits
mailing list