Fuego Papi Client

I have some problems when I used fuegopapi-client.jar, when I use this library in BPM Studio run without errors and retrieve all instance from
a process that I choose in the presentation, but when I run in BPM enterprise throw an exception the process name_process#default1.0 don't exists but the
process exists. Please help with this problems.
//this code retrieve all processId of the process in the BPM proyect(this code run without errors)
Properties configuration = Properties();
configuration.setProperty(ModComponentes.Fuego2.Papi.ProcessService.DIRECTORY_ID, "default");
configuration.setProperty(ModComponentes.Fuego2.Papi.ProcessService.DIRECTORY_PROPERTIES_FILE, "directory.xml");
ModComponentes.Fuego2.Papi.ProcessService procesoService = ModComponentes.Fuego2.Papi.ProcessService.create(configuration);
ModComponentes.Fuego2.Papi.ProcessServiceSession procesoServiceSession =
                                        procesoService.createSession(this.sfcParticipant.name, "123456", null);
ModComponentes.Fuego2.Papi.Process[] ext = (ModComponentes.Fuego2.Papi.Process[])procesoServiceSession.processesGet(false);
foreach(item in ext){     
     this.sfcEstadoCredito.sProcesos[item.id] = item.name;
     this.sfcEstadoCredito.sProcesoId = item.id;                    
procesoServiceSession.close();
procesoService.close();
//this code retrieve all instance from a process( only run in studio but when i run in enterprise throw an exception)
Properties configuration = Properties();
configuration.setProperty(ModComponentes.Fuego2.Papi.ProcessService.DIRECTORY_ID, "default");
//Oracle BPM Studio
//configuration.setProperty(ModComponentes.Fuego2.Papi.ProcessService.PROJECT_PATH, "D://Final//Proyecto");
// Oracle BPM Enterprise
configuration.setProperty(ModComponentes.Fuego2.Papi.ProcessService.DIRECTORY_PROPERTIES_FILE, "directory.xml");
ModComponentes.Fuego2.Papi.ProcessService procesoService = ModComponentes.Fuego2.Papi.ProcessService.create(configuration);
//Oracle BPM Studio
// ModComponentes.Fuego2.Papi.ProcessServiceSession procesoServiceSession = procesoService.createSession(Fuego.Lib.Participant.name, Fuego.Lib.Participant.name, null);
//Oracle BPM Enterprise
ModComponentes.Fuego2.Papi.ProcessServiceSession procesoServiceSession =
                                             procesoService.createSession(Fuego.Lib.Participant.name, "123456", null);
ModComponentes.Fuego2.Papi.Filter filtro = procesoService.createFilter();
filtro.searchScope.participantScope = ModComponentes.ParticipantScope.ALL;
filtro.searchScope.statusScope = ModComponentes.StatusScope.ALL;
filtro.addAttribute(ModComponentes.Fuego.Papi.VarDefinition.getDefaultVarDefinition(ModComponentes.Fuego.Papi.VarDefinition.CREATION_TIME_ID),
     ModComponentes.Comparison.GREATER_OR_EQUALS, this.sfcEstadoCredito.dFechaInicio);
filtro.addAttribute(ModComponentes.Fuego.Papi.VarDefinition.getDefaultVarDefinition(ModComponentes.Fuego.Papi.VarDefinition.CREATION_TIME_ID),
     ModComponentes.Comparison.LESS_OR_EQUALS, this.sfcEstadoCredito.dFechaFin);
filtro.matchAll = true;
ModComponentes.Fuego2.Papi.InstanceInfo[] instanciaByFilter;
instanciaByFilter = ((ModComponentes.Fuego2.Papi.InstanceInfo[])
                         procesoServiceSession.processesGetInstancesByFilter(ProcessIdSet.create.add(this.sfsProcessId), filtro));
procesoServiceSession.close();
procesoService.close();
//**********************************************************************//

Hi,
Please incorporate the following code, hope this help you.
Properties configuration = new Properties();
configuration.setProperty(ProcessService.DIRECTORY_ID, "default");
// Change the path of the directory.xml file accordindly
configuration.setProperty(ProcessService.DIRECTORY_PROPERTIES_FILE, "c://bea//albpm6.0//enterprise//conf//directory.xml");
configuration.setProperty(ProcessService.WORKING_FOLDER, "/tmp");
Bibhu

Similar Messages

  • PAPI Client program is not working

    Hi,
    i'm running a sample bpm project in albpm studio 5.7
    and tried to get the instance details thru PAPI client, but im getting following exception.
    pls help me.
    Code:*
    package papi.example;
    import java.io.Serializable;
    import java.util.Properties;
    import fuego.papi.CommunicationException;
    import fuego.papi.InstanceInfo;
    import fuego.papi.OperationException;
    import fuego.papi.ProcessService;
    import fuego.papi.ProcessServiceSession;
    public class PapiExample implements Serializable {
         private static final long serialVersionUID = 6828488904644822028L;
         public static void main(String[] args) throws Exception {
              Properties configuration = new Properties();
              configuration.setProperty(ProcessService.DIRECTORY_ID, "default");
              configuration
                        .setProperty(ProcessService.PROJECT_PATH,
                                  "C:/Documents and Settings/458232/bpmProjects/ExpenseManagement.fpr");
              configuration
                        .setProperty(ProcessService.WORKING_FOLDER,
                                  "/tmp");
              try {
                   ProcessService processService = ProcessService
                             .create(configuration);
                   ProcessServiceSession session = processService.createSession(
                             "Peter Jones", "", "localhost");
                   for (String processId : session.processesGetIds()) {
                        System.out.println("\n Process: " + processId);
                        for (InstanceInfo instance : session
                                  .processGetInstances(processId)) {
                             System.out.println(" -> " + instance.getId());
                   session.close();
                   processService.close();
              } catch (CommunicationException e) {
                   System.out.println("Could not connect to Directory Service");
                   e.printStackTrace();
              } catch (OperationException e) {
                   System.out.println("Could not perform the requested operation");
                   e.printStackTrace();
    Exception*:
    Local folder /tmp\system\Schema3387192-1626570987\catalogs found.
    Loading catalogs from local folder: /tmp\system\Schema3387192-1626570987\catalogs
    0 jars found locally.
    [CatalogMgrCache] =======================
    Registering CatalogMgr [ExpenseManagement.fpr] ...CatalogManagerCache 25934938:
    Managers:
    Counters:
    [CatalogMgrCache] =======================
    CatalogMgr [ExpenseManagement.fpr] REGISTERED!CatalogManagerCache 25934938:
    Managers:
    {ExpenseManagement.fpr=fuego.util.LocalCatalogManager@facf0b}
    Counters:
    Could not enhance type with bytecode info: java.lang.NoClassDefFoundError: org/apache/bcel/classfile/EmptyVisitor
    Could not enhance type with bytecode info: java.lang.NoClassDefFoundError: org/apache/bcel/classfile/EmptyVisitor
    Could not enhance type with bytecode info: java.lang.NoClassDefFoundError: org/apache/bcel/classfile/EmptyVisitor
    Could not enhance type with bytecode info: java.lang.NoClassDefFoundError: org/apache/bcel/classfile/EmptyVisitor
    Could not enhance type with bytecode info: java.lang.NoClassDefFoundError: org/apache/bcel/classfile/EmptyVisitor
    Could not enhance type with bytecode info: java.lang.NoClassDefFoundError: org/apache/bcel/classfile/EmptyVisitor
    Could not enhance type with bytecode info: java.lang.NoClassDefFoundError: org/apache/bcel/classfile/EmptyVisitor
    Could not enhance type with bytecode info: java.lang.NoClassDefFoundError: org/apache/bcel/classfile/EmptyVisitor
    Could not enhance type with bytecode info: java.lang.NoClassDefFoundError: org/apache/bcel/classfile/EmptyVisitor
    Could not enhance type with bytecode info: java.lang.NoClassDefFoundError: org/apache/bcel/classfile/EmptyVisitor
    Could not enhance type with bytecode info: java.lang.NoClassDefFoundError: org/apache/bcel/classfile/EmptyVisitor
    Could not enhance type with bytecode info: java.lang.NoClassDefFoundError: org/apache/bcel/classfile/EmptyVisitor
    Could not enhance type with bytecode info: java.lang.NoClassDefFoundError: org/apache/bcel/classfile/EmptyVisitor
    Could not enhance type with bytecode info: java.lang.NoClassDefFoundError: org/apache/bcel/classfile/EmptyVisitor
    Could not enhance type with bytecode info: java.lang.NoClassDefFoundError: org/apache/bcel/classfile/EmptyVisitor
    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.
    The connection to 'tcp://01HW316455:8586' was refused. Details:
    tcp://01HW316455:8586. Details: java.io.EOFException)
    Caused by: An exception occurred while attempting to connect to: tcp://01HW316455:8586
    Caused by: java.io.EOFException
    fuego.papi.impl.rmi.EngineLocationStatus$EngineCrashedException: tcp://01HW316455:8586. Details: java.io.EOFException)
         at fuego.papi.impl.rmi.EngineLocationStatus.get(EngineLocationStatus.java:92)
         at fuego.papi.impl.rmi.RMIUtils.connectToLocation(RMIUtils.java:136)
         at fuego.papi.impl.rmi.RMIUtils.connectToEngine(RMIUtils.java:111)
         at fuego.papi.impl.rmi.RMIEngineAccessImpl.createSecureEngineProxy(RMIEngineAccessImpl.java:153)
         at fuego.papi.impl.rmi.RMIEngineAccessImpl.createSecureEngine(RMIEngineAccessImpl.java:105)
         at fuego.papi.impl.ProcessServiceImpl.createSecureEngine(ProcessServiceImpl.java:1222)
         at fuego.papi.impl.ProcessServiceSessionImpl$2.run(ProcessServiceSessionImpl.java:3641)
         at fuego.papi.impl.ProcessServiceImpl.executeEngineOp(ProcessServiceImpl.java:1858)
         at fuego.papi.impl.ProcessServiceSessionImpl.getSecureEngine(ProcessServiceSessionImpl.java:3649)
         at fuego.papi.impl.ProcessServiceImpl.createProcessControl(ProcessServiceImpl.java:1208)
         at fuego.papi.impl.ProcessServiceSessionImpl$1.run(ProcessServiceSessionImpl.java:2481)
         at fuego.papi.impl.ProcessServiceImpl.executeEngineOp(ProcessServiceImpl.java:1858)
         at fuego.papi.impl.ProcessServiceSessionImpl.getProcessControl(ProcessServiceSessionImpl.java:2486)
         at fuego.papi.impl.ProcessServiceSessionImpl.processGetInstances(ProcessServiceSessionImpl.java:2155)
         at papi.example.PapiExample.main(PapiExample.java:41)
    Caused by: fuego.rmi.spi.ConnectException: An exception occurred while attempting to connect to: tcp://01HW316455:8586
         at fuego.rmi.ClientCluster.initialize(ClientCluster.java:486)
         at fuego.rmi.ClientCluster.<init>(ClientCluster.java:107)
         at fuego.rmi.ClientCluster.find(ClientCluster.java:228)
         at fuego.rmi.RemoteProxy.<init>(RemoteProxy.java:73)
         at fuego.papi.impl.rmi.PublicEngineProxy.<init>(PublicEngineProxy.java:33)
         at fuego.papi.impl.rmi.EngineLocationStatus.createPublicEngine(EngineLocationStatus.java:109)
         at fuego.papi.impl.rmi.EngineLocationStatus.get(EngineLocationStatus.java:44)
         ... 14 more
    Caused by: java.io.EOFException
         at java.io.DataInputStream.readShort(Unknown Source)
         at fuego.rmi.Packet.read(Packet.java:129)
         at fuego.rmi.spi.BaseConnection$Receiver.run(BaseConnection.java:190)
    fuego.papi.ProcessNotAvailableException: Process '/ExpenseReport#Default-1.0' not available.
         at fuego.papi.impl.ProcessServiceImpl.createProcessControl(ProcessServiceImpl.java:1215)
         at fuego.papi.impl.ProcessServiceSessionImpl$1.run(ProcessServiceSessionImpl.java:2481)
         at fuego.papi.impl.ProcessServiceImpl.executeEngineOp(ProcessServiceImpl.java:1858)
         at fuego.papi.impl.ProcessServiceSessionImpl.getProcessControl(ProcessServiceSessionImpl.java:2486)
         at fuego.papi.impl.ProcessServiceSessionImpl.processGetInstances(ProcessServiceSessionImpl.java:2155)
         at papi.example.PapiExample.main(PapiExample.java:41)
    Caused by: fuego.papi.impl.EngineNotAvailableException: Engine 'ExpenseManagement.fpr' cannot process requests.
         at fuego.papi.impl.rmi.RMIUtils.connectToEngine(RMIUtils.java:119)
         at fuego.papi.impl.rmi.RMIEngineAccessImpl.createSecureEngineProxy(RMIEngineAccessImpl.java:153)
         at fuego.papi.impl.rmi.RMIEngineAccessImpl.createSecureEngine(RMIEngineAccessImpl.java:105)
         at fuego.papi.impl.ProcessServiceImpl.createSecureEngine(ProcessServiceImpl.java:1222)
         at fuego.papi.impl.ProcessServiceSessionImpl$2.run(ProcessServiceSessionImpl.java:3641)
         at fuego.papi.impl.ProcessServiceImpl.executeEngineOp(ProcessServiceImpl.java:1858)
         at fuego.papi.impl.ProcessServiceSessionImpl.getSecureEngine(ProcessServiceSessionImpl.java:3649)
         at fuego.papi.impl.ProcessServiceImpl.createProcessControl(ProcessServiceImpl.java:1208)
         ... 5 more
    Could not perform the requested operation

    I think problem is with your working folder.
    configuration.setProperty(ProcessService.WORKING_FOLDER,"/tmp");
    set it to where exactly your application folder path.

  • PAPI client is running outside a j2ee container

    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.

    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)

  • OBPM : fuego.papi.exception.NoPermissionException

    Scenario:
    2.     Logged in as A
    3.     Create a new Instance (X) -
    4.     Logged out as Sales Agent.
    5.     Logged in as Another user B to whom OBPM assigned automatically.
    6.     Selected X in B's worklist.
    7.     Assigned back to A.
    8.     Technical Info: fuego.papi.exception.NoPermissionException
    10.     Stacktrace:
    ERROR [[ACTIVE] ExecuteThread: '7' for queue: 'weblogic.kernel.Default (self-tuning)'] webservice.impl.CreditAssessmentTaskMgmtServiceImpl - OperationException while prepareActivityInstance : ReviewCreditAssessmentRequest , /SDSE/CRDACreditAssessmentApplicationProcess#Default-1.0/5847/0
    com.bea.albpm.papiwebservice.OperationException: Instance '/SDSE/CRDACreditAssessmentApplicationProcess#Default-1.0/5847/0', in activity '/SDSE/CRDACreditAssessmentApplicationProcess#Default-1.0/Interactive[ReviewCreditAssessmentRequest]' is assigned to participant 'ELMER', or he/she is executing it. It may be that your execution of '/SDSE/CRDACreditAssessmentApplicationProcess#Default-1.0/Interactive[ReviewCreditAssessmentRequest]' expired. Check with your administrator for more details if this is not the case.
    at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
    2010-10-12 18:48:54,267 DEBUG [[ACTIVE] ExecuteThread: '7' for queue: 'weblogic.kernel.Default (self-tuning)'] jdbc.datasou
    rce.DataSourceUtils - Returning JDBC Connection to DataSource
    2010-10-12 18:48:54,267 DEBUG [[ACTIVE] ExecuteThread: '7' for queue: 'weblogic.kernel.Default (self-tuning)'] transaction.
    jta.WebLogicJtaTransactionManager - Initiating transaction rollback
    2010-10-12 18:48:54,302 DEBUG [[ACTIVE] ExecuteThread: '7' for queue: 'weblogic.kernel.Default (self-tuning)'] webservice.service.CreditAssessmentServiceSOAPHandler - SOAP Fault Message: <S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/"><S:Header/><S:Body><ns2:Fault xmlns:ns2="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns3="http://www.w3.org/2003/05/soap-envelope"><faultcode>ns2:Server</faultcode><faultstring>OperationException kicking Off Work flow Instance for credit Assessment Request Id : 2152</faultstring><detail><ns4:PolicyException xmlns:ns2="http://xmlschema.tmi.telus.com/xsd/Customer/Customer/CreditAssessmentRequestTypes_v1" xmlns:ns3="http://xmlschema.tmi.telus.com/xsd/Enterprise/BaseTypes/types/ping_v1" xmlns:ns4="http://xmlschema.tmi.telus.com/xsd/common/exceptions/Exceptions_v1_0" xmlns:ns5="http://xmlschema.tmi.telus.com/srv/CMO/OrderMgmt/CreditAssessmentServiceRequestResponse_v1"><ns4:messageId>fuego.papi.exception.NoPermissionException</ns4:messageId>
    <ns4:errorCode>CreditAssessmentSvcExceptionCodes.OBPM_EXCEPTION</ns4:errorCode>
    <ns4:errorMessage>fuego.papi.exception.NoPermissionException Technical Info: Instance '/SDSE/CRDACreditAssessmentApplicationProcess#Default-1.0/5847/0', in activity
    '/SDSE/CRDACreditAssessmentApplicationProcess#Default-1.0/Interactive[ReviewCreditAssessmentRequest]' iis assigned to participant 'ELMER', or he/she is executing it.
    It may be that your execution of '/SDSE/CRDACreditAssessmentApplicationProcess#Default-1.0/Interactive[ReviewCreditAssessmentRequest]' expired. Check with your administrator for more details if this is not the case.
    Technical Info: fuego.papi.exception.NoPermissionException: Instance '/SDSE/CRDACreditAssessmentApplicationProcess#Default-1.0/5847/0', in activity
    '/SDSE/CRDACreditAssessmentApplicationProcess#Default-1.0/Interactive[ReviewCreditAssessmentRequest]' is assigned to participant 'ELMER', or he/she is executing it.
    It may be that your execution of '/SDSE/CRDACreditAssessmentApplicationProcess#Default-1.0/Interactive[ReviewCreditAssessmentRequest]' expired. Check with your administrator for more details if this is not the case.
    at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:205)
    at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:345)
    at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:259)
    at fuego.ejbengine.EJBProcessControl_1zamnl_EOImpl_1030_WLStub.runTask(Unknown Source)
    at fuego.papi.impl.j2ee.EJBProcessControlInterfaceWrapper.runTask(EJBProcessControlInterfaceWrapper.java:2201)
    at sun.reflect.GeneratedMethodAccessor1052.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at fuego.papi.impl.AbstractProcessControlHandler.invokeInternal(AbstractProcessControlHandler.java:72)
    at fuego.papi.impl.j2ee.EJBProcessControlHandler.doInvoke(EJBProcessControlHandler.java:116)
    at fuego.papi.impl.j2ee.EJBProcessControlHandler.invoke(EJBProcessControlHandler.java:70)
    What could be the reason for it?
    I got this info from website
    http://download.oracle.com/docs/cd/E13154_01/bpm/docs65/papi_javadocs/fuego/papi/exception/NoPermissionException.html#ACTIVITY_NOT_ABORTABLE
    is that possible to catch this exception and display to user what is the reason and code ?
    like SELECTED_BY_OTHER ,LIMIT_RUN_INSTANCES ,etc.. I would like to show the code to the user.

    X is a new instance created by A and assigned to ELMER(B).
    This instance is never created and associated before.
    When B(Elmer) tries to assign back to A.It thorws error.This happends when I call prepareActivityInstance : m_papiWebService.activityPrepare( activityPrepare );
    Then why should I unassign ?
    how we find out that instance is assigned to somebody?
    how we unassign that instance?
    This happends when I call prepareActivityInstance : m_papiWebService.activityPrepare( activityPrepare );
    impl.CreditAssessmentTaskMgmtServiceImpl - Enter prepareActivityInstance
    2010-10-14 18:29:05,052 DEBUG [[ACTIVE] ExecuteThread: '10' for queue: 'weblogic.kernel.Default (self-tuning)'] webservice.impl.CreditAssessmentTaskMgmtServiceImpl - Enter prepareActivityInstance
    2010-10-14 18:29:05,052 DEBUG [[ACTIVE] ExecuteThread: '10' for queue: 'weblogic.kernel.Default (self-tuning)'] webservice.impl.CreditAssessmentTaskMgmtServiceImpl - Calling papiWebService: activityPrepare....ReviewCreditAssessmentRequest && /SDSE/CRDACreditAssessmentApplicationProcess#Default-1.0/5855/0
    2010-10-14 18:29:05,052 DEBUG [[ACTIVE] ExecuteThread: '10' for queue: 'weblogic.kernel.Default (self-tuning)'] webservice.impl.CreditAssessmentTaskMgmtServiceImpl - Calling papiWebService: activityPrepare....ReviewCreditAssessmentRequest && /SDSE/CRDACreditAssessmentApplicationProcess#Default-1.0/5855/0
    2010-10-14 18:29:05,054 DEBUG [[ACTIVE] ExecuteThread: '10' for queue: 'weblogic.kernel.Default (self-tuning)'] impl.papi.PAPIWebServiceSOAPHandler - enter PAPIWebServiceSOAPHandler.handleRequest
    2010-10-14 18:29:05,054 DEBUG [[ACTIVE] ExecuteThread: '10' for queue: 'weblogic.kernel.Default (self-tuning)'] impl.papi.PAPIWebServiceSOAPHandler - enter PAPIWebServiceSOAPHandler.handleRequest
    2010-10-14 18:29:05,054 DEBUG [[ACTIVE] ExecuteThread: '10' for queue: 'weblogic.kernel.Default (self-tuning)'] framework.ws.RpcClientHandler - handleRequest(): class com.telus.credit.taskmgmt.webservice.impl.papi.PAPIWebServiceSOAPHandler
    2010-10-14 18:29:05,054 DEBUG [[ACTIVE] ExecuteThread: '10' for queue: 'weblogic.kernel.Default (self-tuning)'] framework.ws.RpcClientHandler - handleRequest(): class com.telus.credit.taskmgmt.webservice.impl.papi.PAPIWebServiceSOAPHandler
    2010-10-14 18:29:05,054 DEBUG [[ACTIVE] ExecuteThread: '10' for queue: 'weblogic.kernel.Default (self-tuning)'] impl.papi.PAPIWebServiceSOAPHandler - PAPIWebServiceSOAPHandler.soapHeadersToAttach
    2010-10-14 18:29:05,054 DEBUG [[ACTIVE] ExecuteThread: '10' for queue: 'weblogic.kernel.Default (self-tuning)'] impl.papi.PAPIWebServiceSOAPHandler - PAPIWebServiceSOAPHandler.soapHeadersToAttach
    2010-10-14 18:29:05,054 DEBUG [[ACTIVE] ExecuteThread: '10' for queue: 'weblogic.kernel.Default (self-tuning)'] impl.papi.PAPIWebServiceSOAPHandler - Exit PAPIWebServiceSOAPHandler.handleRequest
    2010-10-14 18:29:05,054 DEBUG [[ACTIVE] ExecuteThread: '10' for queue: 'weblogic.kernel.Default (self-tuning)'] impl.papi.PAPIWebServiceSOAPHandler - Exit PAPIWebServiceSOAPHandler.handleRequest
    2010-10-14 18:29:06,633 ERROR [[ACTIVE] ExecuteThread: '10' for queue: 'weblogic.kernel.Default (self-tuning)'] webservice.impl.CreditAssessmentTaskMgmtServiceImpl - OperationException while prepareActivityInstance : ReviewCreditAssessmentRequest , /SDSE/CRDACreditAssessmentApplicationProcess#Default-1.0/5855/0
    com.bea.albpm.papiwebservice.OperationException: Instance '/SDSE/CRDACreditAssessmentApplicationProcess#Default-1.0/5855/0', in activity '/SDSE/CRDACreditAssessmentApplicationProcess#Default-1.0/Interactive[ReviewCreditAssessmentRequest]' is assigned to participant 'ELMER', or he/she is executing it. It may be that your execution of '/SDSE/CRDACreditAssessmentApplicationProcess#Default-1.0/Interactive[ReviewCreditAssessmentRequest]' expired. Check with your administrator for more details if this is not the case.
    at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
    at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
    at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
    at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
    at com.bea.staxb.runtime.internal.util.ReflectionUtils.invokeConstructor(ReflectionUtils.java:66)
    at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
    at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
    at com.bea.staxb.runtime.internal.util.ReflectionUtils.invokeConstructor(ReflectionUtils.java:66)
    at com.bea.staxb.runtime.internal.CtorArgsMultiIntermediary.constructFinalValue(CtorArgsMultiIntermediary.java:81)
    at com.bea.staxb.runtime.internal.CtorArgsMultiIntermediary.getFinalValue(CtorArgsMultiIntermediary.java:60)
    at com.bea.staxb.runtime.internal.AttributeRuntimeBindingType.getFinalObjectFromIntermediary(AttributeRuntimeBindingType.java:140)
    at com.bea.staxb.runtime.internal.AttributeUnmarshaller.unmarshal(AttributeUnmarshaller.java:39)
    at com.bea.staxb.runtime.internal.UnmarshalResult.unmarshalBindingType(UnmarshalResult.java:189)
    at com.bea.staxb.runtime.internal.UnmarshalResult.unmarshalType(UnmarshalResult.java:227)
    at com.bea.staxb.runtime.internal.UnmarshalResult.unmarshalElement(UnmarshalResult.java:242)
    at com.bea.staxb.runtime.internal.UnmarshallerImpl.unmarshalElement(UnmarshallerImpl.java:166)
    at weblogic.wsee.bind.runtime.internal.LiteralDeserializerContext.unmarshalElement(LiteralDeserializerContext.java:89)
    at weblogic.wsee.bind.runtime.internal.BaseDeserializerContext.internalDeserializeElement(BaseDeserializerContext.java:182)
    at weblogic.wsee.bind.runtime.internal.BaseDeserializerContext.deserializeElement(BaseDeserializerContext.java:117)
    at weblogic.wsee.codec.soap11.SoapCodec.createExceptionFromFault(SoapCodec.java:624)
    at weblogic.wsee.codec.soap11.SoapCodec.decodeFault(SoapCodec.java:306)
    at weblogic.wsee.ws.dispatch.client.CodecHandler.decodeFault(CodecHandler.java:118)
    at weblogic.wsee.ws.dispatch.client.CodecHandler.decode(CodecHandler.java:103)
    at weblogic.wsee.ws.dispatch.client.CodecHandler.handleFault(CodecHandler.java:91)
    at weblogic.wsee.handler.HandlerIterator.handleFault(HandlerIterator.java:309)
    at weblogic.wsee.handler.HandlerIterator.handleResponse(HandlerIterator.java:269)
    at weblogic.wsee.ws.dispatch.client.ClientDispatcher.handleResponse(ClientDispatcher.java:213)
    at weblogic.wsee.ws.dispatch.client.ClientDispatcher.dispatch(ClientDispatcher.java:150)
    at weblogic.wsee.ws.WsStub.invoke(WsStub.java:87)
    at weblogic.wsee.jaxrpc.StubImpl._invoke(StubImpl.java:339)
    at weblogic.wsee.jaxrpc.StubImpl.invoke(StubImpl.java:257)
    at $Proxy319.activityPrepare(Unknown Source)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at org.springframework.remoting.rmi.RmiClientInterceptorUtils.invokeRemoteMethod(RmiClientInterceptorUtils.java:108)
    at org.springframework.remoting.jaxrpc.JaxRpcPortClientInterceptor.doInvoke(JaxRpcPortClientInterceptor.java:617)
    at org.springframework.remoting.jaxrpc.JaxRpcPortClientInterceptor.doInvoke(JaxRpcPortClientInterceptor.java:584)
    at org.springframework.remoting.jaxrpc.JaxRpcPortClientInterceptor.invoke(JaxRpcPortClientInterceptor.java:562)
    at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
    at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
    at $Proxy135.activityPrepare(Unknown Source)
    at com.telus.credit.taskmgmt.webservice.impl.CreditAssessmentTaskMgmtServiceImpl.prepareActivityInstance(CreditAssessmentTaskMgmtServiceImpl.java:655)
    at com.telus.credit.assessment.service.activityactions.WorkflowDrivenAction.prepareActivity(WorkflowDrivenAction.java:132)
    at com.telus.credit.assessment.service.activityactions.WorkflowDrivenAction.executeAction(WorkflowDrivenAction.java:104)
    at com.telus.credit.assessment.webservice.impl.CreditAssessmentServiceImpl.performCreditAssessmentRequestActivities(CreditAssessmentServiceImpl.java:676)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:307)
    at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182)
    at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149)
    at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:106)
    at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
    at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
    at $Proxy280.performCreditAssessmentRequestActivities(Unknown Source)
    at com.telus.credit.assessment.webservice.service.CreditAssessmentServicePortImpl.performCreditAssessmentRequestActivities(CreditAssessmentServicePortImpl.java:138)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at weblogic.wsee.jaxws.WLSInstanceResolver$WLSInvoker.invoke(WLSInstanceResolver.java:92)
    at weblogic.wsee.jaxws.WLSInstanceResolver$WLSInvoker.invoke(WLSInstanceResolver.java:74)
    at com.sun.xml.ws.server.InvokerTube$2.invoke(InvokerTube.java:151)
    at com.sun.xml.ws.server.sei.EndpointMethodHandlerImpl.invoke(EndpointMethodHandlerImpl.java:265)
    at com.sun.xml.ws.server.sei.SEIInvokerTube.processRequest(SEIInvokerTube.java:100)
    at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:604)
    at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:563)
    at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:548)
    at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:445)
    at com.sun.xml.ws.server.WSEndpointImpl$2.process(WSEndpointImpl.java:373)
    at com.sun.xml.ws.transport.http.HttpAdapter$HttpToolkit.handle(HttpAdapter.java:524)
    at com.sun.xml.ws.transport.http.HttpAdapter.handle(HttpAdapter.java:255)
    at com.sun.xml.ws.transport.http.servlet.ServletAdapter.handle(ServletAdapter.java:140)
    at weblogic.wsee.jaxws.WLSServletAdapter.handle(WLSServletAdapter.java:208)
    at weblogic.wsee.jaxws.HttpServletAdapter$AuthorizedInvoke.run(HttpServletAdapter.java:310)
    at weblogic.wsee.jaxws.HttpServletAdapter.post(HttpServletAdapter.java:223)
    at weblogic.wsee.jaxws.JAXWSServlet.doPost(JAXWSServlet.java:124)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)

  • Java papi client 57 UserTransaction lookup fails

    Guys,
    I am trying to write PAPI client which is to run from Tomcat and connecting to ALBPM 5.7 Enterprise which is on Weblogic 92.
    I am able to do all operations how ever do see exceptions when PAPI tries to connect to News Topic.
    Please let me know if some one has seen this problem in ALBPM5.7 and how it was resolved. I think fix may be in directory.properties by adding/removing some properties but dont know what.
    Following is the error message
    An error occurred when subscribing to the JMS Topic engine. Reason:'While trying to lookup 'java:comp.UserTransaction' didn't find subcontext 'java:comp'. Resolved ''
    Caused by: While trying to lookup 'java:comp.UserTransaction' didn't find subcontext 'java:comp'. Resolved ''
    When I checked in directory database, I see following XML in FUEGO_CONFIG table
    <?xml version="1.0" encoding="UTF-8"?>
    <?fuego version="5.7 GA SP3" application="albpmenteprisej2ee"?>
    <set>
         <configuration name="myengine_ENGINE_DB_FUEGOLABS_ARG" type="SQL" subtype="ORACLE">
              <property name="jdbc.pool.idle_timeout" value="5"/>
              <property name="oracle.driver_type" value="thin"/>
              <property name="oracle.dateEqualsTimestamp" value="false"/>
              <property name="jdbc.schema" value="myengine"/>
              <property name="jdbc.host" value="localhost"/>
              <property name="user" value="myengine"/>
              <property name="jdbc.port" value="1521"/>
              <property name="jdbc.pool.min" value="0"/>
              <property name="jdbc.pool.maxopencursors" value="50"/>
              <property name="oracle.sid" value="xe"/>
              <property name="password" value="&lt;encrypted&gt;gGocbn15UL8="/>
              <property name="jdbc.xa" value="false"/>
              <property name="jdbc.pool.max" value="10"/>
         </configuration>
         <configuration name="*myengine_J2EE_LOCAL_FUEGOLABS_ARG*" type="*J2EE*" subtype="*LOCAL_J2EE*">
              <property name="*javax.user.UserTransaction*" value="*java:comp/UserTransaction*"/>
         </configuration>
         <configuration name="myengine_J2EE_RUNTIME_FUEGOLABS_ARG" type="SQL" subtype="REMOTE_JDBC">
              <property name="lookupName" value="XAmyengineDS"/>
              <property name="jdbc.remote.type" value="ORACLE"/>
              <property name="j2ee.provider" value="myengine_J2EE_LOCAL_FUEGOLABS_ARG"/>
         </configuration>
         <configuration name="myengine_J2EE_FDI_FUEGOLABS_ARG" type="SQL" subtype="REMOTE_JDBC">
              <property name="lookupName" value="XAFDIDS"/>
              <property name="jdbc.remote.type" value="ORACLE"/>
              <property name="j2ee.provider" value="myengine_J2EE_LOCAL_FUEGOLABS_ARG"/>
         </configuration>
    </set>
    Following is my directory.properties (I have tweaked a bit to make it work)
    # Directory configuration
    # The following properties define the configuration for a directory provider.
    # Do not modify the prefix of the properties. Always leave "directory.default."
    directory.default.url=oracle://localhost:1521/schema=BEA_FDI,sid=XE
    #directory.default.provider=oracle
    #directory.default.connector-subtype=ORACLE
    #directory.default.directory-res-ref-name=myengine_J2EE_FDI_FUEGOLABS_ARG
    # preset properties.
    directory.default.preset.datawarehouse.participant=administrator
    directory.default.preset.engine.participant=administrator
    directory.default.preset.portal-anonymous.participant_password=<crypted>UA7jo3Pvnu12sc/NMcxJ3ijnJHzgtte9YqKhr3hkgQJeZK2sN9b9waFaN6N8S/fMtkcMRWpbMrUVCeXN8zvx7OLaGtCTBQ==
    directory.default.preset.xobjects.participant=administrator
    directory.default.preset.datawarehouse.participant_password=<crypted>UA7jo3Pvnu12sc/NMcxJ3ijnJHzgtte9Yp/TapxzhLBvmq3JAXqZ/pOgfmVZxXpleLmdse9pFPjhFG4SH4/hmKPhJg==
    directory.default.preset.xobjects.participant_password=<crypted>UA7jo3Pvnu12sc/NMcxJ3ijnJHzgtte9YrahnQoZYB8e7NkVzsFfeKe9qrv/oXpltEQYTDSxMrUVCeXN8zs=
    directory.default.preset.engine.participant_password=<crypted>UA7jo3Pvnu12sc/NMcxJ3ijnJHzgtte9YmixG3O3OYx0FW4CpqZf/pP8fnS8vEpQ6fpD8kG9FNGrZQhP
    directory.default.preset.portal-anonymous.participant=administrator
    # custom properties.
    # fuego properties.
    directory.default.jdbc-user=BEA_FDI
    directory.default.jdbc-password=password
    #directory.default.skip-auth=true
    If you see I have commented following properties above which is basically referring to elements in XML which I have pasted above.
    #directory.default.provider=oracle
    #directory.default.connector-subtype=ORACLE
    #directory.default.directory-res-ref-name=myengine_J2EE_FDI_FUEGOLABS_ARG
    Similarly there is UserTransaction entry in FUEGO_CONFIG table xml as highlighted in bold.
    Is there any fix/tweak in directory.properties which will resolve my problem?
    Thanks in advance for helping.
    Anil
    Edited by: Anil Hemnani on 22-Apr-2010 23:30
    Edited by: Anil Hemnani on 22-Apr-2010 23:30
    Edited by: Anil Hemnani on 22-Apr-2010 23:31

    Dear fellow forum members,
    For future reference:
    After a very very long time we received advise from SAP to perform actions we already suggested.....
    We have ´hacked´ the keydb.xml file. We must say that SAP gave good detailed advise on which entries to change:
    1#. Log on to ABAP and check what password was set for user "ADS_AGENT"
    2#. Go to:
    /tmp/sapinst_instdir/NW04S/LM/AS-JAVA/ADDIN/ADA/CENTRAL/CI/
    1. Save a backup of "keydb.xml" first.
    2. Find the following lines at the keydb.xml:
    This solved the problem for our customer, so this question can be marked as answered by Casper (my colleague). We hope that SAP will launch a patch to solve this problem, as it has cost us a lot of time and we can imagine that other consultants are facing the same issues, as this seems to be a hashing mechanism that does not perform/work correctly.
    Best regards,
    Jan Laros

  • PAPI client calls - stuck threads with albpm57 engine

    PAPI client running on weblogic portal 10.3, connecting to ALBPM 5.7 engine (on weblogic 8.1 cluster).
    threads get stuck in WLP servers (where PAPI client runs), and the call is for getActiveInstances from default view. We have around 15000 active instances, and the papi cache size is configured for 25000.
    "[STUCK] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'" id=17 idx=0x7c tid=6615 prio=1 alive, in native, waiting, daemon
    -- Waiting for notification on: fuego/papi/impl/lock/SimpleLock@0x1f443568[fat lock]
    at jrockit/vm/Threads.waitForNotifySignal(JLjava/lang/Object;)Z(Native Method)
    at java/lang/Object.wait(J)V(Native Method)[optimized]
    at java/lang/Object.wait(Object.java:485)
    at fuego/papi/impl/lock/SimpleLock.readLock(SimpleLock.java:50)
    ^-- Lock released while waiting: fuego/papi/impl/lock/SimpleLock@0x1f443568[fat lock]
    at fuego/papi/impl/InstanceCache$Entry.readLock(InstanceCache.java:708)
    at fuego/papi/impl/InstanceCache.getInstancesByFilter(InstanceCache.java:505)
    at fuego/papi/impl/InstanceCache.getInstancesByFilter(InstanceCache.java:231)
    at fuego/papi/impl/ProcessServiceImpl.getInstancesByFilter(ProcessServiceImpl.java:1084)
    at fuego/papi/impl/ProcessServiceNESessionImpl.getInstancesByFilter(ProcessServiceNESessionImpl.java:754)
    Please help how to resolve this.
    thanks in advance.
    Edited by: 811778 on May 17, 2013 5:05 PM

    support team suggested to use,
    -Dfuego.papi.lockManagerClass=fuego.papi.impl.lock.ParanoidLockManager for each java process, acting as PAPI client. This class available in fuegopapi-client.jar
    additional comments from support team,
    Implementing this property does not generate side-effects. This property detects and kills/recovers deadlocks in the PAPI instance cache

  • Import fuego.papi.ws.ProcessService;

    import fuego.papi.ws.ProcessService;
    import fuego.papi.ProcessService;
    What's the different between the above two sentences?
    I cannot find the fuego.papi.ws.client in the JDev11g. Where is it? Is it replaced by fuego.papi.ws.ProcessService;

    Hi YE,
    Guessing you've probably already discovered this, but in Oracle BPM 10g you'll find the fuegopapi-client.jar for your two import statements in the Enterprise (not Studio) directory <OracleBPMEnterpriseHomeDir>\client\papi\lib.
    In Oracle BPM 10g, you only need to import either "fuego.papi.ws.ProcessService" (the PAPI-WS API) or "fuego.papi.ProcessService" (the PAPI API). The difference between the two is that PAPI is the API that uses Java while PAPI-WS is the API that uses a web service as its underlying implementation. You won't need both of these, since PAPI and PAPI-WS now have about the same functionality in Oracle BPM 10g.
    In earlier releases you'd instead need to import "fuego.papi.ws.client" when accessing the PAPI-WS API only if you were accessing it from a Java application. While it was great having a web service API, the problem with PAPI-WS in earlier releases is that it only provide a subset of the capabilities that PAPI had. Using PAPI-WS, I could only create instances in a process, get the values of variables of a particular instance, send a notification message to a particular instance, run Global activities in a process, return a list of instances for a specific view and finally run an instance in a specific activity.
    This all sounds great, but the fact that PAPI-WS was a subset of PAPI used to be a problem.
    Hope this helps,
    Dan

  • Connect Java PAPI client to 5.7 Studio embedded engine?

    I am coding and unit testing some integration of java PAPI client code against a process inALBPM 5.7. But, it is very cumbersome to have to do a fully deploy to a bpm server to do this unit testing.
    Is it possible to configure the properties used to create the ProcessService object to connect to the engine that is launched from within the Studio so that I can test locally on my PC? What would the directory.properties have to look like to do so?
    Todd

    Hi Adam,
    Could you please explain more about this?
    I want to use PAPI against my local BPM studio. I have the project at "C:\OracleBPMWorkspace\TestProcess". I tried to point the directory to the project, as you suggested. Am i doing it correctly? I get the below exception. Could somebody help me?
    Thanks
    raj
    Configuration:
    Properties configuration = new Properties();
    configuration.setProperty(ProcessService.DIRECTORY_ID, "Default");
    configuration.setProperty(ProcessService.DIRECTORY_PROPERTIES_FILE, "C:\\OracleBPMWorkspace\\TestProcess");
    configuration.setProperty(ProcessService.WORKING_FOLDER, "/tmp");
    Exception:
    java.lang.IllegalStateException: directory configuration runtime fails to initilize with resource: C:\OracleBPMWorkspace\TestProcess
         at fuego.directory.DirectoryConfigurationManager.getDirectoryConfiguration(DirectoryConfigurationManager.java:335)
         at fuego.directory.DirectoryConfigurationManager.getDirectoryConfigType(DirectoryConfigurationManager.java:313)
         at fuego.directory.provider.Factory.getDirectoryFactory(Factory.java:216)
         at fuego.directory.Directory.startAnonymousSession(Directory.java:211)
         at fuego.papi.impl.ProcessServiceFactoryImpl.obtainSchemaId(ProcessServiceFactoryImpl.java:193)
         at fuego.papi.impl.ProcessServiceFactoryImpl.create(ProcessServiceFactoryImpl.java:75)
         at fuego.papi.impl.ProcessServiceFactoryImpl.create(ProcessServiceFactoryImpl.java:63)
         at fuego.papi.ProcessService.create(ProcessService.java:335)
         at com.thomson.tssq.j2012.bpms.PAPI_Test.main(PAPI_Test.java:35)

  • PAPI client in J2EE (Oracle app server, OC4J)

    Hello,
    We have a problem with using RMI-based PAPI in our J2EE application. Our client code runs fine as a standalone program, but doesn't work when it's used as a part of
    a J2EE application deployed to OC4J. There seems to some incompatibility between the XML parser implementation that Oracle supplies (xmlparserv2.jar) and Oracle's
    BPM Papi client.
    Here are the errors that we're getting:
    [Error] :3:69: <Line 3, Column 69>: XML-20129: (Error) Namespace prefix 'xsi' us
    ed but not declared.
    [Error] :8:33: <Line 8, Column 33>: XML-20129: (Error) Namespace prefix 'xsi' us
    ed but not declared.
    [Error] :10:34: <Line 10, Column 34>: XML-20129: (Error) Namespace prefix 'xsi'
    used but not declared.
    [Error] :12:40: <Line 12, Column 40>: XML-20129: (Error) Namespace prefix 'xsi'
    used but not declared.
    [Error] :42:43: <Line 42, Column 43>: XML-20129: (Error) Namespace prefix 'xsi'
    used but not declared.
    [Error] :44:33: <Line 44, Column 33>: XML-20129: (Error) Namespace prefix 'xsi'
    used but not declared.
    [Error] :46:38: <Line 46, Column 38>: XML-20129: (Error) Namespace prefix 'xsi'
    used but not declared.
    [Error] :48:35: <Line 48, Column 35>: XML-20129: (Error) Namespace prefix 'xsi'
    used but not declared.
    Exception in thread "main" java.lang.IllegalArgumentException
    at oracle.xml.jaxp.JXTransformer.setOutputProperty(JXTransformer.java:762)
    at fuego.prefs.engine.storage.EnginePreferencesNode.export(EnginePreferencesNode.java:179)
    at fuego.prefs.engine.EnginePreferences.doExport(EnginePreferences.java:143)
    at fuego.prefs.engine.EnginePreferences.doExport(EnginePreferences.java:134)
    at fuego.directory.project.engine.ProjectEngineAccessor.getEnginePropertiesString(ProjectEngineAccessor.java:137)
    at fuego.directory.project.engine.ProjectEngineAccessor.fetchEngineConfiguration(ProjectEngineAccessor.java:83)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:585)
    at fuego.directory.provider.DirectorySessionImpl$AccessorProxy.invoke(DirectorySessionImpl.java:756)
    at $Proxy5.fetchEngineConfiguration(Unknown Source)
    at fuego.directory.DirEngineConfiguration.fetch(DirEngineConfiguration.java:102)
    at fuego.prefs.engine.storage.EnginePreferencesNode.fetchEngineConfiguration(EnginePreferencesNode.java:112)
    at fuego.prefs.engine.EnginePreferences.initialize(EnginePreferences.java:438)
    at fuego.prefs.engine.EnginePreferences.loadBasePreferences(EnginePreferences.java:220)
    at fuego.papi.impl.ProcessServiceImpl.initializePollingHandledType(ProcessServiceImpl.java:1937)
    at fuego.papi.impl.ProcessServiceImpl.initializeInstanceCache(ProcessServiceImpl.java:1924)
    at fuego.papi.impl.ProcessServiceImpl.<init>(ProcessServiceImpl.java:178)
    at fuego.papi.impl.ProcessServiceFactoryImpl.getOrCreateProcessService(ProcessServiceFactoryImpl.java:127)
    at fuego.papi.impl.ProcessServiceFactoryImpl.create(ProcessServiceFactoryImpl.java:79)
    at fuego.papi.impl.ProcessServiceFactoryImpl.create(ProcessServiceFactoryImpl.java:63)
    at fuego.papi.ProcessService.create(ProcessService.java:335)
    at oasas.wpr.demo.bpm.PapiTest.createProcess(PapiTest.java:36)
    at oasas.wpr.demo.bpm.PapiTest.<init>(PapiTest.java:15)
    at oasas.wpr.demo.bpm.PapiTest.main(PapiTest.java:104)
    The errors above are generated by our standalone client when it runs with xmlparserv2.jar in the classpath. Exactly the same errors are generated by the J2EE app, but we can't remove xmlparserv.jar from OC4J's classpath because it seems to be required by the container itself.
    Please advise if there are any configuration changes that are necessary to have a PAPI client running in Oracle's J2EE environment.
    Thank you in advance,
    Igor

    Hi,
    I only was successful with running the PAPI WS client in OC4J environment, as described here: Re: Error in JAX-WS 2.0 & JDeveloper 10.1.3
    In my case, I copied all jar files from latest Sun's Metro distro and that fixed the problem!
    I also tested the RMI-based PAPI call, but that one still does not work.
    -Igor

  • Adding/deleting attachments using Fuego.Papi in OBPM10g

    Hi,
    I am seeking a resolution to the below issue. It will be really great if somebody can help me on this.
    The scenario is as follows.
    - Using global creation activity to fetch all eligible instances for a particular process using Fuego.Papi api.
    - The aim is to show and add attachments to the instances if required by the user.
    - Need to do this through a presentation, if needed jsp also.
    Problem statement
    - Is there any facility in the Fuego.Papi api to achieve this?
    - Is there any connection between Fuego.Papi api and Fuego.Lib api? As instance variable are directly not accessible via Fuego.Papi.Instance object. Is there any way to typecast Fuego.Papi.Instance to Fuego.Lib.ProcessInstance?
    - Is it possible to show the attachments individually in presentation or jsp is a must?
    Since there is a change in api from 5.7 to 10g, I am finding it difficult to solve it.
    Thanks in advance to all.
    Soubhagya

    Hector -
    Looking at you sequence, it appears that you have calling a subsequence that is removing steps from the caller's sequence. TestStand does not support editing sequences while they are running and we do not test this either. 
    When you execute a sequence in TestStand, the engine creates a runtime copy of the sequence that relies on some of the information stored in the edittime copy of the sequence. TestStand expects that the number of steps in both of these copies of the sequence to be the same. When they are not, it is possible to get an execution into a bad state. At the moment, your sequence is likely working because you are updating only the runtime copy and most of the references back to the edittime copy appear to be holding up. If you had in some way updated the edittime copy, I suspect that you would have seen a crash. Also, we actually reuse runtime copy of sequences within an execution, so the next time you called the sequence, you might find that the steps have already been removed.
    If you somehow want to build a sequence in a sequence file prior to calling it, that would be supported. You just have to ensure that the file is not being used in another execution, i.e parallel or batch model.
    Scott Richardson
    National Instruments

  • Fuego.papi.ProcessNotAvailableException

    Hi guys,
    I use the ALBPM 5.7 enterprise and I want to use PAPI.
    So, I got this code from my friend. He said that this code is correct.
    But it's not working now.
    I don't know what's wrong.
    "/Process" is started on the workspace portal and its version is really 2.0.
    "mih" user has the right authority to start the process.
    This code can make a session but after then the error appears.
    Thanks.
    my source code==========================================================
    package com.bpm.ucity;
    import java.util.Properties;
    import fuego.papi.Arguments;
    import fuego.papi.InstanceInfo;
    import fuego.papi.ProcessService;
    import fuego.papi.ProcessServiceSession;
    public class StartProcess {
         public StartProcess() {
              // TODO Auto-generated constructor stub
         * @param args
         public static void main(String[] args) {
              // TODO Auto-generated method stub
              String strProcessID          = "/Process";
              String strUserName          = "mih";
              String strPassword          = "1";
              ProcessService procServ = null;
              ProcessServiceSession procServSession = null;
              InstanceInfo instInfo = null;
              try {
                   Properties prop      = new Properties();
                   prop.setProperty(ProcessService.DIRECTORY_ID, "default");
                   prop.setProperty(ProcessService.DIRECTORY_PROPERTIES_FILE, "C:/bea/albpm5.7/j2eewl/conf/directory.properties");
                   prop.setProperty(ProcessService.WORKING_FOLDER, "C:/tmp");
                   prop.setProperty("java.naming.factory.initial","weblogic.jndi.WLInitialContextFactory");
                   prop.setProperty("java.naming.provider.url","t3://localhost:7001");     
                   procServ = ProcessService.create(prop);
                   // create session
                   procServSession = procServ.createSession(strUserName, strPassword, "localhost");
                   System.out.println ("procServSession => [" + procServSession + "]" );
                   // create process instance
                   Arguments arguments = Arguments.create();
                   System.out.println ("Arguments1111111111111111=======" + arguments);
                   System.out.println ("Here I am!!!!!!" );          
                   instInfo = procServSession.createProcessInstance(strProcessID, arguments);
                   System.out.println ("instInfo => [" + instInfo + "]" );
                   String strInstanceID = instInfo.getId();
                   System.out.println ("strInstanceID => [" + strInstanceID + "]" );
              } catch (Exception e) {
                   e.printStackTrace();
              } finally {
                   procServSession.close();
    error=================================================================
    procServSession => [abstract class fuego.papi.ProcessServiceSesion]
    Arguments1111111111111111=======fuego.papi.Arguments@8ceeea
    Here I am!!!!!!
    fuego.papi.ProcessNotAvailableException: cannot use process '/Process#Default-2.0'
    at fuego.papi.impl.ProcessServiceImpl.createProcess(ProcessServiceImpl.java:1756)
    at fuego.papi.impl.ProcessServiceImpl.access$2500(ProcessServiceImpl.java:142)
    at fuego.papi.impl.ProcessServiceImpl$SessionProcessLoader.load(ProcessServiceImpl.java:3822)
    at fuego.papi.impl.ProcessManager.get(ProcessManager.java:631)
    at fuego.papi.impl.ProcessServiceImpl.getProcess(ProcessServiceImpl.java:1138)
    at fuego.papi.impl.ProcessServiceNESessionImpl.getProcess(ProcessServiceNESessionImpl.java:1069)
    at fuego.papi.impl.ProcessServiceNESessionImpl.checkBeginPermissions(ProcessServiceNESessionImpl.java:2434)
    at fuego.papi.impl.ProcessServiceNESessionImpl.createProcessInstance(ProcessServiceNESessionImpl.java:1441)
    at fuego.papi.impl.ProcessServiceNESessionImpl.createProcessInstance(ProcessServiceNESessionImpl.java:1434)
    at com.bpm.ucity.StartProcess.main(StartProcess.java:55)
    Caused by: fuego.papi.impl.EngineNotAvailableException: cannot find 'BEA_WL_Engine' EJB in 'engines/BEA_WL_Engine'
    reason: Need to specify class name in environment or system property, or as an applet parameter, or in an application resource file: check java.naming.factory.initial
    project EAR application program to be setted up and to be started
    at fuego.papi.impl.EngineNotAvailableException.cannotFindEJB(EngineNotAvailableException.java:83)
    at fuego.papi.impl.j2ee.J2EEEngineAccessImpl.getEngineHome(J2EEEngineAccessImpl.java:286)
    at fuego.papi.impl.j2ee.J2EEEngineAccessImpl.getSecureEngineInterface(J2EEEngineAccessImpl.java:348)
    at fuego.papi.impl.j2ee.J2EEEngineAccessImpl.createSecureEngine(J2EEEngineAccessImpl.java:158)
    at fuego.papi.impl.ProcessServiceImpl.createSecureEngine(ProcessServiceImpl.java:1280)
    at fuego.papi.impl.ProcessServiceNESessionImpl$2.run(ProcessServiceNESessionImpl.java:2140)
    at fuego.papi.impl.ProcessServiceImpl.executeEngineOp(ProcessServiceImpl.java:1578)
    at fuego.papi.impl.ProcessServiceNESessionImpl.getSecureEngine(ProcessServiceNESessionImpl.java:2148)
    at fuego.papi.impl.ProcessServiceImpl.createProcess(ProcessServiceImpl.java:1709)
    ... 9 more
    Caused by: javax.naming.NoInitialContextException: Need to specify class name in environment or system property, or as a
    n applet parameter, or in an application resource file: java.naming.factory.initial
    at javax.naming.spi.NamingManager.getInitialContext(Unknown Source)
    at javax.naming.InitialContext.getDefaultInitCtx(Unknown Source)
    at javax.naming.InitialContext.getURLOrDefaultInitCtx(Unknown Source)
    at javax.naming.InitialContext.lookup(Unknown Source)
    at fuego.papi.impl.j2ee.J2EEEngineAccessImpl.getEngineHome(J2EEEngineAccessImpl.java:276)
    ... 16 more
    서버 동기화 정보에 대한 JMS Topic 연결이 일시적으로 중단되었습니다. 자세한 정보:주제 연결 팩토리 'XATopicConnectionFacto
    ry'을(를) 찾는 동안 오류가 발생했습니다.
    세부 사항:
    javax.naming.NoInitialContextException: Need to specify class name in environment or system property, or as an applet pa
    rameter, or in an application resource file: java.naming.factory.initial
    원인: Need to specify class name in environment or system property, or as an applet parameter, or in an application reso
    urce file: java.naming.factory.initial
    fuego.papi.impl.j2ee.JMSTopicLookUpException: 주제 연결 팩토리 'XATopicConnectionFactory'을(를) 찾는 동안 오류가 발생했습니다.
    Detail:
    javax.naming.NoInitialContextException: Need to specify class name in environment or system property, or as an applet pa
    rameter, or in an application resource file: java.naming.factory.initial
    at fuego.papi.impl.j2ee.J2EEEngineAccessImpl$TopicSubscriberImpl.lookupTopic(J2EEEngineAccessImpl.java:649)
    at fuego.papi.impl.j2ee.J2EEEngineAccessImpl$TopicSubscriberImpl.run(J2EEEngineAccessImpl.java:540)
    Caused by: javax.naming.NoInitialContextException: Need to specify class name in environment or system property, or as a
    n applet parameter, or in an application resource file: java.naming.factory.initial
    at javax.naming.spi.NamingManager.getInitialContext(Unknown Source)
    at javax.naming.InitialContext.getDefaultInitCtx(Unknown Source)
    at javax.naming.InitialContext.getURLOrDefaultInitCtx(Unknown Source)
    at javax.naming.InitialContext.lookup(Unknown Source)
    at fuego.papi.impl.j2ee.J2EEEngineAccessImpl$TopicSubscriberImpl.lookupTopic(J2EEEngineAccessImpl.java:640)
    ... 1 more
    서버 동기화 정보에 대한 JMS Topic 연결이 일시적으로 중단되었습니다. 자세한 정보:주제 연결 팩토리 'XATopicConnectionFacto
    ry'을(를) 찾는 동안 오류가 발생했습니다.
    세부 사항:
    javax.naming.NoInitialContextException: Need to specify class name in environment or system property, or as an applet pa
    rameter, or in an application resource file: java.naming.factory.initial
    원인: Need to specify class name in environment or system property, or as an applet parameter, or in an application reso
    urce file: java.naming.factory.initial
    fuego.papi.impl.j2ee.JMSTopicLookUpException: 주제 연결 팩토리 'XATopicConnectionFactory'을(를) 찾는 동안 오류가 발생했
    습니다.
    Detail:
    javax.naming.NoInitialContextException: Need to specify class name in environment or system property, or as an applet pa
    rameter, or in an application resource file: java.naming.factory.initial
    at fuego.papi.impl.j2ee.J2EEEngineAccessImpl$TopicSubscriberImpl.lookupTopic(J2EEEngineAccessImpl.java:649)
    at fuego.papi.impl.j2ee.J2EEEngineAccessImpl$TopicSubscriberImpl.run(J2EEEngineAccessImpl.java:540)
    Caused by: javax.naming.NoInitialContextException: Need to specify class name in environment or system property, or as a
    n applet parameter, or in an application resource file: java.naming.factory.initial
    at javax.naming.spi.NamingManager.getInitialContext(Unknown Source)
    at javax.naming.InitialContext.getDefaultInitCtx(Unknown Source)
    at javax.naming.InitialContext.getURLOrDefaultInitCtx(Unknown Source)
    at javax.naming.InitialContext.lookup(Unknown Source)
    at fuego.papi.impl.j2ee.J2EEEngineAccessImpl$TopicSubscriberImpl.lookupTopic(J2EEEngineAccessImpl.java:640)
    ... 1 more

    Hi Ariel,
    You are right. I've got an error in my code using some wrong codes.
    I change my code like this.
    ================================================================
    package com.bpm.ucity;
    import java.util.Properties;
    import fuego.papi.Arguments;
    import fuego.papi.InstanceInfo;
    import fuego.papi.ProcessService;
    import fuego.papi.ProcessServiceSession;
    public class StartProcess {
         public StartProcess() {
              // TODO Auto-generated constructor stub
         * @param args
         public static void main(String[] args) {
              // TODO Auto-generated method stub
              String strProcessID          = "/Process";
              String strUserName          = "mih";
              String strPassword          = "1";
    //changed this part     
         Properties systemProperties = System.getProperties();
         systemProperties.setProperty ("java.naming.factory.initial", "weblogic.jndi.WLInitialContextFactory");
         systemProperties.setProperty("java.naming.provider.url", "t3://localhost:7001");
              ProcessService procServ = null;
              ProcessServiceSession procServSession = null;
              InstanceInfo instInfo = null;
              try {     
                   Properties prop      = new Properties();
                   prop.setProperty(ProcessService.DIRECTORY_PROPERTIES_FILE, "C:/bea/albpm5.7/j2eewl/conf/directory.properties");
                   procServ = ProcessService.create(prop);
                   // create session
                   procServSession = procServ.createSession(strUserName, strPassword, "localhost");
                   System.out.println ("procServSession => [" + procServSession + "]" );
                   // create process instance
                   Arguments arguments = Arguments.create();
                   instInfo = procServSession.createProcessInstance(strProcessID, arguments);
                   System.out.println ("instInfo => [" + instInfo + "]" );
                   String strInstanceID = instInfo.getId();
                   System.out.println ("strInstanceID => [" + strInstanceID + "]" );
              } catch (Exception e) {
                   e.printStackTrace();
              } finally {
                   procServSession.close();
    ================================================================
    and I put weblogic.jar path into the classpath.
    After that, I can get a new process instance, but I've got some errors up to now.
    I think the error is not caused by the code.
    How do you think about it?
    error====================================================
    JMS Topic 엔진에 가입하는 동안 오류가 발생했습니다. reason:'While trying to lookup 'java:comp.UserTransaction' didn't find subcontext 'java:comp'. Resolved ''
    cause by: While trying to lookup 'java:comp.UserTransaction' didn't find subcontext 'java:comp'. Resolved ''
    javax.naming.NameNotFoundException: While trying to lookup 'java:comp.UserTransaction' didn't find subcontext 'java:comp'. Resolved '' [Root exception is javax.naming.NameNotFoundException: While trying to lookup 'java:comp.UserTransaction' didn't find subcontext 'java:comp'. Resolved '']; remaining name 'java:comp/UserTransaction'
         at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:215)
         at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:338)
         at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:252)
         at weblogic.jndi.internal.ServerNamingNode_923_WLStub.lookup(Unknown Source)
         at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:379)
         at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:367)
         at javax.naming.InitialContext.lookup(InitialContext.java:351)
         at fuego.connector.impl.UserTransactionProvider.createForServlets(UserTransactionProvider.java:50)
         at fuego.papi.impl.j2ee.J2EEEngineAccessImpl.createTopicSubcriber(J2EEEngineAccessImpl.java:381)
         at fuego.papi.impl.j2ee.J2EEEngineAccessImpl.<init>(J2EEEngineAccessImpl.java:80)
         at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
         at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
         at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
         at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
         at fuego.prefs.engine.EngineType.createObject(EngineType.java:218)
         at fuego.prefs.engine.EngineType.createEngineAccess(EngineType.java:211)
         at fuego.papi.impl.EngineAccess.getEngineAccess(EngineAccess.java:176)
         at fuego.papi.impl.EngineAccess.getEngineAccess(EngineAccess.java:96)
         at fuego.papi.impl.ProcessServiceImpl.getEngineAccess(ProcessServiceImpl.java:983)
         at fuego.papi.impl.ProcessServiceImpl.createSecureEngine(ProcessServiceImpl.java:1280)
         at fuego.papi.impl.ProcessServiceNESessionImpl$2.run(ProcessServiceNESessionImpl.java:2140)
         at fuego.papi.impl.ProcessServiceImpl.executeEngineOp(ProcessServiceImpl.java:1578)
         at fuego.papi.impl.ProcessServiceNESessionImpl.getSecureEngine(ProcessServiceNESessionImpl.java:2148)
         at fuego.papi.impl.ProcessServiceImpl.createProcessControl(ProcessServiceImpl.java:1266)
         at fuego.papi.impl.ProcessServiceNESessionImpl$1.run(ProcessServiceNESessionImpl.java:1104)
         at fuego.papi.impl.ProcessServiceImpl.executeEngineOp(ProcessServiceImpl.java:1578)
         at fuego.papi.impl.ProcessServiceNESessionImpl.getProcessControl(ProcessServiceNESessionImpl.java:1109)
         at fuego.papi.impl.InstanceCache.getInstancesByFilter(InstanceCache.java:496)
         at fuego.papi.impl.InstanceCache.getInstancesByFilter(InstanceCache.java:247)
         at fuego.papi.impl.ProcessServiceImpl.getInstancesByFilter(ProcessServiceImpl.java:1087)
         at fuego.papi.impl.ProcessServiceNESessionImpl.getInstancesByFilter(ProcessServiceNESessionImpl.java:755)
         at fuego.papi.impl.ProcessServiceNESessionImpl.getSortedInstancesByFilter(ProcessServiceNESessionImpl.java:2293)
         at fuego.papi.impl.ProcessServiceNESessionImpl.getInstancesByView(ProcessServiceNESessionImpl.java:810)
         at com.bpm.ucity.Inbox.main(Inbox.java:44)
    Caused by: javax.naming.NameNotFoundException: While trying to lookup 'java:comp.UserTransaction' didn't find subcontext 'java:comp'. Resolved ''
         at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1139)
         at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:247)
         at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:171)
         at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:206)
         at weblogic.jndi.internal.RootNamingNode_WLSkel.invoke(Unknown Source)
         at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:553)
         at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:224)
         at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:443)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
         at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:439)
         at weblogic.rmi.internal.BasicServerRef.access$300(BasicServerRef.java:61)
         at weblogic.rmi.internal.BasicServerRef$BasicExecuteRequest.run(BasicServerRef.java:983)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)

  • Abort an instance using ProcessService (Fuego.Papi.ProcessService)

    Hi Folks,
    I want to abort a process instance using ProcessService (Fuego.Papi.ProcessService)
    This is how i am trying to do the same:
    +if (ivBPMObject1.bpmObject1Option != "TRUE") {+
    ProcessService.connectTo(url : Fuego.Server.directoryURL, user : "pavan",
    password : "");
    +// ivInstance2Id is the InstanceId of the other split branch which is alive and which needs to be suspended+
    lvInstance = ProcessService.getInstance(instance : ivInstance2Id.id);
    +// abort+
    lvInstance.abort();
    ProcessService.disconnectFrom();
    +}+
    I get the following exception in the line lvInstance.abort() :.
    The batch operation could not be executed for all selected instances.
    Internal Exceptions:
    +>> /MainProcess#Default-1.0/1/2:+
    Instance '/MainProcess#Default-1.0/1/0' could not be locked because participant 'Server' is currently locking it
    I am running this from the Embedded Workspace of Oracle BPM Studio and I dont see any participant 'Server' in the directory.
    How can i suspend/abort this instance?
    Is there a way that my user/participant 'pavan' can be given rights/privelege to take 'Server's instances?
    I tried using 'Server' as user but i dont know the credentials for 'Server' - so that attempt too failed :(.
    can anyone please help me out?
    Regards,
    user8702013

    Thank you Ariel,
    Yes, I have two 'approvals' happening in parallel - in two branches of a split. when one approval comes 'unapproved', there is no point continuing with the other - i have to abort it.
    But if i set the setting to 'generate independent copies', how will i get the 'instanceId' of the second branch when only the first branch has reached the 'join'? (i had thus made the 'shared' to be true).
    My requirement is that i have two branches in a split. these two split branches call two different approval subprocess which go into user interaction tasks. but when one one approval is rejected (and reaches the join), i want to abort the other instance (atleast of the called subprocess) so that the redundant approval user task of the second branch can be avoided.
    I have been struggling with this for the past couple of days :(
    I am trying to see if i can get the 'instances' of the subprocess in question and find the instance to be killed (aborted) by checking the parents (the parent should be my process). i am getting problems there too. am stranded...
    Regards,
    user8702013

  • Fuego.papi.exception.SharedParentInstanceBusyException

    The process has a split-join. Instance in one branch is in join. The interactive activity in another branch cannot be executed. In the Javadoc / PAPI, no enough information about this exception.
    I use BPM standalone 10.3.1 and studio 10.3.0
    Exception in thread "main" fuego.papi.exception.SharedParentInstanceBusyException: Task '0' in activity '/TestPAPI3Process#Default-1.0/Interactive[departmentmanager3]' cannot be executed over instance '/TestPAPI3Process#Default-1.0/9211/2'.
    Another instance copy is executing a task over shared instance.
         at fuego.server.execution.CheckInteractiveExecution.checkShareParentState(CheckInteractiveExecution.java:234)
         at fuego.server.execution.CheckInteractiveExecution.check(CheckInteractiveExecution.java:111)
         at fuego.server.execution.microactivity.InteractiveMicroActivity.checkInteractiveExecution(InteractiveMicroActivity.java:471)
         at fuego.server.execution.microactivity.InteractiveMicroActivity.executeItem(InteractiveMicroActivity.java:443)
         at fuego.server.execution.microactivity.InteractiveMicroActivity.execute(InteractiveMicroActivity.java:104)
         at fuego.server.AbstractProcessBean$48.execute(AbstractProcessBean.java:3198)
         at fuego.server.execution.DefaultEngineExecution$AtomicExecutionTA.runTransaction(DefaultEngineExecution.java:304)
         at fuego.transaction.TransactionAction.startBaseTransaction(TransactionAction.java:470)
         at fuego.transaction.TransactionAction.startTransaction(TransactionAction.java:551)
         at fuego.transaction.TransactionAction.start(TransactionAction.java:212)
         at fuego.server.execution.DefaultEngineExecution.executeImmediate(DefaultEngineExecution.java:123)
         at fuego.server.execution.EngineExecution.executeImmediate(EngineExecution.java:66)
         at fuego.server.AbstractProcessBean.runTask(AbstractProcessBean.java:3202)
         at sun.reflect.GeneratedMethodAccessor48.invoke(Unknown Source)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
         at java.lang.reflect.Method.invoke(Unknown Source)
         at fuego.lang.JavaClass.invokeMethod(JavaClass.java:1410)
         at fuego.lang.JavaObject.invoke(JavaObject.java:227)
         at fuego.component.Message.process(Message.java:585)
         at fuego.component.ExecutionThread.processMessage(ExecutionThread.java:780)
         at fuego.component.ExecutionThread.processBatch(ExecutionThread.java:755)
         at fuego.component.ExecutionThread.doProcessBatch(ExecutionThread.java:142)
         at fuego.component.ExecutionThread.doProcessBatch(ExecutionThread.java:134)
         at fuego.fengine.FEngineProcessBean.processBatch(FEngineProcessBean.java:244)
         at fuego.component.ExecutionThread.work(ExecutionThread.java:839)
         at fuego.component.ExecutionThread.run(ExecutionThread.java:408)
         at fuego.component.CustomExecution.next(CustomExecution.java:176)
         at fuego.papi.impl.rmi.RMIExecution.next(RMIExecution.java:109)
         at fuego.papi.impl.ProcessInstanceOperation.prepareExternalActivity(ProcessInstanceOperation.java:697)
         at fuego.papi.impl.ProcessServiceSessionImpl.activityPrepare(ProcessServiceSessionImpl.java:1423)
         at fuego.papi.impl.ProcessServiceSessionImpl.activityPrepare(ProcessServiceSessionImpl.java:1417)
         at testpapiprocessjava.departmentmanager3.managerPrepareCommit(departmentmanager3.java:53)
         at testpapiprocessjava.departmentmanager3.main(departmentmanager3.java:29)
    Process exited with exit code 1.

    Sorrry - I don't think I was clear. Leave the checkbox checked so that it does generates copies (leave it like it was when you first added the Split activity).
    I could easily be wrong (frequently am) but I ran into a similar problem when I'd changed it from the original setting (make it unchecked) and suspected you might have collided into the same bug I did.
    Dan

  • Fuego.papi.exception.TaskFailedException: Task '0' in activity

    Hi,
    getting below exception in engine log in oracle 10g version. what could be the problem ?
    fuego.papi.exception.TaskFailedException: Task '0' in activity '/SystemCheck#Default-1.0/Interactive[BANKApproval]' for instance '/SystemCheck#Default-1.0/1059/0' could not be successfully executed. The task failed while executing method 'bankApproval'.
    at fuego.papi.exception.TaskFailedException.create(TaskFailedException.java:57)
    at fuego.server.AbstractProcessBean.createTaskFailedException(AbstractProcessBean.java:3594)
    at fuego.fengine.FEngineProcessBean.createTaskFailedException(FEngineProcessBean.java:398)
    at fuego.server.AbstractProcessBean.runTask(AbstractProcessBean.java:3207)
    at sun.reflect.GeneratedMethodAccessor76.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
    at java.lang.reflect.Method.invoke(Unknown Source)
    at fuego.lang.JavaClass.invokeMethod(JavaClass.java:1410)
    at fuego.lang.JavaObject.invoke(JavaObject.java:227)
    at fuego.component.Message.process(Message.java:585)
    at fuego.component.ExecutionThread.processMessage(ExecutionThread.java:780)
    at fuego.component.ExecutionThread.processBatch(ExecutionThread.java:755)
    at fuego.component.ExecutionThread.doProcessBatch(ExecutionThread.java:142)
    at fuego.component.ExecutionThread.doProcessBatch(ExecutionThread.java:134)
    at fuego.fengine.FEngineProcessBean.processBatch(FEngineProcessBean.java:244)
    at fuego.component.ExecutionThread.work(ExecutionThread.java:839)
    at fuego.component.ExecutionThread.run(ExecutionThread.java:408)
    at fuego.component.CustomExecution.next(CustomExecution.java:176)
    at fuego.papi.impl.rmi.RMIExecution.next(RMIExecution.java:111)
    at fuego.papi.impl.ProcessInstanceOperation.runActivity(ProcessInstanceOperation.java:723)
    at fuego.papi.impl.ProcessServiceSessionImpl.activityExecute(ProcessServiceSessionImpl.java:1564)
    at fuego.papi.impl.ProcessServiceSessionImpl.activityExecute(ProcessServiceSessionImpl.java:1503)
    at fuego.papi.impl.ProcessServiceSessionImpl.activityExecute(ProcessServiceSessionImpl.java:1524)
    at fuego.papi.impl.ProcessServiceSessionImpl.runActivity(ProcessServiceSessionImpl.java:1497)
    at com.lol.fuego.impl.service.workflow.ProcessHandlerImpl.executeActivity(ProcessHandlerImpl.java:300)
    at com.lolgroup.dogs.delegate.FuegoProcess.executeActivity(FuegoProcess.java:199)
    at com.lolgroup.dogs.delegate.WorkFlowAction.actionRelease(WorkFlowAction.java:32)
    at com.lolgroup.dogs.delegate.InputAction.action(InputAction.java:158)
    at com.lolgroup.dogs.delegate.ProcessFactoryImpl.process(ProcessFactoryImpl.java:163)
    at com.lolgroup.dogs.delegate.FrameworkManager.doLocalExecute(FrameworkManager.java:45)
    at com.lolgroup.dogs.delegate.FrameworkManager.executeAction(FrameworkManager.java:29)
    at com.lol.aml.cadd.workflow.service.impl.AbstractWorkflowServiceImpl.releaseInstance(AbstractWorkflowServiceImpl.java:1746)
    at com.lol.aml.cadd.webapp.workflow.WorkflowSubmitService.processWorkItemPackageForCoreCADDSubmit(WorkflowSubmitService.java:465)
    at com.lol.aml.cadd.webapp.workflow.WorkflowSubmitController.onSubmit(WorkflowSubmitController.java:1202)
    at org.springframework.web.servlet.mvc.SimpleFormController.processFormSubmission(SimpleFormController.java:267)
    at org.springframework.web.servlet.mvc.AbstractFormController.handleRequestInternal(AbstractFormController.java:250)
    at org.springframework.web.servlet.mvc.AbstractController.handleRequest(AbstractController.java:153)
    at org.springframework.web.servlet.mvc.SimpleControllerHandlerAdapter.handle(SimpleControllerHandlerAdapter.java:48)
    at org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:819)
    at org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:754)
    at org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:399)
    at org.springframework.web.servlet.FrameworkServlet.doPost(FrameworkServlet.java:364)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
    at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
    at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
    at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
    at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
    at org.springframework.web.filter.CharacterEncodingFilter.doFilterInternal(CharacterEncodingFilter.java:77)
    at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:77)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
    at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3496)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(Unknown Source)
    at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2180)
    at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2086)
    at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1406)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    Caused by: fuego.lang.ComponentExecutionException: The method 'CIL_bankApproval' from class 'goahead.SystemCheck.Default_1_0.Instance' could not be successfully executed.
    at fuego.component.ExecutionThreadContext.invokeMethod(ExecutionThreadContext.java:519)
    at fuego.component.ExecutionThreadContext.invokeMethod(ExecutionThreadContext.java:273)
    at fuego.fengine.FEEngineExecutionContext.invokeMethodAsCil(FEEngineExecutionContext.java:219)
    at fuego.server.execution.EngineExecutionContext.runCil(EngineExecutionContext.java:1284)
    at fuego.server.execution.TaskExecution.invoke(TaskExecution.java:401)
    at fuego.server.execution.InteractiveNormalCilExecution.invoke(InteractiveNormalCilExecution.java:425)
    at fuego.server.execution.TaskExecution.executeCIL(TaskExecution.java:513)
    at fuego.server.execution.TaskExecution.executeTask(TaskExecution.java:697)
    at fuego.server.execution.TaskExecution.executeTask(TaskExecution.java:657)
    at fuego.server.execution.TaskExecution.executeTask(TaskExecution.java:154)
    at fuego.server.execution.microactivity.InteractiveMicroActivity.executeNormalCil(InteractiveMicroActivity.java:501)
    at fuego.server.execution.microactivity.InteractiveMicroActivity.executeItem(InteractiveMicroActivity.java:454)
    at fuego.server.execution.microactivity.InteractiveMicroActivity.execute(InteractiveMicroActivity.java:104)
    at fuego.server.AbstractProcessBean$46.execute(AbstractProcessBean.java:3198)
    at fuego.server.execution.DefaultEngineExecution$AtomicExecutionTA.runTransaction(DefaultEngineExecution.java:304)
    at fuego.transaction.TransactionAction.startBaseTransaction(TransactionAction.java:470)
    at fuego.transaction.TransactionAction.startTransaction(TransactionAction.java:551)
    at fuego.transaction.TransactionAction.start(TransactionAction.java:212)
    Edited by: Brijesh Kumar Singh on Apr 25, 2012 10:01 PM

    Hi
    Is there any more stack below what you posted? sometimes there is more information that explains why the method could not be executed - maybe an underlying java error?
    Regards
    Kevin

  • Business Parameter value access through PAPI Client

    I'm new to Oracle BPM. Currently working on PAPI client development and requires a value from a Business Parameter "InterestRate".
    Could somebody help me out. Is it possible to get the Business Parameter value from a PAPI client.
    Thanks

    I could be wrong, but I think the Business Parameters are stored in the FDI. I've never had the need to hit it from Java, but I believe a couple folks on this forum might be able to give you a pointer on the FDI API.
    Dan

