Log filtering in BPM Enterprise Server

Hi ,
How can we filter logs based on different processes viewed inside the Log Viewer in the Process Administrator of Enterprise Server connected via. Weblogic?
So I want to see logs of Process A separately and Process B separately in the Log Viewer..
How can I do that?

Out of the box, ALBPM/Oracle BPM only allows for one level of logging across all projects, activities, business objects, etc. per engine. The only way to see projects separately is to ensure that log messages are standardized and consistently applied throughout all the projects. Since that tends to be a relatively difficult thing to enforce across all development teams and resources, we have created an Extended Logging Framework that enforces standardized logging for processes, activities, screenflows, and objects. It also outputs the log messages in a standard Log4j format that can be viewed and filtered through external log viewers such as LogMx. This allows the log messages to be filtered at an extremely granular level. In addition, the log level for each type of log message can be modified independently and adjusted in real time without having to restart the engine. You can check out a screencast here .

Similar Messages

Trying to install Aqualogic BPM Enterprise Server in a Weblogic domain.

Hi,
I'm trying to configure a AquaLogic BPM Enterprise Server on a currently working WebLogic domain. I have had a lot of problems due to that I needed to copy some AquaLogic/Fuego libraries to the domain lib folder (didn't find any doc about it) and so I could keep on going on with the installation. However, right now I'm completely stopped with an error ... I cannot find anything about it in the Bea forum and not even Google... Here you have it, I hope some of you guys can help me out!!
<16-abr-2008 10H00' CEST> <Info> <Deployer> <BEA-149060> <Module /albpmServices/albpmengine of application 01-eng-albpmengine successfully transitioned from STATE_PREPARED to STATE_ADMIN on server AdminServer.>
<16-abr-2008 10H00' CEST> <Info> <EJB> <BEA-010060> <The Message-Driven EJB: item-execution-albpmengine has connected/reconnected to the JMS destination: queue/ToDoQueue.>
searching for directory.xml in the /META-INF directory
Creating connector [__internal__:J2EE]
Creating connector [fuego:SQL]
Protocol [REMOTE_JDBC] not supported.
Detail:Check that the appropriate pluggin is present in your system or that the provider name is not misspelled.
fuego.directory.exception.ProtocolNotSupportedException: Protocol [REMOTE_JDBC] not supported.
Detail:Check that the appropriate pluggin is present in your system or that the provider name is not misspelled.
 at fuego.directory.exception.ProtocolNotSupportedException.create(ProtocolNotSupportedException.java:34)
 at fuego.directory.provider.Factory.getFactoryFor(Factory.java:173)
 at fuego.directory.provider.Factory.getDirectoryFactory(Factory.java:214)
 at fuego.directory.Directory.fillPassport(Directory.java:122)
 at fuego.ejbengine.Engine.initDirectorySession(Engine.java:297)
 at fuego.ejbengine.Engine.start(Engine.java:123)
...

Hi,
I'm trying to configure a AquaLogic BPM Enterprise Server on a currently working WebLogic domain. I have had a lot of problems due to that I needed to copy some AquaLogic/Fuego libraries to the domain lib folder (didn't find any doc about it) and so I could keep on going on with the installation. However, right now I'm completely stopped with an error ... I cannot find anything about it in the Bea forum and not even Google... Here you have it, I hope some of you guys can help me out!!
<16-abr-2008 10H00' CEST> <Info> <Deployer> <BEA-149060> <Module /albpmServices/albpmengine of application 01-eng-albpmengine successfully transitioned from STATE_PREPARED to STATE_ADMIN on server AdminServer.>
<16-abr-2008 10H00' CEST> <Info> <EJB> <BEA-010060> <The Message-Driven EJB: item-execution-albpmengine has connected/reconnected to the JMS destination: queue/ToDoQueue.>
searching for directory.xml in the /META-INF directory
Creating connector [__internal__:J2EE]
Creating connector [fuego:SQL]
Protocol [REMOTE_JDBC] not supported.
Detail:Check that the appropriate pluggin is present in your system or that the provider name is not misspelled.
fuego.directory.exception.ProtocolNotSupportedException: Protocol [REMOTE_JDBC] not supported.
Detail:Check that the appropriate pluggin is present in your system or that the provider name is not misspelled.
 at fuego.directory.exception.ProtocolNotSupportedException.create(ProtocolNotSupportedException.java:34)
 at fuego.directory.provider.Factory.getFactoryFor(Factory.java:173)
 at fuego.directory.provider.Factory.getDirectoryFactory(Factory.java:214)
 at fuego.directory.Directory.fillPassport(Directory.java:122)
 at fuego.ejbengine.Engine.initDirectorySession(Engine.java:297)
 at fuego.ejbengine.Engine.start(Engine.java:123)
...

Two instances running in AquaLogic BPM Enterprise Server 6.0 Standalone

May i have two different instances running in AquaLogic BPM Enterprise Server 6.0 Standalone?
For example:
One instance should be the Homologation Enviroment, to make some tests.
And the second one should be the definitive Production Enviroment to publish the projects after passing from Homologation Enviroment.

Hi,
By "Homologation Environment" I'm guessing you might be referring to a QA or UAT environment.
If this is the case, you'd have a separate ALBPM Engine running processes in this environment and then use ANT tasks to then publish projects into the true Production environment.
Have them on separate ALBPM Engines is the best practice.
hth,
Dan

How to install AquaLogic BPM Enterprise server in UBUNTU linux

Hello everyone,
I really dont know if it is here that I need to post this, but I cannot find any documentation about how I can install AquaLogic BPM Enterprise server in a machine with UBUNTU server. Can anyone help me with that?
Thanks
Mario Mesquita

Hi,
SAP B1 will not support linux OS. Please check below guide:
http://rels.co.il/wp-content/uploads/2013/02/System-and-Hardware-Requirements-Guide-for-SAP-Business-One-8-8-and-higher.…
Thanks & Regards,
Nagarajan

Changing timeout in BPM Enterprise Server

Hi,
We want to increase the timeout of all automatic activities from 60 seconds to 300 seconds.. We tried doing this by going under:-
Engines-->Name of Engine --> Execution and under retry Interval we change from 60 to 300 seconds...
We then restart the engine but the change does not take place.. The transaction still times out within 60 seconds..
Do we need to recreate the Enginer EAR after doing this? Do we need to change certain timeout settings inside Weblogic Server since we are using WLS Enterprise Server?
Any advice wud be appreciated..

Yes,
Take a look at weblogic transactions. Spefic at JTA transaction timeout.
But please, before increase this XA timeout, take a look at every resource that is participating in the transaction if it's possible to extend the transaction time otherwise you will have an transaction member aborting all the transaction due to timeout. (database , jms, ...)
Regards,
Luiz

Migrate a project from BPM Studio to enterprise server

Hi
can anyone can help me and explain me how to migrate or deploy a project from BPM studio to the BPM enterprise server????????
thanks

From studio, right click on the project, and go to export. This will give you a .exp file which contains all the information relating to the project.
Assuming you have correctly installed Enterprise, just open up the process administrator, go to projects, select deploy, and browse to the location of your .exp file.
Its that easy!
HTH
-Kevin

WLST Failed in Oracle BPM Enterprise for Weblogic Server

