65 Rotating PDC Log Files

Learn how to rotate log files for your Oracle Communications Pricing Design Center applications to prevent them from growing too large.

Topics in this document:

About Rotating PDC Log Files

During log file rotation, PDC writes to a log file until it reaches a maximum size. It then closes the log file and starts writing to a new log file. Rotation prevents your log files from growing too large, making them slow to open and search.

You can set these log file rotation properties for PDC applications:

  • Log level: Sets the logging level, which can be SEVERE, WARNING, INFO, CONFIG, FINE, FINER, or FINEST.

  • Log limit: Sets the log files' maximum file size in bytes. After the log file meets the maximum, PDC closes the log file and creates a new log file.

  • Log file count: Specifies the maximum number of log files to retain for the application.

  • Persist log setting: Specifies whether to persist log files in the database after they are closed. Possible values are:

    • enabled or all: Persists all log files.

    • disabled: Does not persist log files.

    • failed: Persists failed log files only.

    Note:

    Only Real-Time Rating Engine (RRE) and Batch Rating Engine (BRE) transaction log files and ImportExportPricing log files can be persisted.

Table 65-1 lists the PDC application's default log file rotation settings.

Table 65-1 PDC Application Log Files

PDC Application Name or Log File Default Log Level Default Log Limit Default Log File Count Default Persist Log Setting
Pricing Server Log

WARNING

500000

50

N/A

Pricing Server Trace Log

WARNING

500000

50

N/A

ImportExportPricing utility

WARNING

1048576 (1 MB)

100 failed

SyncPDC utility

WARNING

20000

10

N/A

RRE/BRE Transformation Master Log

WARNING

50000

50

N/A

RRE/BRE Transaction Logs

WARNING

N/A

N/A

failed

Configuring Log File Rotation for PDC Applications

To configure log file rotation for PDC applications:

  1. In the PDC_home/PDC/client directory, create a copy of the logging.properties.tmpl file and rename the file logging.properties, where PDC_home is the directory in which you installed PDC.

  2. Open the following files in a text editor:

    • PDC_home/PDC/client/logging.properties

    • PDC_home/apps/conf/log-config.properties

    • BRM_Integration_Pack_Home/apps/syncpdc/log-config.properties

    • BRM_Integration_Pack_Home/apps/transformation/log-config.properties

  3. In each logging properties file, update the custom logging properties, such as:

    • The log level: application.logger.FileHandler.level or java.util.logging.FileHandler.level

    • The log limit: application.logger.FileHandler.limit or java.util.logging.FileHandler.limit

    • The log file count: application.logger.FileHandler.count or java.util.logging.FileHandler.count

    • Whether to persist the log file: persistTransactionLogs or persistIELogs

  4. Save and close the file.

  5. In your WebLogic domain's setDomainEnv.sh file, add the following two lines to the end of the file:

    JAVA_OPTIONS="$JAVA_OPTIONS -Dpdc.logging.properties=PDC_home/PDC/client/logging.properties"
    export JAVA_OPTIONS
  6. Restart the PDC WebLogic domain.

  7. Restart RRE, BRE, SyncPDC, or ImportExportPricing to initialize the configuration.