When developing integration tests, which object represents an instance of a message at a particular point in time while it is being processed by a message flow?
Which caching option provides the fastest lookups across multiple threads of the same message flow in an Integration Server on machines that have multiple processors?
A developer needs ESQL data to be cached in memory so that it survives for the life of the message flow and is shared by all of the threads that run the flow. Which keyword on the DECLARE statement creates this type of variable?
While testing a message flow in a containerized environment, the IntegrationServer crashes and terminates the container.
How can the required diagnostics be collected from the container?
When building a message flow for deployment in an environment that does not have MQ, which built-in nodes support parallel processing of backend services?