Hi,
I am not getting any clue of resolving the following issue. We are using Oracle BPM Enterprise for Weblogic # 100141. Error details:-
Initializing WebLogic Scripting Tool (WLST) ...
Welcome to WebLogic Server Administration Scripting Shell
Type help() for help on available commands
t3://192.68.1.3:
Connecting to t3://192.168.1.3: with userid weblogic ...
This Exception occurred at Tue Jul 3 :56: IST .
weblogic.utils.NestedError: Local host not known?!
 at weblogic.rjvm.JVMID.setLocalClientID(JVMID.java:9)
 at weblogic.rjvm.JVMID.localID(JVMID.java:8)
 at weblogic.protocol.LocalServerIdentity$SingletonMaker.<clinit>(LocalServerIdentity.java:3)
 at weblogic.protocol.LocalServerIdentity.getIdentity(LocalServerIdentity.java:)
 at weblogic.server.channels.ServerChannelImpl.createDefaultServerChannel(ServerChannelImpl.java:3)
 at weblogic.rjvm.t3.ProtocolHandlerT3$ChannelInitializer.<clinit>(ProtocolHandlerT3.java:3)
 at weblogic.rjvm.t3.ProtocolHandlerT3.getDefaultServerChannel(ProtocolHandlerT3.java:4)
 at weblogic.protocol.ServerChannelManager$SingletonMaker$.getOutboundServerChannel(ServerChannelManager.java:339)
 at weblogic.protocol.ServerChannelManager.findOutboundServerChannel(ServerChannelManager.java:43)
 at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(RJVMManager.java:3)
 at weblogic.rjvm.RJVMManager.findOrCreate(RJVMManager.java:94)
 at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(RJVMFinder.java:5)
 at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:88)
 at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:53)
 at weblogic.jndi.WLInitialContextFactoryDelegate$.run(WLInitialContextFactoryDelegate.java:344)
 at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
 at weblogic.security.service.SecurityManager.runAs(Unknown Source)
 at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:339)
 at weblogic.jndi.Environment.getContext(Environment.java:35)
 at weblogic.jndi.Environment.getContext(Environment.java:85)
 at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:)
 at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:66)
 at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:88)
 at javax.naming.InitialContext.init(InitialContext.java:3)
 at javax.naming.InitialContext.<init>(InitialContext.java:9)
 at weblogic.management.scripting.WLSTHelper.populateInitialContext(WLSTHelper.java:5)
 at weblogic.management.scripting.WLSTHelper.initDeprecatedConnection(WLSTHelper.java:565)
 at weblogic.management.scripting.WLSTHelper.initConnections(WLSTHelper.java:35)
 at weblogic.management.scripting.WLSTHelper.connect(WLSTHelper.java:3)
 at weblogic.management.scripting.WLScriptContext.connect(WLScriptContext.java:6)
 at weblogic.management.scripting.utils.WLSTUtil.initializeOnlineWLST(WLSTUtil.java:5)
 at sun.reflect.NativeMethodAccessorImpl.invoke(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:5)
 at java.lang.reflect.Method.invoke(Method.java:59)
 at org.python.core.PyReflectedFunction.__call__(PyReflectedFunction.java:6)
 at org.python.core.PyMethod.__call__(PyMethod.java:96)
 at org.python.core.PyObject.__call__(PyObject.java:48)
 at org.python.core.PyObject.invoke(PyObject.java:6)
 at org.python.pycode._pyx4.connect$(<iostream>:6)
 at org.python.pycode._pyx4.call_function(<iostream>)
 at org.python.core.PyTableCode.call(PyTableCode.java:8)
 at org.python.core.PyTableCode.call(PyTableCode.java:44)
 at org.python.core.PyTableCode.call(PyTableCode.java:8)
 at org.python.core.PyFunction.__call__(PyFunction.java:9)
 at org.python.pycode._pyx6.initConfigToScriptRun$(C:\Documents and Settings\Abhishek\.configWizard\tmp\config.py:5)
 at org.python.pycode._pyx6.call_function(C:\Documents and Settings\Abhishek\.configWizard\tmp\config.py)
 at org.python.core.PyTableCode.call(PyTableCode.java:8)
 at org.python.core.PyTableCode.call(PyTableCode.java:56)
 at org.python.core.PyFunction.__call__(PyFunction.java:69)
 at org.python.pycode._pyx6.f$(C:\Documents and Settings\Abhishek\.configWizard\tmp\config.py:66)
 at org.python.pycode._pyx6.call_function(C:\Documents and Settings\Abhishek\.configWizard\tmp\config.py)
 at org.python.core.PyTableCode.call(PyTableCode.java:8)
 at org.python.core.PyCode.call(PyCode.java:4)
 at org.python.core.Py.runCode(Py.java:35)
 at org.python.util.PythonInterpreter.execfile(PythonInterpreter.java:6)
 at weblogic.management.scripting.WLST.main(WLST.java:9)
 at sun.reflect.NativeMethodAccessorImpl.invoke(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:5)
 at java.lang.reflect.Method.invoke(Method.java:59)
 at weblogic.WLST.main(WLST.java:9)
Caused by: java.net.UnknownHostException: HOME-MITTAL: HOME-MITTAL
 at java.net.InetAddress.getLocalHost(InetAddress.java:353)
 at weblogic.rjvm.JVMID.setLocalClientID(JVMID.java:5)
 ... 6 more
No server running at t3://192.168.1.3: or the user/password is wrong
Exiting WebLogic Scripting Tool.
Even I tried using hostname as "localhost" but still I am facing the same issue.
Please suggest what is the resolution for the same.
Thanks,
Abhishek

Hi,
I was getting same excepction when tried to configure weblogic server (10.3.3 and 10gR3) through BPM Configuration Wizard, so I end up doing everything manually, like setting up JDBC data sources, JMS Server, JMS Modules and created DB (Directory & Engine).
Now, I am stuck at the last step of deploying the EAR files generated using BPM Process Administrator, they EAR's are generated fine but while deploying them to Weblogic server (through BPM Process Administrator), getting following exception (for "01-eng-bpmengine.ear")
<Servlet: "engineStartup" failed to preload on startup in Web application: "/albpmServices/bpmengine".
fuego.directory.DirectoryRuntimeException: Exception [java.sql.SQLException: Invalid column type].
 at fuego.directory.DirectoryRuntimeException.wrapException(DirectoryRuntimeException.java:85)
 at fuego.directory.provider.jdbc.oracle.OraclePersistenceManager.mapSQLException(OraclePersistenceManager.java:183)
 at fuego.directory.provider.jdbc.datadirect.oracle.DataDirectOraclePersistenceManager.mapSQLException(DataDirectOraclePersistenceManager.java:50)
 at fuego.directory.provider.jdbc.JDBCServiceAccessor.mapSQLException(JDBCServiceAccessor.java:78)
 at fuego.directory.provider.jdbc.JDBCParticipantsAccessor.fetchHumanParticipant(JDBCParticipantsAccessor.java:1423)
 at fuego.directory.provider.jdbc.JDBCParticipantsAccessor.authenticateHumanParticipant(JDBCParticipantsAccessor.java:370)
 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 fuego.directory.provider.DirectorySessionImpl$AccessorProxy.invoke(DirectorySessionImpl.java:756)
 at $Proxy246.authenticateHumanParticipant(Unknown Source)
 at fuego.directory.provider.jdbc.JDBCAuthenticationAccessor.getSessionParticipant(JDBCAuthenticationAccessor.java:429)
 at fuego.directory.provider.jdbc.JDBCAuthenticationAccessor.authenticateInternal(JDBCAuthenticationAccessor.java:323)
 at fuego.directory.provider.jdbc.JDBCAuthenticationAccessor.authenticate(JDBCAuthenticationAccessor.java:73)
 at fuego.directory.provider.jdbc.JDBCAuthenticationAccessor.connect(JDBCAuthenticationAccessor.java:127)
 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 fuego.directory.provider.DirectorySessionImpl$AccessorProxy.invoke(DirectorySessionImpl.java:756)
 at $Proxy243.connect(Unknown Source)
 at fuego.directory.provider.DirectorySessionImpl.connect(DirectorySessionImpl.java:250)
 at fuego.directory.provider.Factory.startSession(Factory.java:405)
 at fuego.directory.provider.jdbc.j2ee.RemoteJdbcDirectoryFactory.startSession(RemoteJdbcDirectoryFactory.java:122)
 at fuego.directory.Directory.startSession(Directory.java:268)
 at fuego.ejbengine.Engine.initDirectorySession(Engine.java:351)
 at fuego.ejbengine.Engine.start(Engine.java:122)
 at fuego.ejbengine.servlet.AbstractSchedulerServlet.init(AbstractSchedulerServlet.java:91)
 at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:283)
 at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
 at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
 at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64)
 at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
 at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)
 at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:539)
 at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1976)
 at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1950)
 at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1869)
 at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3126)
 at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1512)
 at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:486)
 at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
 at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
 at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
 at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
 at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
 at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
 at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
 at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
 at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
 at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:1267)
 at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
 at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:409)
 at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:58)
 at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
 at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
 at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
 at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150)
 at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)
 at weblogic.deploy.internal.targetserver.operations.StartOperation.doCommit(StartOperation.java:143)
 at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
 at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
 at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
 at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)
 at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
 at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
 at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
 at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)
 at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
 at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
 at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused By: java.sql.SQLException: Invalid column type
 at oracle.jdbc.driver.SQLStateMapping.newSQLException(SQLStateMapping.java:70)
 at oracle.jdbc.driver.DatabaseError.newSQLException(DatabaseError.java:133)
 at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:199)
 at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:263)
 at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:271)
 at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:445)
 at oracle.jdbc.driver.OraclePreparedStatement.setObjectCritical(OraclePreparedStatement.java:7975)
 at oracle.jdbc.driver.OraclePreparedStatement.setObjectInternal(OraclePreparedStatement.java:7555)
 at oracle.jdbc.driver.OraclePreparedStatement.setObject(OraclePreparedStatement.java:8028)
 at oracle.jdbc.driver.OraclePreparedStatementWrapper.setObject(OraclePreparedStatementWrapper.java:238)
 at weblogic.jdbc.wrapper.PreparedStatement.setObject(PreparedStatement.java:324)
 at fuego.jdbc.FaultTolerantPreparedStatement.setString(FaultTolerantPreparedStatement.java:436)
 at fuego.directory.provider.jdbc.JDBCPersistenceManager.setStringAttribute(JDBCPersistenceManager.java:896)
 at fuego.directory.provider.jdbc.JDBCParticipantsAccessor.fetchHumanParticipant(JDBCParticipantsAccessor.java:1417)
 at fuego.directory.provider.jdbc.JDBCParticipantsAccessor.authenticateHumanParticipant(JDBCParticipantsAccessor.java:370)
 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 fuego.directory.provider.DirectorySessionImpl$AccessorProxy.invoke(DirectorySessionImpl.java:756)
 at $Proxy246.authenticateHumanParticipant(Unknown Source)
 at fuego.directory.provider.jdbc.JDBCAuthenticationAccessor.getSessionParticipant(JDBCAuthenticationAccessor.java:429)
 at fuego.directory.provider.jdbc.JDBCAuthenticationAccessor.authenticateInternal(JDBCAuthenticationAccessor.java:323)
 at fuego.directory.provider.jdbc.JDBCAuthenticationAccessor.authenticate(JDBCAuthenticationAccessor.java:73)
 at fuego.directory.provider.jdbc.JDBCAuthenticationAccessor.connect(JDBCAuthenticationAccessor.java:127)
 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 fuego.directory.provider.DirectorySessionImpl$AccessorProxy.invoke(DirectorySessionImpl.java:756)
 at $Proxy243.connect(Unknown Source)
 at fuego.directory.provider.DirectorySessionImpl.connect(DirectorySessionImpl.java:250)
 at fuego.directory.provider.Factory.startSession(Factory.java:405)
 at fuego.directory.provider.jdbc.j2ee.RemoteJdbcDirectoryFactory.startSession(RemoteJdbcDirectoryFactory.java:122)
 at fuego.directory.Directory.startSession(Directory.java:268)
 at fuego.ejbengine.Engine.initDirectorySession(Engine.java:351)
 at fuego.ejbengine.Engine.start(Engine.java:122)
 at fuego.ejbengine.servlet.AbstractSchedulerServlet.init(AbstractSchedulerServlet.java:91)
 at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:283)
 at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
 at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
 at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64)
 at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
 at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)
 at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:539)
 at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1976)
 at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1950)
 at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1869)
 at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3126)
 at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1512)
 at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:486)
 at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
 at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
 at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
 at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
 at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
 at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
 at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
 at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
 at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
 at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:1267)
 at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
 at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:409)
 at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:58)
 at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
 at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
 at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
 at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150)
 at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)
 at weblogic.deploy.internal.targetserver.operations.StartOperation.doCommit(StartOperation.java:143)
 at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
 at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
 at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
 at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)
 at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
 at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
 at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
 at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)
 at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
 at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
 at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
