First off, thanks a bunch! :) This seems to get me closer...and I need the CMP 2.0 stuff!
What is the principal? Is that like the security requested (another user)? I'm assuming I should just set this to my username as per your description below? Next, how do I reference this in my deployment descriptors and such and make sure that it connects to the correct database inside the database server? I'm used to providing a jdbc url, so I don't know how to add a database entry in this format. Outside of a DTD (which I haven't found yet either), is there any documentation on this? Thanks again! :) -- -bk Quoting Neal Sanche <[EMAIL PROTECTED]>: > On June 5, 2002 02:18 pm, you wrote: > > I've been poking around the conf hierarchy in JBoss 3.0 (very different > > from 2.4.6) and have not been able to locate the datasource definitions. > I > > see that a lot of the documentation lists java:/DefaultDS as the > datasource > > being used, but I don't see that defined anywhere (server, port, user, > > password, etc.). > > > > Any help would be appreciated! > > Yes, that was my first problem when using the JBoss 3.0 structure as well. It > > turns out to be a little strange, but more flexible I think. The trick is > that the definitions are now in the deploy/ directory, and are coupled with > > login information through the JAAS configuration file login-config.xml. > Here's what I've got for using an oracle database. > > Put this fragment into conf/login-config.xml: > > <application-policy name = "OracleDbRealm"> > <authentication> > <login-module code = > "org.jboss.resource.security.ConfiguredIdentityLoginModule" flag = > "required"> > <module-option name = "principal">username</module-option> > <module-option name = "userName">username</module-option> > <module-option name = "password">password</module-option> > <module-option name = > "managedConnectionFactoryName">jboss.jca:service=LocalTxCM,name=OracleDS</module-option> > </login-module> > </authentication> > </application-policy> > > Then you have to use a rather large file to define the oracle service and > it's pretty arcane. If you have the jboss source code handy, or perhaps it's > > included in the JBoss 3.0 final release as well, there's a > docs/examples/jca/oracle-service.xml that is basically what I used. There's a > > number of examples of different databases that can be specified too. Each has > > a comment at the top showing what <application-policy> fragment you should > use. > > Put the XXX-service.xml file into the server/default/deploy directory, and > you should be ready to roll if all of your attributes are set correctly. > > And, you'll also need to drop your JDBC driver into the $TOP/lib directory. > > > Hope this helps. > > -Neal > > _______________________________________________________________ > > Don't miss the 2002 Sprint PCS Application Developer's Conference > August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm > > _______________________________________________ > JBoss-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-user > > _______________________________________________________________ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
