Reliability Improvements in JMS (New) 

Use

In SAP NetWeaver PI 7.1 there are several improvements to the JMS Provider. They concern the reliability and the performance of the message delivery.

JMS Store and Forward

You can now deliver messages reliably between applications that are distributed across two clusters using the JMS Store and Forward (SAF) function. You have to create a SAF Agent using the jms-resources.xml or the SAP NetWeaver Administrator. The SAF Agent is responsible for delivering any messages received on the local destination to the remote destination defined in the deployed application. In case of network disruption or system failure, the SAF Agent stores the messages in an error destination on the local cluster.

More information: Using JMS Store and Forward

Error Destinations

The purpose of the error destinations is to handle dead messages, that is, messages that are not successfully delivered to a consumer. You have to configure an error destination for each destination or use the default one – sapDefaultErrorQueue.

More information: Handling Dead Messages

JMS Virtual Providers Distribution

There is a new property of the JMS Provider service, hostMultipleVPs, which configures the distribution of the JMS Virtual Providers. If its value is true, the cluster node can host more than one Virtual Provider. Otherwise, the number of the Virtual Providers hosted by a node is limited to one.

More information: Creating and Configuring JMS Virtual Providers

General Availability Monitor

In SAP NetWeaver PI 7.1 there is a new monitor, the General Availability Monitor, concerning the availability of the JMS Provider and the message latency.  

More information: Managing JMS Server Configuration