Weblogic Portal Interview Questions?

1. Difference between a website and a portal?

Website is collection web pages, typically it contains information about particular company. A portal is a powerful web site that gives users a single point of access (or gateway) to applications and information in a unified interface. For eg, Yahoo.com(home page) is great example of a portal.  

      2. What are the features of portal?

 Portal has got many features. To name a few: Personalization,  Authentication(single sign-on) and content aggregation.

     3. What are components of weblogic portal?

Look and feel components, header & footer(Shell), Menus, layouts, books & pages, portlets.    

     4. What is the difference between streaming portal and file-based portal?

To know more about this, please do visit my latest blog entry.

     5. What is backing file?

Backing file is java class used to pre-processing before portal object is rendered. The following portal controls support backing files:
    * Desktops
    * Books
    * Pages
    * Portlets
    * JspContent controls.

    6. How to create streaming portal/desktop?

Streaming desktop can be created using portal admin tool.

    7. What are the components of look-and-feel?

     Look & feel determines the appearance portal applications, it can be modified by developers programmatically or administrators using portal admin tool in staging and production environment. The following are components of look and feel:

• Look & Feel file(.laf)
• Skins
• Skeletons
• Themes
• Chromosomes and Genes
• Shells
• Layouts
• Menus  

     8. Difference between skin and skeleton?

Skins are collections of images, cascading style sheets (CSS), and JavaScript files that allow changes to be made to the look and feel of a portal without modifying the portal components directly. Skins basically provide the overall colors, graphics, and styles used by all components in a desktop interface.

Skeletons provide the physical boundaries of the portal components and provides references to the images, CSS, and JavaScript functions from the skin needed to render the portal. A portal web project can have multiple skeletons. When you select a Look & Feel for a desktop, a specific skin and skeleton is used. Each type of portal component, from a desktop to a portlet's title bar, has an associated JSP file, called a skeleton file that renders it.

     9. Difference between Genes and chromosomes?

Genes are implemented as simple text strings that are inserted into CSS styles or JavaScript files as variables. You define genes in an XML .chromosome file. In a .chromosome file, you could define a gene called "bodyColor" and assign it a value of "red," like this:

<gene name="bodyColor">
    <value>#FF0000</value>
</gene>

In your CSS file, you could use bodyColor as a variable:

body {
     border:1px solid ${bodyColor}
     };

When the page is rendered in a browser, the inlined style definition becomes:

body {
     border:1px solid #FF0000
     };

When you use this gene in your CSS files, you only need to modify the gene value itself to cascade the change throughout all configured CSS files rather than changing the value manually in each CSS file.

Chromosomes are simply the files that contain one or more genes. You can create multiple chromosome files that contain the same gene names, though with different gene values. By simply referencing a different chromosome in your Look & Feel file, you can simulate a completely different Look & Feel without changing any of your core Look & Feel files. 

10. What is shell?

Shells define the header and footer regions of a portal. Shells control the content that appears in a desktop's header and footer regions. You can configure a shell to use specific JSPs, page flows, HTMLs to display content in a header or footer. You can place portlets too in a header or footer of a shell.

11. Difference types of portlets?

• JSP and HTML Portlets
• JSR 168 portlets
• Java Page Flow Portlets
• Java Server Faces (JSF) Portlets
• Struts Portlets
• Remote Portlets
• Browser (URL) Portlets
  

12. How is IPC (inter-portlet communication) happening?
Watch this page soon for an answer...

13. What are portlet modes?

Portlet Modes allow you to affect the end user’s ability to edit the portlet or display Help for the portlet. You add icon buttons to a portlet’s title bar to indicate the availability of a mode. The following pre-defined modes exist for WebLogic Portal:

    * Edit – Lets you specify a custom file that lets users modify the portlet's content when they click the Edit button.
    * Help – Lets you specify a custom file that shows users help content for the portlet when they click the Help button.
You can also create your own custom portlet modes using WebLogic Portal.

14. Types of portlet states?

Portlet states determine the end user’s ability to affect the rendering of a portlet. WebLogic Portal supports following portlet states:

•     Normal – the typical rendered appearance of the portlet.
•     Minimize – Collapses the portlet, leaving only the title bar, when the user clicks the Minimize button.
•     Maximize – Makes the portlet take up the entire desktop area (not including the desktop header and  footer) when the user clicks the Maximize button.
•     Float – Displays the portlet in a popup window when the user clicks the Float button.
•     Delete – Removes the portlet from the desktop when the user clicks the Delete button.When you use the Portlet Wizard to create a portlet, state and mode settings are available on the Portlet  Details dialog. These settings can also be edited in the portlet’s Properties view. 

 15. What are different life cycles of backing files?
         init(), handlePostBackData(), preRender(), dispose().