{"id":7119,"date":"2014-02-23T16:37:45","date_gmt":"2014-02-23T20:37:45","guid":{"rendered":"http:\/\/onlineappsdba.com\/?p=7119"},"modified":"2014-02-24T17:09:32","modified_gmt":"2014-02-24T21:09:32","slug":"1z0-133-weblogic-servers-role-in-managing-transactions-weblogic-12c-administrator-certification","status":"publish","type":"post","link":"https:\/\/onlineappsdba.com\/index.php\/2014\/02\/23\/1z0-133-weblogic-servers-role-in-managing-transactions-weblogic-12c-administrator-certification\/","title":{"rendered":"Certification 1Z0-133 : Transactions – WebLogic Server’s role in managing transactions : WebLogic 12c Administrator Certification"},"content":{"rendered":"

In today\u2019s post I am going to cover\u00a0WebLogic Server’s role in managing transactions<\/strong>\u00a0from topic\u00a0Transactions \u00a0<\/strong>for\u00a0WebLogic 12c Certification 1Z0-133 for Administrators<\/a><\/p>\n

<\/div>\n

\"\"<\/a><\/p>\n

 <\/p>\n

1.<\/strong> Transaction<\/strong> is a group of operations as single unit of work. For example when you transfer money from bank account then<\/p>\n

Operation 1 – Debit money from one account
\nOperation 2- Credit money in to second account<\/p>\n

Operation 1 & 2 are two operations treated as one single transaction.<\/p>\n

2.\u00a0<\/strong>Distributed Transaction (aka Global Transaction)<\/a> is group of operations (as part of single transaction) that spans across two or more data-store (database<\/strong>, application server<\/strong>, message queue<\/strong>, transactional cache<\/strong> etc.) on same or different hosts.<\/p>\n

3.<\/strong> Similar to transaction, global<\/strong> (or distributed<\/strong>) transaction<\/strong> must have ACID<\/strong> properties. (Atomic, Consistency, Isolation, Durability)<\/p>\n

4.<\/strong> XA<\/strong> (eXtended Architecture) is standard for executing Global Transaction <\/strong>(aka Distributed Transaction<\/strong>)\u00a0that accesses more than one back-end data store (database, application server, message queue, transactional cache etc.)<\/p>\n

5.<\/strong>\u00a0Transaction Manager <\/strong>(TM<\/strong>)\u00a0is responsible for creating and managing\u00a0Global Transactions<\/strong>\u00a0and deals with each\u00a0Resource Manager<\/strong>\u00a0(RM<\/strong>) like database, message queue, application server etc.<\/p>\n

6.<\/strong> Two-Phase Commit<\/strong> (2PC<\/strong>) protocol<\/strong> coordinates all the processes that participate in Global<\/strong>\/Distributed Transaction<\/strong> to commit or rollback the transaction.<\/p>\n

7.<\/strong> Two-Phase Commit<\/strong> (2PC) protocol<\/strong> uses two steps to commit changes in global<\/strong> (or distributed<\/strong>) transaction<\/strong>.<\/p>\n

a) Phase 1<\/strong> : TM<\/strong> asks RM<\/strong>s to prepare for changes.
\nb) Phase 2<\/strong> : If all RM<\/strong>s report that they are ready to commit, TM<\/strong> asks RM<\/strong>s to commit that makes changes permanent. If any RM<\/strong> is not ready to commit then TM<\/strong> tells all RMs to roll-back.<\/p>\n

8.<\/strong> WebLogic Server implements JTA<\/strong> (Java Transaction API<\/strong>) to manage transactions.<\/p>\n

9.<\/strong> WebLogic Server can act as Transaction Manager<\/strong> (TM) to the various transactional Resource Managers<\/strong> (RM) in Distributed<\/strong>\/Global transaction<\/strong>.<\/p>\n

10.<\/strong> As WebLogic Server manages global transaction, it tracks transaction in binary transaction log<\/strong> called as TLog<\/strong> (Transaction Log<\/strong>)<\/p>\n

 <\/p>\n

In next post I am going to cover next topic in Transactions<\/strong> i.e. Configuring WebLogic Server Transactions<\/strong><\/a> .<\/span><\/p>\n

For list of all exam topics in 1Z0-133 click here<\/a><\/p>\n

Related\/References<\/strong><\/span><\/p>\n