New messaging features include:
Support for the complete JMS 1.1 API.
Message-driven beans (MDBs) can receive message types other than JMS. A J2EE Connector Architecture (JCA) 1.5 resource adapter integrates messaging providers with the container.
Messages can be processed in the order in which they are received, even when multiple consumers access the same queue.
Duplicate messages can be ignored.
Application servers running on a mobile device can initiate pull and push operations; both online and offline modes are supported.
Header and system properties can be used to construct source or target queue addresses; for pull, only system properties can be used.
You can log in to the JMS provider using IIOP single sign-on scripts.
For JMS clients, a new initial context factory class com.sybase.jms.client.InitialContextFactory replaces com.sybase.jms.InitialContextFactory.
The com.sybase.jms.client.InitialContextFactory class performs JNDI lookups to resolve names that are not preconfigured.
The com.sybase.jms.client.InitialContextFactory class supports four provider URL forms:
iiop://host:port – uses
IIOP to access the message service.
jms-provider:jmsProviderName – uses
the named JMS provider.
run-server.server_name – uses
IIOP to access the message service, starts the server in-process
if it is not already running, and selects the server’s
first IIOP listener as the provider URL.
start-server.server_name – uses
IIOP to access the message service, starts the server out-of-process
if it is not already running, and selects the server’s
first IIOP listener as the provider URL.
See the EAServer Java Message Service User’s Guide.
