Explore topic-wise InterviewSolutions in .

The following are the reasons to use PORTALS:

• Unified way of presenting information from DIVERSE sources.
• Services like email, news, infotainment, stock PRICES and other features are OFFERED by portals.
• Provides consistent look and feel for enterprise. Eg. MSN, GOOGLE sites.

The following are the reasons to use portals:

PSML was created to allow abstraction and CONTENT structure within Jetspeed.

It has two markups:

• Registry markup: Describes the AVAILABILITY of resources to the Jetspeed engine. It supports multiple portlet registries.
• Site markup: The availability of portlets are described by this markup, which is DISPLAYED for a given user.

PSML was created to allow abstraction and content structure within Jetspeed.

It has two markups:

This SERVER performs the management of job scheduling and IMPLEMENTATION of a portal. It accesses all REMOTE crawlers and profile services retrieved and STORED from a remote database.

This server performs the management of job scheduling and implementation of a portal. It accesses all remote crawlers and profile services retrieved and stored from a remote database.

The portlet view of the portlet container is defined by PortletContext. It allows the availability of RESOURCES to the portlet. Using this context, the portlet log can be ACCESSED and URL references to resources can be obtained. There is ALWAYS only one context per portlet APPLICATION per JVM.

The portlet view of the portlet container is defined by PortletContext. It allows the availability of resources to the portlet. Using this context, the portlet log can be accessed and URL references to resources can be obtained. There is always only one context per portlet application per JVM.

This server hosts IMAGES and other web PAGE content used by web SERVICES and a PORTAL. With this CONFIGURATION, large static files are to be sent directly to the browser without portal server impacts.

This server hosts images and other web page content used by web services and a portal. With this configuration, large static files are to be sent directly to the browser without portal server impacts.

The ENTERPRISES extend to customers for ORDERING, billing, services by USING B2C portals.

The enterprises extend to customers for ordering, billing, services by using B2C portals.

Function-based portals

• Horizontal Portals: These are the portals are of type general INTEREST. Yahoo!,Lycos,AOL,Freeserve,Sympatico are examples of horizontal portals.
• Vertical Portals: They provide a gateway to the information pertaining to a specific industry such as INSURANCE, banking, finance, automobile, telecom etc.

USER-Based Portals

• B2B Portals : The enterprises extend to suppliers and partners by using B2B portals.
• B2C Portals : The enterprises extend to customers for ordering, billing, services by using B2C portals.
• B2E Portals : The enterprise knowledge base integration and related applications into user CUSTOMIZABLE environment is done with B2E portals. This environment is like one stop shop.

Function-based portals

User-Based Portals

This server INDEXES and SEARCHES all the INFORMATION, applications, COMMUNITIES, documents, web sites through portal.

This server indexes and searches all the information, applications, communities, documents, web sites through portal.

The FOLLOWING are the reasons to use portals:

• UNIFIED way of presenting information from diverse sources.
• Services LIKE email, news, infotainment, STOCK prices and other features are offered by portals.
• Provides consistent look and feel for ENTERPRISE. Eg. MSN, Google sites.

The following are the reasons to use portals:

The enterprise knowledge base integration and RELATED APPLICATIONS into user CUSTOMIZABLE environment is DONE with B2E portals. This environment is LIKE one stop shop.

The enterprise knowledge base integration and related applications into user customizable environment is done with B2E portals. This environment is like one stop shop.

The portlet view of the portlet container is DEFINED by PortletContext. It allows the availability of resources to the portlet. USING this context, the portlet log can be accessed and URL references to resources can be OBTAINED. There is ALWAYS only one context per portlet application per JVM.

The portlet view of the portlet container is defined by PortletContext. It allows the availability of resources to the portlet. Using this context, the portlet log can be accessed and URL references to resources can be obtained. There is always only one context per portlet application per JVM.

WEB CONTENT PUBLICATION and management for portals and web applications are supported by this server. Its functionality can be ACCESSED by a remote web SERVICES through Enterprise Web Development kit.

Web content publication and management for portals and web applications are supported by this server. Its functionality can be accessed by a remote web services through Enterprise Web Development kit.

The ENTERPRISE KNOWLEDGE BASE integration and related applications into user customizable ENVIRONMENT is done with B2E portals. This environment is like one stop SHOP.

The enterprise knowledge base integration and related applications into user customizable environment is done with B2E portals. This environment is like one stop shop.

The enterprises EXTEND to suppliers and PARTNERS by USING B2B portals.

The enterprises extend to suppliers and partners by using B2B portals.

User identification across many requests and transient information storage about the user is processed by PortletSession interace. One PortletSession is created per portlet application per client.

