Integration Server 10.5 | Web Services Developer’s Guide | Web Services Reliable Messaging (WS-ReliableMessaging) | Using Reliable Messaging in Integration Server | Persistent Storage Support for Reliable Messaging Data
 
Persistent Storage Support for Reliable Messaging Data
Integration Server provides persistent storage capability for reliable messaging transactional data. Persistent storage support ensures that the messages that are being exchanged between a reliable messaging source and a reliable messaging destination are not lost in case of system or communication failures. When messages are exchanged in distributed systems, errors can occur during the transmission of messages over communication links or during the processing of messages in system components. Under these conditions, Integration Server ensures that no messages are lost and that messages can be eventually recovered after system failure.
Integration Server provides support for persistent storage of information related to reliable messaging sequences including the essential routing and delivery information.
Keep the following points in mind while configuring Integration Server to provide persistent storage capability for reliable messaging:
*The ISInternal functional alias (specified on the Settings > JDBC Pools screen) must be configured to point to either the embedded IS Internal database or to the external RDBMS that Integration Server must use for persistent storage.
*If the Integration Servers used for reliable message exchanges are in a clustered environment and are connected to the same database, all the Integration Servers must have the same persistence configuration defined on the Settings > Web Services > Reliable Messaging > Edit Configuration page.
*Integration Server supports reliable messaging in a clustered environment only if you configure Integration Server to provide persistent storage capability for reliable messaging.
*For the authentication details to be persisted across Integration Server restarts, you must provide the authentication details for the consumer web service descriptor in the associated consumer endpoint alias and not in the associated connector signature.