Is IBM Webshpere MQ 6 compatible with JBoss EAP 6.2? - ibm-mq

I was trying to deploy a component on JBoss EAP 6.2 serever.My application listens to IBM Websphere MQ 6.I would like to know if MQ 6 is compatible with JBoss 6.2

There aren't any known issues with using IBM MQ 6 with JBoss EAP 6.2. Neither Red Hat nor IBM officially test and support this configuration, however.

Related

Can I upgrade my MQ version to 9.0 while still using WAS 8.5.5?

My employer has an application running on WAS server 8.5.5. It uses MQ client adapter to connect to a MQ setup on version 7. Now my employer is upgrading to version 9 on the MQ but want to retain the WAS server at 8.5.5. Is this possible? In one of the IBM articles I saw the following:
The IBM MQ Version 9.0 resource adapter cannot be deployed into earlier versions of WebSphere Application Server, as these versions are not Java™ EE 7 certified.
If your question is specifically on traditional WAS (rather than Liberty profile), then the answer is yes.
tWAS bundles a level of MQ resource adapter, and this bundled RA inherits the support lifecycle of the application server. [This support does not apply to other versions of the MQ resource adapter that have been manually applied to the tWAS installation, and so using the bundled RA is generally recommended.]
Any supported MQ client can communicate with any supported MQ queue manager, as either side will negotiate the version of MQ communication flows in use down to the mutually appropriate level. This means that the MQ 7.1 resource adapter can communicate with a version 9.0 queue manager, although of course any connections that this client makes will not be eligible to use functionality added to the product after 7.1.

Stadlaone-full set up for wildfly

i'm tryin to run an app that runs on jboss EAP , on jboss Wildfly , but i'm having problems with the standalone-full.xml because some services like hornetq aren't available on Wildfly
is there a possible way to migrate from eap to wildfly?
any help?
This depends on your app.
Wildfly 10 ships with ActiveMq rather than HornetQ.
If your app uses standard JMS then you can configure the WF10 standalone-full to have the same JMS endpoints as your old deployment. If however your app is using the HornetQ specific client you will have to do some more work. ActiveMQ artemis integrates HornetQ protocols but it probably won't work without some trial and error in the configuration.
I would suggest starting with standalone-full.xml from Wildfly 10 and compare it with your JBoss EAP configuration. There should be an analog for each service you need. Once that is set try running your app and see what happens.

Does JBOSS EAP 6.3 support spring + websocket?

I am trying to implement websocket using JBOSS and I understand for enterprise edition websockets are supported from JBOSS EAP 6.3. I am also trying to integrate websockets with spring. I was wondering, does JBOSS EAP 6.3 supports integration of websockets with spring?
I have followed and configured all the steps mentioned at
http://spring.io/guides/gs/messaging-stomp-websocket/
except that, the application is deployed in JBOSS EAP 6.3. When I execute and try to connect, I am hitting with the following error.
GET http://localhost:8080/hello/info 404 (Not Found)
sockjs-0.3.4.min.js:27 u._startsockjs-0.3.4.min.js:27 (anonymous function)
stomp.js:134 Whoops! Lost connection to undefined
the Atmosphere Framework supports JBoss 6.3. Just take a look at this:
https://github.com/Atmosphere/atmosphere/wiki/Installing-JBoss-WebSocket-Support
Just jump on our mailing list for more information.
-- Jeanfrancois

JMS Client for WebSphere Application Server 8.5.5 and 7.0.0.13 with Oracle Java 8

I am using Java JMS client to connect to Websphere Application Server 8.5.5.0 and 7.0.0.13. I using following set of jars in classpath of client:
ibmorb.jar, ibmorbapi.jar, com.ibm.jaxws.thinclient_.jar, com.ibm.ws.ejb.thinclient_.jar, com.ibm.ws.sib.client.thin.jms_.jar.
It works fine with Oracle Java 7. But with Oracle Java 8 it gives java.lang.NoClassDefFoundError: sun/io/MalformedInputException during JNDI lookup. The ibmorb.jar is using sun.io.MalformedInputException class which is no longer shipped with Java 8. I also tried using com.ibm.ws.orb_.jar in place of ibmorb.jar but got same exception.
What is the suggested approach to solve this problem?
I tried with ibmorb.jar from optional IBM Java Developer Kit 7 provided with 8.5.5.3 and it worked. I did not find standalone installer for IBM Java 7 and I don't want to upgrade the AppServer on server side. If using jars from IBM Java 7 is the only option then how can I get the standalone IBM Java 7 installer or IBM Java 7 for 7.0.0.13?
You can get IBM JDK from here - http://www.ibm.com/developerworks/java/jdk/index.html

Version of MQ in WAS 8.5.5

I'm trying to migrate an EJB application from WAS 6 to WAS 8.5.5 and seems to not work entirely, doesn't respond correctly to the message-selector filter I'm using in ejb-jar.xml.
Can somebody tell me the version of MQ server supported in WAS 8.5.5 ?
The version of the MQ client (in the MQ Resource Adapter form) in WAS 8.5.5 is MQ 7.1. This page provides the list of the exact version of the client for each WAS level: https://www-304.ibm.com/support/docview.wss?rs=171&uid=swg21248089
The MQ server supported can be any currently supported version i.e. you can use MQ Server 8/7.5./7.1/7/6 etc with a MQ 7.1 client. However, there are features that might not be available if you are using a certain combination client/server.
For your issue it is probably best to post a new question with the actual error you are seeing.
If you have a Websphere MQ full installation, MQ 8.0 is already out but please check the following information about WAS 8.5 and MQ 7.5: http://www-01.ibm.com/support/knowledgecenter/prodconn_1.0.0/com.ibm.scenarios.wmqwasmig2v85.doc/topics/ts_mqv7cons.htm?lang=el
There are two alternatives depending on what you want to migrate before the other : MQ or WAS.

Resources