PortalTips&Tricks

Getting content path IBM WCM API

2013-08-09T08:32:00.000-07:00

DocumentIdIterator contentIterator = workspace.findByType(DocumentTypes.Content);
while(contentIterator.hasNext())
    {
        contentId = contentIterator.nextId();
    System.out.println(workspace.getPathById(contentId, false, false));
    }

Running syndicator from IBM WCM API

2013-08-06T11:41:00.003-07:00

try
{
Context ic = null;
System.out.println("----------------------JNDI Connection Syndicator---------------------");
Hashtable env = new Hashtable(); env.put(Context.PROVIDER_URL, "iiop://localhost:10035");
env.put(Context.INITIAL_CONTEXT_FACTORY, "com.ibm.websphere.naming.WsnInitialContextFactory");
ic = new InitialContext(env);
SyndicationService syndicationService = (SyndicationService) ic.lookup("portal:service/wcm/SyndicationService");

System.out.println("Context starting at: " + ic.getNameInNamespace());

Workspace workspace = WCM_API.getRepository().getWorkspace( );

Syndicator synd = syndicationService.getSyndicatorByName(workspace, "DEV2INT-TestSydContent");

System.out.println("Syndicator Name :--"+synd.getName());

System.out.println("Syndicator Status :-"+synd.getStatus());

synd.setEnabled(true, workspace);
synd.update();
SyndicationStatus syndStatus = synd.getStatus();
while(syndStatus.isRunning()) {
System.out.println("Updating");
}
synd.setEnabled(false, workspace);
}catch(Exception e) {
e.printStackTrace();
}

Checking Cross Referencing of contents in IBM WCM Libraries

2013-08-04T11:13:00.001-07:00

try

{

Repository repository = WCM_API.getRepository();

Workspace workspace = repository.getWorkspace(request.getUserPrincipal());
String libname="Test-library";

workspace.setCurrentDocumentLibrary(workspace.getDocumentLibrary(libNames));

DocumentIdIterator contentIterator = workspace.findByType(DocumentTypes.Content);

DocumentId contentId = null;

while(contentIterator.hasNext())

{

contentId = contentIterator.nextId();

ArrayList<String> arrayList = new ArrayList<String>();

Reference []ref =workspace.getReferencesFrom(contentId);

for(int i=0 ; i< ref.length ;i++)

{

String refLibName = ref[i].getRefererDocumentId().getContainingLibrary().getName();
System.out.println("--------------Referenced Library Name-------------"+refLibName);

}
}
}

org.omg.CORBA.NO_PERMISSION Exception

2012-07-09T03:51:00.002-07:00

Whenever we are hitting ejb service from portal which is deployed on different WAS , and if we face the below stack trace:---

Exception = org.omg.CORBA.NO_PERMISSION
Source = com.ibm.ws.naming.jndicos.CNContextImpl.doLookup
probeid = 1489
Stack Dump = org.omg.CORBA.NO_PERMISSION:
>> SERVER (id=64e777ef, host=SVHJ0898.ideaconnect.com) TRACE START:
>> org.omg.CORBA.NO_PERMISSION: Subject is null. Authentication Failed. vmcid: 0x49424000 minor code: 300 completed: No
>> at com.ibm.ISecurityLocalObjectBaseL13Impl.PrincipalAuthFailReason.map_auth_fail_to_minor_code(PrincipalAuthFailReason.java:88)
>> at com.ibm.ISecurityLocalObjectBaseL13Impl.CSIServerRIBase.authenticateSecurityTokens(CSIServerRIBase.java:2815)
>> at com.ibm.ISecurityLocalObjectBaseL13Impl.CSIServerRI.receive_request(CSIServerRI.java:622)
>> at com.ibm.rmi.pi.InterceptorManager.invokeInterceptor(InterceptorManager.java:631)
>> at com.ibm.rmi.pi.InterceptorManager.iterateServerInterceptors(InterceptorManager.java:535)
>> at com.ibm.rmi.pi.InterceptorManager.iterateReceiveRequest(InterceptorManager.java:777)
>> at com.ibm.CORBA.iiop.ServerDelegate.dispatchInvokeHandler(ServerDelegate.java:616)
>> at com.ibm.CORBA.iiop.ServerDelegate.dispatch(ServerDelegate.java:480)
>> at com.ibm.rmi.iiop.ORB.process(ORB.java:512)
>> at com.ibm.CORBA.iiop.ORB.process(ORB.java:1571)
>> at com.ibm.rmi.iiop.Connection.respondTo(Connection.java:2680)
>> at com.ibm.rmi.iiop.Connection.doWork(Connection.java:2543)
>> at com.ibm.rmi.iiop.WorkUnitImpl.doWork(WorkUnitImpl.java:62)
>> at com.ibm.ejs.oa.pool.PooledThread.run(ThreadPool.java:118)
>> at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1560)
>> SERVER (id=64e777ef, host=SVHJ0898.ideaconnect.com) TRACE END.
vmcid: 0x49424000 minor code: 300 completed: No
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:67)

