IBM WebSphere V5.0 Security - CGISecurity

►►►Buy-Side HubSell-Side HubTrading ExchangeApplication and Runtime patternsApplication and Runtime patterns are driven by the customer's requirements,they describe the shape of applications and the supporting runtime needed tobuild the e-business solution. In fact, they define how to implement the combinedBusiness and Integration patterns.Application patterns are chosen after selecting Business, Integration orComposite patterns and they lead to Runtime patterns. Runtime patterns areintroduced to group functional groups into physical nodes. The nodes areinterconnected to solve the initial business problem.For more information on patterns, refer to other documents in 11.6, “Moreinformation on Patterns for e-business” on page 367.Note: The ITSOBank sample application presented in this book is a simpleexample of a J2EE application, focusing mostly on the technology andsecurity features used to access customer account and transfer funds. We willuse this example throughout the chapter to present patterns-related aspects inthe design process. However, it cannot be considered a real life solutionreference and should not be used as a reference. It does not take into accountmany customer-related aspects and custom requirements that maysignificantly influence the final design approach.11.1.4 Patterns and the solution design processThe full solution life cycle process should include the review and selection ofeach Business, Integration and Composite pattern and adaptation to thecustomer’s needs. The process can often be shortened, when we already knowmany details about the solution. In such a case, we can jump directly to a specificdesign level.As the main subject of this book is security, we will not go through the full lifecycle process starting from business requirements and integration aspects. Wewill skip these subjects and go directly to the selection of appropriate Businessand Integration patterns. However, a few assumptions need to be made toconsolidate our understanding and lead our future decisions.352 IBM WebSphere V5.0 Security Handbook