PAPI client is running outside a j2ee container

Question

Hi,
I install BPM J2EE 10.3.1 for linux and weblogic 10.3 for linux on Red Hat Linux Enterprise 5. The database' version is 10.2.0.1 for windows and the database is install in window server 2003 sp1 on another machine.
I search this forum and copy and change the code. But I still get error "PAPI client is running outside a j2ee container"
The java code runs in the 3rd machine.
-------------------------java code-------------------------------------------------
Properties configuration = new Properties();
configuration.setProperty(ProcessService.DIRECTORY_ID, "Default");
configuration.setProperty(ProcessService.DIRECTORY_PROPERTIES_FILE, "F:\\share\\192.168.1.103\\directory.xml");
Properties systemProperties = System.getProperties();
systemProperties.setProperty("java.naming.factory.initial", "weblogic.jndi.WLInitialContextFactory");
systemProperties.setProperty("java.naming.provider.url", "t3://192.168.1.103:7001");
ProcessService processService = ProcessService.create(configuration);
ConnectionPassport Conpassport = processService.createPassportWithPreset("container-auth");
Conpassport.setParticipant("jcooper");
Conpassport.setPassword("welcome1");
System.out.println("34");
Conpassport.fillPassport();
System.out.println("36");
ProcessServiceSession session = processService.createSession(Conpassport, null);
System.out.println("38");
String processName = "/processA";
Arguments arguments = Arguments.create();
System.out.println("41");
session.processCreateInstance(processName, "BeginIn", arguments);//
System.out.println("43");
-----------------------error message----------------------------------------------------
D:\JDeveloper11g_20090318\jdk160_05\bin\javaw.exe -client -classpath E:\Jdeveloper10131_20090318\jdev\mywork\GDHZDJDCIntegrationTest\HZGTprocess\classes;D:\BPM_HOME_standalone\client\papi\lib\b1oracle.jar;D:\BPM_HOME_standalone\client\papi\lib\b1util.jar;D:\BPM_HOME_standalone\client\papi\lib\b1base.jar;D:\BPM_HOME_standalone\client\papi\lib\fuegopapi-client.jar hzgtprocess.VM_192_168_1_103_linux
Creating connector [fuego:SQL]
Creating ProcessService with id 'oracle/2009-09-14 13:23:12+08:00'.
********* PAPI (Version 10.3.1.0.0 Mantainance Pack 1 Build # 98982 ) is starting *********
Local folder /tmp\system\Schema3387192-437105321\catalogs found.
Loading catalogs from local folder: /tmp\system\Schema3387192-437105321\catalogs
0 jars found locally.
[CatalogMgrCache] =======================
Registering CatalogMgr [oracle/2009-09-14 13:23:12+08:00] ...CatalogManagerCache 20195943:
Managers:
Counters:
[CatalogMgrCache] =======================
CatalogMgr [oracle/2009-09-14 13:23:12+08:00] REGISTERED!CatalogManagerCache 20195943:
Managers:
{oracle/2009-09-14 13:23:12+08:00=fuego.util.LocalCatalogManager@1cbda0a}
Counters:
ProcessService 'oracle/2009-09-14 13:23:12+08:00' created successfully.
34
36
38
41
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: Cannot instantiate class: weblogic.jndi.WLInitialContextFactory [Root exception is java.lang.ClassNotFoundException: weblogic.jndi.WLInitialContextFactory]
The connection to the JMS Topic engine was completed successfully.
Exception in thread "main" fuego.papi.ProcessNotAvailableException: Process '/processA#Default-1.0' not available.
     at fuego.papi.impl.AbstractProcessLoader.createProcess(AbstractProcessLoader.java:96)
     at fuego.papi.impl.AbstractProcessLoader.createProcess(AbstractProcessLoader.java:36)
     at fuego.papi.impl.SessionProcessLoader.load(SessionProcessLoader.java:254)
     at fuego.papi.impl.ProcessManager.get(ProcessManager.java:894)
     at fuego.papi.impl.ProcessServiceImpl.getProcess(ProcessServiceImpl.java:1380)
     at fuego.papi.impl.SessionProcessManager.getProcess(SessionProcessManager.java:143)
     at fuego.papi.impl.ProcessServiceSessionImpl.processGet(ProcessServiceSessionImpl.java:2665)
     at fuego.papi.impl.ProcessServiceSessionImpl.checkBeginPermissions(ProcessServiceSessionImpl.java:4286)
     at fuego.papi.impl.ProcessServiceSessionImpl.processCreateInstance(ProcessServiceSessionImpl.java:3177)
     at hzgtprocess.VM_192_168_1_103_linux.main(VM_192_168_1_103_linux.java:42)
Caused by: fuego.papi.impl.EngineNotAvailableException: Cannot reach engine 'bpmengine' at URL: ''.
     at fuego.papi.impl.EngineNotAvailableException.wrapConnectionException(EngineNotAvailableException.java:80)
     at fuego.papi.impl.j2ee.J2EEEngineAccessImpl.createSecureEngine(J2EEEngineAccessImpl.java:181)
     at fuego.papi.impl.ProcessServiceImpl.createSecureEngine(ProcessServiceImpl.java:1111)
     at fuego.papi.impl.ProcessServiceSessionImpl$2.run(ProcessServiceSessionImpl.java:3987)
     at fuego.papi.impl.ProcessServiceImpl.executeEngineOp(ProcessServiceImpl.java:1693)
     at fuego.papi.impl.ProcessServiceSessionImpl.getSecureEngine(ProcessServiceSessionImpl.java:3995)
     at fuego.papi.impl.AbstractProcessLoader.createProcess(AbstractProcessLoader.java:48)
     ... 9 more
Caused by: javax.naming.NoInitialContextException: Cannot instantiate class: weblogic.jndi.WLInitialContextFactory [Root exception is java.lang.ClassNotFoundException: weblogic.jndi.WLInitialContextFactory]
     at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:657)
     at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
     at javax.naming.InitialContext.init(InitialContext.java:223)
     at javax.naming.InitialContext.<init>(InitialContext.java:197)
     at fuego.util.InitialContextProvider.create(InitialContextProvider.java:44)
     at fuego.papi.impl.j2ee.J2EEEngineAccessImpl.createInitialContext(J2EEEngineAccessImpl.java:492)
     at fuego.papi.impl.j2ee.J2EEEngineAccessImpl.getInitialContext(J2EEEngineAccessImpl.java:293)
     at fuego.papi.impl.j2ee.J2EEEngineAccessImpl.getEngineHome(J2EEEngineAccessImpl.java:277)
     at fuego.papi.impl.j2ee.J2EEEngineAccessImpl.getSecureEngineInterface(J2EEEngineAccessImpl.java:333)
     at fuego.papi.impl.j2ee.J2EEEngineAccessImpl.createSecureEngine(J2EEEngineAccessImpl.java:178)
     ... 14 more
