Interview Questions

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.

What are the steps involved in deploying themes and skins in a clustered production websphere portal environment ?

• 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.

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).

What changes needs to be done to view changes to your theme and skins JSPs without restarting the portal server ?

You need to enable automatic JSP loading by setting reloading Enable property to true in ibm-web-ext.xmi file of the wps.ear.

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.

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 transferring different release configurations between staging and production environments.

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 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.

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 release 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.

What is the purpose of ReleaseBuilder tool in WebSphere Portal ?

ReleaseBuilder 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.

What are the steps involved in editing WebSphere Member Manager (wmm.xml) files on a federated node ?

• 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.