SOA Composite Becomes Corrupted Whenever The .dbc File Changes Or Connection To EBS Is Changed
(Doc ID 2686817.1)
Last updated on SEPTEMBER 27, 2023
Applies to:
Oracle SOA Suite - Version 12.2.1.3.0 and laterInformation in this document applies to any platform.
Goal
We have xxxxxx as a Composite in our 12.2.1.3 SOA environment. It uses the OracleAppsAdapter to talk to our Oracle 12.2.9 EBS environment. Whenever a patch cycle is run or the EBS environment is cycled / rebooted the xxxxxx composite stops working. IF for some reason the SOA application servers are brought down and back up again, without un-deploying the xxxxxx Composite and redeploying the xxxxxx Composite then the composite becomes corrupted.We have several other composited that perform as expected. we can cycle the SOA environment as much as we want and they never get corrupted.
What would cause one composite to be corrupted?
Solution
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
| Goal |
| Solution |
| References |