Try OpenEdge Now
skip to main content
Configuration
Configuring OpenEdge Databases : Database configuration and administration
 

Database configuration and administration

Using OpenEdge Management or OpenEdge Explorer, you can set properties for a database, its various configurations, and its associated server groups. Any configuration settings that you establish for a managed database, database configuration, or database server group in OpenEdge Management or OpenEdge Explorer are automatically reflected in the OpenEdge database Configuration Manager property file (conmgr.properties), and vice versa.
Note: You cannot create a new physical database from within OpenEdge Management or OpenEdge Explorer. For more information about creating a database, see OpenEdge Data Management: Database Administration.
A database recognized and managed by the AdminServer is called a managed database. A database not managed by an AdminServer is called a scripted database. Scripted databases are administered outside the AdminServer using parameter files (.pf) and operating system-dependent scripts.
A managed OpenEdge database starts up by using the default configuration information stored in the conmgr.properties file. The file contains the property settings for all managed databases on the host where OpenEdge is installed.
The conmgr.properties file resides in the properties subdirectory of the OpenEdge install directory. Each database is represented in the file by the following groups:
*Database — The group that describes the physical database. There is one database group for each physical database.
*Configuration — One or more groups that describe the database arguments and server groups for an active instance of the database. Only one database configuration can be active at one time. The active configuration is the default configuration identified in the server group.
*ServerGroup — One or more groups that describe brokering behavior. The first server group within a configuration defines the primary broker and each subsequent group defines a secondary broker. The properties in a server group define the arguments that are specific to that primary or secondary broker.
You can edit the conmgr.properties file manually; any changes that you make to it are automatically reflected in OpenEdge Management or OpenEdge Explorer.
Note: Although you can make manual edits to the conmgr.properties file, Progress Software recommends that you use the mergeprop utility, OpenEdge Management, or OpenEdge Explorer to make property changes. For more information about the mergeprop utility, see OpenEdge Getting Started: Installation and Configuration.
From OpenEdge Management or OpenEdge Explorer, you can perform the following database-related actions:
*Add an existing database
*Create a new database configuration
*Edit an existing or new database configuration
*Use the default server group
*Create a new database server group
*Edit a new or existing database server group
*Start a database
*Start a database automatically
*Stop a database
*Use the background writers and watchdog processes
*View the status of a database
*Delete a database
*Delete a database configuration (provided there is more than one)
*Delete a database server group (provided there is more than one)
*Configure the properties of an OpenEdge Replication-enabled database
You can also manage and work with databases enabled for multi-tenancy. For details, see OpenEdge Management and OpenEdge Explorer: Configuring Multi-tenancy.
* Viewing the database log file
* Database configuration awareness