If you're looking for IBM WebSphere Portal Developer Interview Questions & Answers for Experienced or Freshers, you are at the right place. There are a lot of opportunities from many reputed companies in the world. According to research, IBM WebSphere Portal Developer has a market share of about 0.1%. So, You still have the opportunity to move ahead in your career in IBM WebSphere Portal Development. Mindmajix offers Advanced IBM WebSphere Portal Developer Interview Questions 2021 that help you in cracking your interview & acquire a dream career as IBM WebSphere Portal Developer.
Are you interested in taking up for Websphere Portal Developer Certification Training? Enroll Our Websphere Portal Developer Training!
IBM WebSphere Portal Developer Interview Questions - Table of Content
IBM WebSphere Portal Developer Interview Questions
Q1): What is Portal?
Ans: Portal is nothing but a web/J2EE application installed on an application server. Portal provides content aggregation, personalization, authorization, and authentication.
Q2): What are Portlets?
Ans: Portlets are applications managed by a portal container that generates a fragment of the portal page rather than a complete page as generated by the servlet.
Q3): Differences between a Portlet and servlet?
Ans: Portlets generate the only fragment of the portal page rather than the entire page
Portlets have a more refined request cycle than servlet
Portlets have predefined modes and window states
Portlets are can be only invoked using portlet URLs
Q4): What are the different types of Portlet URLs and their use?
Ans: Portlet life cycle has following phases
Q5): What are the different types of Portlet URLs and their use?
Ans: There are three types of portlet URLs
Action URL- used for submitting forms
Render URL- used for links
Resource URL – used for ajax calls and serving documents (pdf files).
Q6): Difference between JSR 168 and JSR 286 specifications?
Ans: The major changes in JSR 286 are events, public render parameters, resource serving, and portlet filter.
Q7): How is the inter portlet communication carried out in JSR 168 portlet?
Ans: The inter portlet communication for JSR 168 in the WebSphere portal can be done using Dyna cache or shared library. We can create a hash map or any data structure, where we can store an object that needs to be transported with a unique key and retrieve it from the receiving portlet
Q8): Can you create a DB connection in the render phase? Explain reason?
Ans: Yes, we can create a DB connection in the render phase of the portlet. But it is not suggested to create one in the render phase because it will be called every time any other portlet on the page is changed and may result in stale DB connections.
Q9): What are the different modes supported by JSR 286?
Ans: Different modes supported by JSR 286 are view, edit, and help. A portlet should define its supported mode as a portlet.xml file.
Q10): What are different States supported by JSR 286?
Ans: Different portlet states supported are normal, maximized, and minimized.
Q11): What is Dynacache?
Ans: Dynacache is a disturbing map used to store and retrieve objects from memory. IBM provides API to create, store retrieve the objects.
Q12): What is CSA?
Ans: Client-side aggregation (CSA) is a new method of rendering a WebSphere Portal page that moves the rendering workload from the server to the client. It is made possible by the Representational State Transfer (REST) services introduced in WebSphere Portal 6.1.
In the traditional server-side aggregation (SSA) rendering, the page and each of the portlets is completely rendered on the server, using JSPs, and returned to the client in one big response.
In contrast, in CSA, we request only the pieces of information from the server that are required to update the page as a result of the user’s interactions with the page.
For example, if a page contains four portlets and the user clicks a link in one of the portlets, only that portlet is updated. This means the server must render only one portlet, instead of four portlets plus the theme for an interaction with a single portlet.
The REST services also take greater advantage of caching. Since each individual artifact can be independently cache-able, the client ends up retrieving a greater number of responses directly out of cache, further reducing the server workload.
Q13): What are the different modes available in Websphere Portal?
Subscribe to our youtube channel to get new updates..!
Ans: Apart from standard modes ( view, edit, help) it provides edit_ defaults and configures mode.
Q14): What can you do with XML access scripts?
Ans: XML access is a command-line utility used for exporting and importing portal configurations. It can be used for backing up the configuration of certain environments, for loading new configurations (for new portlets or pages, for example), or for updating existing portlets when a new WAR file is provided by the development. There are few samples C:IBMWebSpherePortalServerdocxml-sample
Q15): What is model spi and what is it used for?
Ans: Web sphere uses a different model for providing content aggregation and navigation The available models are the Content model, navigation model, navigation selection model, and layout model. These models are provided using model spi.
Q16): What is the Navigation model?
Ans: The navigation model is used to get the topology of the navigation available to a user.
Q17): How do you solve problems related to themes and skins?
Q18): What is a Web Content Management System (WCMS)?
Ans: A web Content management system is a software system that helps build and manage Web entities (html pages, documents, etc.) Once setup is complete it provides templates for authoring, workflow management to the content. It is easy to use for non-technical users.
Q19): What is syndication?
Ans: Syndication, (Web syndication in particular) is a ability to provide users updates of the content from the site. The most popular formats of web syndication are RSS and ATOM feeds.
Q20): What is local rendering and remote rendering?
Ans: The web content management portlets can be rendered local or remotely. A local rendering portlet displays content on the same portal as the instance where the web content manager is installed. A remote rendering portlet displays Web content on a different portal server than the instance where Web Content Manager is installed.
Q21): What are the different steps in creating content for WebSphere portal WCM?
Ans: The following are different steps involved in creating the content for the WebSphere portal WCM
Create Site area (Sites are removed in WebSphere Portal 7.0)
Create Authoring templates
Create Presentation templates
Map authoring and presentation templates
Q22): What are workflows?
Ans: A workflow is a sequence of steps that are followed in creating approved content. In the WebSphere Portal, A workflow contains one or more stages. Every stage contains one or more actions, the following are different Workflow actions available in WebSphere Publish, Expire, Email, Scheduled Move, Custom Actions.
Q23): What are Authoring and Presentation Templates?
Authoring Template- This template is defined using authoring portlet, where we define the access information, form properties, and default content. It does not contain any information for presentation and The elements in this form are linked to the presentation template.
Presentation Template- This allows to change the look of a page without having to update what is being displayed on a page. It will allow defining Page style, Page layout, and map element to the authoring templates.
Q24): What is the difference between personalization and customization?
Personalization- It means to serve the user or consumer with user-specific data depending on his interests collected over time. A real-world example would be google serving ads basing on the recent search you made.
Customization- It is the ability provided to the user to change the layout, styling of the page, and save it.
Q25): 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 enable 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 create a portal a website that provides users with a single point of access to Web-based resources by aggregating those resources in one place.
Q26): 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 EarExpander tool to expand the exported wps.ear file.
Copy the updated themes and skins into ../themes/html, ../skins/html folder.
Use EarExpander 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.
Q27): What changes need 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 reloadingEnable property to true in ibm-web-ext.xmi file of the wps.ear.
Q28): What are the 3 different ways of installing a portlet application in WebSphere Portal?
Ans: 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.
Q29): What is the purpose of XMLAccess configuration file Export.xml & ExportRelease.xml? What is the difference & When will you use one over the other?
Export.xml exports the complete portal configuration and useful when transferring configurations between development installations.
ExportRelease.xml exports the complete portal configuration from the release domain as required by the portal ReleaseBuilder tool and useful when tranaferring different release configurations between staging and production environments.
Q30): List me the steps involved in building a release in WebSphere 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 releases onto the production server. Refer to Transferring a complete configuration 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 complete configuration for information.
Develop and build a new release on the staging server.
Export that new release from the staging server.
Use ReleaseBuilder to generate the differential between the two releases.
Import the differential onto the production server.
Q31): What is the purpose of the ReleaseBuilder tool in WebSphere Portal?
Ans: ReleaseBuilder enables management of release configurations independent of user configurations and used during staging of follow-on releases of WebSphere portals, configurations, and artifacts that need to be moved between systems.
Q32): What are the steps involved in editing WebSphere Member Manager (wmm.xml) files on a federated node?
Ans: On the primary node of the WebSphere Portal cluster, check out the files using ./WPSconfig.sh check-out-wmm-cfg-files-from-dmgr task.
Make any changes to the Member Manager files. The files can be edited in the portal_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.
Q33): List different types of user registries supported by WebSphere Portal?
Ans: LDAP (includes LDAP with an optional database user registry).
Database user registry.
Custom User registry, (non-LDAP, non-database).
Q34): What is LDAP realm support and why would I want to use it?
Ans: A Realm allows you to group users from one or more LDAP trees of one user registry and expose them as a coherent user population to WebSphere Portal; this is also referred to as horizontal partitioning. Realms allow flexible user management with various configuration options; for example, you can combine principals from one or more corporate LDAP trees. A realm must be mapped to a Virtual Portal to allow the realm’s defined user population to login to the Virtual Portal.
Q35): What is an Application group and why would I want to use it?
Ans: Application groups is a concept that allows you to define user groups within the database user registry with members (users or groups) contained in the LDAP user registry you configured.
The benefit of application groups is that you can create Groups that are only used in WebSphere Portal particularly in scenarios where there is Read-only LDAP or special group set up specific to the portal.
Q36): 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.
Q37): How do you stop portal traffic to the node being upgraded in the 24×7 cluster upgrade process?
Ans: Locate the cluster member being upgraded, and change the value in the Configured weight column from a value to zero and make sure the plugin config information is propagated to the webserver to stop traffic.
Q38): How to set limits on searches for users and groups?
Ans: Setting a maximum number of search results maximumSearchResults=”200″ in wmm.xml
Q39): What portal resources are scoped for the virtual portal?
Ans: Portal pages.
Portal Search Engine search services and search collections. This includes the search content sources.
Q40): What portal resources can’t be separated for the virtual portal?
Ans: Themes and skins.
Vault segments and vault slots.
Supported clients and markups.
Composite applications and templates.
Q41): 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.
Q42): 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 to the syndication application.
Queued: The syndicator has sent a request to the syndication application, but syndication is not yet active.
Active: Syndication is occurring between the syndicator and subscriber.
Disabled: Syndication is currently disabled.
Q43): What are the two types of rendering portlets?
Ans: Local rendering portlet and Remote rendering portlet
Q44): Explain Portal architecture?
Ans: The core implementation of the portal is UI, hosted by a Portal server. The HTTP requests, HTML responses, and returning appropriate portal pages are handled by the Portal UI. Enterprise Web applications also can be handled by the Portal Server.
The portal architecture has the following:
Automaton Server: This server performs the management of job scheduling and implementation of a portal. It accesses all remote crawlers and profile services retrieved and stored from a remote database.
Image Server: This server hosts images and other web page content used by web services and a portal. With this configuration, large static files are to be sent directly to the browser without portal server impacts.
Search Server: This server indexes and searches all the information, applications, communities, documents, web sites through the portal.
Collaboration Server: Web content publication and management for portals and web applications are supported by this server. Its functionality can be accessed by a remote web service through an Enterprise Web Development kit.
Content Server: Publication and management of web content for portals and web applications along with form-based publishing, branding, templates, content expiration is allowed by this server.
Authentication Server: This server handles the portal authentication for users and remote services can be accessed through EDK.
Remote Servers: Web services written using the EDK are hosted by remote servers. The servers can be in different countries, on different platforms, and on domains.
Q45): What is the PortletSession interface?
Ans: User identification across many requests and transient information storage about the user is processed by the PortletSession interface. 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.
Q46): What is the PortletContext interface?
Ans: The portlet view of the portlet container is defined by PortletContext. It allows the availability of resources to the portlet. Using this context, the portlet log can be accessed and URL references to resources can be obtained. There is always only one context per portlet application per JVM.
Q47): How to change the default portal URI /wps/portal after installation?
Ans: Set the property WpsContextRoot to the new URI and run ./WPSConfig.sh modify-servlet-path task.
Explore Websphere Portal Developer Sample Resumes! Download & Edit, Get Noticed by Top Employers! Download Now!