my assumption is JDBC Data Sources or the Directory/Engine database have some column name mismatch.
Let me know if somebody has a solution for this, or if I am doing something wrong.
NOTE: just found out that this happens only on Windows 2003 server, but not on OEL5 (Oracle Enterprise Linux 5).
Thanks !!

Using Apache Directory Server with BPM Enterprise - BPM Admin Center

Hi All,
I m trying to configure BPM Admin Center in BPM Enterprise standalone. I would prefer to use an external directory service.
Can I use Apache Directory Server ? If yes, please let me know how to configure it else please suggest me the possible directory servers I can use.
I would like to use an open source directory server.
Hope to hear soon.
Many Thanks,
Sophie

Hi All,
I m trying to configure BPM Admin Center in BPM Enterprise standalone. I would prefer to use an external directory service.
Can I use Apache Directory Server ? If yes, please let me know how to configure it else please suggest me the possible directory servers I can use.
I would like to use an open source directory server.
Hope to hear soon.
Many Thanks,
Sophie

OutOfMemoryError when running Oracle BPM Enterprise's Configuration Wizard

Hi,
I was trying to configure Oracle BPM Enterprise via Oracle BPM Admin Center. I left most of the settings to their respective default values; only adding in passwords for the Directory, Engine, etc. However an error was encountered when it is trying to deploy the '01-eng-bpmengine' EAR file. A 'OutOfMemoryError: Java heap space' was logged after running the configuration for a while. Below is the full error log:
AdmCenterConsole.log
FuegoLauncher.main()
fix classpath: C:\OraBPMwlHome\bin;C:\OraBPMwlHome\bin\lax.jar;
new classpath: C:\OraBPMwlHome\bin\lax.jar;FuegoLauncher.main() - 2
arg[0] = C:\OraBPMwlHome\bin\obpmadmcenter.properties
StreamLogOutput: No log file specified in property 'fuego.log.admcenter.file'.
Defaulting to System.err.
[ 03/03/09 20:54:12]
[ 03/03/09 20:54:12] CLASSPATH=C:\bea\patch_wlw1030\profiles\default\sys_manifest_classpath\weblogic_patch.jar;C:\bea\patch_wls1030\profiles\default\sys_manifest_classpath\weblogic_patch.jar;C:\bea\patch_cie660\profiles\default\sys_manifest_classpath\weblogic_patch.jar;C:\Java\JDK16~1.0_1\lib\tools.jar;C:\bea\WLSERV~1.3\server\lib\weblogic_sp.jar;C:\bea\WLSERV~1.3\server\lib\weblogic.jar;C:\bea\modules\features\weblogic.server.modules_10.3.0.0.jar;C:\bea\WLSERV~1.3\server\lib\webservices.jar;C:\bea\modules\ORGAPA~1.5/lib/ant-all.jar;C:\bea\modules\NETSFA~1.0_1/lib/ant-contrib.jar;
[ 03/03/09 20:54:12]
[ 03/03/09 20:54:12] PATH=C:\bea\patch_wlw1030\profiles\default\native;C:\bea\patch_wls1030\profiles\default\native;C:\bea\patch_cie660\profiles\default\native;C:\bea\WLSERV~1.3\server\native\win\32;C:\bea\WLSERV~1.3\server\bin;C:\bea\modules\ORGAPA~1.5\bin;C:\Java\JDK16~1.0_1\jre\bin;C:\Java\JDK16~1.0_1\bin;C:\oracle\product\10.2.0\db_1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Common Files\Roxio Shared\DLLShared\;C:\Program Files\Common Files\Roxio Shared\DLLShared\;C:\Program Files\Common Files\Roxio Shared\9.0\DLLShared\;C:\Java\jdk1.6.0_10\bin;C:\apache-ant-1.6.5\bin;C:\bea\WLSERV~1.3\server\native\win\32\oci920_8
[ 03/03/09 20:54:12]
[ 03/03/09 20:54:12] Your environment has been set.
[ 03/03/09 20:54:12]
[ 03/03/09 20:54:12] CLASSPATH=C:\bea\patch_wlw1030\profiles\default\sys_manifest_classpath\weblogic_patch.jar;C:\bea\patch_wls1030\profiles\default\sys_manifest_classpath\weblogic_patch.jar;C:\bea\patch_cie660\profiles\default\sys_manifest_classpath\weblogic_patch.jar;C:\Java\JDK16~1.0_1\lib\tools.jar;C:\bea\WLSERV~1.3\server\lib\weblogic_sp.jar;C:\bea\WLSERV~1.3\server\lib\weblogic.jar;C:\bea\modules\features\weblogic.server.modules_10.3.0.0.jar;C:\bea\WLSERV~1.3\server\lib\webservices.jar;C:\bea\modules\ORGAPA~1.5/lib/ant-all.jar;C:\bea\modules\NETSFA~1.0_1/lib/ant-contrib.jar;;C:\bea\WLSERV~1.3\common\eval\pointbase\lib\pbembedded57.jar;C:\bea\WLSERV~1.3\common\eval\pointbase\lib\pbtools57.jar;C:\bea\WLSERV~1.3\common\eval\pointbase\lib\pbclient57.jar
[ 03/03/09 20:54:13]
[ 03/03/09 20:54:13] Initializing WebLogic Scripting Tool (WLST) ...
[ 03/03/09 20:54:13]
[ 03/03/09 20:54:19] Welcome to WebLogic Server Administration Scripting Shell
[ 03/03/09 20:54:19]
[ 03/03/09 20:54:19] Type help() for help on available commands
[ 03/03/09 20:54:19]
[ 03/03/09 20:54:19] t3://SN-06-SHENGYUEN:7001
[ 03/03/09 20:54:20] Connecting to t3://SN-06-SHENGYUEN:7001 with userid weblogic ...
[ 03/03/09 20:54:22] Successfully connected to Admin Server 'AdminServer' that belongs to domain 'oft'.
[ 03/03/09 20:54:22]
[ 03/03/09 20:54:22] Warning: An insecure protocol was used to connect to the
[ 03/03/09 20:54:22] server. To ensure on-the-wire security, the SSL port or
[ 03/03/09 20:54:22] Admin port should be used instead.
[ 03/03/09 20:54:22]
[ 03/03/09 20:54:22] Location changed to edit tree. This is a writable tree with
[ 03/03/09 20:54:22] DomainMBean as the root. To make changes you will need to start
[ 03/03/09 20:54:22] an edit session via startEdit().
[ 03/03/09 20:54:22]
[ 03/03/09 20:54:22] For more help, use help(edit)
[ 03/03/09 20:54:22]
[ 03/03/09 20:54:22] Starting an edit session ...
[ 03/03/09 20:54:22] Started edit session, please be sure to save and activate your
[ 03/03/09 20:54:22] changes once you are done.
[ 03/03/09 20:54:22] creating mbean of type JMSServer ...
[ 03/03/09 20:54:22] creating mbean of type JMSSystemResource ...
[ 03/03/09 20:54:22] creating mbean of type SubDeployment ...
[ 03/03/09 20:54:22] creating mbean of type Queue ...
[ 03/03/09 20:54:22] creating mbean of type Topic ...
[ 03/03/09 20:54:22] creating mbean of type ConnectionFactory ...
[ 03/03/09 20:54:22] creating mbean of type ConnectionFactory ...
[ 03/03/09 20:54:22] creating mbean of type JDBCSystemResource ...
[ 03/03/09 20:54:22] creating mbean of type Property ...
[ 03/03/09 20:54:22] creating mbean of type Property ...
[ 03/03/09 20:54:22] creating mbean of type Property ...
[ 03/03/09 20:54:22] creating mbean of type Property ...
[ 03/03/09 20:54:22] creating mbean of type JDBCSystemResource ...
[ 03/03/09 20:54:22] creating mbean of type Property ...
[ 03/03/09 20:54:22] creating mbean of type Property ...
[ 03/03/09 20:54:22] creating mbean of type Property ...
[ 03/03/09 20:54:22] creating mbean of type Property ...
[ 03/03/09 20:54:22] setting attributes for mbean type JMSServer
[ 03/03/09 20:54:22] setting attributes for mbean type JMSSystemResource
[ 03/03/09 20:54:22] setting attributes for mbean type SubDeployment
[ 03/03/09 20:54:22] setting attributes for mbean type Queue
[ 03/03/09 20:54:22] setting attributes for mbean type Topic
[ 03/03/09 20:54:22] setting attributes for mbean type JMSConnectionFactory
[ 03/03/09 20:54:22] setting attributes for mbean type JMSConnectionFactory
[ 03/03/09 20:54:22] setting attributes for mbean type JDBCSystemResource
[ 03/03/09 20:54:22] setting attributes for mbean type JDBCProperty
[ 03/03/09 20:54:22] setting attributes for mbean type JDBCProperty
[ 03/03/09 20:54:22] setting attributes for mbean type JDBCProperty
[ 03/03/09 20:54:22] setting attributes for mbean type JDBCProperty
[ 03/03/09 20:54:22] setting attributes for mbean type JDBCConnectionPoolParams
[ 03/03/09 20:54:22] setting attributes for mbean type JDBCDriverParams
[ 03/03/09 20:54:22] setting attributes for mbean type JDBCDataSource
[ 03/03/09 20:54:22] setting attributes for mbean type JDBCDataSource
[ 03/03/09 20:54:22] setting attributes for mbean type JDBCXAParams
[ 03/03/09 20:54:22] setting attributes for mbean type JDBCDataSourceParams
[ 03/03/09 20:54:22] setting attributes for mbean type JDBCConnectionPoolParams
[ 03/03/09 20:54:22] setting attributes for mbean type JDBCDriverParams
[ 03/03/09 20:54:22] setting attributes for mbean type JDBCDataSourceParams
[ 03/03/09 20:54:22] setting attributes for mbean type JDBCSystemResource
[ 03/03/09 20:54:22] setting attributes for mbean type JDBCProperty
[ 03/03/09 20:54:22] setting attributes for mbean type JDBCProperty
[ 03/03/09 20:54:22] setting attributes for mbean type JDBCProperty
[ 03/03/09 20:54:22] setting attributes for mbean type JDBCProperty
[ 03/03/09 20:54:22] Saving all your changes ...
[ 03/03/09 20:54:22] Saved all your changes successfully.
[ 03/03/09 20:54:22] Your edit session is not stopped, you can continue your edits.
[ 03/03/09 20:54:22] Activating all your changes, this may take a while ...
[ 03/03/09 20:54:22] The edit lock associated with this edit session is released
[ 03/03/09 20:54:22] once the activation is completed.
[ 03/03/09 20:54:23] Activation completed
[ 03/03/09 20:54:23] Creating a user ...
[ 03/03/09 20:54:23]
[ 03/03/09 20:54:23] User already exist
[ 03/03/09 20:54:23] Deploying application from C:\OraBPMwlHome\j2ee\weblogic\deployer\wlj2eedeployer.ear to targets AdminServer (upload=true) ...
[ 03/03/09 20:54:23] <Mar 3, 2009 8:54:23 PM SGT> <Info> <J2EE Deployment SPI> <BEA-260121> <Initiating deploy operation for application, wlj2eedeployer [archive: C:\OraBPMwlHome\j2ee\weblogic\deployer\wlj2eedeployer.ear], to AdminServer .>
[ 03/03/09 20:54:27] .Completed the deployment of Application with status completed
[ 03/03/09 20:54:27] Current Status of your Deployment:
[ 03/03/09 20:54:27] Deployment command type: deploy
[ 03/03/09 20:54:27] Deployment State : completed
[ 03/03/09 20:54:27] Deployment Message : no message
[ 03/03/09 20:54:27] Deploying application from C:\OraBPMwlHome\ears\engine\01-eng-bpmengine.ear to targets AdminServer (upload=true) ...
[ 03/03/09 20:54:27] <Mar 3, 2009 8:54:27 PM SGT> <Info> <J2EE Deployment SPI> <BEA-260121> <Initiating deploy operation for application, 01-eng-bpmengine [archive: C:\OraBPMwlHome\ears\engine\01-eng-bpmengine.ear], to AdminServer .>
[ 03/03/09 20:54:43] Failed to deploy the application with status failed
[ 03/03/09 20:54:43] Current Status of your Deployment:
[ 03/03/09 20:54:43] Deployment command type: deploy
[ 03/03/09 20:54:43] Deployment State : failed
[ 03/03/09 20:54:43] Deployment Message : java.lang.OutOfMemoryError: Java heap space
[ 03/03/09 20:54:43] weblogic.management.scripting.ScriptException: Error occured while performing deploy : Deployment Failed.
[ 03/03/09 20:54:43] at weblogic.management.scripting.ExceptionHandler.handleException(ExceptionHandler.java:48)
[ 03/03/09 20:54:43] at weblogic.management.scripting.WLSTUtils.throwWLSTException(WLSTUtils.java:185)
[ 03/03/09 20:54:43] at weblogic.management.scripting.JSR88DeployHandler.deploy(JSR88DeployHandler.java:536)
[ 03/03/09 20:54:43] at weblogic.management.scripting.WLScriptContext.deploy(WLScriptContext.java:429)
[ 03/03/09 20:54:43] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[ 03/03/09 20:54:43] No stack trace available.
[ 03/03/09 20:54:43] This Exception occurred at Tue Mar 03 20:54:43 SGT 2009.
[ 03/03/09 20:54:43] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
[ 03/03/09 20:54:43] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
[ 03/03/09 20:54:43] at java.lang.reflect.Method.invoke(Method.java:597)
[ 03/03/09 20:54:43] at org.python.core.PyReflectedFunction.__call__(PyReflectedFunction.java:160)
[ 03/03/09 20:54:43] at org.python.core.PyMethod.__call__(PyMethod.java:96)
[ 03/03/09 20:54:43] at org.python.core.PyObject.__call__(PyObject.java:248)
[ 03/03/09 20:54:43] at org.python.core.PyObject.invoke(PyObject.java:2016)
[ 03/03/09 20:54:43] at org.python.pycode._pyx17.deploy$8(<iostream>:223)
[ 03/03/09 20:54:43] at org.python.pycode._pyx17.call_function(<iostream>)
[ 03/03/09 20:54:43] at org.python.core.PyTableCode.call(PyTableCode.java:208)
[ 03/03/09 20:54:43] at org.python.core.PyTableCode.call(PyTableCode.java:404)
[ 03/03/09 20:54:43] at org.python.core.PyFunction.__call__(PyFunction.java:184)
[ 03/03/09 20:54:43] at org.python.pycode._pyx16.deploy_Applications$61(C:\Documents and Settings\shengyuen\.configWizard\tmp\config.py:623)
[ 03/03/09 20:54:43] at org.python.pycode._pyx16.call_function(C:\Documents and Settings\shengyuen\.configWizard\tmp\config.py)
[ 03/03/09 20:54:43] at org.python.core.PyTableCode.call(PyTableCode.java:208)
[ 03/03/09 20:54:43] at org.python.core.PyTableCode.call(PyTableCode.java:256)
[ 03/03/09 20:54:43] at org.python.core.PyFunction.__call__(PyFunction.java:169)
[ 03/03/09 20:54:43] at org.python.pycode._pyx16.f$0(C:\Documents and Settings\shengyuen\.configWizard\tmp\config.py:738)
[ 03/03/09 20:54:43] at org.python.pycode._pyx16.call_function(C:\Documents and Settings\shengyuen\.configWizard\tmp\config.py)
[ 03/03/09 20:54:43] at org.python.core.PyTableCode.call(PyTableCode.java:208)
[ 03/03/09 20:54:43] at org.python.core.PyCode.call(PyCode.java:14)
[ 03/03/09 20:54:43] at org.python.core.Py.runCode(Py.java:1135)
[ 03/03/09 20:54:43] at org.python.util.PythonInterpreter.execfile(PythonInterpreter.java:167)
[ 03/03/09 20:54:43]
[ 03/03/09 20:54:43] Exiting WebLogic Scripting Tool.
[ 03/03/09 20:54:43]
[ 03/03/09 20:54:43]
[ 03/03/09 20:54:43] at weblogic.management.scripting.WLST.main(WLST.java:129)
[ 03/03/09 20:54:43] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[ 03/03/09 20:54:43] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
[ 03/03/09 20:54:43] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
[ 03/03/09 20:54:43] at java.lang.reflect.Method.invoke(Method.java:597)
[ 03/03/09 20:54:43] at weblogic.WLST.main(WLST.java:29)
[ 03/03/09 20:54:43] <Mar 3, 2009 8:54:43 PM SGT> <Warning> <JNDI> <BEA-050001> <WLContext.close() was called in a different thread than the one in which it was created.>
Is there any way that I can increase the heap size of the Configuration Wizard? If not, is there any solution to this problem?