1.Go To Security of the WAS.
2.Then go to global security on clicking Secure administration, applications, and infrastructure.
3. Go To Authentication mechanisms and expiration

Export the keys and import them to the Portal WAS.

Restart Portal server .

calling ajax in jsr 286

2012-06-14T03:46:00.003-07:00

I have created a sample portlet to show the suggestion by calling ajax:-

The sample jsp for calling the ajax as above is:

<%@page language="java" contentType="text/html; charset=ISO-8859-1"
pageEncoding="ISO-8859-1" session="false"%>
<%@taglib uri="http://java.sun.com/portlet_2_0" prefix="portlet"%>
<portlet:defineObjects />
<script type="text/javascript">
function createXMLHttpRequestObject() {
var xmlHttp;
try {
xmlHttp = new XMLHttpRequest();
} catch (e) {
try {
xmlHttp = new ActiveXObject("Microsoft.XMLHttp");
} catch (e) {
}
}
if (!xmlHttp)
alert("Error creating the XMLHttpRequest object.");
else
return xmlHttp;
}
var xmlHttp = createXMLHttpRequestObject();

function makeResourceCall(str){

if (str.length==0)
{
document.getElementById("txtHint").innerHTML="";
return;
}

if (xmlHttp){
var newvalue ="Harish"+str;

try{
var url ="<portlet:resourceURL></portlet:resourceURL>?txtValue="+str;

xmlHttp.open("GET", url, true);
xmlHttp.onreadystatechange = handleRequestStateChange;

xmlHttp.send(null);
}catch (e){
alert("Can't connect to server:\n" + e.toString());
}
}
}

function handleRequestStateChange(){
if (xmlHttp.readyState == 4){
if (xmlHttp.status == 200){

if(xmlHttp.responseText == "")
{
document.getElementById("txtHint").style.display="none";
}
else
{
document.getElementById("txtHint").style.display="block";
document.getElementById("txtHint").innerHTML=xmlHttp.responseText;
}
}
}
}
</script>

Enter Name<input type="text" name="txtValue" onkeyup="JavaScript:makeResourceCall(this.value)" >



<TEXTAREA name="annotationTxt" rows="10" cols="30" style="overflow:hidden;" id="txtHint" maxlength="235"></TEXTAREA>

<script>
function onload()
{
document.getElementById("txtHint").style.display="none";
}
onload();
</script>

Onkeyup I am calling makeResourceCall and from makeResourceCall function calling <portlet:resourceURL>

From this the control will go the portlet class and will call the serverResource method:

public void serveResource(ResourceRequest request, ResourceResponse response)

