Component Configurations

The Configuration Manager allows you to set up the components installed on the system using the Configure tab, which is displayed in the left pane in Configuration Manager.

Different configurations are needed for servers that perform different functions. For example, batch jobs can require a completely different DBMS server configuration than that of an online server. If so, create a DBMS server configuration called "batch" and configure it for batch processing.

The Configuration Manager lets you add, delete, or rename the various configurable server components listed in Configurable Components. For detailed steps on performing these procedures, see the following topics in the Procedures section of the Configuration Manager online help.

• Adding a Server Component Configuration
• Deleting a Server Component Configuration
• Changing the Name of a Server Component Configuration

Note: You can perform these procedures for non-default components configurations only.

Note: You cannot delete configurations for the Name Server and Recovery Server.

Configurable Properties for a Component

Each non-default component configuration has two properties that can be changed. They are:

• Startup Count—The startup count for a component represents the number of instances to be initiated when the Ingres installation is started.

  For example, if you set the startup count to five for the Communications Server, five Communications Servers start at startup time. All components that have a startup count that can be edited are daemon processes (the DBMS Server, Star, GCC, and so on). You can change the startup count for any component using Configuration Manager or the Configuration-By-Forms utility. For instructions on changing startup count, see "Changing the Startup Count" in the Configuration Manager online help.

• Name—Every non-default component can be assigned a name. The name allows you to assign a specific name to a component configuration.

  For instructions on changing component names, see Setting Server Properties in Configuration Manager online help.

Note: You can only rename non-default server components.

Configuration Snapshot

A configuration snapshot file contains information on the installation's parameters including:

• Configuration parameters
• vnode definitions
• System variables
• User variables

The snapshot file can be used to compare configurations changes.

For example, if you encounter problems with the installation later, take another snapshot of the configuration and compare it to the earlier snapshot to determine if any configuration changes have contributed to the problem. Also, keep an on-going record of configuration changes by taking a snapshot of the installation each time you change its configuration.

Note: Before configuring or editing the system parameters, you must use the VCDA tool to create a "snapshot" file of the current configuration.

Configuration Parameters

Ingres configuration parameters are stored in the config.dat file. Some Ingres parameters are dependent on, or derived from other Ingres parameters.

Setting Parameter and Derived Parameter Values

The Parameters page in Configuration Manager lists the parameters associated with a selected component configuration.

For most component configurations, you can edit the value of a parameter, restore the parameter to a value that has been saved in a configuration "snapshot" file, or restore the parameter to its original installation value.

When you select a particular component and click on one of the parameters in the Parameters tab, the Edit Value and Restore buttons become enabled. For instructions on editing and restoring parameter values, see Setting and Restoring Component Parameters in the Procedures section of the Configuration Manager online help.

Using VCDA to Restore Configuration Parameter

VCDA can be used to restore configuration parameter values saved in a snapshot file. For detailed steps on using this tool, see the VCDA online help.

Viewing and Recalculating Derived Parameters

By clicking the Derived tab, you can view a list of, as well as recalculate any of the derived parameters. Any derived parameter can be set in "protected" mode. This means that Configuration Manager or the Configuration-By-Forms utility cannot recalculate the derived value. This allows you to set a desired value for the parameter, even though the value is normally derived by the system from other parameters. If protected mode is disabled, the value of the parameter is adjusted whenever new values are set for other parameters on which the derived value is based. The new and old values are shown in the change log.

For detailed steps on performing these procedures, see the following topics in Configuration Manager online help:

• Recalculating Derived Parameter Values
• Protecting Derived Parameters

Components That Use Derived Parameters

The following components contain parameters that are derived from other parameters:

• DBMS Server
• Star Server
• Security
• Locking System
• Logging System
• Recovery Server

When a parameter is changed, any parameters derived from that parameter are automatically updated.