1 Reply Latest reply on Apr 14, 2003 6:16 AM by pinky

    jtds datasource configuration

    danifanny Newbie

      Has anyone been able to create a DataSource in JBoss using jtds? If so, could you post the appropriate descriptor XML? Thanks!

      Dani

        • 1. Re: jtds datasource configuration
          pinky Newbie

          <?xml version="1.0" encoding="UTF-8"?>

          <!-- ===================================================================== -->
          <!-- -->
          <!-- JBoss Server Configuration -->
          <!-- -->
          <!-- ===================================================================== -->



          <!-- ======================================================================-->
          <!-- New ConnectionManager setup for Microsoft SQL Server 2000 driver -->
          <!-- You may download the latest Microsoft JDBC driver from *Microsoft* -->
          <!-- http://msdn.microsoft.com/downloads/default.asp?url=/downloads/sample.asp?url=/MSDN-FILES/027/001/779/msdncompositedoc.xml&frame=true -->
          <!-- Build jmx-api (build/build.sh all) and view for config documentation -->
          <!-- ===================================================================== -->



          <!-- Include a login module configuration named MSSQLDbRealm.
          Update your login-conf.xml, here is an example for a
          ConfiguredIdentityLoginModule:

          <application-policy name = "MSSQLDbRealm">

          <login-module code = "org.jboss.resource.security.ConfiguredIdentityLoginModule" flag = "required">
          <module-option name = "principal">yourprincipal</module-option>
          <module-option name = "userName">yourusername</module-option>
          <module-option name = "password">yourpassword</module-option>
          <module-option name = "managedConnectionFactoryName">jboss.jca:service=LocalTxCM,name=MSSQLDS</module-option>
          </login-module>

          </application-policy>

          NOTE: the application-policy name attribute must match SecurityDomainJndiName, and the
          module-option name = "managedConnectionFactoryName"
          must match the object name of the ConnectionManager you are configuring here.
          -->
          <!--uncomment out this line if you are using the MSSQLDbRealm above
          MSSQLDbRealm
          -->

          MSSQL
          <depends optional-attribute-name="ManagedConnectionFactoryName">
          <!--embedded mbean-->





          <config-property name="ConnectionURL" type="java.lang.String">jdbc:jtds:sqlserver://zapblr2/WEBCESV1.0</config-property>
          <!-- <config-property name="ConnectionURL" type="java.lang.String">jdbc:jtds:sqlserver://zapblr2:1433/pubs</config-property> -->
          <config-property name="DriverClass" type="java.lang.String">net.sourceforge.jtds.jdbc.Driver</config-property>
          <!--set these only if you want only default logins, not through JAAS-->
          <!--
          <config-property name="UserName" type="java.lang.String">tempuser</config-property>
          <config-property name="Password" type="java.lang.String">temp181z</config-property>
          -->
          <config-property name="UserName" type="java.lang.String">sa</config-property>
          <config-property name="Password" type="java.lang.String">161629</config-property>



          <!--Below here are advanced properties -->
          <!--hack-->
          <depends optional-attribute-name="OldRarDeployment">jboss.jca:service=RARDeployment,name=JBoss LocalTransaction JDBC Wrapper



          <depends optional-attribute-name="ManagedConnectionPool">
          <!--embedded mbean-->


          0
          50
          5000
          15
          <!--criteria indicates if Subject (from security domain) or app supplied
          parameters (such as from getConnection(user, pw)) are used to distinguish
          connections in the pool. Choices are
          ByContainerAndApplication (use both),
          ByContainer (use Subject),
          ByApplication (use app supplied params only),
          ByNothing (all connections are equivalent, usually if adapter supports
          reauthentication)-->
          ByContainer



          <depends optional-attribute-name="CachedConnectionManager">jboss.jca:service=CachedConnectionManager

          <depends optional-attribute-name="JaasSecurityManagerService">jboss.security:service=JaasSecurityManager

          java:/TransactionManager
          <!--make the rar deploy! hack till better deployment-->
          jboss.jca:service=RARDeployer