30.11.2012 Views

OpenEdge Management and OpenEdge Explorer: Configuration

OpenEdge Management and OpenEdge Explorer: Configuration

OpenEdge Management and OpenEdge Explorer: Configuration

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Configuring <strong>OpenEdge</strong> Databases<br />

Managing databases<br />

2–4<br />

You can use <strong>OpenEdge</strong> <strong>Management</strong> or <strong>OpenEdge</strong> <strong>Explorer</strong> to manage your database. You<br />

cannot physically create a database in the management console; however, you can create the<br />

definition of a database so that you can configure, start, stop, or view status for the primary<br />

broker <strong>and</strong> all auxiliary processes associated with that broker, <strong>and</strong> view status for the log file for<br />

the database.<br />

Database configuration information is stored in the conmgr.properties file. For a complete list<br />

of how the database properties map to the comm<strong>and</strong>-line .pf arguments, see the<br />

conmgr.properties.README. You can locate the README file in the<br />

\properties directory.<br />

A database recognized <strong>and</strong> managed by the AdminServer is called a managed database. A<br />

database not managed by an AdminServer is called a scripted database. Scripted databases are<br />

administered outside the AdminServer using parameter files (.pf) <strong>and</strong> operating<br />

system-dependent scripts. You can migrate a scripted database to a managed database.<br />

For details about adding a managed or a scripted database, see <strong>OpenEdge</strong> <strong>Management</strong>:<br />

Database <strong>Management</strong>.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!