Application patterns and shortcuts
Go to Shortcut : Patterns for e-business (Page 1 of 2)
Stand-Alone Single Channel
This Application pattern, also known as User-to-Business topology 1, is used when there is no need to integrate with legacy or third-party applications. It allows developers to replace the monolithic fat client design with a layered approach that uses a thin client with application business logic on the second tier. The second tier can access a local database maintaining the application data.
Review:
Directly Integrated Single Channel
This Application pattern (aka U2B Topology 2) extends the Stand-Alone Single Channel design by integrating with legacy and/or third-party applications. It allows the second tier's new application business logic to access existing applications, such as inventory management, or third party applications, such as a credit check. These applications reside on a third tier elsewhere in the network.
Review:
As-Is Host
This Application pattern (aka U2B Topology 3) helps to structure Intranet access to existing host applications. It does not include runtime patterns, product mappings, and guidelines.
Review:
Customized Presentation to Host
This Application pattern (aka U2B Topology 4) can be used to provide customized presentation to existing host applications without changing the underlying application. It does not include runtime patterns, product mappings, and guidelines.
Review:
Router
This Application pattern (aka U2B Topology 5) links multiple presentation tiers to any back-end client without hiding the back end from the user. This design provides fast, highly scalable, highly available Web enablement of existing business transactions with multiple presentation channels and multiple applications. This application is divided into three logical tiers with a one-to-one relationship between the tiers at runtime.
Review:
Decomposition
This Application pattern (aka U2B Topology 6) extends the Router application pattern by integrating business logic in the intermediate tier, making the third-tier applications seamless. Decomposition provides customer-oriented support systems rather than the product-oriented systems of the Router application pattern. A presentation node is linked to the decomposition node, which controls the application flow. The decomposition node breaks down the user request into individual application requests, forwards the requests to the applications, and then gathers the results to send back to the presentation node. The business logic of the application is divided between the applications and the decomposition node.
Review:
Agent
This Application pattern (aka U2B Topology 7) provides a unified customer-centric view that can be exploited for mass customization of services and for cross-selling purposes. The Agent application pattern allows for personalization of a Web site, with the objective of targeting Web content and applications to specific users. These personalization activities are driven by the application server.
Review: