2 Replies Latest reply on May 24, 2013 8:43 AM by Pier-Erik-Oracle

    Configuring BMQ

      hi All,

      We have a messaging application that uses Bea MessageQ for message transfer across the network. The application is currently hosted on an infrastructure with below specifications.

      OS : Solrais 9
      Oracle Application Server : OAS 10gR2
      Application servers are in a cluster.

      bus id - 3
      Group id - 3017
      Group name - 3017

      We are now planning to install our application in an upgraded environment :

      OS : Solrais 10
      Oracle Application Server : OAS 11g
      Application servers are in a cluster.

      I would now like to know the following ;

      1. if we move to a new hardware, there will be a change in the IP. Is this in anyway related to the busid and groupid configured? Is it possible to run the Bea MessageQ on the new server with the same configuration?
      2. Where can i find the value for parameter "ENDPOINT" that i need to mention in the cross group connections table which is a part of DM.init file?

      Expecting some early responses!

        • 1. Re: Configuring BMQ
          I don't know if this answer is too late for you, but I'll take a crack at answering after a few years away from the product.

          In the %xgroup table the endpoint would be the listen port for your cross-group link listener.

          In the %cls table (for client library connections) it would be a listen port for the Client Library Server for the group. It would be where your client would connect.

          Bus number and group number are not related to IP address. The only things in the group configs that would change when moving to the new machine would be listen addresses for that machine - both for the group.init file on that machine, and in the init files of the remote groups connecting to it. Remember that a specific group number can only run on one machine at Ea time on a given bus.

          In fact, starting in v4.0 I believe, your group could be configured to listen on one or more specific IPs for incoming connections, assuming you had multiple IPs stacked on the machine. You could also have multiple entries for a remote group that would fail over to another machine/IP.

          I'm not sure why you bring up OAS, as that's a different product and there was never an officially-released Java API for DMQ/BMQ/OMQ.

          Hope this helps
          • 2. Re: Configuring BMQ
            As said by Steve in previous reply (it's like bicycle, you cannot forget MessageQ :-) ) there is quite no dependency upon Ip address.
            Here follows my answers in the SR (Service Request) opened by customer to us, Oracle Support, 6-7 months ago.


            1. Is BMQ compatible with Solaris 10 OS?
            Oracle support certifies a number of platforms and OS versions (through regression tests and so on ...) and those certifications are publicly stated in our our documentation site (url= http://http://docs.oracle.com/).
            - research & click on Tuxedo (which is the Product Line Area)
            - for last version (currently Oracle Tuxedo 12c Release 1) click on "View Library" to see Oracle® Tuxedo Family page
            - in "Oracle Tuxedo Family Certified Platforms" paragraph, select "Oracle Message Q Certified Platform Tables"
            - select your target OS, here "Sun Solaris" which gives you the result.
            Oracle have certified MessageQ v.5 (32-bit) on Solaris 10 on SPARC and Intel platforms.
            2. If there is a change in IP address of the server/ the cluster, what
            will be the impact on BMQ and its processes? What are the corresponding
            configurations that need to be changed in BMQ files (which files)? [also
            need to check who will perform these changes in the files]
            MessageQ as a network application is not aware of the IP addresses: the only exception is a particular SBS feature on OpenVMS only, so irrelevant here. The mechanism which is used is the gethostbyname() (C call) hence the namespace(s) that is/are configured.
            MessageQ uses gethostbyname() first to check if local hostname is listed in the cross group list (%XGRP section of the configuration file): if it is not, there is no communication with another group; if there is one matching line, it will create LD (link drivers) to communicate with other groups using the mentioned hostnames and port numbers.
            Last for this item, MessageQ is unaware of the cluster structure.
            3. Is it possible to run BMQ in a virtual server? Changes that need to
            be made when we move the BMQ from an application server that is
            currently physical to a virtual server using flashback mechanism?
            As it is not possible for Oracle to certify each type of emulated Operating System, it has been decided to rely on Emulation vendor responsability: for example, if a software editor claims that his virtual server emulates hardware for Solaris 10, then Oracle MessageQ (or Tuxedo) will be supported on this emulator and any issue that cannot be replicated on real machine will be the responsability of this software vendor.
            4. Is there any dependency on the server IP address and the BUS Id,
            Group Id and Group Name configurations of BMQ?
            There is NO dependency on the server address which is always taken from configurated namespace, or on the BUS Id which is designed to allow parallel buses with no communications between them (impermeable or message-tight buses). Applications are not aware of their BUS Id.
            The Group Name is just a label without any real impact (just for management ease).
            The Group Id has a very important role as it is the first part of any queue address in the bus, so moving the group from one machine to another requires that each MessageQ configuration file has the related line in the cross group list, modified accordingly (old hostname replaced by new).
            5. What is the current version of BMQ (in support version)?
            Current version for MessageQ on Unix and Windows platforms is version 5 (and 5.01 for Itanium OpenVMS); the suggested Rolling Patch level is always the highest (each Rolling Patch N+1 includes all the fixes of RP level N).

            Edited by: user10654299 on May 24, 2013 1:43 AM