What is OPENMOM?

OpenMOM has been designed to provide effective, easy-to-implement, easy-to-use and easy-to-manage communications between heterogeneous software components.
Using OpenMOM, organizations can easily make use of existing client-server and legacy applications at an individual component level to provide services to in-house clients or web users.

OpenMOM enables heterogeneous applications, developed with a wide variety of 4GL tools or languages, to immediately communicate with minimal programming. Using OpenMOM, custom applications are easily de-composed into unique intelligent components, such as processing requests or data delivery services. These components then cooperate with each other thru OpenMOM's message brokers. For example, a desktop service request created with Visual Basic or JAVA can transparently request an application/data service created using OpenROAD, Powerbuilder or Oracle development software, with no re-development.

The OpenMOM Message Broker provides highly reliable and scalable communications thru an easy-to-use programming interface which eliminates the need for lengthy consulting and re-engineering projects, while enabling straightforward cooperation between custom applications.

What are OPENMOM's Benefits?

OpenMOM leverages investments in installed applications to rapidly deploy upgraded or new application services,
without costly and time-consuming development projects.

¥ Using OpenMOM, today's applications can provide the building blocks of tomorrow's component systems. With OpenMOM, any application request or service can be utilized as an independent component. The OpenMOM Message Broker enables these components to communicate with each other as peers, regardless of their original intent. Communication can occur between components on a one-to-one, one-to-many or many-to-many basis.

¥ OpenMOM's interfaces appear as simple extensions to the developer's preferred language, enabling rapid prototyping and deployment. Whether the developer prefers Java, C++, Visual Basic or other, OpenMOM programming interfaces will appear as a familiar environment. There is no need for training in new development paradigms.

¥ The OpenMOM Message Brokers effectively insulates components from the processing environment, acting as a universal translator. OpenMOM's component cooperation architecture masks differences in network, platform, language or database, enabling components to work together without complex re-wiring. As a result, OpenMOM removes the barriers between incompatible development environments. Virtually any application can communicate with any other application at a component level, thanks to OpenMOM's advanced self-describing object technology.

OpenMOM's dynamic environment makes it easy for applications to evolve as businesses do.
OpenMOM eliminates issues surrounding versioning and compatibility.

¥ OpenMOM's dynamic processing environment makes it easy to change or enhance applications in real-time. There's no need for lengthy re-engineering projects or down-time while' new or changed application capabilities are re-loaded. New or enhanced services can be transparently brought on line, minimizing ongoing maintenance costs.

¥ OpenMOM's dynamic environment also enables easy changes to application and system configurations based on processing needs. For example, if a company needs to dedicate more processors for a specific service to enhance performance during critical business hours, it can be done transparently in real-time. If changes need to be made in the distribution of information, it can be accomplished dynamically with no application re-programming.

¥ OpenMOM also features a simple management capability to optimize the usability and reporting mechanisms surrounding an application component and its communications. Messages between components can be managed at a unique level, enabling in-depth customization and tracking of the messaging flow.

OpenMOM ensures the availability of multi-tier applications

¥ Since OpenMOM is based on a Snowflake* architecture, versus a bus architecture or a hub and spoke one, it inherently provides much more flexibility and performance than traditional connectivity solutions. In addition, OpenMOM ensures that message exchanges will not fail, and that the overall application will remain available regardless of hardware, network or software issues.

¥ OpenMOM's asynchronous messaging and fail-safe logging ensures that communications between components are accomplished in a reliable and timely fashion. OpenMOM's logging techniques are unique in the middleware industry, ensuring that each and every communication can be tracked and implemented regardless of system failures.

¥ OpenMOM's distributed architecture ensures a continuing high performance component communications, constantely available. Multiple Message Brokers can be dynamically connected together across multiple computers. Any of these brokers can be dynamically activated to enhance performance or to complete execution in the case of system crash.

* MOM architectures