After transformation, where is the Internal Message stored?

The internal message is stored in the system memory after transformation. This storage method is essential because it allows for immediate access to the message for processing or further operations. By utilizing system memory, the messages can be managed efficiently without the delays that can occur when relying on disk storage or archival processes.

Choosing system memory means that the information is readily accessible for any operations that follow, which is critical in environments that require quick responsiveness, such as those found in financial and banking applications where Avaloq is often utilized. This storage mechanism optimizes performance and ensures that messages can be accessed swiftly as needed within the application lifecycle.

Other options like the outgoing queue, debug log, or parsed message archive have distinct purposes. The outgoing queue, for example, is where messages are held before they are sent out, while the debug log records activity for troubleshooting and validation rather than serving as active storage for internal use. The parsed message archive is intended for storage of historical data rather than immediate processing, making system memory the most appropriate choice for storing transformed internal messages temporarily.