Use the following rules and guidelines when you run real-time sessions:
The session fails if a mapping contains a Transaction Control transformation.
The session fails if a mapping contains any transformation with Generate Transactions enabled.
The session fails if a mapping contains any transformation with the transformation scope set to all input.
The session fails if a mapping contains any transformation that has row transformation scope and receives input from multiple transaction control points.
The session fails if the load scope for the target is set to all input.
The Integration Service ignores flush latency when you run a session in debug mode.
If the mapping contains a relational target, configure the load type for the target to normal.
If the mapping contains an XML target definition, select Append to Document for the On Commit option in the target definition.
The Integration Service is resilient to connection failures to WebSphere MQ and JMS. It is not resilient to any other messaging system.
When a real-time session contains a request and a response, such as in a web service, the session log contains start and end times for the request and response. When a real-time session contains a publish/subscribe or point-to-point architecture, the session log contains statistics that describe when the Integration Service commits rows to the target.