Progress
Installation and Configuration Guide
Version 9
for UNIX


Unified Broker

Unified Broker products include a Unified Broker process that is the initial point of client connection to a Unified Broker product instance. It is the process responsible for managing other process resources that are part of the product, and making those resources available to clients. As such, the Unified Broker process:

Unified Broker Types

One Unified Broker process manages a single Unified Broker product instance of the same type (AppServer, SonicMQ Adapter, WebSpeed, or DataServer). The product documentation for each Unified Broker type identifies this Unified Broker process by a different name, as follows:

For more information on how to configure the Unified Broker process for a product, how clients specify connections, and how the Unified Broker manages connections with clients, see your product documentation.

Application Services

The Application Service that a Unified Broker provides is identified by a list of one or more names that you can optionally specify during broker configuration. Each Application Service name you specify is an arbitrary designation for the business function that the Unified Broker instance provides.

The NameServer maintains a separate Application Service name space for each Unified Broker type. So, an AppServer, WebSpeed Transaction Server, and DataServer instance can each register the same Application Service name with the same controlling NameServer without conflict. However, with the load-balancing option, if you have multiple Unified Broker instances of the same type register the same Application Service name with the same controlling NameServer, you must guarantee that each Unified Broker instance provides exactly the same functionality. For AppServers and WebSpeed Transaction Servers, this means providing the same application procedures and database resources for all instances. For DataServers, this means accessing the same database for all instances.

If, for example, you use the same Application Service name to identify functionality on several AppServers, each of which support different remote procedures and database connections, multiple requests from the same client application are likely to provide inconsistent results.

The Default Service

You actually do not have to designate an explicit Application Service for a Unified Broker. Instead, you can specify that the broker supports the default service. The default service is a special Application Service designation that supports default client connection requests. Thus, any Unified Broker that supports the default service and is of the appropriate type (AppServer, WebSpeed, or DataServer) can satisfy a connection request from a client that does not specify an Application Service name as part of its connection request.


Copyright © 2004 Progress Software Corporation
www.progress.com
Voice: (781) 280-4000
Fax: (781) 280-4095