Maybe you are looking for

  • Where on the apple site can I buy a spare mains cable for my new macbook air?

    the site is really confusing been searhcing for 10 mins now can anyoe post a link for me? regards Chris

  • OBJECT_OBJREF_NOT_ASSIGNED for Text editor

    We tried to use Text editor on a Screen which is RF enabled. It is working fine when we work in SAP. When this is being connected from LM01 the below error message is coming. Runtime error: OBJECT_OBJREF_NOT_ASSIGNED Exception: CX_SY_REF_INITIAL The

  • Problem restoring iTunes backup from DVD - please help.

    Hi all, My iTunes library is currently on our laptop. I've used the iTunes backup wizard to create two backup DVD's using the internal Optiarc DVD writer. When I try to restore the DVD's on my new PC, iTunes freezes up for about 10 minutes with the D

  • How to handle AMC through service contract

    Dear friends, I have an AMC scenario. There is a service contract for AMC of plant equipments. How can we handle payment of the parts replaced by the vendor during the AMC period. The service contract is only for the services. And the cost of the par

  • Some progress,  comparing com.apple.aperture.plist files

    After restoring an old com.apple.Aperture.plist file from a backup on my iDisk with some success in restoring functionality in Full Screen Mode, I am submitting comparisons of some values for both plist values for Leopard (which works very well in Fu