Defining OpenEdge Management monitors for previously scripted databases
By using the Database Migration Utility, you can add a previously scripted OpenEdge database as a resource to OpenEdge Management. 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 AdminServer. After the configuration migration occurs:
OpenEdge Management 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 OpenEdge Management, and to create and enable the database monitor.
The following figure shows the Define monitors for external OpenEdge databases section.
Figure 8. Defining monitors for external OpenEdge databases section
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 OpenEdge Management configuration data store.
OpenEdge Management creates a resource if one does not already exist.