throws PortletException, IOException {

System.out.println("Entering ValidationCacheSamplePortlet.serveResource()");

response.setContentType("text/html");

System.out.println("String input value"+request.getParameter("txtValue"));

inserRec rec = new inserRec();

List list = rec.getData(request.getParameter("txtValue"));

for (Iterator iterator = list.iterator(); iterator.hasNext();)

{

HibernateprjPojo pojo = (HibernateprjPojo) iterator.next();

response.getWriter().println(pojo.getName());

}

In the serve resource method I am making a hibernate call and fetching the related values for txtValue.

From the getwritter the result will be shown in the drop down box.

Hidden portal page

2012-06-14T02:10:00.000-07:00

To create a hidden portal page , first create a page and give it a proper unique name .
Export the portal page and save the xml.
Edit the xml and add the parameter

<parameter name="com.ibm.portal.Hidden" type="string" update="set"><![CDATA[true]]></parameter>
As shown below:-

<?xml version="1.0" encoding="UTF-8"?>

<content-node action="locate" domain="rel" objectid="6_20DO18N3Q4IL40ITIA32AM2085"/>

<content-node action="update" active="true" allportletsallowed="true" content-parentref="6_20DO18N3Q4IL40ITIA32AM2085" create-type="explicit" domain="rel" objectid="6_20DO18N3QCKQ40ITNC79MH00O6" ordinal="200" type="page" uniquename="ibm.home.test">

<supported-markup markup="html" update="set"/>

</localedata>

<parameter name="com.ibm.portal.Hidden" type="string" update="set"><![CDATA[true]]></parameter>

<access-control externalized="false" owner="uid=wpsadmin,o=defaultWIMFileBasedRealm" private="false"/>

</component>

</content-node>

</portal>

</request>

Shared Libraries for portal project

2012-06-12T05:45:00.000-07:00

For creating a shared library open the WAS console and create a shared variable:

After giving the path of your shared library go to

ApplicationServer> WebSphere_Portal> and select java and process Management and select the class loader

and chhose the shared library reference.

and in the shared reference select your shared library reference:

Restart your server and deploy your war file , it will automatically take references of your jars .

PUMA API for anonymous users

2012-06-11T01:52:00.002-07:00

For creating portlets like signUp or forget Password we need the puma api to access the user information .But before accessing attributes you have to give following access rights others wise you won't be able to access the values.
1.From the admin console go to resource permission.

2.Select the User Groups.

3.For All Portal User Groups give the anonymous access for USER,Editor ,Manager,Security administrator.

After that your code will work fine.

java.lang.RuntimePermission getClassLoader exception on portlet deployment

2012-03-01T02:47:00.001-08:00

java.lang.RuntimePermission getClassLoader issue while deploying portlet:-

When you deploy portlet in a in new environment you might get portlet error with below stack trace:--
Error occurred during portlet request dispatcher inclusion
java.security.AccessControlException: Access denied (java.lang.RuntimePermission getClassLoader)
at java.security.AccessController.checkPermission(AccessController.java:103)
at java.lang.SecurityManager.checkPermission(SecurityManager.java:558)
at com.ibm.ws.security.core.SecurityManager.checkPermission(SecurityManager.java:214)
at java.lang.Thread.getContextClassLoader(Thread.java:497)
at org.apache.taglibs.standard.tag.common.fmt.BundleSupport.findMatch(Unknown Source)
at org.apache.taglibs.standard.tag.common.fmt.BundleSupport.findMatch(Unknown Source)
at org.apache.taglibs.standard.tag.common.fmt.BundleSupport.getLocalizationContext(Unknown Source)

Solution:-- For the non root user check for access rights by using chown -R newadmuser:newadmuser

if you are using cluster then also check for dmgr for all folders.

Common WCM and Portal Interview questions.

2012-03-01T02:04:00.000-08:00

what is credential vault
what is themes and skin
wht are the difference between portlet and servlet
what is the credential vault
what is wcm
what is was
what is LDAP
what is WMM
what is single sign on
what are the types of portlet
what is JSR286
have u work on it
how u do the syndication
how u create Pt
what is Authoring template
how u create Workflow
how u define personalisation rule in wcm
what is the difference between portletConfig.getInitParameter()
and PortletContext.getInitParameter()
what is portlet data
what is portlet preference
how to manage portlet page
how to enable single sign on on WAS
what are the different componet u are work on WCM
which data base u r using in portal
what is Cloudscape?
what is struts navigation
what is WSDL
what is copertaive portlet
what is interportlet communication
what is portlet preference
what is the life cycle of JSR168 portlet
what are the difference between JSR168 and IBM Api
what is content agregation
what is jsp component
where u save the jsp file for jsp component
what are the WCM api
how u create a contentr using WCM api
what are the main JSP page on Themes,skin and screen
what are the file u have made changes on Portal onfiguration
how to migrate Cloudscape to Db2 and LDAP
what are the schema on cloudscape
what is PUMA
How to create JNDI on WAS

Portlet Factory Interview Questions

2012-02-22T01:37:00.000-08:00

Why to use portlet factory?

Ø Powerful and flexible tool for rapidly building portlets on top of service oriented architecture.

Ø Portlet created with WPF are dynamic roboust java 2 enterprise edition application that react automaticalli to change, and can be modified by business users in real time to meet changing requirement without requiring any coding , duplicating or versioning of assets.

Ø WPF simplifies the development ,deployment and change management process , saving companies time and money.

Ø Support SOA development.

Ø Roboust integration capabilities with enterprise as well as data.

Ø WPF has around 160 wizard like builders that can be used to automate common development task.

What are building blocks of portlet factory?

WPF consists of three main building blocks:

Ø Builders

Ø Models

Ø Profiles

Developers work withthese above elements builders models and profiles along with other design elements like HTML pages and XML documents and java classes.A WPF mechanism known as Factory generation engine can automatically generate executable applications known as WebApps.

What are builders in WPF?

Builders are the basis of any WPF application.

Builders are wizard based interface that automates common development task, builder can do anything from adding a button to calling a webservice.Builders contains input parameters use to customize the builders output.

Developers usually interact with builders with interface but a combination of java classes and XML are used to create builders on the back end.

What id Model in WPF?

A model is the sequenced collection of builders that generates the application components that implement the behaviour ,structure, data and presantation of the application.

Internally a model is simply a XML file contating a series of calls to the builders.

A single WPF prj. Can contain one or more models and subsequently can contain several portlets.

What is Profile in WPF?

A profile contains a set of inputs that varies the way a portlet behaves.

A profile feeds values into builders based on user identity or other contextual information.

Using profiles you can generate different variations of generic portlets for different users or situations.

List of WPF Builders.

I am assuming that we have put the wsdl files under the file structure as follows

Steps for calling WebService in WPF.

In the WebContent – “WSDL” folder wsdl files are present.

Open the designer – Eclipse - Portlet Factory

Click on “Add a Builder Call to Current Model” button -

Following screen will appear -

Select the “Web Service Call” click on “Ok” button

The Web Service Call builder allows you to execute several different types of services, and displays different inputs according to the type of service call you choose.

The following steps describe the general process of configuring a web service call.

1. In the Service Call Type input, select the type of service call: WSDL, SOAP, HTTP, or Local.

2. Enter the URL for the service.

For WSDL service calls, enter the URL for the WSDL document that describes the service you want to call. The URL may be HTTP-based, for example http://myhost/mywsdl.wsdl or a file within the project, such as WEB-INF/mywsdl.wsdl.

If your organization is using WebSphere Service Registry and Repository (WSRR), you can use WSRR to search for and download WSDL to your project.

3. Specify the values for the arguments to pass to the service.

For WSDL service calls, the builder call editor lists the arguments that the service requires and you must specify their values.

For SOAP and HTTP service calls, you need to know the required arguments and build up the arguments list in the Arguments input in the builder call editor.

4. Enter any authentication information.

The other inputs to the Web Service Call builder are service type-specific, and in the case of WSDL service calls, may be read-only or have default values specified by the WSDL document.

Create the Service operation for this Web-Service

Specify the execute method of the “WebService Call” in the “Action To Call”.

In the Consumer Model (for showing the result on the page purpose model)

User the builder - Service Consumer and specify the Provider builder name (for DB/WebService call builder present)

In the Data page we can follow the following things

Here we are specifying

Which result it should show from the operation and also we are specifying which page and span result should be displayed.

When we run the portlet it will show the result in the data-grid format.

If we do not specify any input value it will take the default value from the “input schema”

Currently for the respective input data, data is not present it is showing the only datapage.

Custom builders in WPF?

You might need custom builders to:

Automate a task that occurs frequently, if same set of some builders appears in your model again and again.

To enforce a particular development standard.

Support a new data type integration.

In such conditions you might need to create custom builders.

Design of a typical builder in WPF.

Link for creating custom builders:http://publib.boulder.ibm.com/infocenter/wpfhelp/v6r1m2/index.jsp?topic=/com.bowstreet.designer.doc/tutorials/Custom_Builder_Introductory_Tutorial.htm

How to personalize a page using Profiling?

Profiling to Personalize Portlets

In this section, you will perform similar tasks to expose builder inputs to the portlet's personalization page.

Individual portlet users with an access level of Privileged User or higher can use the portlet's personalization page. These users can open the personalization page and make their own choices from the available options. The settings they choose control certain behaviors of the portlet depending upon which builder

inputs have been exposed to this page. These settings apply separately to each individual user.

To test the portlet's personalization features, you will need to use the various test users you created in the Setup Requirements section of this tutorial. To be sure these features are working; you will need to log in as one user and make choices on the personalization page then log in as a different user and make different choices.

Using this technique, you should be able to determine that the personalization settings are stored independently for each user.

Since setting up a personalization page is so similar to setting up a configuration page, fewer details are provided in this section as you can refer to the details in the previous section if you need to.

Create the Profile Set and Entries

Personalization pages in portlets often include preferences about how a portlet should appear. The personalization page for this portlet will have options that allow the users to choose which columns of data should appear, how many rows of data should appear on one page, which column to use as the default sort, and whether or not to group the data on the detail page.

In this section, you will create the Profile Set for the personalization page and the Profile Entries in this Profile Set.

1. Create the Profile Set

a. Choose from the File menu File > New > WebSphere Portlet Factory Profile Set

b. Name the Profile Set EP_EditPage

c. In the Description field, enter Employees Portlet Edit Page

d. Click Finish to continue. The new Profile Set will open in the Profile Set Editor. This Profile Set is stored in the WEB-INF\profiles folder in this project and is named EP_EditPage.pset.

2. Create the Profile Entries

By now you should be able to use what you learned while creating the Entries in the EP_ConfigPage Profile Set to create the Entries in this Profile Set without the benefit of detailed instructions. The following table describes the Entries needed in the Profile Set used for the portlet's personalization page.

a. Create the Entries in the EP_EditPage Profile Set. Use the Add button to create new Entries.

b. Save the Profile Set periodically to protect your work.

Profiling the Builder Call Inputs

Some builder call inputs have simple profiling options while others are more complex. Consider the data table in Data Column Modifier. Profiling table rows allows you to enable / disable the entire row or to control the values of individual properties within the row.

1. Open the EP_Profiling_Working model again.

2. Enable control over the number of rows to display

a. Locate the builder call of type Data Column Modifier named allEmployeesFormatting and edit it.

b. In the Settings to control paging of the table data section, locate the input labeled Page Size. This input controls how many rows of data will display at any one time.

c. Profile this input so that the user can choose how many rows to display.

i. Click the next to this input.

ii. Choose the EP_EditPage Profile Set. Be sure to choose the correct Profile Set as this dialog box does not always default to the last Profile Set used.

iii. Choose the PagingRows input you created earlier.

iv. Click OK to save these changes.

d. When completed, this input will be grayed out and the Profile Set : Profile Entry relationship will be displayed below it.

e. Leave this builder call open as you will make more changes to it in the next few steps.

3. Enabling optional display columns

a. In the same builder call, scroll down to the table used to manage the columns of data.

b. Locate the row labeled WORKDEPT and profile it by clicking the on that row. The Profile Row of

Inputs dialog box will open.

i. Note that this box has one to enable / disable the entire row and one for each

property in the row. Since the objective is to profile the Status property which is how a column's visibility is controlled, click the next to Status.

ii. Choose the correct Profile Set and Profile Entry for this input. Be sure to choose the EP_EditPage Profile Set and the WorkDept_OnOff Profile Entry.

iii. Click OK to save these settings.

c. Click OK to close this dialog box. Once saved, the Status column in the WORKDEPT row should be grayed out indicating that it has been profiled.

d. Profile the Status property of the JOB row and the HIREDATE row the same way as the WORKDEPT row. Be sure to choose the correct Profile Set and Profile Entries.

i. Associate the Status property of the JOB row with the Entry called JobTitle_OnOff.

ii. Associate the Status property of the HIREDATE row with the Entry called

HireDate_OnOff.

e. Save and close this builder call by clicking the OK button in the builder call editor.

4. Enabling the default column sorting option

a. Locate the builder call of type Action List named main and edit it. This Action List runs automatically because its name is main. The View and Form builder contains an Action List called main but it is disabled in the Advanced section of the builder call in this model. It was necessary to disable it in order to add the SortSortAction method call described in the next

step.

b. The second action in the list is a call to a method named SortSortAction. Click the button to see the names of the other similar actions.

i. You should see names like SortSortAction, SortSortAction1,

SortSortAction2, etc. Each SortSortAction method corresponds to a sorted

column in the employees data table counting the columns from left to right. For example, if SortSortAction2 is chosen, the third sortable column from the left will be sorted when the page loads for the first time.

ii. Click Cancel to avoid making any changes to the Action List step.

c. Profile the Action List step containing the SortSortAction method call.

i. Click the row in the table containing SortSortAction. The Profile Row of

Inputs dialog box will open.

ii. Click the next to Action List. The idea is to set the name of the method that will be called by using the value in a Profile Entry.

iii. Associate this input with the Default_SortAction Entry in the EP_EditPage Profile Set.

iv. Click OK to save these settings.

d. Save and close this builder call by clicking the OK button in the builder call editor.

5. Save the model.

What are Data Driven Portlets?
In data driven portlets we fetch data from DB either by creating JNDI/connection.In the provider model we use sql Call and other builder data driven builders to fetch data from db.in the consumer model we can use the data.

What is SOA in WPF?

How to achieve Inter portlet communication Between the Portlet in WPF?
- Imported Model
- Linked Model

Difference between Imported Model & Linked Model?
http://www-10.lotus.com/ldd/pfwiki.nsf/dx/07282008035003PMWEBR9U.htm
Recomendations:-
Linked Model -
Recommendation: The Linked Model builder should rarely be used directly. For most scenarios, consider whether techniques such as Service Provider or Model Container can provide the modularity you need.

Imported Model builder -

Recommendation: Use Imported Model when you want to include some builders in multiple models, such as Event Declarations, Shared Variables, or shared utility functions. and method call for example out GETREMOTEUSER METHOD by using substring which we have created.

what is webapp in WPF?

webapp is the name of the structure created by the builders in the model and it is the abstraction for all the elements that can make up a web app including pages, variables, schemas, methods and events.
webappaccess paramater using portlet factory api and used to change variable in webapp.

Logging to the portal directly from the url, Passing parameter to portlet directly from url..

2012-02-15T23:18:00.001-08:00

If you want to login to the portal directly from the url and want to pass some parameter directly to the portlet from the url follow the below steps:-

Step1:-create custom login portlet and in the portlet get the username and password and the argument that u want to pass, Here I am considering parameter as .param1.param2,param3.

the code is as below :-

package com.ibm.customloginportlet;

import java.io.IOException;
import java.util.HashMap;
import java.util.Map;
import javax.naming.InitialContext;
import javax.naming.NamingException;
import javax.portlet.ActionRequest;
import javax.portlet.ActionResponse;
import javax.portlet.GenericPortlet;
import javax.portlet.PortletException;
import javax.portlet.PortletRequest;
import javax.portlet.PortletRequestDispatcher;
import javax.portlet.PortletSession;
import javax.portlet.RenderRequest;
import javax.portlet.RenderResponse;
import javax.security.auth.login.LoginException;
import javax.servlet.http.HttpServletRequest;
import javax.servlet.http.HttpServletRequestWrapper;
import org.apache.log4j.Logger;
import com.ibm.portal.auth.exceptions.AuthenticationException;
import com.ibm.portal.auth.exceptions.AuthenticationFailedException;
import com.ibm.portal.auth.exceptions.PasswordInvalidException;
import com.ibm.portal.auth.exceptions.PortletLoginDisabledException;
import com.ibm.portal.auth.exceptions.SessionTimeOutException;
import com.ibm.portal.auth.exceptions.SystemLoginException;
import com.ibm.portal.auth.exceptions.UserAlreadyLoggedInException;
import com.ibm.portal.auth.exceptions.UserIDInvalidException;
import com.ibm.portal.portlet.service.PortletServiceHome;
import com.ibm.portal.portlet.service.PortletServiceUnavailableException;
import com.ibm.portal.portlet.service.login.LoginHome;
import com.ibm.portal.portlet.service.login.LoginService;
import com.ibm.websphere.security.WSSecurityException;
import com.ipops.vo.CRMRequestDataVo;

/**
* Custom Login Portlet
*/
public class CustomLoginPortlet extends GenericPortlet {

private static final String VIEW_JSP = "/jsp/CustomLoginPortletView.jsp";
private static final String VIEW_JSP_FAILED = "/jsp/LoginFailed.jsp";
private static Logger logger = Logger.getLogger (CustomLoginPortlet.class);
LoginHome loginHome;
public void init() throws PortletException{
try
{
InitialContext ctx = new InitialContext();
PortletServiceHome psh = (PortletServiceHome) ctx.lookup(LoginHome.JNDI_NAME);
loginHome = (LoginHome) psh.getPortletService(LoginHome.class);
}
catch (NamingException e)
{
e.printStackTrace();
}
catch (PortletServiceUnavailableException e)
{
logger.error("PortletServiceUnavailableException",e);
}
}

public void doView(RenderRequest request, RenderResponse response) throws PortletException, IOException
{
response.setContentType("text/html");
CRMRequestDataVo vo =getRequestData(request);
PortletSession session = request.getPortletSession();
PortletRequestDispatcher dispatcher = null;
String pageType = (String)session.getAttribute("pageType");
if(pageType != null && pageType.equalsIgnoreCase("failed"))
{
dispatcher = getPortletConfig().getPortletContext().getRequestDispatcher(VIEW_JSP_FAILED);
}
else
{
request.setAttribute("CRMData", vo);
dispatcher = getPortletConfig().getPortletContext().getRequestDispatcher(VIEW_JSP);

}
dispatcher.include(request, response);
session.removeAttribute("pageType");
}

public void processAction(ActionRequest request, ActionResponse response) throws PortletException, java.io.IOException
{
PortletSession session = request.getPortletSession();
try {
String userId = request.getParameter("param1");
String password = request.getParameter("param2");
LoginService loginService = loginHome.getLoginService(request, response);
Map contextMap = new HashMap();
contextMap.put(LoginService.DO_RESUME_SESSION_KEY, new Boolean(false));
loginService.login(userId, password.toCharArray(), contextMap, null);
response.sendRedirect("/wps/myportal/orderDisplay?orderID="+request.getParameter("param3"));

}
catch (PasswordInvalidException e)
{
logger.error("PasswordInvalidException:",e);
}
catch (UserIDInvalidException e)
{
logger.error("UserIDInvalidException:",e);
}
catch (AuthenticationFailedException e)
{
logger.error("AuthenticationFailedException:",e);
}
catch (AuthenticationException e)
{
logger.error("AuthenticationException:",e);
}
catch (SessionTimeOutException e)
{
logger.error("SessionTimeOutException:",e);
}
catch (PortletLoginDisabledException e)
{
logger.error("PortletLoginDisabledException:",e);
}
catch (UserAlreadyLoggedInException e)
{
logger.error("UserAlreadyLoggedInException:",e);
}
catch (SystemLoginException e)
{
logger.error("UserAlreadyLoggedInException:",e);
}
catch (LoginException e)
{
session.setAttribute("pageType","failed");
logger.error("LoginException:",e);
}
catch (WSSecurityException e)
{
logger.error("WSSecurityException:",e);
}
catch (com.ibm.portal.auth.exceptions.LoginException e)
{
logger.error("com.ibm.portal.auth.exceptions.LoginException:",e);
}
catch (Exception e)
{
logger.error("Exception:",e);
response.sendRedirect("/wps/portal/");
}
}

private CRMRequestDataVo getRequestData(PortletRequest request){

CRMRequestDataVo vo = null;
HttpServletRequest httpServletRequest = (HttpServletRequest)request;
while(httpServletRequest instanceof HttpServletRequestWrapper)
{
HttpServletRequestWrapper httpServletRequestWrapper = (HttpServletRequestWrapper)httpServletRequest;
httpServletRequest = (HttpServletRequest)httpServletRequestWrapper.getRequest();

}

if(httpServletRequest.getParameter("param1") != null && httpServletRequest.getParameter("param2") != null && httpServletRequest.getParameter("param3") != null )
{
vo = new CRMRequestDataVo();
vo.setUserName(httpServletRequest.getParameter("param1"));
vo.setPassword(httpServletRequest.getParameter("param2"));
vo.setOrderID(httpServletRequest.getParameter("param3"));
}else
{
PortletSession psession = request.getPortletSession();
psession.setAttribute("pageType","failed");
}
return vo;

}

}

In the above code I am using 2 jsps, if the vo is not null then i am passing vo to CustomLoginPortletView.jsp.

The jsp code is :-
<%@page language="java" contentType="text/html; charset=ISO-8859-1" pageEncoding="ISO-8859-1" session="false"%>
<%@taglib uri="http://java.sun.com/portlet_2_0" prefix="portlet"%>
<%@page import="com.ipops.vo.*" %>
<portlet:defineObjects />

<form method="post" name="AutoLogin" action="<portlet:actionURL/>">
<%CRMRequestDataVo vo = (CRMRequestDataVo)renderRequest.getAttribute("CRMData"); %>

<input type = "hidden" name="param1" value="<%=vo.getUserName()%>">
<input type = "hidden" name="param2" value="<%=vo.getPassword()%>">
<input type = "hidden" name="param3" value="<%=vo.getOrderID()%>">

</form>

<script language="javaScript" type="text/javascript" >
function autoSubmit()
{

document.AutoLogin.submit();
}
autoSubmit();
</script>

after getting the parameter from the processAction we are redirecting the URL.

Step2:-create a URL Mapping and map it to the portlet where you need the inputs, In my case i am passing param3 as input param.

Step3:- Now logout from the portal and simply put this in the URL:

http://localhost:10040/wps/portal/CRMLogin?param1=wpsadmin&param2=wpsadmin&param3=981139

you will get loged in to the portal and in the portlet you can fetch the param3 and can do further action as per req.

opening PDF as popup in jsr 168 portlet,popup in jsr 168

2011-12-16T00:10:00.000-08:00

Since JSR 168 has only support for html so we need a servlet to be called from the jsp.

Step1- Create a servlet and in doGet use this code

protected void doGet(HttpServletRequest request, HttpServletResponse response) throws ServletException, IOException {

HttpSession httpsession =request.getSession();
Map map = (Map)httpsession.getAttribute("resultMap");
if(map != null)
{
GeneratePDF.generatePDFReciept(map, response);
}
httpsession.removeAttribute("resultMap");
}

Here I am passing map to GeneratePDF method and in this method i am using itext API to generate PDF from the map values.

step2:- use the following code in the process action and set attribute in the HttpSession.

HttpServletRequest httpServletRequest = (HttpServletRequest)request;
while(httpServletRequest instanceof HttpServletRequestWrapper){
HttpServletRequestWrapper httpServletRequestWrapper =
(HttpServletRequestWrapper)httpServletRequest;
System.out.println("HttpServletRequestWrapper " + httpServletRequestWrapper);
httpServletRequest = (HttpServletRequest)httpServletRequestWrapper.getRequest();
}

HttpSession httpsession = httpServletRequest.getSession();

httpsession.setAttribute("resultMap", receiptmap);

3:-Now invoke the servlet as popup from the portlet jsp by simply calling javascript on clicking the button or link, as follows:-

function servletCall()
{

window.open("http://<%=renderRequest.getServerName()%>:<%=renderRequest.getServerPort()%><%=renderRequest.getContextPath()%>/PDFPopup","PrintWindow","toolbar=0 scrollbars=yes");

}

Now you can view your data in popup :)