Hi,
It seems to be a Weblogic OOM (OutOfMemory).
Why don't you try increasing the weblogic memory (you have to modify your domain scripts)
I guess that after increasing your WLS domain memory settings you will be able to configure it using the config wizard.
Hope this helps,
Ariel

Issue with Deploying and calling a BPEL process on ALBPM enterprise server

Hi,
I am trying to put in place a POC using Aqualogic BEA products (using ALBPM 5.7, Enterprise Server 5.7, ALSB 2.6, Weblogic App server 9.2). My goal is to put in place a simple BPEL process (using ALBPM) which would call a webservice exposed through ALSB. This BPEL process is initiated by a wrapper BPMN process calling the BPEL process through fuego code.
Though we are able to do the above on a standalone ALBPM studio, When we try to deploy the exported BPM project on the enterprise server and access it through the hiper workspace portal we are getting the following error in the BPM Process Administrator Log of the Engine.
A component failed while executing activity '/Process#Default-1.0/Global' (BP-method Global). Details: The task could not be successfully executed. Reason: 'fuego.connector.ConnectorException: The configuration name [ProcessService] and type [Web Service] is not defined. Detail:The connector must be configured in the appropiate context. '. Caused by: The configuration name [ProcessService] and type [Web Service] is not defined. Detail:The connector must be configured in the appropiate context. fuego.lang.ComponentExecutionException: The task could not be successfully executed. Reason: 'fuego.connector.ConnectorException: The configuration name [ProcessService] and type [Web Service] is not defined. Detail:The connector must be configured in the appropiate context. '. at fuego.server.execution.EngineExecutionContext.invokeMethodAsCil(EngineExecutionContext.java:916) at fuego.server.execution.EngineExecutionContext.runCil(EngineExecutionContext.java:1068) at fuego.server.execution.TaskExecution.invoke(TaskExecution.java:389) at fuego.server.execution.GlobalTaskExecution.invoke(GlobalTaskExecution.java:106) at fuego.server.execution.TaskExecution.executeCIL(TaskExecution.java:481) at fuego.server.execution.TaskExecution.executeTask(TaskExecution.java:655) at fuego.server.execution.TaskExecution.executeTask(TaskExecution.java:616) at fuego.server.execution.TaskExecution.executeTask(TaskExecution.java:442) at fuego.server.execution.GlobalTaskExecution.executeGlobalCIL(GlobalTaskExecution.java:164) at fuego.server.execution.GlobalTaskExecution.executeGlobalCIL(GlobalTaskExecution.java:142) at fuego.server.execution.Global.execute(Global.java:81) at fuego.server.AbstractProcessBean$38.execute(AbstractProcessBean.java:2496) at fuego.server.execution.DefaultEngineExecution$AtomicExecutionTA.runTransaction(DefaultEngineExecution.java:290) at fuego.transaction.TransactionAction.startBaseTransaction(TransactionAction.java:462) at fuego.transaction.TransactionAction.startTransaction(TransactionAction.java:540) at fuego.transaction.TransactionAction.start(TransactionAction.java:213) at fuego.server.execution.DefaultEngineExecution.executeImmediate(DefaultEngineExecution.java:117) at fuego.server.execution.EngineExecution.executeImmediate(EngineExecution.java:66) at fuego.server.AbstractProcessBean.runGlobalActivity(AbstractProcessBean.java:2491) at fuego.ejbengine.EJBProcessControlAdapter.runGlobalActivity(EJBProcessControlAdapter.java:386) at fuego.ejbengine.EJBProcessControlAdapter_hu750h_EOImpl.runGlobalActivity(EJBProcessControlAdapter_hu750h_EOImpl.java:2877) at fuego.ejbengine.EJBProcessControlAdapter_hu750h_EOImpl_WLSkel.invoke(Unknown Source) at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:174) at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:335) at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:252) at fuego.ejbengine.EJBProcessControlAdapter_hu750h_EOImpl_921_WLStub.runGlobalActivity(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:585) at fuego.papi.impl.AbstractProcessControlHandler.invokeInternal(AbstractProcessControlHandler.java:48) at fuego.papi.impl.j2ee.EJBProcessControlHandler.doInvoke(EJBProcessControlHandler.java:111) at fuego.papi.impl.j2ee.EJBProcessControlHandler.invoke(EJBProcessControlHandler.java:66) at $Proxy77.runGlobalActivity(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:585) at fuego.lang.JavaClass.invokeMethod(JavaClass.java:1478) at fuego.lang.JavaObject.invoke(JavaObject.java:185) at fuego.papi.impl.j2ee.EJBExecution.next(EJBExecution.java:200) at fuego.portal.wapi.InteractiveExecution.process(InteractiveExecution.java:157) at fuego.portal.wapi.WebInteractiveExecution.process(WebInteractiveExecution.java:54) at fuego.portal.wapi.InteractiveExecution.process(InteractiveExecution.java:200) at fuego.portal.servlet.ExecutionDispatcher.runGlobalActivity(ExecutionDispatcher.java:659) at fuego.portal.servlet.ExecutionDispatcher.processRequest(ExecutionDispatcher.java:144) at fuego.portal.servlet.ExecutionDispatcher.doPost(ExecutionDispatcher.java:105) at javax.servlet.http.HttpServlet.service(HttpServlet.java:763) at fuego.portal.servlet.AuthenticatedWamServlet.service(AuthenticatedWamServlet.java:1049) at fuego.portal.servlet.SingleThreadPerSession.service(SingleThreadPerSession.java:73) at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:223) at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125) at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283) at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42) at fuego.servlet.multipart.BaseMultipartFilter.doFilter(BaseMultipartFilter.java:57) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42) at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3243) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121) at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2003) at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:1909) at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1359) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209) at weblogic.work.ExecuteThread.run(ExecuteThread.java:181) Caused by: fuego.connector.ConnectorException: The configuration name [ProcessService] and type [Web Service] is not defined. Detail:The connector must be configured in the appropiate context. at fuego.connector.ConnectorException.connectorNotFound(ConnectorException.java:55) at fuego.connector.ConnectorService.getConnectorInterface(ConnectorService.java:586) at fuego.connector.ConnectorTransaction.getConnectorInterface(ConnectorTransaction.java:618) at fuego.connector.ConnectorTransaction.getResource(ConnectorTransaction.java:254) at fuego.soaptype.WSConfiguration.getInstance(WSConfiguration.java:55) at fuego.soaptype.Endpoint.create(Endpoint.java:42) at fuego.soaptype.WebServiceInstantiator.instantiate(WebServiceInstantiator.java:58) at fuego.component.Component.instantiateDynamic(Component.java:123) at CapGemini.Process.Default_1_0.Instance.CIL_callBPEL(Instance.java:241) at CapGemini.Process.Default_1_0.Instance.CIL_callBPEL(Instance.java:307) 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.server.execution.EngineExecutionContext.invokeMethodAsCil(EngineExecutionContext.java:907) ... 64 more
Two things here that might help to understand the problem better :
1) As I understand the error is due to some issue while calling the BPEL process from the Fuego code.
The Fuego code which call's the BPEL from the BPMN process is as follows :
helloResponse as String = "someoutput"
helloRequest as String = "someinput"
sessionid as String
// Starting a Session.
// In case you are testing this in the Studio,
// the password must be the same as the user
startSession BPELWSDL.ProcessServiceListenerWSDL.ProcessService
using user = "test",
password = "test"
returning sessionid = result
// createTest is the name of the operation
// in the exposed process.
// In this case the process "ExposedProcess"
// has a web service operation
// called "createTest" that is a "Process Creation" type
// and uses the Begin activity's argument set
callHello BPELWSDL.ProcessServiceListenerWSDL.ProcessService
using sessionId = sessionid,
arg1 = helloRequest
returning helloResponse = result
// Closing the session
discardSession BPELWSDL.ProcessServiceListenerWSDL.ProcessService
using sessionId = sessionid
display "The BPEL's response : " + helloResponse
2) Further, I had catalogued the BPEL's wsdl to the location http://localhost:9000/fuegoServices/ws/ProcessServiceListener?WSDL while running the same in Studio, but while deploying on the enterprise server , I made this point to http://localhost:7001/fuegoServices/ws/ProcessServiceListener?WSDL Is this correct ?
Any thought on this issue would be appreciated.
Regards
Deepak

