Consideration for Changing Persistent Stores for JMS Servers, Configured With Oracle Communications Application
(Doc ID 1327699.1)
Last updated on FEBRUARY 01, 2022
Applies to:Oracle Communications Unified Inventory Management - Version 7.1.2 and later
Oracle Communications Order and Service Management - Version 6.3.1 and later
Oracle Communications ASAP - Version 7.0.1 and later
Information in this document applies to any platform.
Will Oracle Communications applications (ASAP, OSM, UIM) support the JDBC stores to replace the file stores? Any specific configuration parameters (e.g. JDBC drivers) that are required. Any schema changes that are required for applications? What needs to be considered to prevent JMS sequence numbering from being reset when we move file locations. Therefore, what will happen if we convert data stores from one to another? How do we bring both in alignment again, what is the process/procedure?
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document