Home/ Questions/Q 8265863
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-08T04:57:08+00:00

My current task in the company is to implement IVY dependency management. Now I

  • 0

My current task in the company is to implement IVY dependency management.
Now I hit the following libraries that I couldn’t find in usual Maven repositories, such as http://mvnrepository.com:

com.ibm.mq.jar

com.ibm.mq.pcf.jar
…

and so forth (they are all with the prefix: com.ibm.mq).

I could found them on a separated website: http://www.java2s.com/
But it’s not Maven compatible.

So, where could I found those? What’s the best solution to overcome this?

I’m thinking, uploading them manually to the team nexus. But is this the usual procedure in such cases?

Thanks a lot in advance.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Best place to find those is directly from IBM. Please see this answer for the different versions of the WMQ Java/JMS client available.

    As for the best way to package these, please be aware that if you want IBM to support them you need to install the client code rather than just bundling in the jar files. The reason IBM is reluctant to support non-standard installs should concern you as well if the app is to be installed in Production. The full client includes considerable additional functionality such as diagnostics, trace functions, crypto libs, JSSE, etc. In addition, it is the only install against which you can apply IBM’s maintenance.

    If you install the jars from a 3rd party site such as the one linked above, do you even know what version they are? Has any of the maintenance been applied? Have the latest patches been applied? Since IBM only distributes the full client, and OEMs are not authorized to distribute the jar files except as part of their application, any site offering the WMQ jar files is by definition pirating them.

    I realize that requiring you to do the full client install is considered burdensome when you are used to being able to just grab some jars and go. On the other hand, if you don’t need support then you might install the WMQ Client on a VM somewhere, keep it up to date and grab the jar files from there. That way you have a known-good set of files that are all in sync and to which you can apply maintenance.

    If you’d like to suggest to IBM that they need a lighter-weight Java solution, feel free to raise the requirement (or vote on it if it already exists) at the IBM Request For Enhancement (RFE) Community.

    • 0