| Author |
Message
|
| mq_population |
 Posted: Wed Feb 22, 2017 5:40 am Post subject: FTE patching |
 |
|
Apprentice
Joined: 14 Jul 2009
Posts: 26
|
|
| Back to top |
|
 |
| tomleend |
| Posted: Wed Feb 22, 2017 2:35 pm Post subject: |
|
|
Acolyte
Joined: 24 Jan 2014
Posts: 51
|
| You do not need to stop any MQ queue managers to apply a WebSphere MQ File Transfer Edition (FTE) Fix Pack. Only the FTE processes themselves (agents and loggers) need to be stopped. |
|
| Back to top |
|
|
| mq_population |
| Posted: Wed Feb 22, 2017 11:50 pm Post subject: |
|
|
Apprentice
Joined: 14 Jul 2009
Posts: 26
|
| tomleend wrote: |
| You do not need to stop any MQ queue managers to apply a WebSphere MQ File Transfer Edition (FTE) Fix Pack. Only the FTE processes themselves (agents and loggers) need to be stopped. |
Thanks . Is there any document or Link for this / OR you have tested it out yourself . I don't want to cause any issues to the existing set-up by doing this , so just confirming . |
|
| Back to top |
|
|
| tomleend |
| Posted: Thu Feb 23, 2017 2:57 am Post subject: |
|
|
Acolyte
Joined: 24 Jan 2014
Posts: 51
|
I have tested it.
But, remember that WebSphere MQ File Transfer Edition (FTE) is a separate product to MQ itself. All that FTE really is is an MQ application that moves files from one file system to another.
If you wanted to update one of your MQ applications that uses the C client, or the MQ classes for JMS, you wouldn't expect to stop the queue manager for all your other applications just to update that one.  |
|
| Back to top |
|
|
| mq_population |
| Posted: Thu Feb 23, 2017 5:42 am Post subject: |
|
|
Apprentice
Joined: 14 Jul 2009
Posts: 26
|
| tomleend wrote: |
I have tested it.
But, remember that WebSphere MQ File Transfer Edition (FTE) is a separate product to MQ itself. All that FTE really is is an MQ application that moves files from one file system to another.
If you wanted to update one of your MQ applications that uses the C client, or the MQ classes for JMS, you wouldn't expect to stop the queue manager for all your other applications just to update that one. |
Great - Thank you !! yes I agree to that . FTE behaves similar to a client application for MQ.
Actually I tried to list FTE packages installed on AIX , but it seems they are not visible in AIX - I could only see installed MQ packages - that caused much of the confusion and I don't want to cause issues to MQ by keeping it running in case they were part of the MQ packages installed . |
|
| Back to top |
|
|
| gbaddeley |
| Posted: Thu Feb 23, 2017 3:52 pm Post subject: |
|
|
Jedi Knight
Joined: 25 Mar 2003
Posts: 2527
Location: Melbourne, Australia
|
FTE is going out of support soon. You should be migrating to IBM MQ MFT. Functionally, it is a drop in replacement for FTE. Migration is not difficult.
_________________
Glenn |
|
| Back to top |
|
|
| mq_population |
| Posted: Fri Mar 03, 2017 7:50 am Post subject: |
|
|
Apprentice
Joined: 14 Jul 2009
Posts: 26
|
Hi All
We are facing another issue with FTE - the Agent fails to start after Fix pack upgrade to 7.0.4.6 from 7.0.4.4
OS is Linux V6 ; The error message is as follows -
+ /opt/IBM/WMQFTE/jre/bin/java -Dcom.ibm.wmqfte.product.root=/opt/IBM/WMQFTE -Dcom.ibm.wmqfte.product.config= com.ibm.wmqfte.agent.bootstrap.impl.BootstrapMain com.ibm.wmqfte.api.ShowAgentDetails -p QTQFTE1 ZTFF004
5655-U80, 5724-R10 Copyright IBM Corp. 2008, 2011. ALL RIGHTS RESERVED
BFGCL0002E: A messaging problem prevented the command from completing successfully. The WebSphere MQ completion code was 2, and the reason code was 2059. A connection could not be established to queue manager XXXXX, on host 'X.Y.Z.com' using port XXX and channel XXXX.XXXX.01.
However , when I run fteDisplayVersion command - it returns successfully and shows correct version - 7.0.4.6
And there is no error in the Installation log .
Any suggestions what could be the issue .
Thanks. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Fri Mar 03, 2017 3:08 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20729
Location: LI,NY
|
| mq_population wrote: |
Hi All
We are facing another issue with FTE - the Agent fails to start after Fix pack upgrade to 7.0.4.6 from 7.0.4.4
OS is Linux V6 ; The error message is as follows -
+ /opt/IBM/WMQFTE/jre/bin/java -Dcom.ibm.wmqfte.product.root=/opt/IBM/WMQFTE -Dcom.ibm.wmqfte.product.config= com.ibm.wmqfte.agent.bootstrap.impl.BootstrapMain com.ibm.wmqfte.api.ShowAgentDetails -p QTQFTE1 ZTFF004
5655-U80, 5724-R10 Copyright IBM Corp. 2008, 2011. ALL RIGHTS RESERVED
BFGCL0002E: A messaging problem prevented the command from completing successfully. The WebSphere MQ completion code was 2, and the reason code was 2059. A connection could not be established to queue manager XXXXX, on host 'X.Y.Z.com' using port XXX and channel XXXX.XXXX.01.
However , when I run fteDisplayVersion command - it returns successfully and shows correct version - 7.0.4.6
And there is no error in the Installation log .
Any suggestions what could be the issue .
Thanks. |
MQRC 2059 is queue manager not available. Any entries in the queue manager log? Are you able to telnet to the queue manager port?
Can you attach a non MQFTE agent (i.e. RFHUtil?) to the queue manager using the same user as the MQFTE Agent?? 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| gbaddeley |
| Posted: Sun Mar 05, 2017 3:22 pm Post subject: |
|
|
Jedi Knight
Joined: 25 Mar 2003
Posts: 2527
Location: Melbourne, Australia
|
| mq_population wrote: |
Hi All
We are facing another issue with FTE - the Agent fails to start after Fix pack upgrade to 7.0.4.6 from 7.0.4.4
OS is Linux V6 ; The error message is as follows -
+ /opt/IBM/WMQFTE/jre/bin/java -Dcom.ibm.wmqfte.product.root=/opt/IBM/WMQFTE -Dcom.ibm.wmqfte.product.config= com.ibm.wmqfte.agent.bootstrap.impl.BootstrapMain com.ibm.wmqfte.api.ShowAgentDetails -p QTQFTE1 ZTFF004
5655-U80, 5724-R10 Copyright IBM Corp. 2008, 2011. ALL RIGHTS RESERVED
BFGCL0002E: A messaging problem prevented the command from completing successfully. The WebSphere MQ completion code was 2, and the reason code was 2059. A connection could not be established to queue manager XXXXX, on host 'X.Y.Z.com' using port XXX and channel XXXX.XXXX.01. |
Use your normal FTE trouble shooting procedures ???
Check the command.properties, coordination.properties and agent.properties files for correct MQ connection config details. Check that the qmgrs, channels and ports are available.
_________________
Glenn |
|
| Back to top |
|
|
| mq_population |
| Posted: Tue Mar 14, 2017 7:32 am Post subject: |
|
|
Apprentice
Joined: 14 Jul 2009
Posts: 26
|
| Quote: |
Use your normal FTE trouble shooting procedures ???
Check the command.properties, coordination.properties and agent.properties files for correct MQ connection config details. Check that the qmgrs, channels and ports are available. |
| Quote: |
MQRC 2059 is queue manager not available. Any entries in the queue manager log? Are you able to telnet to the queue manager port?
Can you attach a non MQFTE agent (i.e. RFHUtil?) to the queue manager using the same user as the MQFTE Agent?? |
Yes we followed our standard trouble shooting steps. Unfortunately that did not help much , and we generated traces to see the error . It was related to SSL set-up for channels !!
However , the problem has taken a different turn now - after we modified our SSL Set-up . The Agent connected to Agent/Command Queue Manager over SSL but failed to connect to Co-Ordination QM over SSL - while using the same configuration (of course) . And the error code is same - 2059.
$ ./ftePingAgent XXXXXXXX
5655-U80, 5724-R10 Copyright IBM Corp. 2008, 2011. ALL RIGHTS RESERVED
BFGCL0002E: A messaging problem prevented the command from completing successfully. The WebSphere MQ completion code was 2, and the reason code was 2059. A connection could not be established to queue manager XXXXXXX, on host 'YYYYYY' using port ZZZZZ and channel XXXXX.YYYYYY.ZZZZ
Not surprising though - but everything runs OK over Non-SSL.
Any suggestions anyone ?
Thanks ! |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed Mar 15, 2017 5:30 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20729
Location: LI,NY
|
Make sure both the queue manager the agent connects to and the coordination queue manager use the correct (and same ? cipherspec )
Are channels between coordination queue manager and queue manager the agent is connected to working correctly with SSL?
Have fun
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
