Configuring Vector
Configurable Components
After the installation is running, all Vector servers must be monitored to ensure that they are running and that they are configured for top performance. You can also configure selected Vector parameters.
You can view and set values for the following components:
• Server components
– X100
– DBMS
– JDBC
– Data Access
– Communications
– Bridge
– Name
– Recovery
• System components
– Security
– Locking system
– Logging system
– Primary and dual transaction logs
Configuration Tools
Vector provides the following tools to configure an installation.
• Configuration-By-Forms (CBF) or the visual tool equivalent, Configuration Manager (VCBF)
• Visual Configuration Difference Analyzer (VCDA)
Access Configuration-By-Forms Utility
Configuration-By-Forms (CBF) is an interactive forms-based utility that is available in all environments in which Vector runs. All configuration parameters are described in CBF's online help facility.
To access the Configuration-By-Forms utility
Enter cbf at the command line.
How You Navigate in CBF
Here are tips on how to navigate in CBF to locate and set parameters:
• On the main screen, all system components are listed. Use the arrow keys to highlight the component you want to configure.
• The menu at the bottom of each screen lists the functions you can perform. Use the key combination for the function. For example, to Configure, press SH+F1.
• To scroll through all available functions shown in the menu at the bottom of the screen, press the ESC key.
• To cancel an action, press the ESC key.
• To return to the previous screen, press F10.
• To exit CBF, press F6 from the Main Screen.
• For help on any screen or parameter, press F1.
Component Configurations
You can add, delete, or rename the various configurable server components listed in
Configurable Components.
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.
Notes:
• You can perform these procedures for non-default components configurations only.
• 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:
• Startup Count—The startup count for a component represents the number of instances to be initiated when the 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.
• Name—Every non-default component can be assigned a name. The name allows you to assign a specific name to a component configuration.
Note: You can rename non-default server components only.
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 configuration 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
Vector configuration parameters are stored in these files:
vectorwise.conf
Stores X100 Engine parameters. These parameters must be set by manually editing the file. For more information, see
X100 Engine Configuration.
config.dat
Stores parameters for the other components of the installation.
Note: Do not edit the config.dat file directly. Use Configuration-By-Forms (or its visual equivalent Configuration Manager, if available) to set parameter values.
Some parameters are dependent on, or derived from other parameters.
For instructions on configuring specific parameters, see the online help for Configuration-By-Forms or Configuration Manager.
Setting Parameter and Derived Parameter Values
For most component configurations in config.dat, 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.
For instructions on editing and restoring parameter values, see online help.
Using VCDA to Restore Configuration Parameter
Visual Configuration Differences Analyzer (VCDA) can be used to restore configuration parameter values saved in a snapshot file. For detailed steps, see the VCDA online help.
Protecting or Recalculating Derived Parameters
The settings of some configuration parameters are derived from those of other parameters. When a parameter is changed, any parameters derived from that parameter are automatically updated.
Any derived parameter can be set in "protected" mode, which means that the Configuration-By-Forms utility or Configuration Manager cannot recalculate the derived value. Protected mode 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 online help.
Components That Use Derived Parameters
The following components contain parameters that are derived from other parameters:
• DBMS Server
• Security
• Locking System
• Logging System
• Recovery Server