Caused by: java.lang.ClassNotFoundException: weblogic.jndi.WLInitialContextFactory
     at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
     at java.security.AccessController.doPrivileged(Native Method)
     at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
     at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
     at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:276)
     at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
     at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)
     at java.lang.Class.forName0(Native Method)
     at java.lang.Class.forName(Class.java:247)
     at com.sun.naming.internal.VersionHelper12.loadClass(VersionHelper12.java:46)
     at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:654)
     ... 23 more
The connectivity to the JMS Topic for the server synchronization information has been temporarily interrupted.
Details:
The connectivity to the JMS Topic has been broken due to a JNDI Context initialization problem.
Details:
javax.naming.NoInitialContextException: Cannot instantiate class: weblogic.jndi.WLInitialContextFactory [Root exception is java.lang.ClassNotFoundException: weblogic.jndi.WLInitialContextFactory]
Caused by: Cannot instantiate class: weblogic.jndi.WLInitialContextFactory
Caused by: weblogic.jndi.WLInitialContextFactory
fuego.papi.impl.j2ee.JMSTopicLookUpException: The connectivity to the JMS Topic has been broken due to a JNDI Context initialization problem.
Details:
javax.naming.NoInitialContextException: Cannot instantiate class: weblogic.jndi.WLInitialContextFactory [Root exception is java.lang.ClassNotFoundException: weblogic.jndi.WLInitialContextFactory]
     at fuego.papi.impl.j2ee.J2EEEngineAccessImpl$TopicSubscriberImpl.lookupTopic(J2EEEngineAccessImpl.java:665)
     at fuego.papi.impl.j2ee.J2EEEngineAccessImpl$TopicSubscriberImpl.run(J2EEEngineAccessImpl.java:574)
Caused by: javax.naming.NoInitialContextException: Cannot instantiate class: weblogic.jndi.WLInitialContextFactory [Root exception is java.lang.ClassNotFoundException: weblogic.jndi.WLInitialContextFactory]
     at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:657)
     at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
     at javax.naming.InitialContext.init(InitialContext.java:223)
     at javax.naming.InitialContext.<init>(InitialContext.java:197)
     at fuego.util.InitialContextProvider.create(InitialContextProvider.java:44)
     at fuego.papi.impl.j2ee.J2EEEngineAccessImpl.createInitialContext(J2EEEngineAccessImpl.java:492)
     at fuego.papi.impl.j2ee.J2EEEngineAccessImpl.access$1000(J2EEEngineAccessImpl.java:68)
     at fuego.papi.impl.j2ee.J2EEEngineAccessImpl$TopicSubscriberImpl.lookupTopic(J2EEEngineAccessImpl.java:660)
     ... 1 more
Caused by: java.lang.ClassNotFoundException: weblogic.jndi.WLInitialContextFactory
     at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
     at java.security.AccessController.doPrivileged(Native Method)
     at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
     at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
     at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:276)
     at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
     at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)
     at java.lang.Class.forName0(Native Method)
     at java.lang.Class.forName(Class.java:247)
     at com.sun.naming.internal.VersionHelper12.loadClass(VersionHelper12.java:46)
     at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:654)
     ... 8 more
Process exited.

Answer 1

Could this be a CLASSPATH issue?
Caused by: java.lang.ClassNotFoundException: weblogic.jndi.WLInitialContextFactory
at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
at java.security.AccessController.doPrivileged(Native Method)