Red Hat 6.2.1
Manuals and User Guides for Red Hat 6.2.1. We found 5 manuals for free downloads User Guide, Development Guide, Developer Guide
JBoss Fuse 6.2.1 is a lightweight, modular, and extensible integration platform that allows you to connect different applications and services together. You can use it to create complex integration flows, manage transactions, and monitor your applications.
Key Features
Lightweight and modular
Extensible with a wide range of connectors and components
Supports various transaction management mechanisms
Provides tools for monitoring and managing your integrations
Based on Apache Camel and Spring
Pages: 163 Red Hat 6.2.1 User Guide
Brand: Red Hat Category: Software Size: 1 MB
Languages: English
Table of contents
- 5 Table of Contents
- 8 CHAPTER 1. INTRODUCTION TO TRANSACTIONS
- 8 1.1. BASIC TRANSACTION CONCEPTS
- 8 What is a transaction?
- 8 ACID properties of a transaction
- 8 Transaction clients
- 9 Transaction demarcation
- 9 Resources
- 9 Transaction manager
- 9 Managing single or multiple resources
- 9 Transactions and threading
- 10 Transaction context
- 10 Distributed transactions
- 10 X/Open XA standard
- 11 1.2. TRANSACTION QUALITIES OF SERVICE
- 11 Overview
- 11 Qualities of service provided by resources
- 11 Transaction isolation levels
- 12 Support for the XA standard
- 12 Qualities of service provided by transaction managers
- 12 Support for multiple resources
- 13 Support for suspend/resume and attach/detach
- 13 Distributed transactions
- 13 Transaction monitoring
- 13 Recovery from failure
- 13 1.3. GETTING STARTED WITH TRANSACTIONS
- 13 1.3.1. Prerequisites
- 14 Overview
- 14 Java Runtime
- 14 Apache Maven 3
- 14 1.3.2. Generate a New Project
- 14 Overview
- 14 Steps
- 16 1.3.3. Configure a Transaction Manager and a Camel Route
- 16 Overview
- 16 Steps
- 18 1.3.4. Create the MyTransform Bean
- 18 Overview
- 18 Steps
- 18 1.3.5. Build and Run the Example
- 18 Overview
- 18 Steps
- 21 CHAPTER 2. SELECTING A TRANSACTION MANAGER
- 21 2.1. WHAT IS A TRANSACTION MANAGER?
- 21 Transaction managers in Spring
- 21 Local transaction managers
- 22 Global transaction managers
- 23 Distributed transaction managers
- 23 2.2. SPRING TRANSACTION ARCHITECTURE
- 23 Overview
- 24 Standalone Spring container
- 24 Data source
- 24 Local transaction manager
- 25 2.3. OSGI TRANSACTION ARCHITECTURE
- 25 Overview
- 25 OSGi mandated transaction architecture
- 26 Spring transaction integration
- 26 Reference
- 26 2.4. PLATFORMTRANSACTIONMANAGER INTERFACE
- 26 Overview
- 26 PlatformTransactionManager interface
- 27 TransactionDefinition interface
- 27 TransactionStatus interface
- 27 Using the PlatformTransactionManager interface
- 28 2.5. TRANSACTION MANAGER IMPLEMENTATIONS
- 28 Overview
- 28 Local transaction managers
- 29 Global transaction managers
- 30 2.6. SAMPLE CONFIGURATIONS
- 30 2.6.1. JDBC Data Source
- 30 Overview
- 30 Sample JDBC configuration
- 31 JDBC data source transaction manager bean
- 31 JDBC data source bean
- 32 Standalone data sources
- 33 J2EE data source adapters
- 34 Data source proxies for special features
- 35 Third-party JDBC driver managers
- 39 2.6.2. Hibernate
- 39 Overview
- 39 Sample Hibernate configuration
- 40 Hibernate transaction manager bean
- 40 Hibernate session factory bean
- 41 2.6.3. JPA
- 41 Overview
- 41 Sample JPA configuration
- 42 JPA transaction manager bean
- 42 Entity manager factory bean
- 43 JPA entity manager factories
- 43 JPA bootstrap contract
- 43 Sample persistence.xml file
- 45 Sample annotated class
- 47 CHAPTER 3. JMS TRANSACTIONS
- 47 3.1. CONFIGURING THE JMS COMPONENT
- 47 Overview
- 47 Camel JMS component configuration
- 49 Cache levels and performance
- 50 Example using CACHE_CONSUMER
- 51 Example using CACHE_CONNECTION
- 52 3.2. INONLY MESSAGE EXCHANGE PATTERN
- 52 Overview
- 52 Enforcing the InOnly message exchange pattern
- 53 InOnly scenario
- 53 Description of InOnly scenario
- 53 3.3. INOUT MESSAGE EXCHANGE PATTERN
- 54 Overview
- 54 Enabling InOut mode in JMS
- 54 Problems combining InOut mode with transactions
- 55 Refactoring routes to avoid InOut mode
- 56 A special case
- 57 CHAPTER 4. DATA ACCESS WITH SPRING
- 57 4.1. PROGRAMMING DATA ACCESS WITH SPRING TEMPLATES
- 57 Overview
- 57 JmsTemplate class
- 58 JdbcTemplate class
- 58 SimpleJdbcTemplate class
- 58 NamedParameterJdbcTemplate class
- 58 SqlMapClientTemplate class
- 58 HibernateTemplate class
- 59 JdoTemplate class
- 59 JpaTemplate class
- 59 4.2. SPRING JDBC TEMPLATE
- 59 Overview
- 59 JdbcTemplate class
- 59 Querying
- 61 Updating
- 61 Other SQL operations
- 61 Example application
- 62 Format of money transfer orders
- 62 CreateTable class
- 63 AccountService class
- 64 AccountService.credit() method
- 65 AccountService.debit() method
- 66 AccountService.dumpTable() method
- 67 CHAPTER 5. TRANSACTION DEMARCATION
- 67 5.1. DEMARCATION BY MARKING THE ROUTE
- 67 Overview
- 67 Sample route with JDBC resource
- 67 Route definition in Java DSL
- 68 Using SpringRouteBuilder
- 68 Route definition in Spring XML
- 68 Default transaction manager and transacted policy
- 69 Transaction scope
- 70 No thread pools in a transactional route
- 70 Breaking a route into fragments
- 71 Resource endpoints
- 72 Sample route with resource endpoints
- 72 5.2. DEMARCATION BY TRANSACTIONAL ENDPOINTS
- 72 Overview
- 72 Sample route with JMS endpoint
- 73 Route definition in Java DSL
- 74 Route definition in Spring XML
- 74 transacted() not required
- 75 Transactional endpoints
- 75 5.3. PROPAGATION POLICIES
- 75 Overview
- 75 Spring transaction policies
- 76 Propagation behaviors
- 77 Defining policy beans in Spring XML
- 78 Sample route with PROPAGATION_NEVER policy in Java DSL
- 79 Sample route with PROPAGATION_NEVER policy in Spring XML
- 79 5.4. ERROR HANDLING AND ROLLBACKS
- 79 Overview
- 79 How to roll back a transaction
- 80 Runtime exceptions as rollbacks
- 80 The rollback() DSL command
- 81 The markRollbackOnly() DSL command
- 82 How to define a dead letter queue
- 83 Catching exceptions around a transaction
- 85 CHAPTER 6. XA TRANSACTIONS IN RED HAT JBOSS FUSE
- 85 6.1. TRANSACTION ARCHITECTURE
- 85 Overview
- 85 OSGi mandated transaction architecture
- 86 Spring transaction integration
- 86 Red Hat JBoss Fuse transaction implementation
- 86 Installing the transaction feature
- 87 Geronimo transaction manager
- 87 Accessing Geronimo directly
- 87 HOWL transaction log
- 87 JTA-based application bundles
- 87 Spring-based application bundles
- 88 References
- 88 6.2. CONFIGURING THE TRANSACTION MANAGER
- 88 Overview
- 88 Configuration file
- 88 Transaction manager properties
- 89 Sample settings
- 90 6.3. ACCESSING THE TRANSACTION MANAGER
- 90 Overview
- 90 Blueprint XML
- 90 6.4. JAVA TRANSACTION API
- 90 Overview
- 90 UserTransaction interface
- 91 UserTransaction methods
- 92 When to use UserTransaction?
- 92 TransactionManager interface
- 93 TransactionManager methods
- 93 When to use TransactionManager?
- 94 Transaction interface
- 94 Transaction methods
- 95 When to use Transaction?
- 95 Reference
- 95 6.5. THE XA ENLISTMENT PROBLEM
- 95 The problem of XA enlistment
- 95 How to enlist an XA resource
- 96 Auto-enlistment
- 96 JMS XA wrapper
- 97 6.6. GENERIC XA-AWARE CONNECTION POOL LIBRARY
- 97 Overview
- 98 Dependencies
- 98 PooledConnectionFactory
- 102 XaPooledConnectionFactory
- 103 JcaPooledConnectionFactory
- 103 Examples
- 107 CHAPTER 7. JMS XA TRANSACTION INTEGRATION
- 107 7.1. ENABLING XA ON THE CAMEL JMS COMPONENT
- 107 Overview
- 107 Accessing the XA transaction manager
- 108 XA connection factory bean
- 108 XA pooled connection factory bean
- 109 Camel JMS component and JMS configuration bean
- 110 7.2. JMS XA RESOURCE
- 110 Overview
- 111 XA two-phase commit process
- 112 Embedded MQ broker
- 113 Default MQ broker
- 113 7.3. SAMPLE JMS XA CONFIGURATION
- 113 Spring XML configuration
- 114 Listing notes
- 116 7.4. XA CLIENT WITH TWO CONNECTIONS TO A BROKER
- 116 Overview
- 116 jms.rmIdFromConnectionId option
- 116 Setting rmIdFromConnectionId option on an endpoint URI
- 117 Setting rmIdFromConnectionId option directly on ActiveMQXAConnectionFactory
- 117 Example using rmIdFromConnectionId
- 119 CHAPTER 8. JDBC XA TRANSACTION INTEGRATION
- 119 8.1. CONFIGURING AN XA DATA SOURCE
- 119 Overview
- 119 javax.sql.DataSource interface
- 119 javax.sql.XADataSource interface
- 119 Standard JDBC data source properties
- 121 Apache Derby
- 121 Derby data sources
- 122 Derby data source properties
- 123 Data sources as OSGi services
- 123 Blueprint
- 124 References
- 124 8.2. APACHE ARIES AUTO-ENLISTING XA WRAPPER
- 124 Overview
- 124 derby-ds bundle
- 125 Automatic wrapper instantiation
- 125 XADataSourceEnlistingWrapper
- 125 Installing the Aries transaction wrapper bundle
- 125 Accessing the enlisting wrapper
- 126 Blueprint
- 127 JDBC connection pool options
- 131 CHAPTER 9. XA TRANSACTION DEMARCATION
- 131 9.1. DEMARCATION BY TRANSACTIONAL ENDPOINTS
- 131 Overview
- 131 Auto-demarcation by JMS consumer endpoints
- 131 JMS producer endpoints
- 132 Transactional and non-transactional JMS endpoints
- 132 9.2. DEMARCATION BY MARKING THE ROUTE
- 132 Overview
- 132 Demarcation using transacted()
- 133 Specifying the transaction policy explicitly
- 134 XML syntax
- 134 9.3. DEMARCATION BY USERTRANSACTION
- 134 Overview
- 134 Accessing UserTransaction from Apache Camel
- 135 Example with UserTransaction
- 135 9.4. DEMARCATION BY DECLARATIVE TRANSACTIONS
- 135 Overview
- 135 Bean-level declaration
- 136 Top-level declaration
- 136 tx:transaction attributes
- 139 CHAPTER 10. XA TUTORIAL
- 139 10.1. INSTALL APACHE DERBY
- 139 Overview
- 139 Downloading
- 139 Installing
- 139 Environment variables
- 140 10.2. INTEGRATE DERBY WITH JBOSS FUSE
- 140 Overview
- 140 Derby system
- 140 derby.system.home Java system property
- 140 Setting derby.system.home in the OSGi container
- 140 10.3. DEFINE A DERBY DATASOURCE
- 140 Overview
- 141 Derby data source implementations
- 141 Auto-enlisting an XA data source
- 141 Prerequisites
- 141 Steps to define a Derby datasource
- 145 10.4. DEFINE A TRANSACTIONAL ROUTE
- 145 Overview
- 145 Database schema
- 145 Sample incoming message
- 146 The transactional route
- 146 Provoking a transaction rollback
- 146 Steps to define a transactional route
- 154 10.5. DEPLOY AND RUN THE TRANSACTIONAL ROUTE
- 154 Overview
- 154 Steps to deploy and run the transactional route
- 159 APPENDIX A. OPTIMIZING PERFORMANCE OF JMS SINGLE- AND MULTIPLE-RESOURCE TRANSACTIONS
- 159 OPTIMIZATION TIPS FOR ALL JMS TRANSACTIONS
- 159 OPTIMIZATION TIPS FOR JMS XA TRANSACTIONS
- 161 APPENDIX B. ACCOUNTSERVICE EXAMPLE
- 161 B.1. ACCOUNTSERVICE EXAMPLE CODE
- 161 Overview
- 161 Database schema
- 161 AccountService class
- 163 INDEX
Other manuals and documents
Frequently Answers and Questions
What is JBoss Fuse?
JBoss Fuse is an open-source integration platform that allows you to connect different applications and services together. It is based on Apache Camel and Spring and provides a powerful and flexible way to create complex integration flows.
How do I use transactions in JBoss Fuse?
You can use transactions in JBoss Fuse to ensure that your integration flows are reliable and consistent. JBoss Fuse supports various transaction management mechanisms, including local transactions, global transactions (XA), and JMS transactions.
What are the benefits of using JBoss Fuse?
JBoss Fuse provides a number of benefits, including:
- Reduced development time and effort
- Improved integration efficiency
- Increased application reliability and consistency
- Enhanced application performance
- Support for various messaging protocols and data formats
advertisement