Show TOC Start of Content Area

Background documentation Checklist for JMS Development Locate the document in its SAP Library structure

Use this checklist to avoid common errors in Java Message Service (JMS) development.

JMS Development

This graphic is explained in the accompanying text

Do you use the default connection factories provided with the J2EE Engine?

We recommend that you use the default connection factories provided by the J2EE Engine, located in jmsfactory/default/TopicConnectionFactory or jmsfactory/default/QueueConnectionFactory.

This graphic is explained in the accompanying text

Did you close the JMS connection correctly?

When you implement the onException() method, do not close the client connections that were used up to that moment. The JMS Provider takes care of that. The client has to get the objects he or she requires from the factory that was already obtained.

This graphic is explained in the accompanying text

Are you using message delivery limitation on a point-to-point scenario?

When using message delivery attempts limitation, remember it is supported only for point-to-point scenarios.

This graphic is explained in the accompanying text

Are you using more than one durable subscriber?

When using durable subscribers, remember that a durable subscription can have only one active subscriber at a time.

This graphic is explained in the accompanying text

Are you applying security restrictions over the JMS connections?

No encryption is available on the JMS communication. Even though the binary format is hard to decode this may imply a security risk if messages contain sensitive information.

 

End of Content Area