JBOSS-BM WebSphere MQ-ACTIVEMQ

It programmer development Essentials-all kinds of resources download list, history of the most IT resources, personal collection summary.

1. After JBoss was acquired by Red Hat, JBoss messaging was released as the default JMS provider instead of JBOSSMQ, but currently jboss messaging is in bug fix mode, JMS is fully supported by HORNETQ.

2. IBM WebSphere MQ

IBM WebSphere MQ is the cornerstone of IBM's business integration and is one of the leading products in the messaging middleware market for more than more than 10 years.

The value of WebSphere MQ as a messaging middleware is its ability to solve it-related business problems and provide reliable messaging mechanisms. The features provided through WebSphere MQ are:

-No time-bound messaging-applications and Web services can exchange information freely without worrying about whether an application or service is valid when communicating. For example, you can enter an order during the day and send it to the order execution system for processing, but the Order fulfillment system can batch the order at night. This is especially important when an application that is receiving messages is temporarily invalid.

Ø ensure message delivery-once the information is created, WebSphere MQ has the responsibility to properly send it.

Ø trading Support-Typically, exchanging a message between apps is not enough, often a set of messages. For example, an order entry program typically publishes a message for each entry in the order, rather than posting the order as a message. If a message error occurs before a set of messages are fully processed (for example, the first 4 in 10 messages), you must roll back this part of the message (1th through 4th) before you can guarantee that a full set of messages will be republished when you start again. This mechanism is often summed up as supporting work units.

Ø Parallel processing of information delivery-because many background applications are also valid for new users (such as customers entering the order system via the Web), these applications should not disappoint customers. For example, having a long wait for a customer during an order process can make the customer very frustrated. In a messaging environment, this delay is reduced because the message is not sent directly to the application but is placed in the queue. Once the message is submitted to WebSphere MQ, the app resumes interaction with the user.

Ø Secure Messaging-the ability to use high-level security to transfer risks inherent in high-value/high-risk exchanges. WebSphere MQ supports industry-standard SSL and provides an extended, secure version of Advanced security feature requirements.

Ø consistent programming Interface--java The Messaging service is the due process interface contained within the Java EE Standard specification. It is recommended that you use the JMS interface when deploying new information due to the program, but you can use the MQ interface (MQI) for businesses that are ready to adopt non-Java applications and already use a large number of non-Java applications. The programming interface is a multi-platform and user-friendly interface.

Ø application is independent of network or system failure-the application uses either of the program interfaces (JMS or MQI) to send and receive messages through WebSphere MQ. WebSphere MQ provides most of the complexity of handling messaging, which means that there should be programming that focuses on dealing with business issues rather than IT infrastructure and network issues.

Ø efficient utilization of system resources-when users of different platforms use cluster operations, they can develop underutilized resources or reduce platform costs.

Ø scalability-can be scaled horizontally or vertically through clustering. You can increase the message processing capability on multiprocessor platforms by adding additional queue managers (such as adding one for each processor) or by architecting the cluster on multiple platforms. Since WebSphere MQ can be deployed on all common platforms, a desktop-based implementation can also grow into a host-platform-based implementation.

Ø file Transfer-through WebSphere MQ information, the file transfer should allow you to send and receive any format and any type of file in the format of WebSphere MQ messages. These files include images, documents processed by word, spreadsheets, reports, letters, memos, charts.

IBM WebSphere MQ products enable applications to communicate with each other through networks of different components such as processors, subsystems, operating systems, and communication protocols. For example, IBM WebSphere MQ supports more than 35 different operating systems.

IBM WebSphere MQ supports two different application programming interfaces: Java messaging Service (JMS) and Message Queuing interface (MQI). On the IBM WebSphere MQ Server, the JMS binding method is mapped to MQI. The application is directly associated with its local queue manager by using MQI for a conversation, and MQI is a set of calls that require the Queue Manager to provide services. The attraction of MQI is that it only provides 13 calls. This means that it is a very easy-to-use interface for application programmers because most of the hard work will be done transparently.

3, ActiveMQ

Key features offered by ACTIVEMQ include:

1. Write clients in multiple languages and protocols. Languages: Java, C, C + +, C #, Ruby, Perl, Python, PHP. Application protocol: Openwire,stomp REST,WSNOTIFICATION,XMPP,AMQP

2. Full support for JMS1.1 and the Java EE 1.4 specification (persistence, XA messages, transactions)

3. Support for spring, ACTIVEMQ can easily be embedded into the system using spring, but also support the features of Spring2.0

4. Tested by common Java EE servers (such as Geronimo,jboss 4,glassfish,weblogic), with the configuration of JCA 1.5resource adaptors, Allows ACTIVEMQ to automatically deploy to any compatible Java 1.4 Business Server

5. Support multiple transfer protocols: In-vm,tcp,ssl,nio,udp,jgroups,jxta

6. Support for high-speed message persistence through JDBC and journal

7. Designed to ensure a high-performance cluster, client-server, peer-to-peer

8. Support Ajax

9. Support for integration with axis

10. It is easy to call the embedded JMS provider for testing

The ACTIVEMQ official website gives the advantages of ACTIVEMQ contrast JBOSSMQ:

ØACTIVEMQ runs well in any JVM, not in the JBoss application server

ØACTIVEMQ implements a very numerous cross-language client (languageclients)

ØACTIVEMQ supports a variety of different co-protocols such as Ajax, REST, Stomp, OPENWIRE,XMPP

ØACTIVEMQ supports a number of features, such as message Groups, Exclusiveconsumer, Composite destinations, Advisory message

ØACTIVEMQ provides highly reliable connections with configurable (configurable) auto-reconnect

ØACTIVEMQ has very good spring support (Spring supports)

ØACTIVEMQ supports distributed destinations across networks

The

Ø        activemq is very fast, typically 10 times times the JBOSSMQ.