concept global transaction in category camel

This is an excerpt from Manning's book Camel in Action.
Camel uses Spring Transaction to manage transactions via its
TransactionManagerAPI. Depending on the kinds of resources that are taking part in the transaction, an appropriate implementation of the transaction manager must be chosen. Spring offers a number of transaction managers out of the box that work for various local transactions such as JMS and JDBC. But for global transactions, you must use a third-party JTA transaction manager implementation; JTA transaction manager is provided by Java EE application servers. Spring doesn’t offer that out of the box, only the necessary API abstract that Camel uses. We cover using third-party transaction managers in section 12.3.2.

This is an excerpt from Manning's book Camel in Action.
When talking about transactions, we need to distinguish between single- and multiple-resource transactions. The former are also known as local transactions and the latter as global transactions. In the next two sections, we’ll look at these two flavors.
So what is the JtaTransactionManager, and how is it different from the JmsTransactionManager used in the previous section (see figure 9.7)? To answer this, you first need to learn a bit about global transactions and where the Java Transaction API (JTA) fits in.