Websphere portal

JSR 286 Concepts :- The major changes in JSR 286 are events, public render parameters, resource serving and portlet filter.
Public render parameters :- render state that can be shared between portlets.
1)define in portlet.xml
2) response.setRenderParameter("zip-id", "10025")
3) response.getParameter("zip-id")
Events:- portlet events that a portlet can receive and send (processEvent())
1)Define event-definition,supported-publishing,processing-event
2)issue an event(response.setEvent())
3)Process the event(request.getEvent())
Resource Serving :- enables a portlet to dynamically serve a resource. ResourceURL has been introduced for this. The Resource URL calls the new serveResource() of portal class
Portlet Filter :-  used to modify the content of the portlet request and portlet response before or after any life cycle method of the portlet (Action,Event,Render,ResourceFilter)
Portlet service :- used to provide common functionality to portlets(SearchService, LocationService, or a MailService). It uses a JNDI lookup to retrieve a PortletServiceHome object, which is used to retrieve a portlet service implementation
Credential Vault :- The credential vault is a repository where credentials are stored
WEB integration :- is a solution which allows external web applications like Quickr to be integrated with WebSphere Portal
Application Object :- is a java object existing at a known location in the request context and which implements the SelfInitializingApplicationObject interface.
Portal URL's :-  

• Render URLs :  This type of URL is used for retrieving a general view of a Portal page.
• Action URLs :  An Action URL typically targets a specific portlet, and might cause server-side state changes.
• Resource URLs: Create a URL to the resource in your page to trigger the serveResource life cycle using: Either the <portlet:resourceURL/> tag or Or the RenderResponse.createResourceURL() API in the render() method.
• Friendly URLs : Friendly URLs have human-readable strings in the URL that describe the path to a Portal page, it might also include an encoded Navigational State document.
• Vanity URLs : Vanity URLs are similar to Stateless Friendly URLs, in that they are human-readable and do not have an encoded Navigational State document.

PUMA API :- used to access (find, create, modify and delete) the information about WebSphere Portal users and groups
Vanity URL :- Vanity URLs are short URLs that people can easily remember. They are shorter than full WebSphere Portal URLs. They are sometimes also called marketing URLs. You can publish vanity URLs for marketing campaigns through different channels, such as email or print. This way, you can use vanity URLs to direct customers to a specific portal page or content item. To create vanity URLs, you use the IBM® WebSphere Portal tool-bar. 
Business users can assign vanity URLs to pages or to content on pages easily and change them frequently, for example, for promotion purposes. For site visitors, vanity URLs are self-speaking, short, and easy to remember. Site visitors can easily remember and type vanity URLs.
Vanity URL   :- Open the toolbar --> Page --> Vanity URL --> New vanity URL  --> provide "Vanity URL name, language, web content to load"
URL mappings :- Administration -> Portal Settings -> url mapping and click on new context.  provide URL name, lets say "myurl" - http://localhost:10039/wps/myportal/myurl
Friendly URL :- Manage Pages --> New Page --> provide values of "title, unique name, friendly URL name" and click on "Edit page layout" and add portlet to that page. http://localhost:10039/wps/myportal/Home/portal2 (where portal2 is friendly url name)
Script Portlet :- is a tool that enables a script developer to quickly develop portlets without having knowledge of Java, portlets or the JSR 286 portlet specification
Page --> Edit  Mode - On -->Create --> Applications --> Web Content --> Script portlet --> drag it to page