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.