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

Create successful ePaper yourself

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

Client/server configurations<br />

Client/server configurations<br />

Wherever it runs, multi-user <strong>OpenEdge</strong> functions in a client/server architecture. On a<br />

single machine, <strong>OpenEdge</strong> provides multi-user access to a database by using a<br />

separate client process for each user. In a client/server configuration, one or more<br />

clients access the database through a server. The server provides a connection to the<br />

database through the shared memory. While separate <strong>and</strong> distinct, the <strong>OpenEdge</strong><br />

client <strong>and</strong> server processes compete for the same machine resources.<br />

In client/server configurations, the client application <strong>and</strong> the database server are<br />

separate processes. Client processes can be local or remote.<br />

The <strong>OpenEdge</strong> user interface <strong>and</strong> <strong>OpenEdge</strong> applications execute in the client<br />

session, sending requests to the <strong>OpenEdge</strong> server. The <strong>OpenEdge</strong> server accesses<br />

the database on behalf of each client session.<br />

Terminology<br />

This section introduces the terminology used to describe client/server configurations.<br />

Application workstation<br />

An application workstation is any node that runs one or more <strong>OpenEdge</strong> clients.<br />

Depending on its configuration, an application workstation might run local clients <strong>and</strong><br />

servers as well.<br />

Database server machine<br />

A database server machine is any node that runs one or more <strong>OpenEdge</strong> servers for<br />

local or remote <strong>OpenEdge</strong> clients.<br />

Network file server<br />

A network file server is any node that provides shared services such as file, printing,<br />

<strong>and</strong> security services to other nodes, including application workstations <strong>and</strong> database<br />

server machines. A network file server usually provides these services by allowing<br />

other nodes to access its local files <strong>and</strong> printers as if they were local. For example,<br />

<strong>OpenEdge</strong> clients can run application procedures <strong>and</strong> <strong>OpenEdge</strong> servers can access<br />

database files stored on a remote network file server.<br />

A network operating system (NOS) is a network environment that includes one or more<br />

network file servers that provide a common set of resource sharing <strong>and</strong> security<br />

services to other nodes. A network file server usually runs the kernel of an NOS, the<br />

program that controls access to shared network resources. Depending on its operating<br />

system, a network file server might also run one or more <strong>OpenEdge</strong> database clients<br />

<strong>and</strong> servers.<br />

Although Progress Software Corporation recommends that you store the database on<br />

a disk locally attached to the database server machine, you can store the database on<br />

a network file server. Clients can access shared application code <strong>and</strong> communicate<br />

with the database server. However, depending on your application <strong>and</strong> network<br />

environment, you might lose database integrity.<br />

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

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

Saved successfully!

Ooh no, something went wrong!