PAPI example not working

Question

Hi Guys, i have deployed a process on the Wblogic server. My process runs fine. I am trying to run the PAPI example given at the bea website. It also runs fine. but i do not get the desired result.
My directory.xml points to the right database and all the information given out there seems to be correct.
Any help will be greatly appreciated.
Thanks
Here is the configuration code:
Properties configuration = new Properties();
configuration.setProperty(ProcessService.DIRECTORY_ID, "default");
configuration.setProperty(ProcessService.DIRECTORY_PROPERTIES_FILE, "F:/bea/albpm6.0/j2eewl/conf/directory.xml");
configuration.setProperty(ProcessService.WORKING_FOLDER, "/tmp");
try {
ProcessService processService = ProcessService.create(configuration);
Result What i get is
Creating connector [fuego:SQL]
Creating local folder: /tmp\system\Schema33871921693956582\catalogs
Loading catalogs from local folder: /tmp\system\Schema33871921693956582\catalogs
0 jars found locally.
[CatalogMgrCache] =======================
Registering CatalogMgr [bea/2008-09-10 14:52:59-04:00] ...CatalogManagerCache 25865024:
Managers:
Counters:
[CatalogMgrCache] =======================
CatalogMgr [bea/2008-09-10 14:52:59-04:00] REGISTERED!CatalogManagerCache 25865024:
Managers:
{bea/2008-09-10 14:52:59-04:00=fuego.util.LocalCatalogManager@f102d3}
Counters:
Session Created!!!!!!!!!!!!!!!
[CatalogMgrCache] =======================
Unregistering CatalogMgr [bea/2008-09-10 14:52:59-04:00] ...CatalogManagerCache 25865024:
Managers:
{bea/2008-09-10 14:52:59-04:00=fuego.util.LocalCatalogManager@f102d3}
Counters:
{bea/2008-09-10 14:52:59-04:00=1}
[CatalogMgrCache] =======================
CatalogMgr [bea/2008-09-10 14:52:59-04:00] UNREGISTERED!CatalogManagerCache 25865024:
Managers:
Counters:
{}

Answer 1

Thanks for your response. I really could not get chance to try it out again. But now if i use process Participants user name and pasword, i get an exception about NoInitialContext fund. Did you do something extra to run this simple example?
Here is my stack trace:
Creating connector [fuego:SQL]
Local folder /tmp\system\Schema33871921693956582\catalogs found.
Loading catalogs from local folder: /tmp\system\Schema33871921693956582\catalogs
0 jars found locally.
[CatalogMgrCache] =======================
Registering CatalogMgr [bea/2008-09-10 14:52:59-04:00] ...CatalogManagerCache 25865024:
Managers:
Counters:
[CatalogMgrCache] =======================
CatalogMgr [bea/2008-09-10 14:52:59-04:00] REGISTERED!CatalogManagerCache 25865024:
Managers:
{bea/2008-09-10 14:52:59-04:00=fuego.util.LocalCatalogManager@f102d3}
Counters:
Session Created!!!!!!!!!!!!!!!
Process: /ExpenseReport#Default-1.0
Unreachable Engine Tolerance (seconds):
by default: 0
to be used: 0
This papi client will not cache exceptions which imply that an engine could not be reached.
A user transaction provider is not available for reading Papi News received through the JMS Topic (probable reason: PAPI client is running outside a j2ee container). Papi News will be processed anyway. Details: javax.naming.NoInitialContextException: Need to specify class name in environment or system property, or as an applet parameter, or in an application resource file: java.naming.factory.initial
The connection to the JMS Topic engine was completed successfully.
The connectivity to the JMS Topic for the server synchronization information has been temporarily interrupted.
Details:
Error looking up Topic Connection Factory 'XATopicConnectionFactory'.
Details:
javax.naming.NoInitialContextException: Need to specify class name in environment or system property, or as an applet parameter, or in an application resource file: java.naming.factory.initial
Caused by: Need to specify class name in environment or system property, or as an applet parameter, or in an application resource file: java.naming.factory.initial
fuego.papi.impl.j2ee.JMSTopicLookUpException: Error looking up Topic Connection Factory 'XATopicConnectionFactory'.
Details:
javax.naming.NoInitialContextException: Need to specify class name in environment or system property, or as an applet parameter, or in an application resource file: java.naming.factory.initial
     at fuego.papi.impl.j2ee.J2EEEngineAccessImpl$TopicSubscriberImpl.lookupTopic(J2EEEngineAccessImpl.java:628)
     at fuego.papi.impl.j2ee.J2EEEngineAccessImpl$TopicSubscriberImpl.run(J2EEEngineAccessImpl.java:519)
Caused by: javax.naming.NoInitialContextException: Need to specify class name in environment or system property, or as an applet parameter, or in an application resource file: java.naming.factory.initial
     at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:645)
     at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:247)
     at javax.naming.InitialContext.getURLOrDefaultInitCtx(InitialContext.java:284)
     at javax.naming.InitialContext.lookup(InitialContext.java:351)
     at fuego.papi.impl.j2ee.J2EEEngineAccessImpl$TopicSubscriberImpl.lookupTopic(J2EEEngineAccessImpl.java:619)
     ... 1 more
