System for portal architecture
A system for a portal architecture may include a model service component. The model service component may be arranged to connect a presentation device to a business manager component. An aspect oriented architecture may be associated with the model service component. A service oriented architecture may be associated with the model service component, the service oriented architecture being arranged orthogonal to the aspect oriented architecture.
1. A portal system, comprising:
a user interface component;
process components;
a business manager component implementing business functions as services and comprising business logics;
a computer processor for executing a model service component, the model service component being arranged between a presentation device and the business manager component and separating the user interface component and the process components from the business manager component;
wherein the model service component implements common logic and common functionality with an aspect oriented architecture having aspect components associated with the model service component;
wherein the business manager component is arranged to use the common logic and the common functionality provided by the aspect components, the business manager component configured with a service oriented architecture and
wherein by running the aspect oriented architecture and the service oriented architecture, the service oriented architecture creates a specific logic to exploit service and the aspect oriented architecture creates generic components to manage the service;
a business manager interface, the business manager interface being arranged between the business manager component and the model service component;
wherein the model service component is arranged to connect the user interface component and the process components to the business manager component through the business manager interface by using a web services transportation protocol.
2. The system of claim 1 wherein the aspect oriented architecture comprises security, exception handling, logging and caching aspects.
3. The system of claim 1 wherein the service oriented architecture comprises support, order, catalogue, account and customer services.
4. The system of claim 1 wherein the presentation device comprises web and mobile portals.
5. The system of claim 1 further including legacy systems, wherein the business manager component connects the model service component to the legacy systems.
6. The system of claim 1 further including a layout database for storing data, wherein the data comprises layout information.
7. The system of claim 6 wherein the layout information comprises information about different portals, the information comprising: webparts displayed, webpart access rules, and contents of webparts.
8. The system of claim 6 further comprising a web application, wherein the web application reads the data from the layout database.
9. The system of claim 6 wherein at least two entities which are located in different locations contribute to the layout database, the entities comprising a plurality of users.
10. The system of claim 9 wherein the entities define a state machine to be shared via a dynamic link library.
11. A model service component for connecting different portals to legacy systems, comprising:
a computer processor for executing the model service component;
an aspect oriented architecture means having aspect components, the aspect components implementing common logic and common functionality; and
a service oriented architecture means having service components, the service components being arranged to use the common logic and the common functionality provided by the aspect components, the service components comprising a specific logic to exploit service;
wherein by running the aspect oriented architecture and the service oriented architecture, the service oriented architecture creates the specific logic to exploit service and the aspect oriented architecture creates generic components to manage the service;
where the model service component is arranged to connect a user interface component and process components to a business manager component through a business manager interface by using a web services transportation protocol, the model service component separating the user interface component and the process components from the business manager component.
12. The model service component of claim 11 wherein the aspect oriented architecture means comprises security, exception handling, logging and caching aspects.
13. The model service component of claim 11 wherein the service oriented architecture means comprises support, order, catalogue, account and customer services.
14. The model service component of claim 11 wherein the aspect oriented architecture means and service oriented architecture means connects the different portals to the legacy systems.
15. The model service component of claim 11 further including a layout database means for storing data, wherein the data comprises layout information.
16. The model service component of claim 15 wherein the layout information comprises information about the different portals, the information comprising: webparts displayed, webpart access rules, and contents of webparts.
17. The model service component of claim 15 further comprising a web application means, wherein the web application means reads the data from the layout database means.
18. The model service component of claim 15 wherein at least two entities which are located in different locations contribute to the layout database means, the entities comprising a plurality of users.
19. The model service component of claim 18 wherein the entities define a state machine to be shared via a dynamic link library.