1 Reply Latest reply on May 2, 2002 5:58 PM by David Jencks

    Resource Adapter Configuration under JBoss 3.0

    Mark Polman Newbie

      Hi all,

      I recently deployed my resource adapter under JBoss-2.4.4
      without any problems. Now, I tried to achieve the same
      under JBoss 3.0. However, it is not quite clear to me
      where to place the appropriate mbean code and how the
      required mbean code has changed.

      I used the following mbean under JBoss-2.4.4:




      UserName=Administrator
      Password=secret
      DatabaseName=MyDatabase
      PropertiesURL=d:/xhive/bin/xhive.properties.default
      LogLevel=4

      XhiveDS
      XhiveDS
      java:/TransactionManager
      JCA:service=RARDeployer
      XhiveConnector
      MinervaXACMFactory


      MinSize=0
      MaxSize=100
      Blocking=true
      GCEnabled=false
      IdleTimeoutEnabled=false
      InvalidateOnError=false
      TrackLastUsed=false
      GCIntervalMillis=120000
      GCMinIdleMillis=1200000
      IdleTimeoutMillis=1800000
      MaxIdleTimeoutPercent=1.0


      <!-- Principal mapping configuration -->
      org.jboss.resource.security.ManyToOnePrincipalMapping

      userName=Administrator
      password=secret



      How should I convert this to a JBoss-3.0 compliant mbean.
      I tried several other possibilities, among which the one
      below:

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





      XhiveDS
      java:/TransactionManager
      <mbean-ref name="ResourceAdapterName">JCA:service=RARDeployment,name=XhiveConnector</mbean-ref>
      <mbean-ref name="ConnectionManagerFactoryLoaderName">JCA:service=ConnectionManagerFactoryLoader,name=MinervaXACMFactory</mbean-ref>


      UserName=Administrator
      Password=secret
      DatabaseName=MyDatabase
      PropertiesURL=d:/xhive/bin/xhive.properties
      LogLevel=4


      PoolConfiguration=per-factory
      MinSize=0
      MaxSize=100
      BlockingTimeoutMillis=-1
      IdleTimeoutMinutes=30
      MaxIdleTimeoutPercent=1.0
      CleanupIntervalMinutes=30


      <!-- Principal mapping configuration -->
      org.jboss.resource.security.ManyToOnePrincipalMapping

      userName=Administrator
      password=secret




      and another with "depends" elements instead of "mbean-ref"
      elements. Every time JBoss claims to have successfully
      deployed the resource adapter, but it always turns out
      that the name XhiveDS is not bound. What am I doing wrong?

      Thanks in advance for any input

      regards

      --Mark Polman--

        • 1. Re: Resource Adapter Configuration under JBoss 3.0
          David Jencks Master

          1. Please get jboss 3 rc2 (or 3.1 from cvs if you are feeling adventurous)

          2. Get the firebird-service.xml from docs/examples/jca as a starting point. (It is an xa compliant jca adapter, not using a wrapper)

          3. Starting up with your rar in the deploy dir you should get a jboss.jca:service=RARDeployment,name=<display name of your adapter> mbean showing on port 8082. If not, I'd suspect a problem in your packaging or ra.xml. Some error should be reported.

          4. Set the OldRarDeployment attribute in your *-service to the object name of what you found in (3).

          5. Set the ManagedConnectionFactoryProperties appropriately. You can use the format in ra.xml or a condensed format (I think I converted the firebird example, if not look at another one)

          6. Set up the security following the instructions in the example file.

          There's a lot of explanation of each attribute in the generated jmx-api documentation under docs.