Default message flow behavior

IBM® App Connect Enterprise controls the behavior of your message flows, and defines the default actions that are taken if you do not modify the message flow behavior.

The following default actions are provided for all messages that are processed by your message flows:

The execution and threading model
When you deploy a message flow to an integration server, App Connect Enterprise allocates a certain number of threads to that message flow. For further information about how this processing works, see Execution and threading models in a message flow.
Error handling
When you configure your message flows to process messages, you can include error processing of your own. App Connect Enterprise runs default processing if an error occurs for which you have not provided additional processing; this processing is independent of the protocol that you are using for communication. It is described in Default error handling.
Transactional support
App Connect Enterprise handles all messages individually, and does not relate an action taken by the message flow to other actions, processes, or messages. A message flow that is not configured to implement transactional support succeeds or fails regardless of the outcome of interactions with, or updates to, other resources such as IBM MQ queues and databases. Learn more about transactional support in Message flow transactions.
Data conversion
Different hardware platforms and operating systems operate in different code pages. Operating system code pages are also affected by the locale in which you operate. App Connect Enterprise does not allow for these differences unless you change some aspects of its configuration. If you are exchanging messages between unlike systems, you might have to update App Connect Enterprise or IBM MQ configuration, or design and supply your own conversion procedures.

For information about how you can change the configuration of App Connect Enterprise, its IBM MQ queue manager, and your message flows to influence these behaviors, see Changing message flow behavior.