The PortletSession interface PROVIDES a way to identify a user across more than one request and to store transient information about that user.

The storing of information is defined in two scopes- APPLICATION_SCOPE and PORTLET_SCOPE.

APPLICATION_SCOPE: All the objects in the session are available to all portlets,servlets, JSPs of the same portlet application, by USING APPLICATION_SCOPE.

PORTLET_SCOPE: All the objects in the session are available to the portlet during the requests for the same portlet window. The attributes persisted in the PORTLET_SCOPE are not PROTECTED from other WEB components.

User identification across many requests and transient information storage about the user is processed by PortletSession interace. One PortletSession is created per portlet application per client.

The PortletSession interface provides a way to identify a user across more than one request and to store transient information about that user.

The storing of information is defined in two scopes- APPLICATION_SCOPE and PORTLET_SCOPE.

APPLICATION_SCOPE: All the objects in the session are available to all portlets,servlets, JSPs of the same portlet application, by using APPLICATION_SCOPE.

PORTLET_SCOPE: All the objects in the session are available to the portlet during the requests for the same portlet window. The attributes persisted in the PORTLET_SCOPE are not protected from other web components.

Publication and MANAGEMENT of web content for portals and web applications ALONG with FORM based publishing, BRANDING, templates, content expiration is allowed by this server.

Publication and management of web content for portals and web applications along with form based publishing, branding, templates, content expiration is allowed by this server.

• Highly integrated web applications’ costs reduce by portals. JBoss enables the reusability of branding and deploying new applications of composite NATURE.
• The users and the industry can be customized, personalized their experiences in a secure and WELL governed manner by using JBoss portal.
• JBoss incorporate components into a portal as REUSABLE and standardized portlets, as Jboss is PLATFORM independent.
• Performance and scalability is ensured.

They PROVIDE a gateway to the information pertaining to a specific INDUSTRY such as insurance, banking, FINANCE, automobile, TELECOM etc.

They provide a gateway to the information pertaining to a specific industry such as insurance, banking, finance, automobile, telecom etc.

The CORE implementation of the portal is UI, hosted by a Portal server. The HTTP requests, HTML responses, and returning appropriate portal pages are handled by the Portal UI. Enterprise Web application also can be handled by the Portal Server.

The portal architecture has the following:

• Automaton Server: This server performs the management of job SCHEDULING and implementation of a portal. It ACCESSES all remote crawlers and profile services retrieved and stored from a remote database.
• Image Server: This server hosts images and other web page content used by web services and a portal. With this configuration, large static FILES are to be sent directly to the browser without portal server impacts.
• Search Server: This server indexes and searches all the information, applications, communities, documents, web sites through portal.
• Collaboration Server: Web content publication and management for portals and web applications are supported by this server. Its functionality can be accessed by a remote web services through Enterprise Web Development kit.
• Content Server: Publication and management of web content for portals and web applications along with form based publishing, branding, templates, content expiration is allowed by this server.
• Authentication Server: This server handles the portal authentication for users and remote services can be accessed through EDK.
• Remote Servers: Web services written using the EDK are hosted by remote servers. The servers can be in different countries, on different platforms and domains.

The core implementation of the portal is UI, hosted by a Portal server. The HTTP requests, HTML responses, and returning appropriate portal pages are handled by the Portal UI. Enterprise Web application also can be handled by the Portal Server.

The portal architecture has the following:

PSML was created to allow abstraction and CONTENT structure within Jetspeed. It has two markups:

1. Registry markup: DESCRIBES the availability of resources to the Jetspeed engine. It SUPPORTS multiple portlet registries.
2. SITE markup: The availability of portlets are DESCRIBED by this markup, which is displayed for a given user.

PSML was created to allow abstraction and content structure within Jetspeed. It has two markups:

These are the portals are of TYPE GENERAL INTEREST. YAHOO!,Lycos,AOL,Freeserve,Sympatico are examples of horizontal portals.

These are the portals are of type general interest. Yahoo!,Lycos,AOL,Freeserve,Sympatico are examples of horizontal portals.

Portlets are UI COMPONENTS that are pluggable and are managed, displayed in a web portal. Markup CODE fragments are produced by the portlets which are aggregated into a portal page.

A portlet resembles an application that is web based and is hosted in a portal. EMAIL, discussion forums, news, BLOGS, weather reports are some of the examples of portlets.

Portlets are UI components that are pluggable and are managed, displayed in a web portal. Markup code fragments are produced by the portlets which are aggregated into a portal page.

A portlet resembles an application that is web based and is hosted in a portal. Email, discussion forums, news, blogs, weather reports are some of the examples of portlets.