What Sun Java System Portal 7.1 can and has

Original author: sun documentation center
  • Transfer
This article is a translation - compilation of several docks on the portal. I added a comparison to the coolest portal server - IBM WebSphere Portal


References :
Sun Java SystemPortal Server 7.1 Technical overview.pdf

Single Sign-On Authentication (SSO)


Using SSO, a user can access portal resources after passing authentication once. No re-entry of user credentials is required.

AccessManager


In the Java Enterprise System, an access manager component manages SSO. The portal server is one of the components of the system in which SSO is running.

SSO Adapter service

- In order to receive data from third-party servers whose servers are not integrated into the AccessManager, the Portal Server uses the SSO Adapter service. Services accessed through the SSO Adapter can provide mail, scheduling, address books, etc.

Portal server desktop


The portal server aggregates and displays information to the user. What the user sees in the browser is called Standard Desktop (standard desktop).
In addition to the standard desktop, there is Mobile Desktop (mobile desktop) and Voice Desktop (voice desktop).

A standard desktop is a web page whose contents are arranged in rows and columns. The portal server uses two ways to send content to the desktop:

Channels

(channels) is a special area for content, which is a small window on a web page. A channel consists of:
• Provider object
• Configuration files
• Data files: XML, HTML templates that can be processed by a channel
For example:
News channel - displays links to news
Mail channel (Mail channel) - displays messages sent to users

Container channels

(Channel container) - aggregates channels. The portal server supports AJAXTableContainerProvider, which enables asynchronous loading of channel content, provides drag'n'drop functionality.
For example:
Table container - Arrange channels in rows and columns.
Tab container - Distributes channels (most often table containers) into tabs

Supported channel types:
The portal server supports the following channel types:
Standard Java portlets , which use the standard Portlet 1.0 defined in JSR 168.
Providers that use proprietary interfaces:
JSP providers to compile and execute JSP pages
XML providers for translating XML files
Remote portlets that use W eb Services for Remote Portlets WSRP 1.0 standard is a special protocol for web services used to integrate portlets (special JSR 168) located on remote resources.

Portal Server Community Roles


(Roles of users of community services running on the portal server)
There are three types of roles:
Owner (Community owner), Member (Community member), Visitor (Visitor).
The owner of the community can create and delete the community, give out membership, as well as deprive users of access rights to the community. It can carry out any operations with content (creating articles, downloading files, deleting, etc.).
A community member can participate in community activities (surveys, discussions), create content, see other community members, general information about the community.
The visitor is deprived of all basic rights, can view content created in the community

Services for community users:


Wiki

- The Wiki container and corresponding portlets allow the community to work with an interactive site that hosts community content. Community members can create new and modify existing content (pages, files).
• Discussions — Discussions in a community are a mechanism for sharing information within a community. There is a mechanism for subscribing, searching for information.
• Blogs - The blog portlet enables community members to blog on the web.
• Surveys and Polls - Community members can participate in surveys and surveys. Questions format: yes / no, optional answers, free form.
• Searches (Search) - Community members can search the community portal.
• Events and Tasks - Community members can use calendar planning based on SunTM Calendar Server software to create, edit, and respond to events and tasks of community projects.
• File Sharing - Members of the 8566a community can share files: create folders, upload and download documents, any other kind of information.

Portal Server Search Server Robot


(portal server search robot) The
search robot searches, converts and organizes the resources available to portal users.
Search robot functionality:
Separating links to resources and navigating through them (writing to the registry)
Formalized description of found resources
Recording resource descriptions in the database (indexing)

You can customize the behavior of a search robot using the following steps:
Setting a work schedule
Defining a meta search for resources
Setting the depth of a resource search
Specifies the types of resources that the robot is looking for.

AJAXTableContainerProvider


References :
Java SystemPortal Server 7.1 Update 1 AJAX Table Container.pdf


The provider integrates the capabilities of Asynchronous JavaScript and XML (AJAX) into the portal framework. The container provides the ability to asynchronously load individual channels and portlets on the portal page. Let's say there are three fast channels and one slow channel on the page. The container will download the first three channels, and the user will be able to start working without waiting for the full loading of the contents of the web page.
Container features
• Positioning channels and individual portlets by dragging and dropping
• Asynchronous interaction on events: minimizing and maximizing a channel, deleting a channel from the user’s page.
• Independent updating of individual channels, portlets without reloading the entire page.
• Editing portlets without reloading the entire page.
• Quick and easy adding and removing channels.
• Customizable look of the portal page.
Limitations of AJAXTableContainerProvider
• JavaScript must be enabled in user browsers.
• The container does not automatically add the functionality of the AJAX component. The developer himself must write the appropriate code in order to use the capabilities of the AJAX container.
• By default, the editing mode for channels and portlets is hidden from the user. The fact is that in an AJAX container, the width of the window in edit mode is smaller, in a similar mode
• In another container.
• Only one AJAX container can be placed on the portal page.

Conclusion:
And so, finally, the 7.1 portal has come close to the existing standard of the portal of all time, to the WebSphere portal.
I want to remind you that IBM is an extremely conservative company. Now there is an active migration from portals 5.0 to portals 5.1. On portals 5.0, Java 1.3 works, on portals 5.1 - Java 1.4, and only on portal 6.1 Java 1.5 appeared
. On the Sana portal, you can write under 1.6.
In 6.1 version of WebSphere there is an analogue of AJAXTableContainerProvider, when our portlets are overloaded and react to events independently of each other, and page reloading is not required.
Unfortunately, 7.1 only works with JSR-168, and IBM portals, in addition to their specification, support the JSR-168 specification.
Currently, the Sanovo portal 7.2 is available, which holds both the 168th and 286 specifications. By the way, IBM approved the specification 286, so it is expected that the company's portals will also work with the native Sanovo specification.
Together with the IBM portal, you can put WCM-Web Content Manager, this is a kind of CMS in the interpretation of IBM. If interested, I can tell you what its originality is. When I had to work with WCM, I was extremely surprised by its architecture, I had never seen anything like it before. WCM 2.0 sat on portal 5.0, and WCM 5.1 sat on portal 5.1. The
guys decided to synchronize the portal and content manager versions. In addition to versions, more significant changes have occurred in WCM, but more about that some other time.
In addition to the CMS for portals, IBM has exactly the same SSO technology. By the way, because of it, interesting glitches occurred on the portal 5.0 (WebSphere Portal Server) and the application server 5.0 (WebSphere Application Server):
Suppose you log in to the portal under the same user from the same browser and then to the admin console of the application server. When debugging an application, such a need often arises.
After entering the admin console, your session on the portal is forcibly killed. You make changes on the application server (for example, restart the web service your portlet goes to), switch to the portal tab in the browser and find that your session is no longer valid.
You re-log into the portal, test your portlet, go back to the browser tab with the admin console and find that the session on the admin console is dead. By logging in to the admin console, you are killing the session on the portal.
Here is such a strange jamb with a general user session on the portal and application server of this portal.

In general, the 7.1 portal is not much inferior to the IBM portals. The main thing is that JSR-286 gets support, begins to live, then IBM may have a serious competitor in the field of portal technologies.

Also popular now: