Persistent Store Configuration & Operational Considerations for JMS, SAF & WebLogic tlogs in OSM
(Doc ID 2469767.1)
Last updated on JULY 05, 2019
Oracle Communications Order and Service Management - Version 220.127.116.11.0 and later Information in this document applies to any platform.
Using file store for persistence of JMS messages and JTA transaction logs (tlogs) can lead to unusable or corrupted backups and DR/GR synchronization, as well as increased maintenance (monitoring for size, and outages for compaction). Avoiding this maintenance leads to performance issues.
This applies to OSM 18.104.22.168 and higher
Note: The recommendation herein apply to older OSM releases as well, but for those releases, JDBC persistence is only available for JMS/SAF and not for tlogs. So the older releases will continue to have the same sync issues with tlog files, but will be protected for the more numerous message handling scenario.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!