Along with providing interactive applications to handle its orders and billing information, TSP wants to integrate the Web application with backend services to automate processes of order provisioning, fulfillment, and banking services to enhance the application's efficiency. XML should be supported in the process. As business rules change frequently, the company should be able to modify or update the application at runtime. The application will also be used as the basis for a product sold by TS to other businesses within the telecom distribution industry. Each circle denotes a pattern, with arrows representing the relationships among patterns.
Architectural patterns are green-colored to indicate the beginning of the language.
On the B2B side, the REAI architectural and related design patterns deal with distributed integrations. Before delving into the language details, let us work through the language to show how the patterns work together. In our scenario, a customer accesses the TSP Website using a Web browser, hits the items of interest, and generates HTTP requests to the Web server, which directs all the requests to the Application Mediator, with the mediator working as a single entry point to the application. As the name suggests, the Template Method combines with JSP Tags and JSP Pages to handle the presentation scenario. Following that, it independently forwards the customer's requests to the Event Processor pattern.