O'Reilly - Java Message Service

Java Message Service
JMQ does not support firewall tunneling. JMQ provides a username/password
authentication support, but doesn't provide any authorization (access control) for
administered objects.
9.5.2 Next Version
Version 2.0 of JMQ will be a complete rewrite and will no longer be based on Enron's
InterAgent product. JMQ will be written in Java, which will increase the number of
platforms the server can run on. JMQ 2.0 will support the optional JMS Application Server
Facilities, JDBC for persistence, JMS XA interfaces for two-phase commit, server
clustering, HTTP/HTTPS firewall tunneling, authentication, some access control, and
improved Admin GUI console.
9.6 BEA: WebLogic Server
BEA was one of the first (and most important) companies to introduce a full-fledged EJB
container. Their approach to JMS has been to add a JMS server to their existing product,
WebLogic Server.
9.6.1 Version 5.1
WebLogic Server is an application server that includes an EJB container, servlet, and JSP
container and other facilities. In addition, WebLogic includes a JMS service provider that
was introduced in version 4.5.1. In earlier versions, WebLogic provided a proprietary
messaging system called WebLogic Events, which is still supported but is not the basis of
their JMS implementation.
WebLogic's JMS service is compliant with JMS 1.0 and provides support for both the
pub/sub and the p2p JMS messaging models. The server and clients are written in Java and
therefore run on any platform with a Java Virtual Machine ( JDK 1.1 or higher).
WebLogic uses a centralized architecture based on the hub-and-spoke model. Clustering of
JMS services is not currently supported, so load balancing and scalability are limited to a
single server instance. The WebLogic server provides administrators with a GUI console
that includes support for configuring JMS administered objects.
Persistent messages are supported through any relational database that can be accessed
with JDBC. WebLogic does not support 2PC, but it does support coordinated transactions
between their EJB container and JMS clients, provided that the database used for JMS
persistence is the same database used by the enterprise beans.
WebLogic supports HTTP 1.1 tunneling (as well as HTTPS) which can be used to tunnel
through both client-side and server-side firewalls. Support for tunneling is one of the core
services provided by the WebLogic server. For authentication and access control,
WebLogic supplies a pluggable "realm" Service-Provider Interface and a set of default
realms (LDAP, NT, Unix, and a simple file-based realm). WebLogic supports SSL,
including client-side certificates. WebLogic also supports access control lists on topics and
queues; access lists control who may send or receive messages to a particular destination.
Access control is used on message delivery, and when establishing consumers. It can also
be used in their JNDI naming service to prevent access to administered objects.
139