Re: AQ/Referenceable Objects work with MDB on WebLogic

Question

          Great work! So you don't have to touch any of Oracle's classes, correct?
          Do you have time to document the whole thing and post it here, including the source
          code of all your custom classes?
          Eric Ma
          "Diptanshu Parui" <[email protected]> wrote:
          >
          >Forgot to add an important point.
          >The extended classes have to in the oracle.jms package (not necessarily
          >in the
          >same jar) to extend the Oracle classes. And I have used aqapi13.jar.
          >
          >Dips
          >
          >"Diptanshu Parui" <[email protected]> wrote:
          >>
          >>Hi,
          >>
          >>After days of work on getting to integrate Oracle's AQ with WebLogic
          >>I have managed
          >>to get to a solution without making changes to the Oracle's AQ API.
          >>
          >>Eric Ma had managed to provide a solution about an year back changing
          >>Oracle's
          >>API and making the AQjmsConnection, AQjmsSession, AQjmsQueueConnectionFactory
          >>& AQjmsDestination NOT implement Referenceable. This solution worked
          >>with WebLogic
          >>but meant that this cannot be deployed on Production environment.
          >>
          >>There was a myth that WebLogic's JNDI didn't provide support to Referenceable
          >>objects like Oracle's AQjmsQueueConnectionFactory etc.
          >>
          >>This myth has been broken. Referenceable object CAN be bound and looked
          >>up from
          >>WebLogic's JNDI provided right Factory classes are written and the correct
          >>constructor
          >>for Reference is used in the getReference method of the Referenceable
          >>implementation.
          >>
          >>In case of Oracle's objects, I wrote classes extending AQjmsQueueConnectionFactory
          >>& AQjmsDestination. In the extended classes, I wrote toString method
          >>and set private
          >>String variable.
          >>This string variable is just special character separated concat of all
          >>parameters
          >>used to call the constructor of the extended class.
          >>Then, in the getReference method of the extended class, I used the following
          >>constructor
          >>of Reference.
          >>
          >>return new Reference( DipsAQQueueConnectionFactory.class.getName(),
          >new
          >>StringRefAddr("value",
          >>value), DipsAQConnectionFactory.class.getName(), null);
          >>
          >>DipsAQQueueConnectionFactory is my class extending AQjmsQueueConnectionFactory
          >>and DipsAQConnectionFactory is the factory class for DipsAQQueueConnectionFactory.
          >>The object value passed in the StringRefAddr above is nothing but the
          >>toString
          >>of the extended class which was stored in the private String variable.
          >>In the
          >>factory class, the string is taken out the StringRefAddr and stripped
          >>to get individual
          >>parameters which were separated by special characters. Once, the individual
          >>parameters
          >>are got back, the Factory class instantiates the Referenceable object
          >>and returns
          >>it back.
          >>
          >>Another important point is in the extended class DipsAQQueueConnectionFactory
          >>I wrote this method
          >> public QueueConnection createQueueConnection() throws JMSException
          >>
          >> {
          >>     return createQueueConnection("user","user");
          >> }     
          >>
          >>And then using a startup class I bound the DipsAQQueueConnectionFactory
          >>& DipsAQDestination
          >>Referenceable objects to WLS. The MDB deployed on WLS was made lookup
          >>for the
          >>bound QF & Q and it started reading AQ messages.
          >>
          >>Few other points to note.
          >>I have kept the user & pwd of WLS same as DB.
          >>I have used OCI driver.
          >>
          >>Please feel free to raise further queries/suggestions.
          >>
          >>Dips
          >
          

