Is it possible to programatically stop an MDB from listening to a queue in Weblogic 8.1?
I know this can be done in JBoss and later versions of Weblogic but I wasn't sure if it's possible in 8.x.
This is possible with Weblogic 9.x and Weblogic 10.x through the MessageDrivenEJBRuntimeMBean that exposes suspend/resume methods (see BEA WebLogic Server 9.0 API Reference or WebLogic Server 10.3 API Reference) as explained in this Thread: Suspending/Pausing a MDB's Consumption Programmatically. AFAIK, this feature has been introduced in version 9.0 and I don't know if it was backported to 8.1 (in a service pack or as a patch). You might want to check this with BEAOracle support.
You can undeploy the application that contains your MDB. You can use WLST to do that.
Related
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.
Our product will support IBM MQ7 and MQ8 based on client requirement. Now, we like to know latest client jar version that we may use for our application?
We would like to use JMS 1.1 specification. I have found following link for MQ 7.5 JAR-
http://www.ibm.com/support/knowledgecenter/SSFKSJ_7.5.0/com.ibm.mq.dev.doc/q120070_.htm
Is it sufficient if we use above mentioned client jar to connect MQ 7 and MQ 8 server?
Application will use JRE 1.7 and WAS liberty 8.5.5.9.
If you are using WebSphere Liberty as your application server, then you will need to the MQ JCA Resource Adapter (MQ-RA) to make use of MQ JMS messaging. Liberty (unlike traditional WebSphere Application Server) does not ship a copy of the MQ-RA, but you can download and install one pretty easily and then link to it from within the Liberty server's server.xml configuration file. Here's a link to explain how to do this:
http://www-01.ibm.com/support/docview.wss?uid=swg21633761
Now, Liberty can use a copy of the WebSphere MQ V7.5.0.5 (or later) Resource Adapter, which only supports the JMS 1.1 API, and the Liberty feature you will want to enable with that version is "wmqJmsClient-1.1".
However, I would suggest you consider the latest version of the IBM MQ-RA (at the time of writing this is V9.0.0.0). The MQ V8.0.0.3 and V9 RAs support both the JMS 1.1 "classic" API as well as the newer 2.0 "simplified" API. Therefore you can use the newer MQ-RA levels but your JMS 1.1 application will still work perfectly fine. If using a V8 or V9 IBM MQ-RA, then the Liberty feature to enable to is "wmqJmsClient-2.0".
The V7.5, V8 and V9 MQ Resource Adapters can connect to any MQ queue manager version; the major or maintenance versions between the JMS client and the MQ server do not need to match.
For reference, here are a couple of links I recommend reading over as well:
http://www.ibm.com/support/knowledgecenter/SSFKSJ_9.0.0/com.ibm.mq.dev.doc/q031610_.htm
http://www.ibm.com/support/knowledgecenter/SSAW57_8.5.5/com.ibm.websphere.wlp.nd.doc/ae/twlp_dep_msg_wmq.html
http://www.ibm.com/support/knowledgecenter/SSAW57_8.5.5/com.ibm.websphere.wlp.nd.doc/ae/rwlp_restrict.html
I hope this helps!
I have a Java application (which comunicate via JMS, connects using client mode) which need to support multiple versions of the websphere mq (v6,v7.1) (some clients want to remain on version 6 and others to upgrade to version 7). The problem can be solved if i will create two bundles with specific code/configuration for each version. But i want to avoid this. So there is a solution to avoid this problem?
For example to have the latest clients jar(v7) as dependency and work with older mq(v6) also or vice-versa?
Can somebody point me to some documentation which presents the compatibility between the client jars and mq versions.
Yes, MQ v7 clients can connect to MQ v6 queue manager. But note all features that are specific to V7 will not work when connecting V6 queue manager.
I would like remind you, MQ v6 is already out of support. You have to migrate to at least V7.0.1 and possibly latest fix pack.
My task to monitor the IBM Websphere through pmi client.Pmi client is an agent provided by the IBM to get MBeans and is running under IBM Java. I tried it to run under Sun java. But, it fails to create the Pmiclient. Did Anyone come across this issue?
The IBM JRE has slightly customized classes. This is unfortunately not uncommon with PMI (and also JMX by the way) when working with different WebSphere Application Server versions.
There are hacks around involving copying the relevant IBM implementations and running them with the Sun/Oracle JRE but I don't think that is valid according to the licensing terms. What you really should do is to use the IBM provided JRE.
If you want a riskless shortcut you will build an applicaton (perhaps EJB or servlets) that runs on the WebSphere Application Server and exposes the results from PMI via custom interface. For instance web service.
Anybody knows about a performance comparison for Tomcat vs Websphere app server's web container?
www.webperformanceinc.com provides such a comparison but it's very outdated, somebody knows if there is a newer one, say with Websphere v6.1 or v7?
Websphere uses Tomcat under the hood. It only adds some more Java EE capabilities (EJB and so on) and of course the IBM sausage over it, so I wouldn't expect Websphere to be much faster than Tomcat.