> #### Defining monitors for previously scripted databases

> By using the Fathom Database Migration Utility, you can add a previously scripted OpenEdge database as a resource to Fathom. These databases are typically managed outside the AdminServer using parameter files (`.pf`) and operating system-dependent scripts.

> With the Database Migration Utility, you can identify the database as manageable through the Progress Explorer and the AdminServer. After the configuration migration occurs:

> - Fathom creates a resource if one does not already exist.
> - You can define trend and monitoring options.
> Note: Before you perform the database migration process, you should shut down the database you intend to migrate. This shutdown activity enables the AdminServer to recognize the database as managed when the database is restarted through Fathom, and to create and enable the database monitor.

> Figure 5–6 shows the Define monitors for external Progress databases section.

> Figure 5–6: Defining monitors for external databases

> Note: When you add a managed database using the values you enter on the Database Migration Utility page and then submit the Getting Started page, a database configuration is created in the `conmgr.properties` file, and a database resource is created in the Fathom configuration data store.

> ##### Adding a managed database

> For Fathom to monitor a database fully, the database must be managed.

> Click Add Database. The Database Migration Utility page appears and is comprised of two areas:

> - An Instructions area at the top of the page, describing how to add a managed database.
> - A Database information area at the bottom of the page, where you enter the database values. Note that any field name in red requires a value; all other fields are optional.

> Figure 5–7 shows the Instructions area.

> Figure 5–7: Adding a managed database—instructions

> Figure 5–8 shows the Database information area.

> Figure 5–8: Adding a managed database—information

> To add the managed database:

> 1. Enter the database display name in the Database Display Name field.
> 2. Enter the database path and filename associated with the physical database in the Database Path and Filename field.
> 3. Optionally provide values to add database arguments, using either or both of these methods:
> - In the Parameter File Name field, enter the name of the parameter file (`.pf`) that contains database argument values if you have overriding arguments defined for database brokers.
> - Enter the database argument values explicitly in the Other Database Broker Arguments field. If you want to specify a port for the database, type -S and then the port number.
> If the port specified for the database is 0, the database is considered non-networked and will not be monitored by Fathom.

> Note that you can enter any miscellaneous, non-AdminServer-recognized arguments using either of the previous methods.

> Values set using the parameter file method can be overridden by the values specified in the Other Database Broker Arguments field. Processing difficulties related to these values are handled as follows:

> - If an argument defined in the `.pf` file is not recognized, it is ignored. Any ignored arguments will be displayed in an alert box when you submit the Getting Started page.
> - If an error occurs either when the database configuration is created or when the database resource is created, the configuration is not added to the `conmgr.properties` file, and the resource is not created.
> 4. Select one of the Database Broker Type options to indicate the type of client that is allowed to connect to the broker: 4GL brokers allow only 4GL client connections and SQL brokers allow SQLExplorer or other SQL client connections. The default option, Both, allows 4GL and SQL clients.
> Remember that the client type choice you make here is honored only when you have installed the proper licenses for that client.

> 5. Select AutoStart Database Broker to start the database broker automatically when the AdminServer is started.
> 6. Select Watch Dog Process (WDOG) to start a watchdog process for the database.

> The following are Enterprise-only options that are automatically started only if the database broker is also automatically started:

> - Select After Image Process (AIW) to start an after-image writer for the database.
> - Select Before Image Process (BIW) to start a before-image writer for the database.
> - Enter a numeric value in the Asynchronous Page Writers (APW) field to define the number of asynchronous page writers to start. The default value is 1. You can change this default value by specifying a port in either a named`.pf` file or the Other Database Broker Arguments field.
> If you are running the Workgroup database, the default value for each of the writers is zero, and you cannot change it.

> ##### Making changes to a managed database configuration

> You can view, modify, or delete a managed database configuration by using the Progress Explorer. If the Progress Explorer is connected to the AdminServer, the new database node is automatically added to the Progress Explorer database tree node, and the new node displays once you refresh the database tree.

> Note: From within the Fathom product, you can use the Control page to start and stop a database configuration. For more information about starting and stopping the database in Fathom, see the Database Management Guide.

> If you use the Progress Explorer to delete a database that Fathom also recognizes, Fathom asks if you want to delete the resource. It is possible to enable this database again at a later time if you choose to add the database again by using the Progress Explorer or the Database Migration Utility. You can optionally choose to delete the database from Fathom using the Database Resource page.

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