<% if Request("name") = "" then %> Introduction

BEA MessageQ is easy-to-use, fast, and reliable message software that allows applications to communicate using the industry-leading queued message bus technology. A proven and widely deployed middleware solution for distributed enterprise applications, BEA MessageQ allows the reliable exchange of guaranteed application messages across heterogeneous platforms. BEA MessageQ provides a robust application integration architecture for building high-performance message-based applications using multi-mode communications.

BEA MessageQ offers the following features:

• Interoperability with IBM platforms via TCP/IP, LU6.2.

• Publish and subscribe

• Large message size-up to 4MB

• Self-describing messages for automatic data conversion between heterogeneous platforms

• Connectivity to BEA Tuxedo, BEA eLink Platform, MQSeries, Legacy Applications, SAP R/3, and more

Benefits

• Unmatched Performance - Up to thousands of messages per second

• Flexible - Synchronous as well as asynchronous message delivery

• Robust - Recoverable messaging on all BEA MessageQ clients and servers

• Open - Broadest platform support: UNIX, Windows, Win NT, OpenVMS, IBM, and Unisys mainframes

• Easy - Common API, FML support

Operating Systems

MessageQ product runs on VMS, UNIX, Windows 95 and NT.

<% elseif Request("name") = "Feature" then %> Features

Synchronous and Asynchronous Messaging
Application developers can select the messaging style that best serves their applications. While one-way, asynchronous messaging is the typical usage scenario for MessageQ, it is possible to send messages using the familiar synchronous request/response paradigm.

Publish and Subscribe
Publish and subscribe allows one message to be sent to several receivers simultaneously. This simplifies application coding because developers do not have to be aware of the number, location, or Readiness State of each recipient. This capability increases the efficiency and performance of a distributed application since a single message can reach several recipients at once. At the same time, publish-and-subscribe messaging reduces the network traffic of an application since messages can be generated on a proactive basis, with the publisher sending a message to all subscribers when a predefined event occurs. This eliminates the subscriber's need to constantly "query" the publisher for relevant information, cutting down on the number of redundant messages being generated by the application. More users can be supported on the same system - increasing the application's return on investment.

Self-describing Messages
Self-describing messages allow automatic data marshaling between platforms that may use different data formats. Receiver programs can easily "decode" the message because it contains the information needed to decipher the contents.

Global Naming
Global naming allows queues to be visible network-wide, which facilitates systems configuration and other operations. Programs can send and retrieve information without concern for a queue's network location or identifier.

Message Selection
The message selection feature lets application developers use selection filters based on message type, class, sending application, and message data contents. It increases efficiency and performance by enabling applications to process only those messages that meet predefined selection criteria.

Message Recovery Services
Message recovery is a facility that prevents loss of message data. Queues are housed on disk rather than in volatile main memory. If a failure occurs in an application, on a communication line, or on the system where the application is running, data in transit is written to disk and preserved for delivery after the failed elements recover.

Large Message Size
Support for messages up to 4MB eliminates the need for message partitioning.

BEA MessageQ Monitor Utility
This utility helps developers and system managers monitor and control the BEA MessageQ environment. The error logging utility displays and captures informational, warning, and error messages during processing.

Correlation IDs
BEA MessageQ contains support for correlation IDs. Correlation IDs are user defined tags that are associated with a request message and are returned with any response thus allowing applications to match multiple outstanding requests against a single incoming response. The correlation ID structure is compatible with BEA Tuxedo's and BEA eLink Platform correlation ID. Providing connectivity to BEA Tuxedo and BEA eLink Platform gives BEA MessageQ users access to BEA Tuxedo/BEA eLink Platform services and transactional queuing using their existing programs.

FML Support
BEA MessageQ supports FML (Field Manipulation Language). Specifically, this includes providing libraries and files that enable developers to build FML based applications. BEA MessageQ will be FML aware so it can properly exchange FML messages and enforce appropriate FML semantics. Applications using SDM messages will be converted to FML. Since FML is a widely accepted full-featured self-describing message format, BEA Tuxedo/BEA eLink Platform and BEA MessageQ customers can now use a standard format in building applications.

<% elseif Request("name") = "Info" then %> More Info

Application Integration
BEA MessageQ can be used for batch or real-time applications in different locations and on different platforms to exchange messages asynchronously, so that they can operate as a single, mission-critical operation. The messages are guaranteed. Since communication uses store and forward methodology, the receiving computer program need not be ready to receive or even be connected when the message is sent. Message delivery is the basis on which this style of application integration relies, and can be used with systems on OpenVMS, UNIX, Windows NT, SAP R/3, Unisys, and IBM Mainframes legacy systems and MQSeries.

