Configuration Overview
x

The characteristics of an individual server are determined by a set of configuration files. These configuration files define the protocols, services, and data sources supported by the server. In the UNIX, z/OS HFS Deployment (USS), Windows, OpenVMS, and IBM i (formerly known as i5/OS) environments, these files are maintained in directories designated by the environment variable EDACONF.

The initial installation procedure creates an installation instance, represented in manuals as the logical name EDAHOME, and one default configuration instance, known as EDACONF. After you successfully install the server, you can configure a default configuration instance to create an operational instance, or create an additional one at your site. An operational instance of the server is one that is configured to support specific protocols, services, and access to data sources.

You must run the Installation/Configuration Utility for each new instance of the server that you want to configure, and then use the Web Console to configure all necessary functionality.

To configure a server instance, use the Web Console to:

  1. Select and configure data adapters.
  2. Optionally, configure remote servers.
  3. Configure communications nodes and protocols.
  4. Optionally, set parameters for deferred query processing.

If necessary, you may edit configuration files. Some configuration errors can make the server start in a limited mode called safe mode, in which the Web Console is still operational, to enable you to correct the errors.


iWay Software