Could not perform the requested operation
fuego.papi.ProcessNotAvailableException: Process '/ExpenseReport#Default-1.0' not available.
     at fuego.papi.impl.ProcessServiceImpl.createProcessControl(ProcessServiceImpl.java:1203)
     at fuego.papi.impl.ProcessServiceSessionImpl$1.run(ProcessServiceSessionImpl.java:2360)
     at fuego.papi.impl.ProcessServiceImpl.executeEngineOp(ProcessServiceImpl.java:1817)
     at fuego.papi.impl.ProcessServiceSessionImpl.getProcessControl(ProcessServiceSessionImpl.java:2365)
     at fuego.papi.impl.ProcessServiceSessionImpl.processGetInstances(ProcessServiceSessionImpl.java:2034)
     at com.alger.papi.PapiExample.main(PapiExample.java:29)
Caused by: fuego.papi.impl.EngineNotAvailableException: Cannot reach engine 'albpmengine' at URL: ''.
     at fuego.papi.impl.EngineNotAvailableException.wrapConnectionException(EngineNotAvailableException.java:80)
     at fuego.papi.impl.j2ee.J2EEEngineAccessImpl.createSecureEngine(J2EEEngineAccessImpl.java:161)
     at fuego.papi.impl.ProcessServiceImpl.createSecureEngine(ProcessServiceImpl.java:1210)
     at fuego.papi.impl.ProcessServiceSessionImpl$2.run(ProcessServiceSessionImpl.java:3509)
     at fuego.papi.impl.ProcessServiceImpl.executeEngineOp(ProcessServiceImpl.java:1817)
     at fuego.papi.impl.ProcessServiceSessionImpl.getSecureEngine(ProcessServiceSessionImpl.java:3517)
     at fuego.papi.impl.ProcessServiceImpl.createProcessControl(ProcessServiceImpl.java:1196)
     ... 5 more
Caused by: javax.naming.NoInitialContextException: Need to specify class name in environment or system property, or as an applet parameter, or in an application resource file: java.naming.factory.initial
     at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:645)
     at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:247)
     at javax.naming.InitialContext.getURLOrDefaultInitCtx(InitialContext.java:284)
     at javax.naming.InitialContext.lookup(InitialContext.java:351)
     at fuego.papi.impl.j2ee.J2EEEngineAccessImpl.getEngineHome(J2EEEngineAccessImpl.java:259)
     at fuego.papi.impl.j2ee.J2EEEngineAccessImpl.getSecureEngineInterface(J2EEEngineAccessImpl.java:313)
     at fuego.papi.impl.j2ee.J2EEEngineAccessImpl.createSecureEngine(J2EEEngineAccessImpl.java:158)
     ... 10 more