Interview Questions on websphere portal - Series1
1)servlet and portlet difference
2)portlet wiring
3)jsr 286
4)interportlet comm
5)jsr 168 286
6)url mappings
7)portlet code vs servlet
8)themes and skins
9)rad
*10)maven
*11))oblix
=======================================
==========================ADMIN======================================
for admin,
xmlaccess,
page creation,
tam configuration,
ldap configuration,
clustering,
troubleshooting, logging and tracing,
theme deployment,
portlet deployment,
database transfers,
perf tuning
===============================================
WebSphere Portal Interview Questions for an Administrator
List of interview questions that will help you in technical interview.
1.
What is the difference between Application Server and Portal Server ?
Application servers extend the ability of a Web server to handle Web application requests,and enable a server to generate a dynamic, customized response to a client request. A portalserver extends the application server by providing a portlet container that can run port letsand to create portal a website that provides users with a single point of access to Web-basedresources by aggregating those resources in one place.
2.
What are the steps involved in deploying themes and skins in a clustered production websphere portal environment?
Export the Web Sphere 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 andskins.
3.
What changes needs to be done to view changes to your theme and skins JSPs withoutrestarting the portal server?
You need to enable automatic JSP loading by setting reloading Enable property to true inibm-web-ext.xmi file of the wps.ear.
4.
What are the 3 different ways of installing a portlet application in web Sphere 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 andthen registering the portlet using xmlaccess.
5.
What is the purpose of XML Access configuration file Export.xml & ExportRelease.xml? Whatis the difference? & When will you use one over the other?
Export.xml exports the complete portal configuration and useful when transferringconfigurations between development installations.ExportRelease.xml exports the complete portal configuration from the release domain asrequired by the portal Release Builder tool and useful when transferring different releaseconfigurations between staging and production environments.
6.
List me the steps involved in building a release in web Sphere Portal ?If you have a completely new installation of the staging server and the production server:Install the staging server, then install the production server.Develop a release on the staging server.
Build the release on the staging server.Empty portal contents on the production server by running the WPSconfig.sh|bat action-empty-portal task.Import that release onto the production server. Refer to Transferring a completeconfiguration for information.If you already have a production server without a staging system:Export the release of your production server.Install an empty staging server using one of the following two methods:Install the staging server with the flag -W emptyPortal.active=True.After installing and configuring the staging server, run the WPSconfig.sh|bat action-empty-portal task.Import the production release onto the staging server. Refer to Transferring a completeconfiguration for information.Develop and build a new release on the staging server.Export that new release from the staging server.Use Release Builder to generate the differential between the two releases.Import the differential onto the production server.
7.
What is the purpose of Release Builder tool in web Sphere Portal ?Release Builder enables management of release configurations independent of userconfigurations and used during staging of follow-on releases of WebSphere portals,configurations, and artifacts need to be moved between systems.
8.
What are the steps involved in editing WebSPhere Member Manager (wmm.xml) files on afederated node ?On the primary node of the WebSphere Portal cluster, check out the files using./WPSconfig.sh check-out-wmm-cfg-files-from-mgr. task.Make any changes to the Member Manager files. The files can be edited in theportal_server_root/wmm directory on the WebSphere Portal node.When you have completed your changes, check the files back in using ./WPSconfig.sh check-in-wmm-cfg-files-to-dmgr.
9.
How to change the default portal URI /wps/portal after installation ?Set the property WpsContextRoot to the new URI and run ./WPSConfig.sh modify-servlet-path task.
10.
List different types of user registry supported by WebSphere Portal ?LDAP (includes LDAP with an optional database user registry).Database user registry.Custom User registry, (non-LDAP, non-database).
11.
What is LDAP realm support and why would I want to use it?A Realm allows you to group users from one or more LDAP trees of one user registry andexpose them as a coherent user population to WebSphere Portal; this is also referred to ashorizontal partitioning. Realms allow a flexible user management with various configuration
options; for example, you can combine principals from one or more corporate LDAP tree. Arealm must be mapped to a Virtual Portal to allow the realm's defined user population tologin to the Virtual Portal.
12.
What is an Application group and why would I want to use it ?Application groups are a concept that allows you to define user groups within the databaseuser registry with members (users or groups) contained in the LDAP user registry youconfigured. The benefit of application groups is that you can create Groups that are onlyused in WebSphere Portal particularly in scenarios where there is Read-only LDAP or specialgroup setup specific to the portal.
13.
What are the two methods to install the empty staging WebSphere portal server ?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.
14.
How do you stop portal traffic to the node being upgraded in 24x7 cluster upgrade process ?Locate the cluster member being upgraded, and change the value in the Configured weightcolumn from a value to zero and make sure the plugin config information is propagated towebserver to stop traffic.
15.
How to set limits on searches for users and groups?Setting a maximum number of search results maximumSearchResults="200"in wmm.xml
16.
What portal resources are scoped for virtual portal?Portal pages.Portlet instances.Portal Search Engine search services and search collections. This includes the search contentsources.
17.
What portal resources can't be separated for virtual portal ?Themes and skins.Vault segments and vault slots.Supported clients and mark-ups.Composite applications and templates.Policies.
18.
How do you enable temporary and extended trace logging for WebSphere Portal ?Temporary traces can be set for a temporary period by using the administration portletEnable Tracing or the IBM WebSphere Application Server administrative console and alsousing 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 onesession, switch them on in the WebSphere Application Server configuration, save the
updates and restart the portal server.
19.
What are the different states of the syndication process ?Idle: No syndication is occurring.Pending: A request has been made to the syndicator, but it has yet to initiate a request tothe syndication application.Queued: The syndicator has sent a request to the syndication application, but syndication isnot yet active.Active: Syndication is occurring between the syndicator and subscriber.Disabled: Syndication is currently disabled.
20.
What are the two types of rendering portlets ?Local rendering portlet and Remote rendering portlet =============================================
IBM WebSphere Portal Interview Questions
ANS: Essentially, Servlets provide content that normally takes up the whole page in a browser (unless you're using frames), and portlets provide content that is wrapped by a window. With portlets, you can have multiple portlets side by side with one another and each one can provide content and functionality that is different from the other. A portlet can provide the complete interaction for one type of application, while another portlet can provide content for another type of application. The portal can provide some house keeping functionality and secured single point of entry to all of the portlets on a page. As for the particulars (similarities/differences) between them, please continue reading.
Here are some similarities:
Servlets and portlets are web based components that utilize Java for their implementation
Portlets are managed by a portlet container similar to a servlet container
Both of these components generate content, which can be static or dynamic
Both portlets and servlets have a lifecycle that is controlled by the container
The client/server model is used for both servlets and portlets
The packaging and deployment are essentially the same
The manner in which the classes are loaded and the class loaders that perform the work are also the same
Lifecycle management is similar
The Request and Response semantics are also similar
Here are some differences:
Servlets can provide complete web pages, whereas portlets only provide fragments. These fragments are then aggregated to form a complete web page by the portal
Portlets aren?t allowed to generated HTML code that contains tags such as base, body, frame, frameset, head, html, or title. The iframe tag can be used with caution.
The user cannot access a portlet directly using a URL in the way that a servlet is accessed. Instead, the URL points to the page containing all of the portlets on one page
Communication between the web client and the portlets is performed through the portal
Portlets can be provided with buttons or controls to manipulate the portlets? window states or portlet modes
Multiple instances of a single portlet can be placed onto the same page
Portlets support persistent configuration and customization
Portlets also support user profile information
Portlets support two scopes within the session; application scope and portlet scope
There are several things that servlets are allowed to do, but portlets aren?t. These include the following:
Portlet aren?t allowed to set the character set encoding of the response
Portlet also aren?t allowed to set the HTTP headers on the response
Portlet cannot manipulate the URL of the client request to the portal
---------------------------------------------------------
What is a portal ?
A portal can be best described as a web site that acts as a "point of entry" or a gate to a larger system. While it seems pretty difficult to define a portal in the strictest sense, these are some of the common features of portals:
Content aggregation:
Portals tend to aggregate content from multiple, disparate sources and provide one unified view of the same.
Personalization:
This refers to the ability of the portal to tailor the content/services that it offers according to the user of the portal.
Search:
Most if not all portals, offer some form of searching of it's content and sometimes even content from external sources.
Single Sign On:
Allows users to authenticate once to the portal and thereby allows access to many other systems without the need for re authentication.
---------------------------------------------------------
Portlet Lifecycle and when init and destroy method gets called?
ANS:
This life cycle of a portlet is expressed through the init, processAction,
render and destroy methods of the Portlet interface.
A servlet's init(ServletConfig) method is called by the server immediately after the server constructs the servlet's instance.
Depending on the server and its configuration, this can be at any of these times:
When the server starts
When the servlet is first requested, just before the service() method is invoked
At the request of the server administrator
The init() method is typically used to perform servlet initialization--creating or loading objects that are used by the servlet in the handling of its requests. Why not use a constructor instead? Well, in JDK 1.0 (for which servlets were originally written), constructors for dynamically loaded Java classes (such as servlets) couldn't accept arguments. So, in order to provide a new servlet any information about itself and its environment, a server had to call a servlet's init() method and pass along an object that implements the ServletConfig interface. Also, Java doesn't allow interfaces to declare constructors. This means that the javax.servlet.Servlet interface cannot declare a constructor that accepts a ServletConfig parameter. It has to declare another method, like init(). It's still possible, of course, for you to define constructors for your servlets, but in the constructor you don't have access to the ServletConfig object or the ability to throw a ServletException.
Servlet programming is made possible through the classes and interfaces of two packages: javax.servlet and javax.servlet.http. Of these classes and interfaces, the javax.servlet.Servlet interface is the most important interface. All servlets must implement this interface or extend a class that does.
The Servlet interface has five methods, whose signatures are as follows:
public void init(ServletConfig config) throws ServletException
public void service(ServletRequest request, ServletResponse response)
throws ServletException, java.io.IOException
public void destroy()
public ServletConfig getServletConfig()
public java.lang.String getServletInfo()
Related Reading
The init, service, and destroy methods are the servlet's lifecycle methods. The init method is called once by the servlet container after the servlet class has been instantiated to indicate to the servlet that it being placed into service. The init method must complete successfully before the servlet can receive any requests. A servlet programmer can override this method to write initialization code that needs to run only once, such as loading a database driver, initializing values, and so on. In other cases, this method is normally left blank.
The service method is then called by the servlet container to allow the servlet to respond to a request. The servlet container passes a javax.servlet.ServletRequest object and a javax.servlet.ServletResponse object. The ServletRequest object contains the client's HTTP request information and the ServletResponse encapsulates the servlet's response. These two objects enable you to write custom code that determines how the servlet services the client request.
The servlet container calls the destroy method before removing a servlet instance from service. This normally happens when the servlet container is shut down or when the servlet container needs some free memory.
This method is called only after all threads within the servlet's service method have exited or after a timeout period has passed. After the servlet container calls destroy, it will not call the service method again on this servlet. The destroy method gives the servlet an opportunity to clean up any resources that are being held (for example, memory, file handles, and threads) and make sure that any persistent state is synchronized with the servlet's current state in memory.
--------------------------------------------------------------
Difference between JSR168 and JSR286?
ANS:
--------------------------------------------------------------
Difference between WPS5.0 and WPS6.1?
ANS:
--------------------------------------------------------------
How to Customize Login functionality.?
ANS:
In WebSphere Portal 6.0.1 and later versions, there is a new portlet service that allows you to log into Portal. This service still takes advantage of the LoginUserAuth in the login process. You can also write your own Login portlet and handle any validation or processing before or after the login process.
To use this service with Rational Application Developer (RAD), you must be sure to add the following to your build path:
wp.auth.cmd.jar
wp.auth.base.jar
You can find these two .jar files in the <portalserver>\base\wp.auth.base\shared\app and <portalserver>\base\wp.auth.cmd\shared\app directories in your WebSphere Portal 6.1 install.
The first portlet service is the following:
com.ibm.portal.portlet.service.login.LoginService
To access this service, add code similar to the following (best done in the "init" method of the portlet):
PortletServiceHome psh;
javax.naming.Context ctx = new javax.naming.InitialContext();
psh = (PortletServiceHome) ctx.lookup(LoginHome.JNDI_NAME);
loginHome = (LoginHome) psh.getPortletService(LoginHome.class);
Then, in your processAction, you can log the user in using code such as:
LoginService loginService = (LoginService) loginHome.getLoginService(request, response);
String userId = request.getParameter(FORM_ID);
String password = request.getParameter(FORM_PASSWORD);
Map contextMap = new HashMap();
contextMap.put(LoginService.DO_RESUME_SESSION_KEY, new Boolean(false));
try {
loginService.login(userId, password.toCharArray(), contextMap, null);
} catch (Exception ex) {
System.err.println("this login failed with = " + ex.getMessage());
ex.printStackTrace();
}
You must also add a login form to the JSP page which has already been done and is in the first portlet provided.
At this point, you would be logged in or not, depending on the response from the LoginService. Remember that once you call the login service method, the control will not return to your portlet code if the user is logged in because Portal will do a redirect to the proper Portal page (unless there is an authentication error or a block).
Link : https://www-304.ibm.com/support/docview.wss?uid=swg21358508
--------------------------------------------------------------
What are portlet filters?
ANS:
--------------------------------------------------------------
What is credential vault?
ANS:
--------------------------------------------------------------
What virtual portal?
ANS:
--------------------------------------------------------------
What is LDAP?
ANS:
LDAP is an Internet standard protocol used by applications to access information in a directory.
In LDAP, directory entries are arranged in a hierarchical tree-like structure, starting at a root and then branching down into individual entries. At the top level of the hierarchy, entries represent larger organizations. Under these larger organization in the hierarchy might be entries for smaller organizations. The hierarchy might end with entries for individual people or resources.
--------------------------------------------------------------
What is difference between PortletContext and PortletSession?
ANS:
--------------------------------------------------------------
What to create customize Mode.?
ANS:
--------------------------------------------------------------
How to change Portlet Title in JSR286?
ANS:
--------------------------------------------------------------
What are difference ways to deploy Themes and Portlets.?
ANS:
--------------------------------------------------------------
What is path of serverlogs on UNIX?
ANS:
cd /opt/WebSphere61/wp_profile/logs/wpsAS01;view SystemOut.log
--------------------------------------------------------------
How to run xmlaccess script on UNIX?
ANS:
ssh rasde90002-man.nl.rbsgrp.net;
sudo su - was
opt/WebSphere61/PortalServer/bin/xmlaccess.sh -in /var/tmp/XYZ.xml -user abcd -pwd abcd -url http://abcd.nl.net/gts/config/ -out /var/tmp/abcd_OUT.xml
--------------------------------------------------------------
How maven is configured and use?
ANS:
--------------------------------------------------------------
Difference between public render parameter and eventing.
ANS:
--------------------------------------------------------------
Why struct can not be used with portlets?
ANS:
--------------------------------------------------------------
How two do cross page communication?
ANS:
--------------------------------------------------------------
How AJAX can be used with servresource method.
ANS:
--------------------------------------------------------------
Difference between HASHMAP and HASHTABLE?
ANS:
--------------------------------------------------------------
Explain collection framework?
ANS:
--------------------------------------------------------------
How personilization works in WPS?
ANS:
--------------------------------------------------------------
What is use of Config mode?
ANS:
--------------------------------------------------------------
What is dojo classes?
ANS:
--------------------------------------------------------------
What is JQuery and what is the use?
ANS:
--------------------------------------------------------------
What is difference between PortletContext.getParameter and PortletConfig.getParameter?
ANS:
Context-wide init-params share the same context space as Servlets and JSPs belonging to the same application and they are defined in the web.xml file. You can get them using PortletContext.getInitParameter() method.
Portlet-wide initialization parameters on the other hand belong in the portlet.xml file and you can get them using PortletConfig.getInitParameter() method.
--------------------------------------------------------------
How portlet Preference are stored and retrieved?
ANS:
--------------------------------------------------------------
What is WCM and how it is used?
--------------------------------------------------------------
Can we able to access PortletSession in ServeResource Method?
-------------------------------------------------------------
What is a PortalSession Interface ?
ANS:
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.
---------------------------------------------------------------
What is the difference between application server and web server?
ANS:
ApplicationServer: takes care of Security, Transaction, Multithreading, Resource pooling, load balancing, clustering, performence, highly availability, scalability, etc. Exposes business logic to client applications through various protocols, possibly including HTTP. Supports deployment of .war and .ear filesApplication server = webserver + EJB container.
Webserver: handles HTTP protocol. Receives HTTP request, it responds with an HTTP response.
---------------------------------------------------------------
What is a portlet container and where will I find one?
A portlet container runs portlets and provides them with the required runtime environment. A portlet container contains portlets and manages their lifecycle. It also provides persistent storage for portlet preferences. A portlet container receives requests from the portal to execute requests on the portlets hosted by it.A portlet container is not responsible for aggregating the content produced by the portlets. It is the responsibility of the portal to handle the aggregation.
A portal and a portlet container can be built together as a single component of an application suite or as two separate components of a portal application
==================================================
No comments:
Post a Comment