| Overview | Package | Class | Deprecated |
The 5620 SAM-O JMS interface has evolved over several releases. This page identifies changes to the JMS interface. Changes are divided into two sections, event changes and interface changes. They are listed at a high level, detail of the change is defined in the developers guide. Please review the JmsTest class for examples on how to handle backwards compatibility for changes identified below.
Release SAM 5.0 R6 to SAM 5.0 R7
logFileAvailableEvent - New event sent on the 5620-SAM-topic-xml-file topic during accounting statistics collection to notify clients that use the registerLogToFile functionality. The message includes the file location, server address and router Id.
None.
Release SAM 5.0 R2 to SAM 5.0 R3
ManagedRouteEvent - New event sent by the Control Plane Aware Manager to indicate that a managed route was added.
None.
Release SAM 5.0 R1 to SAM 5.0 R2
None.
- eventName - Event name that appears in the body (not properties, it is not a filterable field) of XML messages is deprecated.
Release SAM 4.0 R9 to SAM 5.0 R1
- ExceptionEvent - New event sent by the policy to report the policy distribution errors.
- StatsEvent - New event sent during polling/accounting stats (one sent at the start, one at the end) that identifies the type and NE.
- Object topic - Using object based messaging (Object topic - 5620-SAM-topic) is no longer allowed.
- Jar changes - All previous jars that were required have been replaced by one jar (samOssJBoss.jar, samOss.jar or samOssNoJms.jar). This jar must be used in 5.0.
- Encapsulated XML Messages - All Text Messages are encapsulated in ObjectMessages. The text message can be easily unwrapped and processed the same way as previous SAM XML Messages. This change allows all XML messages to be compressed to save resources. Note: The header properties will be contained in the ObjectMessage, not the Text Message.
- ExternalContext Reference - The lookup for the connection factory has changed. JMS is now an external resource to SAM and therefore must be looked up through SAM. This does hide location changes for JMS.
- StateChangeEvent JmsMissedEvents - JMS Missed Events messages appear for durable and non-durable subscribers if the subscribers can not keep up.
- KeepAliveEvents no longer stored - Keep alive events will no longer take up space for durable subscribers listening to them. If the subscriber is no longer connected but still subscribed, no keep alive messages will be added to persistent storage.