IBM MQ Internet Pass-Thru licensing requirement - websphere

We have an IBM MQ Internet Pass-Thru V2.1.0.1(MQIPT) configured within our organization that consumes the messages published by an external organization 'X'. The external organization 'X' has distributed this MQIPT to use within our premises. We are trying to consume the messages published by 'X' to an IBM MQ (fully licensed) hosted on their side via the MQIPT hosted in our premises.
We have used the .NET library 'XMS.Net' (https://www.ibm.com/support/pages/xms-net-%E2%80%93-overview) to consume the messages via MQIPT. The licensing says it is free for a period of 90 days.
In this configuration, what is the licensing requirement that we need for using the XMS.NET IBM C# library?
Can anybody tell me if we need to purchase any licenses in addition to what 'X' already has? If yes, how much does it usually cost?
I am trying to get help from IBM, but considering their prioritization, I hope I can get a quicker answer from here.

Your question covers 2 separate products, MQ Client and MQ IPT.
XMS.Net is part of the MQ Client for .Net, which is a free product:
https://www.ibm.com/docs/en/ibm-mq/9.2?topic=information-mq-client-net-license
But MQIPT requires a license. Though I don't think it is licensed on its own, but as part of a full MQ license:
"If you have purchased IBM MQ entitlement, you can install as many copies as required of MQIPT. MQIPT installations are not counted against your purchased IBM MQ entitlement."
https://www.ibm.com/docs/en/ibm-mq/9.1?topic=overview-mq-internet-pass-thru
You will need to ask IBM whether the MQ license of company X covers the MQIPT installations in your network (unlikely), or what is the minimum MQ license you need to purchase to use MQIPT.

Related

Open Liberty support Network Deployment?

Does Open Liberty support network deployment?
Are we able to buy IBM Support for Open Liberty? and How?
Can Open Liberty be used to replace WebSphere Application server v9 in HA environment? e.g Having Load balancer (hardware) received request from web application and auto distribute received request to 2 or more standalone Open Liberty installed in separate VM/Machine?
Thanks
Your question is a bit vague, so I'll try my best.
Does Open Liberty support network deployment?
Depends what you mean by that support. You can install multiple Open Liberty on multiple VM/machines that will serve your applications and use LB/or IHS to route to them.
You cannot centrally manage via single console, for that you need WebSphere Liberty ND version that supports collectives.
However most recent deployments will use more 'farm' like or container orchestration approaches rather than central management via dedicated manager (as Dmgr in WAS v9).
Are we able to buy IBM Support for Open Liberty? and How?
Yes you can. See Get IBM or Red Hat support for Open Liberty page for general info and contact IBM sales representative for best option for your needs.
Can Open Liberty be used to replace WebSphere Application server v9 in HA environment?
Depends on your application and non-functional requirements. You can setup LB or IHS with plugin (for more intelligent balancing) to route requests to multiple VM/machines with Open Liberty.
Check for example this Configuring IBM HTTP Server for Liberty and here Open Liberty Plugin Configuration. Few manual steps will be needed to edit generated config file to support many servers.

Differences between version for MQ

Where can I find the differences between the IBM MQ versions V8.0.0.5 and V9.0? I tried to look it up on IBM website but no luck.
IBM's v9 Knowledge center page "What's new in Version 9.0.0" lists new things in v9.0.
New family features
are:
Additional quality of protection for IBM MQ AMS
Web addressable access to the client channel definition table (CCDT)
IBM MQ AMS supported in non-IBM JREs in Java clients
Updated Resource Adapter for traditional WebSphere Application Server
Enhanced Unicode data conversion support
IBM MQ Managed File Transfer Protocol Bridge Agent logging enhancements
New features for distributed platforms
are:
Performance monitoring API and enhanced activity trace available through publish/subscribe
[Windows] LDAP authorization on Windows platforms
[UNIX] runmqsc command line editor for UNIX platforms
New z/OS® features
are:
Data manager page set statistics
JMS support within CICS OSGI Server
JMS support within IMS Server
Improved control of messages by using message expiry
Increased number of active logs
Using IBM z/OSMF to automate IBM MQ
IBM's v9 Knowledge center page "What's changed in Version 9.0.0" lists what has changed.
[V9.0.0.0]Changes to supported platforms
For IBM MQ Version 9.0, some changes are made to the platforms that
are supported.
[V9.0.0.0]Changes to commands
A number of commands have changed at IBM MQ Version 9.0
[V9.0.0.0]Command level changes for Version 9.0
The command level changes to 900 at IBM MQ Version 9.0
[V9.0.0.0]Deprecated, stabilized and removed features
A number of features are deprecated, stabilized or removed from IBM MQ
Version 9.0.
[z/OS][V9.0.0.0]z/OS: Prerequisites for Version 9.0
Some prerequisites have changed for Version 9.0.
[z/OS][V9.0.0.0]z/OS: Changes to OPMODE
In previous versions of IBM MQ, if a queue manager was started with
OPMODE=(COMPAT,vrm), new functions added at command level vrm would
always be available. In IBM MQ Version 9.0 this is no longer the case.
You need to look at "What's new" document which comes with every MQ release. Search for "IBM MQ Knowledge Center," and navigate to "What's new." Version 9.0 is here.

MQ 6.0 testing by UFT 12.02

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).

IBM WAS Liberty Network Deployment : Is free or license is required

I know Liberty is free but want to confirm that either IBM WAS Liberty Network Deployment profile is free too ? and we can build clusters as well.
This article says:
Liberty profile Network Deployment can be downloaded as a trial if you
do not already have a WebSphere license.
Just to clarify a few things.
WebSphere Liberty is free for development purposes.
For production you may use version downloaded from wasdev.net for free (without support), if the heap size doesn't excess 2GB in the whole organization you are working. See details about that here What the Liberty runtime license lets you do
For any other versions like Liberty Core, Base, ND, or z/OS you need a valid WebSphere license.
So for example, if you already have WebSphere ND license, you can use Liberty instead of full WebSphere.
If you don't have any WebSphere licenses and you would like to use WebSphere Liberty in production you have to buy licenses, see here WebSphere Application Server family
Trial versions are only for 60 days.

Requirement for creating WebSphere MQ FTE agents in Windows

I am designing a new file transfer infrastructure using WebSphere MQ v7.5 FTE product and like to know for creating an FTE agent in a Windows box, what is the basic minimum requirement? Does it require the MQ v7.5 server edition installed or will it work with the MQ v7.5 client libraries?
You need at least one WMQ queue manager to act as the queuing hub for all the agents. The regular FTE agents can be client-based. Typically, these are placed local to the file endpoints and access the underlying filesystem directly. For most agents a client connection to a central queue manager works great. The exception is a node where the transfer volume is very high, in which case it might warrant having a local queue manager.
The exception is the "Protocol Bridge" agents which are the ones that talk to remote FTP, SFTP and FTPS servers. These must reside on the same host as the queue manager.
Short answer: on your Windows box a client agent is the minimal requirement. Just point its configuration to a queue manager somewhere on the network.

Resources