As promised, want to share some additional information on steps connecting to an IBM Websphere MQ from Talend...Please note that i am neither an expert on Websphere MQ or on Talend, nor do i represent any company here, these are just my personal experiences shared only to help people and can not be considered as authenticated in any means. This documentation is an extension of one of the earlier posts https://community.talend.com/t5/Migration-Configuration-and/Connect-to-IBM-WebSphere-MQ-server-using... written by some one that i am completely unaware of..tried reusing some verbage from the previous post.
==============================================================================================================================================================================================
Question
How do you configure the tJMSInput component to connect to an IBM WebSphere MQ?
Solution
Steps:
- Create a .bindings file (if you have one, skip to point 2 below)
creating .bindings file
- Launch your MQ Explorer
- Create a Queue Manager
- Right Click on Queue Mgr and proceed with all defaults
- Upon confirming that the Queue mgr. is created, you will find that couple of other folders under the Queue Manager would surface, of which Channels and Listener are of consideration to us in this context
- Create a Queue
- Under the Queue Manager you created in Step 2 above, you will find Queues folder, right click it to create a Queue
- Create 2 queues if you wish, one for reading and one for writing.
- Create a channel
- Right click the Channels and choose the channel type.
- In my view Server-connection channel is ideal, if you think otherwise you can explore further
- Go to JMS Administered Objects, Create a InitialContext
- Here it is important to choose File System as the JNDI Namespace locator so that you can use that path as your Server URL when configuring tJMSINPUT component.
- Go to the path mentioned and ensure that the ‘.bindings’ file is created before proceeding to configure the tJMSINPUT component
- Add three tLibraryLoad components to your Talend Job for the following JARs:
- jar (located in your WMQ installation under IBM\WebSphere MQ\java\lib)
- jar (located in your WMQ installation under IBM\WebSphere MQ\java\lib)
- jms-api-2.0.1.jar (you can download this from the Maven Repository, at http://central.maven.org/maven2/javax/jms/javax.jms-api/2.0.1/javax.jms-api-2.0.1.jar)
Though not necessarily an issue, when I downloaded the jar it comes as javax.jms-api-2.0.1.jar and I had hard time making Talend recognize this jar, so I have to manually take away the javax. and have the jar name as jms-api-2.0.1.jar. I am not from Java background, so this is just my observation.
One more important point to remember here is, every job where you are trying to connect to a MQ using tJMSINPUT component should have these tLibraryLoad components, just because you find these libraries in the list of installed libraries you can not assume that these components are not needed for the next MQ connectivity job.
- tJMSINPUT component configuration - This is where I spent a whole lot of time and looks like there is a small bug/overlook here at Talend…so pay close attention to this point:
Module List : select ‘com.ibm.mq.allclient-8.0.0.4.jar’ library from the list. If the list has 8.0.0.9 or something higher than ‘8.0.0.4’, it is quite ok, no issues. If you don’t find this in your list of installed components then follow this steps:
1.
Pick the .jar (if you don’t have download) and then click on ‘Detect the module install status’ to ensure that the .jar is already installed.
Here is the trick, when you click on ‘Detect the module install status’ Talend will say that this Maven object is already installed, but when you run the job, it will not be able to instantiate the jar. What I did is, I went to find by name and then tried to search by name, when it shows not found, so then if you go to install a new module, it installs and will start showing up in your list of modules available from the list button under platform.
- Context Provider: enter "com.sun.jndi.fscontext.RefFSContextFactory" this is what Talend suggests as of this writing. In fact this value would come from IBM Websphere MQ tool itself. You can check this value when you try creating an initial context on your MQ Client or explorer
- Server URL: This is where your ‘.bindings’ file should reside for the tJMSINPUT to be able to perform correctly. It is not necessary that you should have created ‘.bindings’ file at this location, if it created else where, you can copy that ‘.bindings’ file to this location. Your file path should reflect like this "file:/C:/abcd/xyz/" note that the word ‘file’ should also be part of the value, ‘abc’ and ‘xyz’ are directories/subdirectories to reflect your path
- Connection Factory JNDI Name: You would typically get this value from your MQ admin, if not this is the value that you have given at the time of creating the ‘.bindings’ file
- Message Type: select Queue from the pull-down menu.
- Message From: enter the name of the Queue from where you intend to read your messages or if you have added a destination JNDI object while creating the ‘.bindings’ file, you can specify a JNDI destination name instead of the real queue name.
binding file and configuration.docx
