Hi Folks,

we are running an old version of the MQ operator in openshift (2021). The MQ console is pretty poor - if we upgrade the operator do we get the very latest version of the console i.e. the same as it is in the standalone product. Or is the MQ console in openshift going to be behind the main product?

many thanks !
John.

Hi Folks,

we are running an old version of the MQ operator in openshift (2021). The MQ console is pretty poor - if we upgrade the operator do we get the very latest version of the console i.e. the same as it is in the standalone product. Or is the MQ console in openshift going to be behind the main product?

many thanks !
John.

Hi John,

The MQ Operator doesn't have its own console.  The MQ console is provided by the queue manager, and is the same as found in MQ on distributed platforms.  Upgrading to a new MQ Operator will allow you to use the newer MQ queue manager versions, and thus get a newer console.

The reason that sometimes this gets confusing, is that in the Cloud Pak for Integration, the Platform UI (formerly the Platform Navigator) applies its own UI header, to enable cross-product consistency - otherwise the console is exactly the same code though, and is still served by the individual queue manager container.  The MQ Operator doesn't yet support the standalone web server.

Regards,

Hi Folks,

we are running an old version of the MQ operator in openshift (2021). The MQ console is pretty poor - if we upgrade the operator do we get the very latest version of the console i.e. the same as it is in the standalone product. Or is the MQ console in openshift going to be behind the main product?

many thanks !
John.

Hi John,

The MQ Operator doesn't have its own console.  The MQ console is provided by the queue manager, and is the same as found in MQ on distributed platforms.  Upgrading to a new MQ Operator will allow you to use the newer MQ queue manager versions, and thus get a newer console.

The reason that sometimes this gets confusing, is that in the Cloud Pak for Integration, the Platform UI (formerly the Platform Navigator) applies its own UI header, to enable cross-product consistency - otherwise the console is exactly the same code though, and is still served by the individual queue manager container.  The MQ Operator doesn't yet support the standalone web server.

Regards,

Hi Folks,

we are running an old version of the MQ operator in openshift (2021). The MQ console is pretty poor - if we upgrade the operator do we get the very latest version of the console i.e. the same as it is in the standalone product. Or is the MQ console in openshift going to be behind the main product?

many thanks !
John.

Hmm, What is this "standalone web server" that you speak of @Arthur Barr ? I would rather not have to upgrade our production QM just to get a console that I can work with. Unfortunately, the alternative is that I install MQExplorer on a jumpbox - at that point I need ILMT to audit the licencing (which I REALLY don't want !)

If this standalone console were available could I remotely connect it to me current QM (Without an upgrade) and would I need some other licencing mechanism - or would it be in open-shift??

cheers !

Hi John,

The MQ Operator doesn't have its own console.  The MQ console is provided by the queue manager, and is the same as found in MQ on distributed platforms.  Upgrading to a new MQ Operator will allow you to use the newer MQ queue manager versions, and thus get a newer console.

The reason that sometimes this gets confusing, is that in the Cloud Pak for Integration, the Platform UI (formerly the Platform Navigator) applies its own UI header, to enable cross-product consistency - otherwise the console is exactly the same code though, and is still served by the individual queue manager container.  The MQ Operator doesn't yet support the standalone web server.

Regards,

Hi Folks,

we are running an old version of the MQ operator in openshift (2021). The MQ console is pretty poor - if we upgrade the operator do we get the very latest version of the console i.e. the same as it is in the standalone product. Or is the MQ console in openshift going to be behind the main product?

many thanks !
John.

Hmm, What is this "standalone web server" that you speak of @Arthur Barr ? I would rather not have to upgrade our production QM just to get a console that I can work with. Unfortunately, the alternative is that I install MQExplorer on a jumpbox - at that point I need ILMT to audit the licencing (which I REALLY don't want !)

If this standalone console were available could I remotely connect it to me current QM (Without an upgrade) and would I need some other licencing mechanism - or would it be in open-shift??

cheers !

Hi John,

The MQ Operator doesn't have its own console.  The MQ console is provided by the queue manager, and is the same as found in MQ on distributed platforms.  Upgrading to a new MQ Operator will allow you to use the newer MQ queue manager versions, and thus get a newer console.

The reason that sometimes this gets confusing, is that in the Cloud Pak for Integration, the Platform UI (formerly the Platform Navigator) applies its own UI header, to enable cross-product consistency - otherwise the console is exactly the same code though, and is still served by the individual queue manager container.  The MQ Operator doesn't yet support the standalone web server.

Regards,

Hi Folks,

we are running an old version of the MQ operator in openshift (2021). The MQ console is pretty poor - if we upgrade the operator do we get the very latest version of the console i.e. the same as it is in the standalone product. Or is the MQ console in openshift going to be behind the main product?

many thanks !
John.