B2B 11g: Java Transport Callout not Journaling Incoming Acknowledgement Messages (ACK) from External Application
(Doc ID 1547580.1)
Last updated on NOVEMBER 13, 2023
Applies to:
Oracle SOA Suite - Version 11.1.1.6.0 and laterInformation in this document applies to any platform.
Symptoms
On : 11.1.1.6.0 version, B2B Engine
ACTUAL BEHAVIOR
---------------
Java Transport callout not journaling incoming acknowledgement messages (ACK) from external application
You are using java callout at the transport level (for each endpoint) so that we can journal the HL7 payload
to a journal file that is stored in a secured locations.
EXPECTED BEHAVIOR
-----------------------
For the incoming messages to an endpoint, the java callout works well and archives the incoming HL7 payload
and the outgoing acknowledgement (ACK) to a journal file.
ACTUAL BEHAVIOR
-----------------------
Problem: For the outgoing messages to an endpoint, the java callout archives the outgoing HL7 payload
to the journal file but DOES NOT archive the incoming acknowledgement from the external application.
Cause
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
Symptoms |
Cause |
Solution |
References |