8.1.1.2 categories.cfg File

In the <INSTALL_DIR>/database/db_tools/mantas_cfg/categories.cfg file, you can modify the default location to where you want to direct logging output for each utility. The entries that you make require a specific format; the file contains instructions and examples of correct formatting.

The following snippet provides a sample categories.cfg file.

# Common Logging categories configuration for Oracle Financial Services Database #
# Specify the log location for messages of a specific category.
# The property name should be of the form: log.category.{CATEGORY_NAME}.location # If logging to a category that is not specified below, the messages are logged # a configurable default location.
# Valid values are console, syslog, eventviewer, mantaslog, an e-mail address, o # full path to a file.
# If specifying mantaslog, also specify the property log.mantaslog.location with # the desired path to the logfile in install.cfg. If running the algorithms, use
# format job<job #>-datetimestamp for the mantaslog filename. For other subsyste the
# format is mantaslog-datetimestamp. #
# NOTE: Category names cannot contain the following reserved words: fatal, # warning, notice, diagnostic, trace, category, or location.
# List multiple locations for each property by using a comma delimiter. #
# NOTE: These are commented out because Oracle Financial Services does not curre route by
# category. Entries are placed in the configured default location in install.cfg # These can be uncommented and modified if routing by category is necessary.
#
log.category.ALERT_PURGE.location=/users/orion/mantas /database/db_tools/logs/ alert_purge.log
log.category.BATCH_CONTROL.location=/users/orion/mantas /database/db_tools/logs/ batch_control.log
log.category.CALENDAR_MANAGER.location=/users/orion/mantas /database/db_tools/lo calendar_manager.log
log.category.DATA_RETENTION_MANAGER.location=/users/orion/mantas /database/db_to logs/DRM_Utility.log
log.category.TRUNCATE_MANAGER.location=/users/orion/mantas /database/db_tools/lo truncate_manager.log
log.category.COMMON_UTILITIES.location=/users/orion/mantas /database/db_tools/lo common_utilities.log
log.category.EXTRACT.location=/users/orion/mantas /database/db_tools/logs/extrac log.category.LOAD.location=/users/orion/mantas /database/db_tools/logs/load.log
log.category.REFRESH_TEMP_TABLE.location=/users/orion/mantas /database/db_tools/ refresh_temp_table.log
log.category.RUN_STORED_PROCEDURE.location=/users/orion/mantas /database/db_tool logs/
run_stored_procedure.log
log.category.GET_DATASET_QUERY.location=/users/orion/mantas /database/db_tools/ logs/
get_dataset_query.log
log.category.PUSH_EMAIL.location=/users/orion/mantas /database/db_tools/logs/ push_email.log
log.category.HIGHLIGHT_GENERATOR.location=/users/orion/mantas /database/ db_tools/logs/
highlight_generator.log
log.category.REPORT.location=/users/orion/mantas /database/db_tools/logs/ report.log
log.category.DATA_ANALYSIS_TOOL.location=/users/orion/mantas /database/ db_tools/logs/
data_analysis_tool.log


# Specify the location of messages of a specific severity and category. # The valid values are the same as for category.
# List multiple locations for each property by using a comma delimiter.
# If an entry for a severity does not appear here, the message is logged to # the location specified for the category by the above property. If that
# does not exist, it is logged to the configured default location in install.cfg.
#
# NOTE: The entry below is just an example. It is commented out because mantas # does not route by category/severity. These can be uncommented and modified if # routing by category/severity is necessary.
#
#log.EXAMPLE_CATEGORY.warning.location=syslog