1 Reply Latest reply on Apr 11, 2019 9:04 AM by Martien van den Akker

    AQ adapter - Queue payload type SYS.AQ$_JMS_TEXT_MESSAGE vs Object type

    Vijayaragavan Ramasamy

      Hello,

       

      I would like to know the advantages / disadvantages over below two from SOA suite integration perpective.

       

      1. Soa suite composites to dequeue an AQ that has a queue payload type of object type in DB

      2. SOA suite composite to dequeue an AQ that has a queue payload type of SYS.AQ$_JMS_TEXT_MESSAGE

       

      As per this link, there are additional configurations needed if there is queue payload type is  SYS.AQ$_JMS_TEXT_MESSAGE.

       

      I want to understand the advantages of using a AQ of type SYS.AQ$_JMS_TEXT_MESSAGE. over object type payload type.

       

      Regards,

      Vijay

        • 1. Re: AQ adapter - Queue payload type SYS.AQ$_JMS_TEXT_MESSAGE vs Object type
          Martien van den Akker

          Hi Vijay,

           

          The SYS.AQ$_JMS_TEXT_MESSAGE object is meant and specially created to create an AQ QueueTable that supports JMS access. So if you use database AQ as a JMS Server, you need to create queues based on that object. At our current customer we created a ForeignServer, based on a datasource that makes our AQ queues accessible as JMS queue destinations. Therefor we need to create those queues based on the SYS.AQ$_JMS_TEXT_MESSAGE object. So, if you plan to use AQ as a persistent layer to JMS and want to access those through the JMS adapter, or another JMS client, then it makes sense to use the SYS.AQ$_JMS_TEXT_MESSAGE object.

           

          However, if you want to use AQ Adapter, you can use it, but it might make more sense to use a specific custom type.

           

          Regards,
          Martien