O'Reilly - Java Message Service
O'Reilly - Java Message Service
O'Reilly - Java Message Service
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
<strong>Java</strong> <strong>Message</strong> <strong>Service</strong><br />
iBus//<strong>Message</strong>Bus uses IP multicast, so clustering is not applicable; JMS clients in<br />
iBus//<strong>Message</strong>Bus are peer-to-peer. iBus//<strong>Message</strong>Bus also provides a protocol<br />
composition framework that allows other protocols to be implemented and integrated by<br />
third parties. iBus//<strong>Message</strong>Bus doesn't provide any administration or configuration tools -<br />
configuration for each JMS client is based on a local text file conforming to the<br />
java.util.Properties format.<br />
iBus//<strong>Message</strong>Bus doesn't provide persistence. Only local transactions are supported, so<br />
iBus//<strong>Message</strong>Bus can't participate as a resource in a two-phase commit.<br />
iBus//<strong>Message</strong>Bus provides support for HTTP tunneling, but only between two dedicated<br />
JMS clients. Client authorization (access control) is supported by a plug-in, which can be<br />
replaced by the customer to integrate the JMS application into existing systems. SSL is<br />
supported, including authorization using certificates, which can be made available to the<br />
authorization plug-in.<br />
9.4.2 iBus//<strong>Message</strong>Server 4.1<br />
The iBus//<strong>Message</strong>Server product is based on a centralized message server that uses a huband-spoke<br />
model. It was developed for JMS and supports both the pub/sub and p2p<br />
messaging models.<br />
iBus//<strong>Message</strong>Server is compliant with the JMS 1.0.2 specification. The JMS clients for<br />
iBus//<strong>Message</strong>Server are written in <strong>Java</strong> and can be run on JDK 1.1 or 1.2 ( <strong>Java</strong> 2) Virtual<br />
Machines. The iBus//<strong>Message</strong>Server is also written in <strong>Java</strong> and can be run on any platform<br />
with a JDK 1.2 ( <strong>Java</strong> 2) Virtual Machine.<br />
iBus//<strong>Message</strong>Server does not support clustering or fail-over, although it is fault tolerant,<br />
allowing the client to reconnect transparently after a timeout is reached. It supports<br />
firewall tunnelling using SSL and HTTP. iBus//<strong>Message</strong>Server is also built on top of a<br />
protocol composition framework that allows other protocols to be implemented and<br />
integrated by third parties. The iBus//<strong>Message</strong>Server provides a proprietary XML<strong>Message</strong><br />
type that takes either XML text or a DOM tree as a payload. It offers an administration<br />
API as well as command-line and GUI administration and configuration tools.<br />
This product uses a proprietary file-based storage or, optionally, JDBC for persistence.<br />
Only local transactions are supported, so iBus//<strong>Message</strong>Server cannot participate as a<br />
resource in a two-phase commit.<br />
iBus//<strong>Message</strong>Server provides HTTP 1.0 and HTTPS client- and server-side firewall<br />
tunneling. Access control and SSL are supported.<br />
9.4.3 iBus//Mobile 1.0<br />
Softwired AG also offers support for wireless JMS clients with its iBus//Mobile product.<br />
iBus//Mobile is used by JMS clients on hand-held devices like cell phones and pocket<br />
organizers that work with iBus//<strong>Message</strong>Server. iBus//Mobile can run on wireless devices<br />
running PalmOS, EPOC, Symbian, or Windows CE.<br />
137