01.06.2013 Views

OpenEdge Getting Started: Installation and Configuration - Product ...

OpenEdge Getting Started: Installation and Configuration - Product ...

OpenEdge Getting Started: Installation and Configuration - Product ...

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Appendix F: <strong>Configuration</strong> Models<br />

The sections that follow explain the components of the architecture.<br />

Broker<br />

The initial database server process is identified as the broker (_mprosrv). The broker<br />

process manages shared resources <strong>and</strong> starts servers for remote users, as needed.<br />

<strong>OpenEdge</strong> Database Monitor utility<br />

The <strong>OpenEdge</strong> Database Monitor utility (_dbagent) displays performance <strong>and</strong> usage<br />

information about database status <strong>and</strong> activity.<br />

For more information about the Database Monitor utility, see the description of the<br />

PROMON utility in <strong>OpenEdge</strong> Data Management: Database Administration.<br />

<strong>OpenEdge</strong> Watchdog utility<br />

If a process terminates improperly, it can maintain a lock on a record or shared-memory<br />

structure. This can impact database concurrency. The <strong>OpenEdge</strong> Watchdog utility<br />

detects processes that have terminated improperly <strong>and</strong> cleans up after them.<br />

At regular intervals, the Watchdog utility checks for processes that have terminated<br />

unexpectedly. If it finds one, it releases any locks or shared-memory structures that the<br />

process might hold.<br />

The Watchdog utility checks for inactive processes approximately once every 10<br />

seconds. It also checks for self-service clients that are no longer active, releases all the<br />

appropriate record locks, backs out of any live transactions, <strong>and</strong> releases any<br />

shared-memory locks. If a server process terminates unexpectedly, the Watchdog<br />

utility disconnects <strong>and</strong> cleans up the server’s remote clients.<br />

For more information about the Watchdog utility, see the description <strong>and</strong> other details<br />

about the PROWDOG utility in <strong>OpenEdge</strong> Data Management: Database Administration.<br />

Background writers<br />

The <strong>OpenEdge</strong> Enterprise RDBMS offers three background writer processes that<br />

improve performance. These processes continually perform certain housekeeping<br />

functions in the background. Because these functions are performed regularly by the<br />

dedicated background writer processes, client <strong>and</strong> server processes rarely have to wait<br />

for these functions to be performed.<br />

The three types of background writers, asynchronous page writers, before-image<br />

writers, <strong>and</strong> after-image writers, are described in the “Processes on Windows <strong>and</strong><br />

UNIX platforms” section on page 201 <strong>and</strong> in the “Processes on UNIX platforms” section<br />

on page 206. The AdminService starts the background writers if the AdminService has<br />

been configured to do this by <strong>OpenEdge</strong> Management or <strong>OpenEdge</strong> Explorer. For<br />

more information about background writers, see <strong>OpenEdge</strong> Data Management:<br />

Database Administration.<br />

508 <strong>OpenEdge</strong> <strong>Getting</strong> <strong>Started</strong>: <strong>Installation</strong> <strong>and</strong> <strong>Configuration</strong>

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

Saved successfully!

Ooh no, something went wrong!