Websphere Portal

Here are some the artifacts to consider when creating build and deployment scripts.
  1. Portlets
  2. Skins
  3. Themes
  4. Property files
  5. NLS Resource Bundles
  6. Configuration files that go under /shared/app/config/services
  7. Shared Libraries
  8. XMLAccess scripts
  9. Web Files

Portal: 
- A set of J2EE application supported by Websphere's web container.
- A Container providing services to Java programs called portlets.
Portlet is an application, which are deployed on to a page.
Page is nothing but a website.
Themes - decides the look and feel of the page (Header and Footer) -                                default.jsp
Skin - decides the look and feel of the Portlet. - control.jsp




API - Application programming Interface
JSR API - is an independent API 

We have 2 JSR's 
JSR 168 - Supports 5.0, 5.1, 6.0, 6.1 and 7.1
JSR 286 - Introduced from 6.1 


Portal Components:

  • Websphere Application Server
  • Websphere Member Manager
  • Websphere Portal Personalization
  • Document Manager
  • Websphere Portal Search
  • Administration
https://www.ibm.com/developerworks/community/forums/html/topic?id=77777777-0000-0000-0000-000014068984

websphere Portal runtime application is wps.ear 
websphere admin console application is adminconsole.ear

create and set access to pages
Deploy portlet
set access to portlets
create search index
create and manage virtual portals

Configuration Tools:

ConfigEngine - command line configuration tool
configizard - gui based portal configuration tool
dpiwiz - gui based Domino/portal integration tool



http://www-10.lotus.com/ldd/portalwiki.nsf/xpViewCategories.xsp?lookupName=Deployment%20Scenarios%20for%20WebSphere%20Portal














Comments

Popular posts from this blog

Aix Interview Commands

Install Jenkins Using Chef on Redhat OS