The problem faced in development of the portlet UI is noted below. <br />
<br />
From portal web client we are trying to get the human tasks generated on a r
emote process server, using HumanTask APIs. The steps followed are:<br />
<p />
¨ Obtain the remote HumanTaskManager instance. (successful)<br />
<br />
¨ Execute the method htm.query(“..”, “..”,..) (s
hown below) to get the task ids of human task. <br />
<p />
<br />
o The query used is: QueryResultSet resultSet = htm.query("TASK.TKIID","(TAS
K.STATE = TASK.STATE.STATE_READY OR TASK.STATE = TASK.STATE.STATE_CLAIMED) A
ND TASK.KIND = TASK.KIND.KIND_PARTICIPATING AND WORK_ITEM.REASON = WORK_ITEM
.REASON.REASON_POTENTIAL_OW
NER ","TASK.TKIID", (Integer)null, (TimeZone)null);<br />
<p />
<br />
¨ Variable <b>“resultSet” returned has size 0</b>, even thou
gh tasks are there in BPEDB.<br />
<p />
<br />
We have also added the required jars –(task137650.jar, taskapi.jar)- t
o the Web-App libraries.<br />
<p />
<br />
Enviornment: Websphere Portal Server 6.0, Websphere Process Server 6.0.0.2<b
r />
<p />
<br />
<b>Another point</b> to be noted is that the query is returning the required
 resultSet when it is executed in a web project running on the process serve
r. Here both remote and local access is working.<br />
<p />
<br />
Please help us in finding a solution to the same.

[ Post a follow-up to this message ]

As I am trying to access HumanTaskManagerHome from a websphere portal thats 
installed on top of BPC configured websphere process server, the code for ge
tting the HumanTaskManagerHome was returning the local HumanTaskManagerHome 
instance instead of the rem
ote HumanTaskManagerHome instance.<br />
<br />
The code i used was similar to this one:<br />
<br />
try{<br />
System.out.println("getHumanTaskHome()- access HumanTaskManagerHome");<br />
//Obtain the default initial JNDI context<br />
Hashtable env = new Hashtable();<br />
env.put(Context.PROVIDER_URL, "corbaloc:iiop:" + serverIp + ":" + port);<br 
/>
InitialContext initialContext = new InitialContext(env);<br />
System.out.println("getHumanTaskHome()- got initialContext"+InitialContext.P
ROVIDER_URL);<br />
<br />
//Lookup the  home interface of the HumanTaskManager bean<br />
Object result = initialContext.lookup("ejb/HumanTaskManagerHome");<br />
System.out.println("got lookup: "+result);<br />
<br />
//Convert the lookup result to the proper type<br />
HumanTaskManagerHome taskHome = (HumanTaskManagerHome)javax.rmi.PortableRemo
teObject.narrow(result,HumanTaskManagerHome.class);<br />
System.out.println("getHumanTaskHome()-got htmHome"+taskHome);<br />
<br />
//Access the  interface of the  session bean<br />
htm = taskHome.create();<br />
System.out.println("HTM home created");<br />
<br />
}catch(Exception e){<br />
System.out.println("Exception message: "+e.getMessage());<br />
System.out.println("exception getfHumanTaskManager():"+e);<br />
}<br />
<p />
Its really surprising that code was looking at initial context. After updati
ng to portal server 6.0.1.1 the issue fo context got solved. But now I am ge
tting this exception which i will post as new thread.<br />
<br />
Exception is:<br />
exception: javax.naming.NameNotFoundException: Context: serverip-cell/nodes/
Node01/servers/server1, name: ejbs/DefaultSession: First component in name e
jbs/DefaultSession not found. <strike><b>Root exception is org.omg.CosNaming
.NamingContextPackage.NotFo
und: IDL:omg.org/CosNaming/NamingContext/NotFound:1.0</b></strike>

[ Post a follow-up to this message ]