The expression portal (lat. porta, "gate ") designates an application system, which is characterized by the following characteristics in computer science:
Briefly: "The ideal portal opens a common, personalisierten entrance to data, expert's assessments and applications "(Dataquest).
A further-seizing definition is:
Individual applications often become in Unterfenstern, which Portlets so mentioned organizes. In the Portlets contents from different sources on a portal side are summarized. The individual Portlets can be partly personalisiert by the user. The Portlets can be minimized or removed and had often also own assistance and configuration menus.
A further functionality is the integration of Web services. Since these were originally written for communication between applications, the presentation is not trivial, since for example input fields are provided with internal variable names to the necessary values only. Newer developments such as GUIDD try to repair this bad state.
The advantages of the portal technology are in the fact that a fundamental infrastructure is made available, which holds a part ready of the standard functionality of applications of Web. Depending upon manufacturer this basis functionality is more or less pronounced. With the large offerers "out the OF reach the box "functionality of Collaboration management over Personalisierung up to document and Knowledge management integration. Small ones and open SOURCE offerer do not come usually (still) beyond navigation and user management.
By the announcement of several applications under a surface the advantage comes to carries that the users of the portal do not have to change between applications and the necessary information gets at the correct time indicated. This is above all the case if during the portal conversion consistently the view is held level of the business processes. Therefore a Enterprise portal is a component of the concept of service-oriented architecture (SOA).
Disadvantages of the portal technology come above all to day if it concerns existing applications into a portal to transfer. The announcement and treatment of pure data can be usually made over Web services and integration environments such as SAP XI or IBM WebSphere MQ. As soon as however the Client of application which can be integrated makes further Workflow available, then this must be placed behind in the portal or over generic Tools to be provided. This is usually very
The general architecture of a portal plans a Web server, which receives and to the Portletengine forwards the requests of the users. This administers the life cycle of the Portlets and passes the action and Renderanfragen on to the individual Portlets, which are to be indicated in the inquired side. The Portlets looks for each other from the pertinent data sources its contents together. Here it is to be stated that data sources can be classical data bases, in addition, Web services and applications can be used here as sources. The Portlets is not on it is limited from a data source to serve, but can their contents from several data pots arrange.
Communication runs as follows internally between the Portletengine and the Portlets. On the Request, which is placed to the portal, identify the Portlet container the necessary Portlets. If the inquiry is an action inquiry, then on the appropriate Portlet the method is implemented performAction (). As soon as this is terminated becomes the Rendermethoden doView (), doEdit () or doHelp () the Portlets which can be indicated implemented. Which of these methods is implemented, determines the condition of the Portlets, which is administered by the container. These conditions can be extended by application and portal-specific conditions. Within the treatment of the Rendermethoden can be addressed now Beans or other processing classes or functions. The Rendering can besides by JSPs is supported, which are called over a dispatcher.
As standards for the Design of a Web-based portal in principle the same standards as to are considered any web page:
Standards for the integration from existing systems are:
For the portal technology relevant specifications are:
For the storage of articles and their short description several XML based file formats educate a family of standards:
Standards for the program-supported administration of contents are:
With a portal stand making available application-spreading achievements and thus the aspect of integration and not the technical implementation (e.g. Web-been based) in the foreground. It is obvious to fall back with the structure of a portal either to an infrastructure to use the Enterprise Application integration (EAI) for the component or a portal standard software the EAI availed itself.
Many portal solutions are programmed in Java, in order to achieve a greatest possible system independence.
By portal standard software, frequently also as Enterprise portal designation, is understood generally a software program, which it permits enterprises a portal to construct. In addition such a software has functions how:
After the Gartner Group (commercial) the portal often commodity market can be divided dependent on market operational readiness level ("Ability OF Execute ", German about "ability for execution ") and cover degree ("Completeness OF vision ", German "completeness of the vision ") in four quadrants:
| \ | "Challengers "("challengers ") manufacturer with high market operational readiness level, but with insufficient cover degree of their portal system.
| "Leaders "("market leaders ") manufacturers with high market operational readiness level and high-grade integrated and scalable products.
|
|---|---|---|
"Niche Players "("niche participants ") niche manufacturer with the concentration on smaller markets and specialization on some function or operational areas.
| "Visionaries " ") manufacturer without large market operational readiness level, but with large visions.
| |
| Market organization according to Gartner (2005, see Gartner: Magic quadrant for horizontal portal Products, 2005) | Cover degree \ rightarrow | |
In addition, beside commercial portal often commodity open SOURCE portal systems exist, e.g. Liferay, DotNetNuke or Apache of portal and Cocoon of the Apache software Foundation.
We found here 2 articles.
P» Portal (computer science)» PSYCED |
We found here 4 related websites.
Index | Privacy | Terms Of Use | Sitemap | Feedback