Multiple Apps and Multiple Queues/Topics

Question

          In WL7, is it possible to have two applications both do the same JNDI lookup and get
          different queues? This is possible with EJB's because Weblogic has its own local
          JNDI lookup that the java:comp/env/ejb/XXX references, however you cannot do the
          local lookup with JMS queues/topics. My situation is that I may have more than one
          client on a given box, and the messages going into a queue are destined for specific
          clients, but the programs are both looking up the same queue (e.g., jms/UpdateCache).
          Is the only way to do this through using filters? I don't want to make any code changes
          from one client app to the next.
          

Answer 1

You can configure same queue/topic on multiple servers by using
          JNDINameReplicated=false on the queue/topic so each queue/topic is only
          known locally. Then you can use dedicated connection Factory for each
          server and you can use different url to connect to different server.
          e.g.
          # two connection factories deployed on two different WLS servers
          # myserver1 has url like this: 192.0.0.1:7001
          # myserver2 has url like this: 192.0.0.2:7001
          # two JMS Servers deployed on two different WLS servers
          # each JMS server has an identical queue
          # you do not need to specify JNDIName for the queue if you can use
          createQueue
          # queueSession.createQueue("./exampleQueue1");
          # client (sender/consumer) using 192.0.0.1:7001 to get initialContext
          will use "cf1" and
          # lookup queue on myserver1
          # client (sender/consumer) using 192.0.0.2:7002 to get initialContext
          will use "cf2" and
          # lookup queue on myserver2
          # port of config.xml
          <JMSConnectionFactory
          JNDIName="jms.connection.exampleFactoryFormyServer1"
          Name="cf1" Targets="myserver1"/>
          <JMSConnectionFactory
          JNDIName="jms.connection.exampleFactoryFormyServer2"
          Name="cf2" Targets="myserver2"/>
          <JMSServer Name="exampleJMSServer1" Targets="myserver1">
          <JMSQueue
          JNDIName="jms.queue.exampleQueue1"
          JNDINameReplicated="false"
          Name="exampleQueue1"/>
          </JMSServer>
          <JMSServer Name="exampleJMSServer2" Targets="myserver2">
          <JMSQueue
          JNDIName="jms.queue.exampleQueue1"
          JNDINameReplicated="false"
          Name="exampleQueue1"/>
          </JMSServer>
          "David Cherryhomes" <[email protected]> wrote in message
          news:[email protected]...
          >
          > In WL7, is it possible to have two applications both do the same JNDI
          lookup and get
          > different queues? This is possible with EJB's because Weblogic has its own
          local
          > JNDI lookup that the java:comp/env/ejb/XXX references, however you cannot
          do the
          > local lookup with JMS queues/topics. My situation is that I may have more
          than one
          > client on a given box, and the messages going into a queue are destined
          for specific
          > clients, but the programs are both looking up the same queue (e.g.,
          jms/UpdateCache).
          > Is the only way to do this through using filters? I don't want to make any
          code changes
          > from one client app to the next.