 | a) The benefits of the product's functionality in Version 1; and |
| b) How organizations can position themselves to take advantage of this next generation message broker. |
Climate
In order to survive in today's rapidly changing economic environment, businesses must rely more on other businesses, either through integration of their system activities and processes, or through mergers and acquisitions. Furthermore, the Internet and e-Commerce have made this need even more evident. Historical departmental and corporate boundaries are quickly becoming blurred. Businesses are starting to develop new strategic solutions by combining heritage or legacy applications with newer web technologies. At the same time, those applications demand inter/intra system communication with internal as well as with outside systems. Solutions aimed at business integration are not new, but in most cases these attempts have lacked the flexibility and scalability demanded by enterprise environments.
Why Enterprise Application Integration?
Many corporations in their past IT developments have been driven primarily by internal systemic or marketing needs. These projects were usually completed by disparate groups within the IT organizations using purchased software packages. The resulting systems, however efficient, were usually designed for specific departmental needs, not for use by other internal/external organizations.
Enter the Internet.
The Internet has forever changed the way businesses approach IT
development. Today, there is no such thing as a standalone system.
Companies are realizing that in order to compete, they must be able to
reach their customers in untraditional ways. Customers are no longer
willing to call a service center number and sit on hold or "push
button" their way through a voice response unit in order to obtain
information about their account or recently placed order. Enhancements
to existing systems or new component development must be approached with
a open, loosely coupled architecture in mind. Interfaces must be easily
maintained and must not require any rework when changes or additions are
needed.
An example of a MessageFlow:
Message Brokers
Asynchronous messaging has become the de facto standard for data interchange. Whether it's business to business, business to consumer or intercommunication between applications within an organization, messaging is becoming the solution of choice. In the beginning, message brokers were first introduced to ease the complexity of large messaging environments, and to simplify the network connections needed.
New language and message format support, XML and EDI. Import and export tools to aid developers. Combining Pub/Sub into the mainstream message broker functions. ODBC connectivity. Message flows to encapsulate even more process functionality in the message broker itself. Message flow sub-components can be reused as subsets of larger message flows.
Self-monitoring message broker components. A "watch dog" over the described broker domain configuration in order to ensure constant availability. Uses CORBA and underlying transport to provide assured message delivery.
Scalability
Broker domains provide better throughput, resource optimization and efficiency. A processing threading model designed for faster and more assured processing of input streams. Use of patented rule applying algorithm for faster throughput and processing of messages.
|
|||||||||||
|
|||||||||||
| Name | |
| Title | |
| Company | |
| Address | |
| Phone |