JMS 2.0 Server at PO

[ivomarquardt]

Good Morning

we use at our PO 7.5 the standard SAP JMS Server. Due to errors in version 1.x we would switch to version 2.x. This should allow using multi subscription of JMS clients at one JMS Channel. But we couldn´t find details about JMS Server 2.0 in PO at SAP´s Launchpad. So could anybody offer some hints about this problem?

Kind regards

Ivo

[vadimklimov]

Hello Ivo,

In PO 7.5, out of the box JMS adapter is compatible with JMS 1.x - if you want it to support JMS 2.0, please follow recommendations provided in SAP Note 2310443.

Regards,

Vadim

[ivomarquardt]

Hello Vadim

we found note 2310443. But after a discussion with SAP Support we noticed that this note is a description how to implement JMS 2.0 client drivers in SAP PO....

So it does not resolve our problem. We need a Server which provides this services at SAP PO side due to the fact that at SAP PO our JMS Server run.

kind regards

ivo

[vadimklimov]

Hi Ivo,

Sorry, I was confused, I thought you question compatibility of JMS adapter of PO with JMS version 2.0, but it now looks to me like the question is about application server Java JMS Provider. SAP NetWeaver Application Java 7.5 is compliant with Java EE version 5, hence it is compliant with JMS version 1.1, but not 2.0.

Regards,

Vadim

[ivomarquardt]

Is it possible to use a higher Java EE version which supports JMS 2?

[vadimklimov]

No, not something I would be aware of in scope of the application server. The application server is compatible with the certain version of Java EE platform specification (which is, in case of NetWeaver Application Server Java 7.5, Java EE version 5). And the specific version of the Java EE platform specification lists certain versions of Java EE components and technologies (individual components' specifications) that are contained in it - for example, for Java EE 5, this is JMS version 1.1. JMS version 2.0 was only introduced in Java EE version 7, which SAP NetWeaver Application Server doesn't implement currently.

What you can consider as a workaround / alternative, is to run a standalone JMS broker service (and not to make use of JMS Provider embedded in SAP NetWeaver Application Server Java in your integration scenarios), and use it in scenarios requiring JMS 2.0 functionality. This adds extra dependency and maintenance efforts, since the JMS broker has to be fault tolerant, reliable and support expected load, provide failover capabilities and proper administration and monitoring toolset, but provides you with the demanded functionality. There are multiple freeware and commercial products on the market that can fulfil this kind of requirement - and you might want to check internally within your organization to see if any of them is already in use by another departments and can be utilized for your scenarios.

Regards,

Vadim