Converting Qpid Broker configuration from older versions to new

[Brian O'Shea <bo...@salesforce.com>]

Hello,

I am in the process of upgrading the Qpid Broker version that my
organization is using from 0.32 to 7.0.6.  I know this is quite a big jump. 
A former employee already did some of the work to upgrade to 6.0.5, but we
never finished the upgrade before he left, and now we want to upgrade to
7.0.6.  I mention this because we don't have adequate testing around the
configuration for 6.0.5, so the most well-known, stable configuration that
we have is for 0.32.

Do you provide tools for converting the JSON configuration from older
versions to newer versions?

Thanks,
Brian O'Shea




--
Sent from: http://qpid.2158936.n2.nabble.com/Apache-Qpid-users-f2158936.html

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org

Re: Converting Qpid Broker configuration from older versions to new

[Keith W <ke...@gmail.com>]

Hello Brian,

For the most part of Broker-J will handle the upgrade of configuration
from 0.32 and any BDB message store automatically.  Take a backup of
the ${QPID_WORK} from your old Broker and start the new pointed at the
same location.   It will automatically rewrite the configuration and
message store as it comes up for the first time.   The upgrade is one
way so an upgraded configuration and message store cannot be used with
an older version of Broker-J.

One area of configuration that is not covered by automatic upgrade any
ACL rules.   If you are using ACLs, check the rules that you use
against the documentation.

One of the biggest differences between 0.32 and 7.0.x is the way the
Broker uses memory.  The 7.0.x Broker uses both heap and direct
memory, the latter being used to cache messages during their traversal
through the Broker.   The way the Broker uses memory is documented
[2].  You'll need to reevaluate any sizing decisions you made for the
old Broker.  There are formulae in the documentation to help you.

The other big area of change is the matured support for AMQP 1.0
available in Broker-J 7.0.x.    AMQP 1.0 support was added alongside
the support for the older protocols (AMQP 0-9 and 0-10), so your
existing applications will continue to function without change.   You
will want to consider upgrading client applications to AMQP 1.0 based
libraries, but you don't need to conflate this with your broker
upgrade.    Broker-J supports on the fly message translation so having
application A using say AMQP 0-10 and application B using AMQ 1.0 is
supported.  This can allow any upgrade to be phased.

Hope this helps

Keith.

[1] https://qpid.apache.org/releases/qpid-broker-j-7.0.6/book/Java-Broker-Security-AccessControlProviders.html#Java-Broker-Security-AccessControlProviders-ACLRules
[2] https://qpid.apache.org/releases/qpid-broker-j-7.0.6/book/Java-Broker-Runtime-Memory.htmlOn
Sat, 29 Sep 2018 at 01:48, Brian O'Shea <bo...@salesforce.com> wrote:
>
> Hello,
>
> I am in the process of upgrading the Qpid Broker version that my
> organization is using from 0.32 to 7.0.6.  I know this is quite a big jump.
> A former employee already did some of the work to upgrade to 6.0.5, but we
> never finished the upgrade before he left, and now we want to upgrade to
> 7.0.6.  I mention this because we don't have adequate testing around the
> configuration for 6.0.5, so the most well-known, stable configuration that
> we have is for 0.32.
>
> Do you provide tools for converting the JSON configuration from older
> versions to newer versions?
>
> Thanks,
> Brian O'Shea
>
>
>
>
> --
> Sent from: http://qpid.2158936.n2.nabble.com/Apache-Qpid-users-f2158936.html
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> For additional commands, e-mail: users-help@qpid.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org