calling body onload javascript in portlet jsr 168.

2011-11-01T03:51:00.000-07:00

Since we are not calling body tag in jsp in jsr 168 portlet so simply create a script tag and call function as :-

function checkEnter()

{

document.body.onkeypress = enterKey

}

checkEnter();

</script>

Simply add this in your jsp and in check enter function you can call your own functions as I am calling enterKey Functions,

Here I am checking for the enter key press :

function enterKey(evt) {

var evt = (evt) ? evt : event;

var charCode = (evt.which) ? evt.which : evt.keyCode;

if (charCode == 13) {

setOperationName('POST','RECEIPT');

return false;

}

return true;

}

</script>

personalization of theme ,showing group related links in a theme

2011-10-18T04:12:00.000-07:00

Below code personalizes the theme , and you can show only the related links for groups, in this code i have created a url mapping for change password portlet and personalised it by fetching group name by PUMA api, u have to use this code in the banner_toolbar.jspf in ur theme.

PUMA Api code to reset password, Verify old password in websphere portal

2011-06-27T03:51:00.000-07:00

When you are not using LDAP and you have to change user password with verifying old password the only option left is by using WAS Programatic Login.you can reset new password by Puma API and verify the old password by WAS Authentication, the below code is working fine for me.

PortletServiceHome psh = null;

