The Uniface Universal Request Broker (URB) architecture allows you to deploy an application independently of architecture. It supports bidirectional, synchronous, and asynchronous communication between components. Components can access data in distributed databases and can be configured to run on any supported architecture.
The URB provides an open interface that connects Uniface and non-Uniface components in a distributed environment. To do so, it relies on a number of Uniface software engines, servers, services, and connectors. For more information, see Uniface Application Middleware .
Support for Third-Party Middleware
Components can have Uniface or non-Uniface implementations. The URB transparently brokers requests between different components based on different interaction standards. It provides call-in and call-out mechanisms for integrating various component implementations into an application using middleware.
The URB supports the following classes of middleware:
(Distributed) Object Middleware—Uniface supports .NET and COM/DCOM (Microsoft’s standard for Windows). Uniface also offers support for Java components to call Uniface components, and the ability to distribute Java or Uniface components over the network using the Remote Method Invocation (RMI) Server.
Transaction Processing (TP) monitors—TP monitors are used in large distributed applications that process transactions on the server and have a thin client handling the user interface.
Custom-built interfaces—Custom-built interfaces can be constructed to provide access to other third-party middleware.