Hi Deepak,
We are also facing a similar problem, while accessing an external webservice from a BPM process.
Were you able to resolve this issue.
If so, Could you please let us know the procedure that you followed to resolve the issue.
Thanks in Advance,
Krishnaveni.

BPM Enterprise - Can's see the Deploy

Hello all
I am new to BPM and i am trying to deploy into bpm enterprise and i hope somebody could help me
I have installed and configured everything needed (weblogic server, bpm enterprise, bpm studio) and i configured and i have created a bpm directory service, bpm domain, etc (using the configuration wizard)
I am trying to deploy a sample proyect. I followed the admin guid and i deployed using Process Administrator --> Proyects, deploy etc (i used the option smart publish)
How can i access my deployed application???
I accessed to workspace application (using the admin account so that i have admin privileges and i can see all the deployments) and i don't see my deploy :(
Am I missing or doing something wrong?
Thanks in advance to all :)

Hi,
In the web based Process Administration tool, add a 'test' participant. Assign this participant all the roles inside your process.
Log into the Workspace using this new participant. If this doesn't work try starting and stopping the Engine from the Process Administration tool.
Hope this helps,
Dan

Adding an External Resource - ALBPM Enterprise Server V 6.0

Hi ,
In our BPM application, we are consuming an external webservice. In BPM studio, when we tested the application, It was working fine.
But when we deployed our application in Enterprise server, We are facing issues while invoking the external web service.
We are getting the following exception in the logs of Enterprise Server.
A component failed while executing activity '/LocateTerminal#Default-1.0/ComponentExecution[fetchlocation]' (BP-method fetchlocation) over instance '/LocateTerminal#Default-1.0/82/0'.
Details:
The method 'CIL_fetchlocation' from class 'bea.LocateTerminal.Default_1_0.Instance' could not be successfully executed.
Caused by: The configuration name [null] and type [Web Service] is not defined.
Detail:The connector must be configured in the appropiate context.
fuego.lang.ComponentExecutionException: The method 'CIL_fetchlocation' from class 'bea.LocateTerminal.Default_1_0.Instance' could not be successfully executed.
     at fuego.component.ExecutionThreadContext.invokeMethod(ExecutionThreadContext.java:506)
     at fuego.component.ExecutionThreadContext.invokeMethod(ExecutionThreadContext.java:260)
     at fuego.fengine.FEEngineExecutionContext.invokeMethodAsCil(FEEngineExecutionContext.java:215)
     at fuego.server.execution.EngineExecutionContext.runCil(EngineExecutionContext.java:1175)
     at fuego.server.execution.microactivity.ComponentExecutionMicroActivity.runCil(ComponentExecutionMicroActivity.java:127)
     at fuego.server.execution.microactivity.ComponentExecutionMicroActivity.execute(ComponentExecutionMicroActivity.java:85)
     at fuego.server.execution.microactivity.MicroActivityEngineExecutionHandler.executeActivity(MicroActivityEngineExecutionHandler.java:89)
     at fuego.server.execution.ImmediateActivity.execute(ImmediateActivity.java:42)
     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.DefaultEngineExecution.executeAutomaticWork(DefaultEngineExecution.java:63)
     at fuego.server.execution.EngineExecution.executeAutomaticWork(EngineExecution.java:42)
     at fuego.server.execution.ToDoItem.executeAutomaticWork(ToDoItem.java:264)
     at fuego.server.execution.ToDoItem.run(ToDoItem.java:559)
     at fuego.component.ExecutionThread.processMessage(ExecutionThread.java:767)
     at fuego.component.ExecutionThread.processBatch(ExecutionThread.java:747)
     at fuego.component.ExecutionThread.doProcessBatch(ExecutionThread.java:143)
     at fuego.component.ExecutionThread.doProcessBatch(ExecutionThread.java:135)
     at fuego.fengine.ToDoQueueThread$PrincipalWrapper.processBatch(ToDoQueueThread.java:446)
     at fuego.component.ExecutionThread.work(ExecutionThread.java:831)
     at fuego.component.ExecutionThread.run(ExecutionThread.java:409)
