> #### Managing broker resources

> On systems that support shared processes, a broker is a main server process. It functions like a traffic director, handling client requests for specific resources that support the business logic associated with an application. A broker identifies and accounts for resource availability and consumption; it accomplishes these tasks by processing a pool of servers or agents and attempting to fulfill specific resource requests.

> For example, an AppServer broker manages connection requests initiated by its clients for the business logic and processes located on an AppServer. In this context, a broker executes its tasks somewhat in isolation, only executing and performing according to its defined configuration properties and parameters.

> Using Fathom you can optimize broker performance; the Fathom Management console supports viewing status details, controlling, monitoring, and managing broker components to ensure appropriate resources are available.

> Note: The term Fathom as used throughout this guide refers to Fathom Management Standard Edition.

> ##### The ubroker.properties file

> The `ubroker.properties` file stores all the configuration definitions for each instance of the Transaction Server, the AppServer, and the NameServer. Each configuration definition contains environment variables, registry entries (for Windows), and property settings for each product instance. Fathom references and displays this configuration data as it relates to the performance data you can gather and analyze in Fathom.

> While you can use Fathom Management to perform limited configuration tasks, you should continue to use Progress Explorer or the command line to customize configuration details stored in the `upbroker.properties` file.

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