IBM WebSphere V5.0 Security - CGISecurity

The process flows as described below:1. The user provides the account name for the customer or the branch thenclicks the query button. The application uses a singleton helper class(ConsultationHelper) to look up and store the reference to the Consultationsession EJB.2. The Consultation EJB is a stateless session EJB, it performs the query on theserver side. It follows the facade pattern to hide the logic at the back-end.3. The Consultation EJB performs a query on one of the accounts using eitherthe BranchAccount or CustomerAccount entity EJBs, and returns the result tothe application.To follow the processes in the runtime, you can check the log file for theapplication server, SystemOut.log. The detailed runtime information about theapplication can only be found there, for example: the branch account updateusing JMS messaging, or detailed information about the client’s subject.Security rolesThe following roles are defined for the secured ITSOBank sample:► manager► clerk► accountant► consultant► mdbuser► AllAuthenticated► EveryoneNote: MDBUser is created to be used for delegation. The IncomingTransferMDB is using this role to call the Transfer Session Bean.There should be one user mapped to this role; that user will be used to do therun-as mapping.Deploying the sample applicationThis section provides step-by-step instructions on how to deploy the ITSOBankapplications.450 IBM WebSphere V5.0 Security Handbook