Caused by: fuego.connector.ConnectorException: The configuration name [null] and type [Web Service] is not defined.
Detail:The connector must be configured in the appropiate context.
     at fuego.connector.ConnectorException.connectorNotFound(ConnectorException.java:55)
     at fuego.connector.CompositeConnectorService.getConnectorInterface(CompositeConnectorService.java:268)
     at fuego.connector.ConnectorTransaction.registerConnectorInterfaceCoordinator(ConnectorTransaction.java:649)
     at fuego.connector.ConnectorTransaction.getResource(ConnectorTransaction.java:265)
     at fuego.webservices.connector.WSConfiguration.create(WSConfiguration.java:57)
     at fuego.soaptype.WebServiceInstantiator.instantiate(WebServiceInstantiator.java:70)
     at fuego.component.Component.instantiateDynamic(Component.java:133)
     at bea.LocateTerminal.Default_1_0.Instance.CIL_fetchlocation(Instance.xcdl:3)
     at bea.LocateTerminal.Default_1_0.Instance.CIL_fetchlocation(Instance.xcdl)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
     at java.lang.reflect.Method.invoke(Unknown Source)
     at fuego.component.ExecutionThreadContext.invokeMethod(ExecutionThreadContext.java:499)
Can you please tell me , to how to configure an external webservice in Enterprise Server.
please help me in resolving this issue.
Thanks,
Krishnaveni.

