I installed a WAS MQ 7.0 on linux then create some QMGRs there.
After a while I decide to use WAS MQ 7.5 for security reasons. Then I unistall version 7.0 and install version 7.5.
In 7.5 I want to delete all QMGRs that I created in version 7.0, So I try to delete those QMGR but I face to this error:
Queue manager 'X' is associated with a different
installation ('installation0') exitvalue=62
How can I delete this queue manager?
Associate MQ v7.0 queue managers to MQ v7.5 using setmqm command and then delete.
SETMQM -m <qm> -n <mqv75 installation name>
Related
In one of the windows system the administrator has installed the IBM MQ version 8. But after installation we are not ale to see the IBM MQ (installation 1) listed in the services. and also not able to see the file amqsvc.exe file.
If we launch Prepare Websphere MQ wizard it also just exits without any actions.
But on the control panel -programs and features able to see the IBM MQ installation1 is present . how to find out if the installation was done correctly?
Was this a MQ client installation instead of MQ server installation? how to find out what is the issue here as the MQ service is not present or its related files?
I have a complex situation. I have MQ and FTE installed in one Windows server. There were few agents defined long back. Now the coordination and command queue managers are removed long back. However the agent services are still there in the Windows server. I am unable to delete the agent now.
The MQ setup in the server is not required any more. My query is if I uninstall MQ, will be uninstall MFT as well and the agent services?
Any help will be appreciated.
It looks like you are running MFT agent as Windows service. These steps should help you:
1) First run fteModifyAgent to convert the agent (running as Windows service) to standard agent. This will remove the agent from Windows service list.
2) Run fteDeleteAgent to delete the agent configuration. The output of the command provides a list of MQ objects to delete in agent queue manager. Delete those MQ objects.
3) Then uninstall MQ and MFT.
4) Clean the MFT configuration directory on the file system.
Current version running is MQ7 in windows 2008 server. What to know about migration process steps from MQ7 to MQ8/MQ9?.New Version of MQ8/MQ9 Server to be installed and how existing Queue definition can be migrated?
Will Server Installation take care of QM definition also?
windows 2008 server will be good for mq9?
There is a MQ-Client7 contacting MQ-Server7, so if we upgrade MQ7 to MQ9 then MQ-Client also will be upgraded to MQ9?
There will be any issue in contacting MQ9-Client to MQ7 Server?
dspmqver will give MQ server details , how to verify MQ-Client version?
If you install the new version (V8 or V9) as an upgrade to the V7 installation on the same machine then then next time you start the queue manager it will be migrated to the new version.
If you install the new version alongside the V7 installation on the same machine, then you have to use the setmqm command to force the queue manager to move from V7 to the new version.
If you install the new version on a completely different machine, the no automatic migration can take place. You will have to create a brand new queue manager and then copy across the definitions from the old one.
The command to export all the object definitions is:
dmpmqcfg -m QM1 -x all > DEFS.mqs
The command to import all the object definitions is:
runmqsc QM1 < DEFS.mqs
The system requirements (e.g. minimum O/S levels) are documented by IBM here.
There is no requirement for the MQ Client to be the same version as the MQ Queue Manager. The MQ Client can be a higher version or a lower version than the MQ Queue Manager and still operate perfectly. The only thing to remember if the MQ Client is a higher version than the MQ Queue Manager is that new features cannot yet be used.
You can see the version of the MQ Client being used when it connects to the queue manager by looking in DISPLAY CHSTATUS for the field called RVERSION.
I am trying to configure test automation project in UFT 12.02 for IBM Websphere MQ 6.0
I am facing the following error while connecting to MQ Queue Manager
(To run tests with IBM’s MQ client, make sure to install the MQ client on all machines running these tests.)
as per the above error description I need to install MQ client on my machine, but I cannot install it because IBM has been stopped supporting MQ 6.0 accordingly I didn't find it anywhere.
I have configured the same but in IBM RIT (Rational Integration Tester) and it was only required to configure the JAR files (com.ibm.mq.jar & connector.jar)
My question is; Is it applicable in UFT to configure only above two JAR files (just like IBM RIT) or it is necessary to install the MQ 6.0 Client?
And can I test the MQ 6.0 through UFT along with installing MQ 7.0 Client instead of 6.0, taking in consideration that the AUT is IBM Websphere MQ 6.0?
Also if applicable, can anyone provide the MQ Client download URL rather than IBM website?
Prior to V8.0 it was required to install the full client to receive support. Just grabbing the jar files worked but you risked IBM not supporting it if you wanted to open a PMR.
As of v8.0, IBM offers an all-Java client. I just provided the download instructions in another answer so instead of copying them, I'll link to that answer:
WMQ V8 Connection Factory setup on Tomcat using JNDI
One of the reasons this was not previously supported was that the old Java jars didn't have as much diagnostic function built in. IBM relied on the full client install for binary cient-side tracing, test programs, etc. The v8.0 stand-alone jars are really the way to go if you need an all-Java solution.
Note that support is based on the QMgr's license, not the client license (because that's free). If you are running a v6.0 QMgr other than the Linux Itanium version, then either you are paying a LOT of money for IBM Support or are running unsupported. If it is the latter, then you can't open a PMR anyway.
An unpatched v6.0 QMgr is effectively not secure. Even if you have applied the recommended security configurations, enough security-relevant APARS have now been discovered that you should consider an unpatched QMgr as being wide open.
As Tim notes in the comments, any version of MQ Client is supported with any version of MQ QMgr. Head over to the SupportPacs page and look for ones with names like MQC**. Pro tip - If you download a new client, it comes with XA transactionality enabled. No need to go grab the transactional client jar file (which put you out of license compliance anyway).
I have been using WebSphere MQ lately to send message from local machine to the WebSphere MQ present on same (local) machine. Which works fine as expected.
I dont know how to install WebSphere MQ in other/remote Machine so that I can send message form my local machine to that remote machine.
Thanks,
There are a number of ways to do this but the most likely is that you will need to install an Websphere MQ Client onto the remote machine. I am not sure what version you want to use but the WMQ 7.5 client is available here MQC75 You can google for other versions by changing the number (MQC7, MQC71, MQC8 etc).
You haven't said what language your application is written in, if it is Java then the WMQ Client provides everything you need, if it is C/C++ or .NET then the page I linked to has more information about what you need for these languages.