1 Reply Latest reply on Jul 15, 2002 3:25 PM by taude

    HELP!  FreeTDS and JBoss 3.0

    jmejia424

      Since I can't get the Microsoft JDBC drivers to work with JBoss 3.0, Has anyone successfully been able to get the FreeTDS drivers to work with JBoss 3.0 and SQL Server 7?

      If you have, can you please give me instructions to do so.

      Thanks!

        • 1. Re: HELP!  FreeTDS and JBoss 3.0
          taude

          It worked for me, no problem.

          Make sure you copied TwFreeTds_1.0.jar to the correct lib folder. (mine is /server/default/lib)

          My config files look like this:

          === from login-config.xml ===
          <application-policy name = "MSSQLDbRealm">

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

          </application-policy>
          === from login-config.xml ===


          === from mssql-service.xml ===


          <!-- ======================================================================-->
          <!-- 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 -->
          <!-- ===================================================================== -->



          <!-- since the security is in login-config.xml, reference it here -->
          MSSQLDbRealm

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


          MSSQLDS



          <config-property name="ConnectionURL" type="java.lang.String">jdbc:twtds:sqlserver://usjwaws609/AdvisorClientWeb</config-property>
          <config-property name="DriverClass" type="java.lang.String">com.thinweb.tds.Driver</config-property>

          <!-- we're not doing this, but set these only if you want only default logins, not through JAAS
          <config-property name="UserName" type="java.lang.String">sa</config-property>
          <config-property name="Password" type="java.lang.String"></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:name=JaasSecurityManager

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




          === from mssql-service.xml ===


          good luck,
          Todd