Did you install the correct JMS java libraries in the Informatica server/bin directory (or other location in your LIBPATH environment variable)?
Try the JMS connectivity outside of informatica using the below test connectivity tool
If this also doesnt work, please involve your JMS admins to get it resolved.
In addition to the above tool, verify the configuration. Check the below:
Also make sure you copy all the required *.jar files either into "/server/bin/javalib" or add them into CLASSPATH.
I have opened Informatica SR some time back and I got above JMS testing tool from them too. I ran this tool and it gave me error as below.
JNDI API lookup failed: javax.naming.ConfigurationException: Unsupported scheme "eblcap98.xcelenergy.com" in provider URL "eblcap98.xcelenergy.com:7276:BootstrapTunneledMessaging"
javax.naming.ConfigurationException: Unsupported scheme "eblcap98.xcelenergy.com" in provider URL "eblcap98.xcelenergy.com:7276:BootstrapTunneledMessaging"
I contacted back Informatica Support and they told me that IBM WAS (Websphere Application Server) usually require that the JMS provider URL be set to the .binding file location. Something like below example:
JMS Provider URL: file:///D:/JNDI-Directory/WDI
I am not sure how to do this and my JMS administrator also told me that such option might be there for MQ JMS and not for WAS.
Please suggest me how to proceed on this.
Thanks Rajan, your answer was really helpful. I have copied the JAR files to the java directory. Now I copied it to /server/bin/javalib folder and re-started my job and it completed like a charm. I am able to send messages to the WAS queue.
Yes, the JMS Provider URL would look somewhat like file:///D:/JNDI-Directory/WDI for MQ JMS as the configuration part (a .binding file is created which would hold the queue/topic details). But the same is not necessary for WAS. WAS has totally different configuration.