Configuring Windows modules
- Last Updated: May 2, 2024
- 1 minute read
- OpenEdge
- Version 12.8
- Documentation
Configuring Windows modules
A DataServer configuration that includes Windows can be a local configuration, where all the components run on the same machine, or a remote, client/server configuration. It can also include clients or servers running on different platforms. For example, a Windows client can access a DataServer running remotely on a UNIX host. See The following table for a list of the possible configurations for Windows. It describes what you must do to set up the client and server modules.
In a remote configuration, the following two DataServer modules run on the host even though you use only one executable:
- Broker — The _probrkr executable starts the broker, which spawns the DataServer process.
- DataServer — The broker spawns this process, so you do not interact with it directly. However, you must make sure that the broker uses the _orasrv DataServer executable.
The following sections explain how to configure and run the local DataServer and how to configure and run the DataServer modules in the Windows host machine. For instructions on setting up the client side of remote configurations:
- On UNIX — See Configuring UNIX modules for information.
- In Windows — See Configuring the DataServer in the Windows host for information.