Section - 3 : Application Maintenance
Error Queue Cleanup
Messages that have failed outbound processing due to communication errors are held in an error queue. These messages can be manually resubmitted via the QuickView tools. This allows you an opportunity to resubmit these messages once communication issues are resolved. To avoid performance issues, periodically clear the queue of any messages that have not been resubmitted by following the instructions below.
- Login to the WebLogic Admin console.
- From Domain Structure, navigate to Messaging → JMS Modules.
Figure 3.3.1 - Domain Structure - Select OICSJMSModule from the JMS Modules table.
- Select OICSJMSErrorQueue from the Summary of Resources table.
- Navigate to the Monitoring table.
- Select the check-box against 'OICSJMSModule!OICSJMSErrorQueue' in the table and click Show.
Figure 3.3.2 - Settings - Select Delete → Delete All option to clean all the messages in the queue.
Figure 3.3.3 - Delete All
Debatch and Process Queue Cleanup
If an application crash occurs for some reason, it is possible for messages to get stuck in the Debatch and Process queues. In this scenario, these queues need to be cleared by following the same steps described above for Error Queue Cleanup.
Log4j Log Files Cleanup
OIDG installation provides configurations to create and purge Log4J log files. The default configuration purges log files older than 30 days. You can modify this configuration in oidx_dsl_log4j.xml file. Refer the below url for more details on Log4j log files purging.
https://logging.apache.org/log4j/log4j-2.9.1/manual/appenders.html
Database Logs Cleanup
With the default installation, database logs will be cleared per the ‘Data Retention Period’ property configuration in AdminView. However, the customer can clear database logs whenever needed by running the ‘PURGE_LOGS’ stored procedure.