> #### Stages of a warm start

> The general stages in an AdminServer warm start are:

> 1. An advanced user opens the `ubroker.properties` file in an editor and makes minimal configuration changes.
> 2. The user saves the changes to submit configuration property changes.
> 3. The AdminServer validates the configuration property changes.
> Fathom cannot accept any other broker-related requests that users might try to initiate. This situation means that you, and other users logged in to Fathom at this time, might see links grayed out or disabled that are normally available.

> 4. Complete Fathom functionality is restored when the AdminServer completes the warm start. This includes the availability of all temporarily disabled links.

> ##### Validating the property changes

> You can also use the product-specific configuration utilities to validate the configuration property changes.

> See the appropriate OpenEdge documentation for information about how to use these configuration utilities:

> - WSCONFIG`` — To display and validate values associated with the property settings in the `ubroker.properties` file for a Transaction Server.
> - ASCONFIG`` — To display and validate values associated with the property settings in the `ubroker.properties` file for an AppServer.
> - NSCONFIG`` — To display and validate values associated with the property settings in the `ubroker.properties` file for a NameServer.

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