Distributed banking Application in JAVA using RMI implementing two phase commit protocol

**Programming Language:**JAVA using RMI for distributed application **Database:**MS Access I need a simple distributed banking application with two servers. The transactions need to be handled by “Two Phase Commit Protocol??, The out line of the protocol is given in the attached “Detailed specs?? document. **_Functionality to be included._** - There should be two types of accounts *Manager Account *User Accounts - Only manager should be able to create new user accounts or delete old accounts. - Manager should have access to all accounts. - User login & Manager login to be authenticated using Account Number and Password. - User account should be divided into (i) savings account (ii) checking account - User should be able to transfer money from savings to checking and vica-versa - The user should be able to withdraw and deposit money into his account. **_NOTE:_** - Transaction need to be applied as in the form of co-ordinator class. (not at the database level) - Both the servers will be updating their tables whenever any transaction takes place. ## Deliverables 1) Complete and fully-functional working program(s) in executable form as well as complete source code of all work done. 2) Deliverables must be in ready-to-run condition, as follows (depending on the nature of the deliverables): a) For web sites or other server-side deliverables intended to only ever exist in one place in the Buyer's environment--Deliverables must be installed by the Seller in ready-to-run condition in the Buyer's environment. b) For all others including desktop software or software the buyer intends to distribute: A software installation package that will install the software in ready-to-run condition on the platform(s) specified in this bid request. 3) All deliverables will be considered "work made for hire" under U.S. Copyright law. Buyer will receive exclusive and complete copyrights to all work purchased. (No GPL, GNU, 3rd party components, etc. unless all copyright ramifications are explained AND AGREED TO by the buyer on the site per the coder's Seller Legal Agreement). 4)The code needs to be well documented 5)The interaction between various classes need to be explained properly using class interaction diagrams. ## Platform "Windows XP", "in all 3.0+ versions of Internet Explorer and Netscape", "Linux (fedora)"