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

Appendix F: Configuration Models
Preparing to run OpenEdge on a TCP/IP network
You can make OpenEdge operational in a network environment by following these
guidelines:
• Identify and configure the nodes on your network for use as application
workstations, database server machines, application server machines, and
network file servers.
• Install OpenEdge on each node, or if your network has a network file server, install
OpenEdge on the file server. For more information, see the “Sharing an
OpenEdge installation on a network overview” section on page 152.
• If any application workstations and database server machines have incompatible
processors or operating systems, you must install the appropriate OpenEdge
product on each node.
• Set up network system files on each node.
• If you are using a network file server, make its resources, including printers and
directories, available to all other nodes that require them.
• If you installed OpenEdge on a network file server, you might want to distribute the
appropriate OpenEdge system files to the compatible application workstations
and database server machines that use them. This takes advantage of networks
where the local file and data access is faster than using the network.
• Set up your OpenEdge databases on each file server, database server, and
application server machine.
Installing OpenEdge on your TCP/IP network
When installing OpenEdge on your network, note the following basic considerations:
• Where to place your database
• Where to place your OpenEdge executables and r-code files
Locating your database
Place your database on the hard disk of the machine that runs the OpenEdge server.
If you place the database on a remote file server, synchronous writes are lost along with
your database’s integrity, in the event of a system crash.
Synchronous writes ensure database integrity by flushing system buffers directly to
disk. This is especially important for maintaining the before-image (BI) file. Therefore,
if you must keep your database separate from the database server machine, use the
before-image filename startup parameter to keep the before-image file local to the
database server.
Note: Remote OpenEdge clients do not have to be concerned about synchronous
writes because they do not write to the database.
518 OpenEdge Getting Started: Installation and Configuration