Application Portability
BEA MessageQ is a powerful development environment that helps you integrate distributed applications across a wide range of hardware platforms and operating systems. This easy-to-use software enables messages to be sent from one application to another through an advanced queuing bus. Consequently, your developers can concentrate on building mission-critical applications that equate to success for your business.
BEA MessageQ uses a common API for all environments, thus allowing applications to move easily using systems from different vendors as well as homegrown applications. For example, if you develop BEA MessageQ applications for Intel PCs running Microsoft Windows NT, the same application programs will run on all major UNIX systems by recompiling and re-linking the applications in their target environment.
The BEA MessageQ API forms a layer between the application and the operating system and network environment, ensuring application portability and shielding applications from changes in underlying software. The development team is now free from dealing with the low-level details of a multi-vendor environment.

Guaranteed Message Delivery
BEA MessageQ provides a suite of distributed communication features such as publish and subscribe priority selection, recovery, and guaranteed delivery. If the message recovery service is used, messages will be placed in a journal on local or remote disks prior to their delivery. When using message recovery, if a communications line is down or if the process or node "crashes," the message is automatically resent later. If the message has reached a remote disk and the target system goes down, the message is preserved for delivery after reboot of the system. The message bus, rather than the application, is responsible for delivery of messages. Distributed communications is achieved based on a peer-to-peer mechanism called the Message Queuing Bus. This message bus serves as a "data highway" that can be used to transfer messages between processes. Messages can be a request for service across the network or a request for information needed by a distributed application.

Investment Protection
Applications written with BEA TuxedoŽ, or deployed on BEA's enterprise integration engine, BEA eLink Platform, can now send messages to BEA MessageQ queues using standard BEA MessageQ verbs and have those messages automatically and transparently redirected to BEA Tuxedo or BEA eLink Platform queues and services. Similarly, BEA Tuxedo or BEA eLink Platform programs can send messages to their standard queues and services using standard BEA Tuxedo/BEA eLink Platform functions and have those messages automatically and transparently redirected to BEA MessageQ queues. Verb/function behavior and associated responses and return codes all continue to operate without any change. BEA MessageQ applications receiving messages originating in the BEA Tuxedo or BEA eLink Platform space will also be able to respond to these messages and have the response find its way back to the response queue specified by the original BEA Tuxedo/BEA eLink Platform application and vice-versa.
Application developers will be able to do all of this without formatting or sending additional control messages to set up run-time sessions or connections between BEA MessageQ and BEA Tuxedo/BEA eLink Platform. All mapping of BEA MessageQ queues and BEA Tuxedo or BEA eLink Platform resources will be done automatically making it transparent to users.
On the other hand, message queuing systems do not inherently allow applications to send messages directly to queues owned and managed by different message queuing systems. For example, BEA MessageQ applications cannot place messages on MQSeries queues and vice-versa without a special interface.

Connectivity to Mainframe Systems
BEA MessageQ MQSeries Connection provides a seamless connection to MQSeries that allows message exchange between BEA MessageQ and IBM MQSeries. Application developers can write their applications using either message queuing system. BEA MessageQ MQSeries Connection makes sure that messages are properly passed between the two message queuing systems, and that the message header information is in the proper format for the target application. BEA MessageQ MQSeries Connection solves the integration problem by allowing messages to be passed seamlessly between the two queuing systems.
BEA MessageQ LU6.2 services allow BEA MessageQ applications running on an OpenVMS platform to exchange messages with cooperating applications on an IBM host via an appropriate gateway system running DECNet or TCP/IP. BEA MessageQ MVS Client provides application developers yet another way to integrate their MVS mainframe environments with distributed heterogeneous systems. BEA MessageQ MVS Client, with support for MVS CICS and MVS batch processing, provides guaranteed message delivery between IBM mainframe applications and other applications running on any BEA MessageQ supported platforms by means of a direct TCP/IP network connection.

Simplified Application Development
In addition to its advanced communications capabilities, BEA MessageQ also provides application development tools including testing and debug facilities. Distributed client/ server applications based on BEA MessageQ can also benefit from its built-in system management utilities. The BEA MessageQ monitor helps developers and system managers optimize their system configurations, while the error logging utility helps troubleshoot system problems.

<% end if %>