Hi,
There is nothing to do with the versioning. There is a problem with the tool (Configuration Wizard).
This is how the problem was solved,
After creating the Directory Service start and login to the Process Admininstrator,
ALBPM web console-> Organizational settings->Export->Views, export the views.xml and check for any invalid characters.
After removing the invalid characters save the xml and import the modified views.xml to the same location.
This should solve the problem.
Thanks,
Krina

Can not able to log into the BPM workspace ?

Hi All,
I am using ALBPM 5.7 enterprise server and deployed my project into the enterprise server.
After the deployment when I tried to log into the workspace it is not taking any of the password.
PS: Before deployment I never tried to login to the workspace since I do not have user id for the project.
There are users in the participant wizard and I even tried to reset the password of existing user but it is still not working. I even tried to create a new participant but still it is not taking the password for the same user.
Is it like the new password/participant will get active only after certain time interval say 24 hrs.
But this is not the case of ALBPM 6.0 as far as my knowledge is concern.
Can somebody let me know where I made anything wrong.
If somebody has BPM administration document (Password Reset/Create participant in 5.7), please let me know.
Thanks in advance.
Bibhu
Edited by: Bibhuti Bhusan on Aug 18, 2010 9:57 PM

It sounds like you are trying to log into the workspace with the admin user..... not a participant.
The participants need to be set up in the Process Administrator, (which you will log in via the admin user / pass that was created for the engine).
Here are the 5.7 Documents: [http://download.oracle.com/docs/cd/E13165_01/albsi/docs57/index.html|http://download.oracle.com/docs/cd/E13165_01/albsi/docs57/index.html]
Specifically the 'Process Admin Document' at: [http://download.oracle.com/docs/cd/E13165_01/albsi/docs57/olh_processadministrator/index.html|http://download.oracle.com/docs/cd/E13165_01/albsi/docs57/olh_processadministrator/index.html]
HTH
-Kevin

BPM enterprise configuration

Hi all,
I am using BPM 10.3.1.
I configured BPM enterprise and try to start process engine from Process Admin console.
but i can't able to start it. I found the following error.
[HTTP:101216]Servlet: "engineStartup" failed to preload on startup in Web application: "/albpmServices/bpmenginetest". javax.ejb.EJBException: The directory schema used to generate this module does not match the schema that this server is connected to. at fuego.ejbengine.Engine.initDirectorySession(Engine.java:378) at fuego.ejbengine.Engine.start(Engine.java:129) at fuego.ejbengine.servlet.AbstractSchedulerServlet.init(AbstractSchedulerServlet.java:91) at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:283) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) at weblogic.security.service.SecurityManager.runAs(Unknown Source) at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64) at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58) at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48) at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:521) at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1893) at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1870) at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1790) at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:2999) at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1371) at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:468) at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37) at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60) at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200) at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:117) at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37) at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60) at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27) at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:635) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37) at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212) at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:16) at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:162) at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79) at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:140) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:106) at weblogic.deploy.internal.targetserver.operations.StartOperation.doCommit(StartOperation.java:143) at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323) at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:820) at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1227) at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:436) at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:181) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:12) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:67) at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201) at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)

I am getting this error when deploying bpm-engine using process admin
<Aug 26, 2010 9:11:56 AM EDT> <Notice> <StdErr> <BEA-000000> <engineId = bpm_dev_eng_04>
<Aug 26, 2010 9:11:56 AM EDT> <Notice> <StdErr> <BEA-000000> <- MailDispatcher switching to runlevel 4 (PRL:0)>
<Aug 26, 2010 9:11:57 AM EDT> <Error> <JDBC> <BEA-001112> <Test "select count(*) from SELECT 1 FROM DUAL" set up for pool "XAEngineDS" failed with exception: "java.sql.SQLException: [BEA][Oracle JDBC Driver][Oracle]ORA-00903: invalid table name
".>
<Aug 26, 2010 9:11:58 AM EDT> <Error> <HTTP> <BEA-101216> <Servlet: "engineStartup" failed to preload on startup in Web application: "/albpmServices/bpm_dev_eng_04".
fuego.server.exception.EngineRuntimeException: Server runtime exception. [BEA][Oracle JDBC Driver][Oracle]ORA-01031: insufficient privileges
 at fuego.server.exception.EngineRuntimeException.create(EngineRuntimeException.java:45)
 at fuego.server.service.EngineConnectorService.migrateTo(EngineConnectorService.java:2632)
 at fuego.server.service.EngineConnectorService.checkMigration(EngineConnectorService.java:1081)
 at fuego.server.service.EngineConnectorService.start(EngineConnectorService.java:413)
 at fuego.server.service.EngineConnectorService.initialize(EngineConnectorService.java:368)
 Truncated. see log file for complete stacktrace
java.sql.SQLException: [BEA][Oracle JDBC Driver][Oracle]ORA-01031: insufficient privileges
 at albpm.jdbc.base.BaseExceptions.createException(Unknown Source)
 at albpm.jdbc.base.BaseExceptions.getException(Unknown Source)
 at albpm.jdbc.oracle.OracleImplStatement.execute(Unknown Source)
 at albpm.jdbc.base.BaseStatement.commonExecute(Unknown Source)
 at albpm.jdbc.base.BaseStatement.executeInternal(Unknown Source)
 Truncated. see log file for complete stacktrace
>
<Aug 26, 2010 9:11:58 AM EDT> <Error> <Deployer> <BEA-149265> <Failure occurred in the execution of deployment request with ID '1282828304616' for task '24'. Error is: 'weblogic.application.ModuleException: [HTTP:101216]Servlet: "engineStartup" failed to preload on startup in Web application: "/albpmServices/bpm_dev_eng_04".
fuego.server.exception.EngineRuntimeException: Server runtime exception. [BEA][Oracle JDBC Driver][Oracle]ORA-01031: insufficient privileges
 at fuego.server.exception.EngineRuntimeException.create(EngineRuntimeException.java:45)
 at fuego.server.service.EngineConnectorService.migrateTo(EngineConnectorService.java:2632)
 at fuego.server.service.EngineConnectorService.checkMigration(EngineConnectorService.java:1081)
 at fuego.server.service.EngineConnectorService.start(EngineConnectorService.java:413)
 at fuego.server.service.EngineConnectorService.initialize(EngineConnectorService.java:368)
 at fuego.ejbengine.Engine.startServices(Engine.java:393)
 at fuego.ejbengine.Engine.start(Engine.java:119)
 at fuego.ejbengine.servlet.SchedulerServlet.init(SchedulerServlet.java:95)
 at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:283)
 at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
 at weblogic.security.service.SecurityManager.runAs(Unknown Source)
 at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64)
 at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
 at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)
 at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:521)
 at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1893)
 at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1870)
 at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1790)
 at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:2999)
 at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1371)
 at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:468)
 at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
 at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
 at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
 at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
 at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:117)
 at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
 at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
 at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
 at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
 at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:635)
 at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
 at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
 at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:16)
 at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:162)
 at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
 at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
 at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:140)
 at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:106)
 at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
 at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:820)
 at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1227)
 at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:436)
 at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
 at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:181)
 at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:12)
 at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:67)
 at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
 at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
 at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: java.sql.SQLException: [BEA][Oracle JDBC Driver][Oracle]ORA-01031: insufficient privileges
 at albpm.jdbc.base.BaseExceptions.createException(Unknown Source)
 at albpm.jdbc.base.BaseExceptions.getException(Unknown Source)
 at albpm.jdbc.oracle.OracleImplStatement.execute(Unknown Source)
 at albpm.jdbc.base.BaseStatement.commonExecute(Unknown Source)
 at albpm.jdbc.base.BaseStatement.executeInternal(Unknown Source)
 at albpm.jdbc.base.BaseStatement.execute(Unknown Source)
 at fuego.jdbc.FaultTolerantStatement.execute(FaultTolerantStatement.java:226)
 at fuego.server.service.EngineConnectorService.migrateTo(EngineConnectorService.java:2616)
 ... 48 more
