What is container-managed transaction in SAP BC-JAS - Java Application Server?

SAP Term: container-managed transaction

• Component: BC-JAS

• Component Name: Java Application Server

• Description: A transaction whose demarcation is managed by the application server. The developer may declare transaction attributes in the deployment descriptor of an enterprise bean to define specific transactional behavior for its methods. However, the developer is not required to implement transaction demarcation in the component's source code.

Smart SAP Assistant

• Key Concepts: 
  Container-managed transaction (CMT) is a type of transaction management in the SAP BC-JAS Java Application Server. It is a way of managing transactions in an application server environment, where the application server is responsible for managing the transactions. The application server manages the transactions by using a set of predefined rules and policies. 
  
  How to use it: 
  In order to use CMT, the application server must be configured to use it. This can be done by setting the “transaction-type” attribute in the deployment descriptor of the application. Once this is done, the application server will manage all transactions within the application according to the predefined rules and policies. 
  
  Tips & Tricks: 
  When using CMT, it is important to remember that all transactions must be completed within a single transaction boundary. This means that any changes made within a transaction must either be committed or rolled back before another transaction can begin. Additionally, it is important to ensure that all resources used within a transaction are properly released when the transaction is completed. 
  
  Related Information: 
  For more information on container-managed transactions, please refer to the SAP BC-JAS Java Application Server documentation. Additionally, there are many online resources available that provide more detailed information on CMT and how to use it effectively.