DataCaster Configuration Reference

DataCaster provides a wide range of configuration paramaters for each of the modules in the server. Most of these options can be set using configuration files in DataCaster. Administrators can configure many aspects of a DataCaster instance by setting the preferences parameters provided by the configuration files in the configuration directory.

Some of the configuration options can be changed at runtime, via template parameters, or using the WebAdmin administration tool. However, many of the configuration options will be set using the configuration files. Most parameters have default values that do not need to be set. In a few cases the parameters need to be set before DataCaster will work properly.

Precedence of Configuration Settings

In addition to the configuration files, many configuration options are controlled via template paramaters. Template parameters can be set using template files in the template sub-directories under the conf/db/templates directory. Please see the Template Parameter Reference for more details. For many configuration parameters, the values can be configured using any of the following: top-level preferences file (dbprefs.xml), template files, or setting template parameters at runtime. Wherever applicable, the runtime settings take precedence, followed by the template files, and finally the preferences file.

Use the following to determine when to use the dbprefs, template files, or runtime template parameters.

• Preferences File The preferences file setting (dbprefs.xml) can be used for many but not all parameters. See the dbprefs reference for a full list of parameters supported by this configuration file. Use this file to set parameters that should apply to all databases and all objects within these databases. These settings will apply unless explicitly set for all or specific instances using template files or runtime parameters.
• Template Files Template files can be used to set parameters for all or specific instances of database objects, including a database itself. Use the default template file to set object specific parameters. Use specific template files to set the values for specifici instances of objects, e.g. the inventory database, or the products primary key index. In this way you can set defaults for parameters (i.e. change system defaults for all instances), while setting other values for specific instances as needed.
• Runtime (Session) Template Parameters For some, but not all, template parameters, values can be set at runtime so that the next object created or used will use the values you set. In such cases, the values you set override ant template file or top-level preferences setting. This is useful when a specific user or session needs to change parameter values while creating or using database objects.

Top Level Configuration Files

• The Database Preferences File (dbprefs.xml) : The primary database configuration file that can be used to set many of the available parameters.

• The Server Preferences File )serverprefs.xml): The primary server configuration file to configure server-specific parameters, including communication with remote DataCaster clients.

Other Configuration Files

The following configuration files are in the db sub-directory.

• Index Configuration (indexes.xml): The configured index types.

• Data Type Configuration (types.xml): The data types configuration file.

• SQL Functions Configuration: The administrator-configured SQL functions.

• Stored Procedure Configuration: The administrator-configured stored procedures.

• Text Search Configuration (search.xml): Configuration file for text search implementations.

• Log Listener Configuration: To configure log listeners to listen for transaction log events.

• Trace Level Configuration: To configure trace levels for different modules.

Server-specific Configuration Files

The following are the configration files in the server sub-directory.

• Configuring Server Applications: The applications.xml conf file specifies the list of configured Applications. DataCaster supports additional server applications that can be co-resident with the DatCaster server, and started and stopped via the DatCaster administration interface.

Messaging Configuration Files

The following are the configuration files in the msg sub-directory.

• Configuring Messaging Listeners: The listeners.xml file specifies the list of configured network Listeners (e.g. HTTP) for the data server, each of which needs a Listener implementation class.

• Configuring Messaging Queues: The queues.xml conf file specifies the list of configured Queues on the data server.

• Configuring Messaging Topics: The topics.xml conf file specifies the list of configured Topics on the data server.