Loader controller configuration

You can disable the loader controller from starting up automatically or change the default log level for the service log.

Automatically starting the loader controller service

Enable automatic startup of the loader controller service: By default, automatic startup of the loader controller service is enabled. If you changed the behavior to disable automatic startup, and want to set it back to the default setting, use the cluster management console to configure the loader controller service profile, and set the profile to include the <sc:StartType>AUTOMATIC</sc:StartType> setting.
Disable automatic startup of the loader controller service: By default, automatic startup of the loader controller service is enabled. To disable automatic startup, use the cluster management console to configure the loader controller service profile, and set the profile to include the <sc:StartType>MANUAL</sc:StartType> setting.

Log file

Specify the default log level of your loader controller log file

To specify the default log level of your loader controller log file, edit the log4j.properties file: EGO_CONFDIR/../../perf/conf/log4j.properties.

Specify the default log level, using the following syntax:

log4j.logger.domain_name.perf.dataloader=log_level, domain_name.perf.dataloader

where log_level is the default log level of your loader controller log file.

The loader controller only logs messages of the same or less detail as log_level. Therefore, if you change the log level to ERROR, the loader controller will only log ERROR and FATAL messages.