weblogic.application.ModuleException: [HTTP:101216]Servlet: "engineStartup" failed to preload on startup in Web application: "/albpmServices/bpm_dev_eng_04".
fuego.server.exception.EngineRuntimeException: Server runtime exception. [BEA][Oracle JDBC Driver][Oracle]ORA-01031: insufficient privileges
 at fuego.server.exception.EngineRuntimeException.create(EngineRuntimeException.java:45)
 at fuego.server.service.EngineConnectorService.migrateTo(EngineConnectorService.java:2632)
 at fuego.server.service.EngineConnectorService.checkMigration(EngineConnectorService.java:1081)
 at fuego.server.service.EngineConnectorService.start(EngineConnectorService.java:413)
 at fuego.server.service.EngineConnectorService.initialize(EngineConnectorService.java:368)
 at fuego.ejbengine.Engine.startServices(Engine.java:393)
 at fuego.ejbengine.Engine.start(Engine.java:119)
 at fuego.ejbengine.servlet.SchedulerServlet.init(SchedulerServlet.java:95)
 at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:283)
 at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
 at weblogic.security.service.SecurityManager.runAs(Unknown Source)
 at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64)
 at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
 at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)
 at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:521)
 at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1893)
 at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1870)
 at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1790)
 at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:2999)
 at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1371)
 at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:468)
 at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
 at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
 at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
 at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
 at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:117)
 at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
 at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
 at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
 at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
 at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:635)
 at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
 at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
 at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:16)
 at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:162)
 at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
 at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
 at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:140)
 at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:106)
 at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
 at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:820)
 at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1227)
 at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:436)
 at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
 at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:181)
 at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:12)
 at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:67)
 at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
 at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
 at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: java.sql.SQLException: [BEA][Oracle JDBC Driver][Oracle]ORA-01031: insufficient privileges
 at albpm.jdbc.base.BaseExceptions.createException(Unknown Source)
 at albpm.jdbc.base.BaseExceptions.getException(Unknown Source)
 at albpm.jdbc.oracle.OracleImplStatement.execute(Unknown Source)
 at albpm.jdbc.base.BaseStatement.commonExecute(Unknown Source)
 at albpm.jdbc.base.BaseStatement.executeInternal(Unknown Source)
 at albpm.jdbc.base.BaseStatement.execute(Unknown Source)
 at fuego.jdbc.FaultTolerantStatement.execute(FaultTolerantStatement.java:226)
 at fuego.server.service.EngineConnectorService.migrateTo(EngineConnectorService.java:2616)
 ... 48 more
 at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1373)
 at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:468)
 at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
 at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
 at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
 Truncated. see log file for complete stacktrace
java.sql.SQLException: [BEA][Oracle JDBC Driver][Oracle]ORA-01031: insufficient privileges
 at albpm.jdbc.base.BaseExceptions.createException(Unknown Source)
 at albpm.jdbc.base.BaseExceptions.getException(Unknown Source)
 at albpm.jdbc.oracle.OracleImplStatement.execute(Unknown Source)
 at albpm.jdbc.base.BaseStatement.commonExecute(Unknown Source)
 at albpm.jdbc.base.BaseStatement.executeInternal(Unknown Source)
 Truncated. see log file for complete stacktrace

BPM Enterprise - Create domain Fails

Hello all
I am new to BPM Enterprise
I am using BPM Enterprise 10.3.1.0
I am using WebLogic server 10.3 (R3)
Databas Oracle 11g
I run the configuration wizard to create the directory service and configure the engine. It works fine, but when it reachs to create the weblogic DOMAIN, it fails.
The log says:
CLASSPATH=C:\bea\patch_wlw1030\profiles\default\sys_manifest_classpath\weblogic_patch.jar;C:\bea\patch_wls1030\profiles\default\sys_manifest_classpath\weblogic_patch.jar;C:\bea\patch_cie660\profiles\default\sys_manifest_classpath\weblogic_patch.jar;C:\bea\JDK160~1\lib\tools.jar;C:\bea\WLSERV~1.3\server\lib\weblogic_sp.jar;C:\bea\WLSERV~1.3\server\lib\weblogic.jar;C:\bea\modules\features\weblogic.server.modules_10.3.0.0.jar;C:\bea\WLSERV~1.3\server\lib\webservices.jar;C:\bea\modules\ORGAPA~1.5/lib/ant-all.jar;C:\bea\modules\NETSFA~1.0_1/lib/ant-contrib.jar;
PATH=C:\bea\patch_wlw1030\profiles\default\native;C:\bea\patch_wls1030\profiles\default\native;C:\bea\patch_cie660\profiles\default\native;C:\bea\WLSERV~1.3\server\native\win\32;C:\bea\WLSERV~1.3\server\bin;C:\bea\modules\ORGAPA~1.5\bin;C:\bea\JDK160~1\jre\bin;C:\bea\JDK160~1\bin;c:\ORACLE\app\pepe\product\11.1.0\db_1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Symantec\pcAnywhere\;C:\bea\WLSERV~1.3\server\native\win\32\oci920_
Your environment has been set.
CLASSPATH=C:\bea\patch_wlw1030\profiles\default\sys_manifest_classpath\weblogic_patch.jar;C:\bea\patch_wls1030\profiles\default\sys_manifest_classpath\weblogic_patch.jar;C:\bea\patch_cie660\profiles\default\sys_manifest_classpath\weblogic_patch.jar;C:\bea\JDK160~1\lib\tools.jar;C:\bea\WLSERV~1.3\server\lib\weblogic_sp.jar;C:\bea\WLSERV~1.3\server\lib\weblogic.jar;C:\bea\modules\features\weblogic.server.modules_10.3.0.0.jar;C:\bea\WLSERV~1.3\server\lib\webservices.jar;C:\bea\modules\ORGAPA~1.5/lib/ant-all.jar;C:\bea\modules\NETSFA~1.0_1/lib/ant-contrib.jar;;C:\bea\WLSERV~1.3\common\eval\pointbase\lib\pbembedded57.jar;C:\bea\WLSERV~1.3\common\eval\pointbase\lib\pbtools57.jar;C:\bea\WLSERV~1.3\common\eval\pointbase\lib\pbclient57.jar
Initializing WebLogic Scripting Tool (WLST) ...
Welcome to WebLogic Server Administration Scripting ShellType help() for help on available commands
Starting server BPMServer
Please see the server log files for startup messages available at C:\bea\user_projects\domains\BPM_DOMAIN (BUT THE FORDER IS EMPTY)
Starting weblogic server ...
WLST-WLS-1254257611468: Error occurred during initialization of VM
WLST-WLS-1254257611468: Could not reserve enough space for object heap
WLST-WLS-1254257611468: Stopped draining WLST-WLS-1254257611468
WLST-WLS-1254257611468: Stopped draining WLST-WLS-1254257611468
No stack trace available.
Exiting WebLogic Scripting Tool.Any sugestions??? I have been searching in forums and documentation, but i can't find the problem
I really appreciate any help :)
Thanks in advance to all

Hello
I am running on my laptop which has 2GB of memory.
I think the WLST can't allocate the memory specified in it's shell script. But i don't know where i can modify this parameter.
Somehow i am able to start the <BEA_HOME>wlserver10.3\common\bin\wlst.cmd (which starts the wlsto). I opened this script and i can't see where the memory is set :(
In the log file...it says that WLST is started successfully, but the problem of memory came when "STARTING BPM SERVER"
Does anyone here have a sugestion where i could see/modify the parameter of memory for starting a server using WLST?
Thanks in advance

Log filtering in BPM Enterprise Server

Similar Messages

Maybe you are looking for