Answer 1

          Eric,
          This is the relevant part of the config.xml you were looking for.
               <JMSDistributedQueue JNDIName="DQueue1" Name="DQueue1" Targets="ClusterTwo" Template="DQueue1">
                    <JMSDistributedQueueMember JMSQueue="Queue1" Name="DQM1"/>
                    <JMSDistributedQueueMember JMSQueue="Queue2" Name="DQM2"/>
               </JMSDistributedQueue>
               <JMSBridgeDestination
                    ConnectionFactoryJNDIName="AQJMSConnectionFactory" ConnectionURL="t3://ip:port"
                    DestinationJNDIName="AQJMSQueue" Name="AQJMSDest"/>
               <JMSConnectionFactory JNDIName="ConnectionFactory" Name="ConnectionFactory"
                    ServerAffinityEnabled="false" Targets="IAServer,ClusterTwo" XAConnectionFactoryEnabled="true"/>
               <JMSBridgeDestination ConnectionFactoryJNDIName="ConnectionFactory" ConnectionURL="t3://ip:port"
                    DestinationJNDIName="DQueue1" Name="Dest"/>
               <MessagingBridge Name="MB1" QualityOfService="Duplicate-okay"
                    SourceDestination="AQJMSDest" TargetDestination="Dest"
                    Targets="IAServer,MS1 (migratable),MS2 (migratable),ClusterTwo"/>
          No, I haven't used Oracle's OC4J 10g's AQJMS XA TX support classes.
          cheers!
          Dips
          "Eric Ma" <[email protected]> wrote:
          >
          >Dips:
          >
          >Can you post your config.xml here to show how you set up WLS messaging
          >bridges?
          >
          >Also, have you played with OC4J 10g's AQJMS XA TX support classes?
          >
          >Eric
          >
          >"Diptanshu Parui" <[email protected]> wrote:
          >>
          >>The sample code is now available at
          >>http://dev2dev.bea.com/codelibrary/code/startupclass.jsp
          >>
          >>cheers,
          >>Dips
          >>
          >>
          >>"Diptanshu Parui" <[email protected]> wrote:
          >>>
          >>>Yes, no need to touch Oracle's code at all.
          >>>
          >>>I will post the whitepaper/code soon.
          >>>
          >>>
          >>>"Eric Ma" <[email protected]> wrote:
          >>>>
          >>>>Great work! So you don't have to touch any of Oracle's classes, correct?
          >>>>
          >>>>Do you have time to document the whole thing and post it here, including
          >>>>the source
          >>>>code of all your custom classes?
          >>>>
          >>>>Eric Ma
          >>>>
          >>>>
          >>>>"Diptanshu Parui" <[email protected]> wrote:
          >>>>>
          >>>>>Forgot to add an important point.
          >>>>>The extended classes have to in the oracle.jms package (not necessarily
          >>>>>in the
          >>>>>same jar) to extend the Oracle classes. And I have used aqapi13.jar.
          >>>>>
          >>>>>Dips
          >>>>>
          >>>>>"Diptanshu Parui" <[email protected]> wrote:
          >>>>>>
          >>>>>>Hi,
          >>>>>>
          >>>>>>After days of work on getting to integrate Oracle's AQ with WebLogic
          >>>>>>I have managed
          >>>>>>to get to a solution without making changes to the Oracle's AQ API.
          >>>>>>
          >>>>>>Eric Ma had managed to provide a solution about an year back changing
          >>>>>>Oracle's
          >>>>>>API and making the AQjmsConnection, AQjmsSession, AQjmsQueueConnectionFactory
          >>>>>>& AQjmsDestination NOT implement Referenceable. This solution worked
          >>>>>>with WebLogic
          >>>>>>but meant that this cannot be deployed on Production environment.
          >>>>>>
          >>>>>>There was a myth that WebLogic's JNDI didn't provide support to
          >Referenceable
          >>>>>>objects like Oracle's AQjmsQueueConnectionFactory etc.
          >>>>>>
          >>>>>>This myth has been broken. Referenceable object CAN be bound and
          >>looked
          >>>>>>up from
          >>>>>>WebLogic's JNDI provided right Factory classes are written and the
          >>>>correct
          >>>>>>constructor
          >>>>>>for Reference is used in the getReference method of the Referenceable
          >>>>>>implementation.
          >>>>>>
          >>>>>>In case of Oracle's objects, I wrote classes extending AQjmsQueueConnectionFactory
          >>>>>>& AQjmsDestination. In the extended classes, I wrote toString method
          >>>>>>and set private
          >>>>>>String variable.
          >>>>>>This string variable is just special character separated concat
          >of
          >>>>all
          >>>>>>parameters
          >>>>>>used to call the constructor of the extended class.
          >>>>>>Then, in the getReference method of the extended class, I used the
          >>>>following
          >>>>>>constructor
          >>>>>>of Reference.
          >>>>>>
          >>>>>>return new Reference( DipsAQQueueConnectionFactory.class.getName(),
          >>>>>new
          >>>>>>StringRefAddr("value",
          >>>>>>value), DipsAQConnectionFactory.class.getName(), null);
          >>>>>>
          >>>>>>DipsAQQueueConnectionFactory is my class extending AQjmsQueueConnectionFactory
          >>>>>>and DipsAQConnectionFactory is the factory class for DipsAQQueueConnectionFactory.
          >>>>>>The object value passed in the StringRefAddr above is nothing but
          >>>the
          >>>>>>toString
          >>>>>>of the extended class which was stored in the private String variable.
          >>>>>>In the
          >>>>>>factory class, the string is taken out the StringRefAddr and stripped
          >>>>>>to get individual
          >>>>>>parameters which were separated by special characters. Once, the
          >>individual
          >>>>>>parameters
          >>>>>>are got back, the Factory class instantiates the Referenceable object
          >>>>>>and returns
          >>>>>>it back.
          >>>>>>
          >>>>>>Another important point is in the extended class DipsAQQueueConnectionFactory
          >>>>>>I wrote this method
          >>>>>> public QueueConnection createQueueConnection() throws JMSException
          >>>>>>
          >>>>>> {
          >>>>>>     return createQueueConnection("user","user");
          >>>>>> }     
          >>>>>>
          >>>>>>And then using a startup class I bound the DipsAQQueueConnectionFactory
          >>>>>>& DipsAQDestination
          >>>>>>Referenceable objects to WLS. The MDB deployed on WLS was made lookup
          >>>>>>for the
          >>>>>>bound QF & Q and it started reading AQ messages.
          >>>>>>
          >>>>>>Few other points to note.
          >>>>>>I have kept the user & pwd of WLS same as DB.
          >>>>>>I have used OCI driver.
          >>>>>>
          >>>>>>Please feel free to raise further queries/suggestions.
          >>>>>>
          >>>>>>Dips
          >>>>>
          >>>>
          >>>
          >>
          >