try {
if (psh == null) {
javax.naming.Context ctx = new javax.naming.InitialContext();
psh = (PortletServiceHome) ctx.lookup("portletservice/com.ibm.portal.um.portletservice.PumaHome");
}
} catch (NamingException e) {

e.printStackTrace();

}
HashMap userAttrs = new HashMap();

String oldPwd = request.getParameter("OLD_PASSWORD");
String pwd1 = request.getParameter("PASSWORD");
String pwd2 = request.getParameter("PASSWORD_CONFIRM");

try
{

PumaHome service=(PumaHome) psh.getPortletService(PumaHome.class);
PumaLocator pLocator=service.getLocator();
PumaController pc = service.getController();
com.ibm.wps.puma.User vuser = (com.ibm.wps.puma.User)request.getAttribute("com.ibm.portal.puma.request-user");
String userid = vuser.getUserID();

if( pwd1 != null && oldPwd != null )
{

//verify password

LoginContext lc = null;
Subject subject = null;
System.out.println("old pwd::"+oldPwd);
try {
lc = new LoginContext("WSLogin",
new WSCallbackHandlerImpl(userid, oldPwd));

} catch (LoginException le) {
System.out.println("Cannot create LoginContext. " + le.getMessage());

} catch(SecurityException se) {

System.out.println("Security Exception. " + se.getMessage());
}

try {
lc.login();
subject = lc.getSubject();
System.out.println("loged in");
passwordVerification = true;
com.ibm.websphere.security.auth.WSSubject.setRunAsSubject(subject);
} catch(LoginException le) {
passwordVerification = false;
System.out.println("Fails to create Subject. " + le.getMessage());

}

if(passwordVerification)
{
userAttrs.put("uid", userid);
userAttrs.put("password", pwd1);

List userList = pLocator.findUsersByAttribute("uid", userid);
User editUser = (User)userList.get(0);
pc.setAttributes(editUser, userAttrs);

passwordChanged = true;

}

WebSphere Portal Project Architecture,Portal Project Flow Diagram

2011-06-09T03:31:00.000-07:00

This Diagram Shows a Portal project flow Diagram, Project flow can vary according to requirements.

Inter Portlet Communication in JSR -168 by RAD 7.5,Portlet Wiring.

2011-06-07T02:43:00.000-07:00

1.First create a new portlet project or use existing one,The source and target portlet should be in same workspace.
2.Create Portlet IPC1 & IPC2.
3.Create Source and Target Portlets as shown below.

Select The Data Type For Source Portlet, as shown below.

Similarly make a cooperative target portlet, as shown.

As for source portlet, select Data Type for target portlet.

Then in the source portlet JSP use the Cooperative Source Trigger to create an event on click,

After setting the event use
if(actionValue != null && "TargetAction".equals(actionValue)) {

        String input = request.getParameter("inputProperty");

            session.setAttribute("input", input,session.PORTLET_SCOPE);
        }
in target portlet process action to fetch the value that you have set in the scope.

After that you can use bean or session to render the value from process action to targer portlet jsp.

Then deploy the portlet, and add them on a page, Then edit page layout and do the WIRING between source and target portlets. as shown below.

Now your Inter Portlet communication is done.you can put the value in the source portlet and after clicking submit value will be shown on target portlet.

On submitting the output will be:-

For any help or issue please contact me at sanjeetsinghmerhal@gmail.com.
Please follow me if material is useful for you.
Thanks

giving signer certificates and trust stores in WAS to run services from Portal.

2011-05-27T02:56:00.000-07:00

1.First import the certificates by running ikeyman.sh utility from the /bin, use xmanger for running this utility the UI will not appear in Putty.you can refer
http://publib.boulder.ibm.com/infocenter/adiehelp/v5r1m1/index.jsp?topic=/com.ibm.wasee.doc/info/ee/ae/tsec_importsigner.html for importing keys.

2.put the imported keys in WAS server by winscp.

3.Open WAS administration console and go to signer certificates ,
put entry for client as shown below.

4. Similarly put entries for trust stores for default and Client as shown below by clicking on trust stores.
5. Restart WAS , and start hitting services from portal, your EJB will run on WAS properly.

Steps for Adding custom Attribute in profile WebSphere Portal 6.1.

2011-05-27T02:02:00.000-07:00

First install the attribute installer.

1.Restart Portal Server

2.Edit wkplc.properties with the following info:
la.propertyName=userCompanyId
la.entityTypes=PersonAccount
la.dataType=String
la.multiValued=false

Run ConfigEngine.bat wp-add-property -DWasPassword=secret

After running the above command, a file wimxmlextension.xml will be created in \config\cells\\wim\model folder.

Put an entry for your attribute by directly editing the file wimxmlextension.xml

Restart Portal Server

Run ConfigEngine.bat wp-query-attribute-config -DWasPassword=secret

This will create availableAttributes.html report in /ConfigEngine/log & now you can check your newly created
attribute from the Administration.