Websphere Portal interview question and Answers
ANS: 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.
2. What are the 3 different ways of installing a portlet application in WebSphere Portal ?
* Install a portlet using the portal administration page using Web Modules portlet.
* Install a portlet using xmlaccess tool.
Pre-deploy a portlet as a standard EAR by installing the portlet WAR file in WAS console and then registering the portlet using xmlaccess.
3. What is the purpose of Release Builder tool in WebSphere Portal?
ANS: Release Builder enables management of release configurations independent of user configurations and used during staging of follow-on releases of WebSphere portals, configurations, and artifacts need to be moved between systems.
4. What is the difference between Application Server and Portal Server ?
ANS: Application servers extend the ability of a Web server to handle Web application requests, and enables a server to generate a dynamic, customized response to a client request. A portal server extends the application server by providing a portlet container that can run portlets and to create portal a website that provides users with a single point of access to Web-based resources by aggregating those resources in one place.
5. What changes needs to be done to view changes to your theme and skins JSPs without restarting the portal server ?
ANS: You need to enable automatic JSP loading by setting reloading Enable property to true in ibm-web-ext.xmi file of the wps.ear.
6. List different types of user registry supported by WebSphere Portal ?
ANS: LDAP (includes LDAP with an optional database user registry).
Database user registry.
Custom User registry, (non-LDAP, non-database).
7. What are the steps involved in deploying themes and skins in a clustered production websphere portal environment?
ANS: Export the WebSphere wps.ear (Portal EAR) using wsadmin.
Use Ear Expander tool to expand the exported wps.ear file.
Copy the updated themes and skins into../themes/html…/skins/html folder.
Use Ear Expander tool to collapse the EAR directory into an EAR file.
Use wsadmin to update the wps.ear to complete the deployment of updated themes and skins.
8. What are the two methods to install the empty staging WebSphere portal server?
ANS: Empty portal contents on the staging server by running the ./WPSconfig.sh action-empty-portal.
Install portal with the ./install.sh -W emptyPortal.active=”True” option.
9. What portal resources are scoped for virtual portal?
ANS: Portal pages.
Portal Search Engine search services and search collections. This includes the search content sources.
10. How do you enable temporary and extended trace logging for WebSphere Portal?
ANS: Temporary traces can be set for a temporary period by using the administration portlet Enable Tracing or the IBM WebSphere Application Server administrative console and also using the Enable Tracing portlet in the portal administration page.
To enable extended trace settings for a longer period of time, that is, for more than one session, switch them on in the WebSphere Application Server configuration, save the updates and restart the portal server.
11. What are the two types of rendering portlets?
ANS: Local rendering portlet and Remote rendering portlet.