I would like to connect to the IBM MQ using a wmq jmsra resource adapter.
Am trying to connect to the IBM MQ server that is on version 8.0.0.5, which adapter can I use ?
Can I use adapter of version for example 7.5 ?
Problem is that for example with change from adaper 7 to 8 I also need to change version of jboss from 6 to 7 based on this :
https://access.redhat.com/documentation/en-us/red_hat_jboss_enterprise_application_platform/6.4/html/administration_and_configuration_guide/deploy_the_websphere_mq_resource_adapter
My cipher should not be a problem I think as I see that is supported by for example version 7.5
http://www-01.ibm.com/support/docview.wss?rs=171&uid=swg1IV66840
Also that I see that ibm is creating fixes for versions 7.5 etc
An IBM MQ 7.5.0.8 jmsra resource adapter can connect to an IBM MQ queue manager at a higher level such as v8.0.0.5.
IBM Technote "MQ 7.x, MQ 8.0 and MQ 9.0 compatibility with previous versions - including usage of CCDT files, JMS .bindings, SSL/TLS" states:
Compatibility statement:
WebSphere MQ V7.0, V7.1, V7.5, V8.0 and V9.0 queue managers and
clients inter operate with queue managers and clients from any
previous level of the WebSphere MQ or MQSeries products.
This means that ...
A 7.0, 7.1, 7.5, 8.0 and 9.0 client can connect to all queue managers, non-version 7, as well as version 7.0, 7.1, 7.5, 8.0 and 9.0
A 7.0, 7.1, 7.5, 8.0 and 9.0 queue manager can interact with all clients, non-version 7, as well as version 7.0, 7.1, 7.5, 8.0 and 9.0
Note however that IBM MQ v7.5 has an end of service date of April 30th 2018. I would recommend you use either v8.0 or v9.0 which have not had end of service dates announced yet. Newer MQ client versions can connect to older MQ queue managers. You can download a java only install of MQ 8.0 or MQ 9.0 jar files at the links below:
IBM MQ v8.0 Client
IBM MQ v9.0 Client
Note that to use TLS ciphersuites with a non-IBM JRE (ex: Oracle JRE) you will need to be at a minimum of the following levels of IBM MQ:
Version Maintenance Level
v7.5 7.5.0.5
v8.0 8.0.0.2
v9.0 9.0.0.0
Related
I have done everything possible from my end.
OS Linux data is coming from server.
but data of wildfly (i.e heap thread etc.) is not coming.
does anyone have template of wildfly 20?
There are several solutions widely available on the internet
Zabbix-JBoss-Agent
Zabbix_wildfly_eap_jboss_monitoring
WildFly (formerly JBoss) is a Java application and can be monitored with JMX agent
I would strongly recommend upgrading to a newer version of Zabbix, as version 4.0 will become unsupported on October 31, 2021.
I'm looking for dates until when patches for known vulnerabilities will be delivered for the products mentioned above. I found the same for RedHat's JBoss Enterprise Application Platform, but not for JBoss AS or Wildfly.
Here's an example.
Regarding JBoss Middleware, there is a product update and support policy.
For long-life products, JBoss offers Full support for 4 years, Maintenance support for 3 years and Extended-life support for other 3-6 years.
Although you can imagine JBoss engineers working on the underlying Widlfly software creating patches and solutions for all the time of the Full Support, there is not any guarantee. In addition, note that the version numbers of the JBoss EAP are not the same of the used by Wildfly.
The JBoss EAP v 7.0 (released in 2016, for Java EE 7) uses the Wildfly 9.x (alias "Kenny", released in 2015)
The JBoss EAP v.7.1Beta (released in 2017) uses Wildfly 10.x (released in 2016).
Today (September 6, 2017), reviewing the Issue Tracker for Wildfly, almost all the updated issues in the last week are related to the last versions: 20 are for the version 11.x, 3 for the 12.x-Beta, and 1 for the 8.x. Other 31 do not specify a version. All the resolved issues (9/9) in the last week are related to the version 11.x.
I think you must consider to use one of the last two GA versions of Wildfly. The community is more active in these versions. According to the Wildfly governance page, they deliver a new final major version in around a nine month cycle.
You don't get any guaranteed support for community projects like WildFly and JBoss AS. Commercial support is only available for commercial products like JBoss EAP.
I am using WebLogic Server 10.0 and would like to use JPA 2.0. I have found that there are compatibility problems between the two. I have found plenty of tutorials about getting JPA 2.0 to work with Weblogic 10.3.x. Is it possible to do the same for 10.0, or would using JPA 2.0 require a newer WebLogic version?
It is not possible to have JPA 2.0 support using WebLogic 10.0.
This is described in Oracle Document ID: 1091853.1
Does WebLogic Server 10.3 provide full support for JPA 2.0?
- WebLogic Server 10.3.4+ allows to enable full JPA 2.0 support.
- WebLogic Server 10.3.0 - 10.3.3 partially support JPA 2.0
More details in this thread: Oracle Community
Same question here: https://stackoverflow.com/questions/8172421/using-jpa-2-0-with-a-weblogic-10-0
I need to set the EAR server runtime for my WebSphere Application Server v6.1. I am not able to - I only get version 1.2, 1.3, or 1.4. My coworker uses the same server/IDE (IBM RAD 7.5.4) but sees '5.0' as an option, but I do not. Do you know why this isn't an option for me?
WAS 6.1 JavaEE level is 1.4, I would believe that the problem is on your coworker side.
See this chart for more detail http://en.wikipedia.org/wiki/IBM_WebSphere_Application_Server
The issue was that I wasn't using the latest version of WAS v6.1.
I have to set up a Hornetq Core-Bridge to a Hornetq 2.1.X Server, but I would like to use a more updated version on my side of the architecture (2.2.X). Is it compatible?
I haven't found info about it on documentation (as always btw, regarding to hornetq).
Obs: The 2.1.X Server is running on a JBoss AS, and mine is on stand-alone mode.
Until hornetq 2.2.2, hornetq didn't have version compatibility support. That means that you would need all your servers on the same version. (same as you would need for your clients).
After hornetQ 2.2.2 we offer version compatibility, however the client has to be older than the server. We don't test a 2.2.5 talking to a 2.2.2 server.
So, if the core-bridge is installed in a 2.2.2 talking to a 2.2.5, you would be fine.
a 2.2.5 talking to a 2.2.2.. probably not
A 2.1.X talking to 2.2.x.. definitely not.