Distributed JMS Queues and Port Information

Question

Hello,
          I am a reasonably inexperience WebLogic user, so forgive my ignorance.
          We are setting up a distributed JMS queue as a destination for messages being sent from our EAI server. The distribution will be across 2 servers in our QA environment and 3 servers in our production. We are using WebLogic Server 8.1.3 on an Windows 2003 environment.
          The people in our EAI environment need a port number on for the Queue in order to forward their messages to us. My question's are:
          1) Is the listen port for the Distributed Queue the same as the listen port for the Admin Server?
          2) If it is not, does it correspond to the listen port for the individual queues (which is the same between our environments)?
          3) If there is a third port in play, how does this get configured and where do I retreive this information?
          I appreciate any answers people are willing to give me on the issue.
          Thank you,
          Steven Enk
          Harley-Davidson Motor Company

Answer 1

Hi Steven,
          WebLogic JMS shares the same WebLogic port as other WebLogic services, regardless of whether or not the destinations are distributed.
          One way to determine which ports are configured for a particular WebLogic server is to look at the log for that server.
          Ports are usually configured to support multiple protocols, and typically, one uses the "t3" protocol for URLs (its the highest performer), but there are other options (such as "http" for tunneling).
          You can configure additional ports (beyond the "default" port(s)) using the "channel" feature - i think you can find channels under the "WebLogic server" tabs on the console.
          For a server or client to establish communication with a remote cluster, one need only specify a URL for any one of the server's within the remote cluster. J2EE JNDI name location transparancy and WebLogic RMI load balancing will usually take care of the rest, although some customers setup DNS to help with load balancing (by for example, configuing their DNS "round-robin" addresses).
          Best practice is for the administrative server to be restricted to administrative purposes only. This means the admin server typically (A) doesn't host JMS (or any other services or any applications) and (B) is not a member of a cluster. So typically you won't be able to access JMS using an admin server's URL.
          Tom