BPM - Formerly galaxy

Is BPM part of CE7.1 only? Is EHP CE7.1 required?
Is it also available as part of EHP for 7.0?
Please let me know.
thanks

The BPM environment comes shipped as of CE 7.1 EHP1 SP1. The official release
of the BPM environment will be called 'Galaxy'. So there is no possibility to integrate
BPM into NetWeaver 7.0.
Regards,
Wesley

Similar Messages

Guided Procedures Vs BPM

Hi
Can anybody tell me the difference betwwen two and which one is better and in what terms??
Is there any way out to migrate GP applications to BPM? It may sound weird but don't have any knowledge in this regard.
Thanks
Monika

Hi Monika,
Netweaver BPM aka Galaxy is said to be the successor of Guided Procedures which will be phased out in future. SAP will be supporting GP only until 2013. Also there are several differences between GP and BPM. Some of them are:
With BPM, you can change your process easily as compared to GP
Mapping between tasks is a pain in GP, but easy in BPM
BPM is pretty new while GP is around for sometime and much more stable than BPM
BPM gives you the flexibilty to design the process Graphically that is easily uderstood by Business and Tecnical guys
In BPM lot more features are there currently and more will be there once Netweaver 7.2 is released.
Hope this helps!!
Regards,
Arafat

BI extractor and/or content for BPM available?

Hallo
I have a question concerning BPM. Does anybody know if there is standard content and/or an extractor to retrieve BPM Process Data from the CE 7.1? I am looking for something similar as the SAP Workflow extractor and/or data model.
Does someone have a suggestion?
Regards,
mingolo

NO, not really. This content covers ccBPM within PI. I am looking for BPM (former Galaxy) based extractors --> extracting BPM Data from a CE 7.1.
Anybody got some information on that topic?
Regards,
Minima

[Oracle BPM 6.0.2 - formerly ALBPM 6.0.2] Error using BAM Updater Service

Hi All -
I'm getting a similar error to the one below (posted byFabricio Soares) when the BAM updates service is working. We are using ALBPM 6.0.2 alongwith Oracle OID / LDAP (integrated using a custom FDI plugin).
Any idea what could cause this problem? I've verified the BAM configuration - and the database tables exist (though are empty...).
Thanks in advance -
Deepak Natarajan
From: Fabricio Soares [mailto:[email protected]]
Sent: 17. december 2008 14:10
To: /USER bpmblazers
Subject: problem when I try to update the BAM
Importance: High
Hi Folks,
I'm having the following problem when I try to update the BAM.
If anyone knows about this problem I appreciate.
In attachment have the complete logs files.
Thanks and Regards,
Stack trace:
<S> 17/12/08 10:08:29]
java.lang.NullPointerException:
at fuego.analyzer.OrganizationMetadata.getDWInForOU(OrganizationMetadata.java:92)
at fuego.analyzer.OrganizationMetadata.synchronizeParticipants(OrganizationMetadata.java:422)
at fuego.analyzer.OrganizationMetadata.synchronize(OrganizationMetadata.java:135)
at fuego.analyzer.UpdaterRunner.synchronizeMetadata(UpdaterRunner.java:467)
at fuego.analyzer.UpdaterRunner.run(UpdaterRunner.java:280)
at fuego.analyzer.UpdaterRunner.runUpdater(UpdaterRunner.java:183)
at fuego.analyzer.service.BAMUpdaterRunnerService.run(BAMUpdaterRunnerService.java:135)
at fuego.analyzer.service.WarehouseService$WarehouseServiceThread.runItem(WarehouseService.java:421)
at fuego.analyzer.service.WarehouseService$WarehouseServiceThread.run(WarehouseService.java:354)
[<S> 17/12/08 10:08:29] Updater runtime exception.
Caused by:
fuego.analyzer.UpdaterRuntimeException: Updater runtime exception.
at fuego.analyzer.UpdaterRuntimeException.wrapException(UpdaterRuntimeException.java:87)
at fuego.analyzer.UpdaterRunner.synchronizeMetadata(UpdaterRunner.java:518)
at fuego.analyzer.UpdaterRunner.run(UpdaterRunner.java:280)
at fuego.analyzer.UpdaterRunner.runUpdater(UpdaterRunner.java:183)
at fuego.analyzer.service.BAMUpdaterRunnerService.run(BAMUpdaterRunnerService.java:135)
at fuego.analyzer.service.WarehouseService$WarehouseServiceThread.runItem(WarehouseService.java:421)
at fuego.analyzer.service.WarehouseService$WarehouseServiceThread.run(WarehouseService.java:354)
Caused by: java.lang.NullPointerException:
at fuego.analyzer.OrganizationMetadata.getDWInForOU(OrganizationMetadata.java:92)
at fuego.analyzer.OrganizationMetadata.synchronizeParticipants(OrganizationMetadata.java:422)
at fuego.analyzer.OrganizationMetadata.synchronize(OrganizationMetadata.java:135)
at fuego.analyzer.UpdaterRunner.synchronizeMetadata(UpdaterRunner.java:467)
... 5 more

I've received a reply from the support guys at BEA:
I just got notified from several other engineers , here at the labs , that there’s an issue on the installer itself . The BUG report has been already filed .
In the meantime the only alternative is to install ALBPM Studio 6.02 from scratch , with the following considerations :
- Uninstall
- Make sure that the directory had been fully erased
- Reboot the machine
- Install ALBPM 6.02
- Apply the latest Hotfix

Error During Deploying BPM.

Dear Experts,
I have created a BPM process, and while trying to deploy I am facing the following error:
(Part of summary Log after failed BPM deploy Process:)
=============
Adapter com.sap.glx.adapter.internal.Transformer has refused deploy unit 1977e4888545e19a17fbf55802ac5d05 using configuration mode DEPLOYMENT
-> Transformer could not get lock within 60 seconds
=============
I Did not face this error on my earlier deployments.. This is a new error for me!!!
Attaching the error Log and summary log.
Response for the query is Highly appreciated.
Thank you,
Best Regards,
Ajay

Hi Anand,
I have restarted the Java services, (Galaxy core service in particular) and it has resolved the issue.
Please check and do let me know if that solves your issue.
Thank you,
Best Regards,
Ajay

Deployment issue in NWDS while deploying BPM

Hi Experts,
I m getting following deployment error in NWDS (SAP Enhancement Package 1 for SAP NetWeaver Developer Studio 7.3 SP11 PAT0002) while deploying BPM.
can u plz revert back if you have encountered similar issue.
com.sap.engine.services.dc.api.deploy.DeployException: [ERROR CODE DPL.DCAPI.1027] DeploymentException.
Reason: ASJ.dpl_dc.001085 Operation [deploy] of [DC-I205] failed
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deployItems(DeployProcessorImpl.java:862)
at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deploy(DeployProcessorImpl.java:259)
at com.sap.ide.eclipse.deployer.dc.deploy.DeployProcessor70.deploy(DeployProcessor70.java:105)
at com.sap.ide.tools.services.dc.EngineDcDeployService.deployFiles(EngineDcDeployService.java:257)
at com.sap.ide.tools.services.dc.EngineDcDeployService.deploy(EngineDcDeployService.java:135)
at com.sap.ide.dii05.ui.internal.actions.dc.DcDeployAction$5$1.run(DcDeployAction.java:282)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
Caused by: com.sap.engine.services.dc.cm.deploy.DeploymentException: ASJ.dpl_dc.001085 Operation [deploy] of [DC-I205] failed
at com.sap.engine.services.dc.cm.deploy.impl.OnlineDeployProcessor.performDelivery(OnlineDeployProcessor.java:246)
at com.sap.engine.services.dc.cm.deploy.impl.BulkOnlineDeployProcessor.deploy(BulkOnlineDeployProcessor.java:67)
at com.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor$DeployProcessorHelper.visit(AbstractDeployProcessor.java:282)
at com.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:84)
at com.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor.deploy(AbstractDeployProcessor.java:100)
at com.sap.engine.services.dc.cm.deploy.impl.DeployThread.run(DeployThread.java:39)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101)
at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:328)
Caused by: com.sap.engine.services.dc.gd.DeliveryException: [ERROR CODE DPL.DC.3298] Operation [deploy] of [DC-I205] failed
at com.sap.engine.services.dc.gd.impl.ApplicationDeployer.deploy(ApplicationDeployer.java:167)
at com.sap.engine.services.dc.gd.impl.InitialApplicationDeployer.performDeployment(InitialApplicationDeployer.java:138)
at com.sap.engine.services.dc.gd.impl.InitialGenericDeliveryImpl.deploy(InitialGenericDeliveryImpl.java:57)
at com.sap.engine.services.dc.cm.deploy.impl.OnlineDeployProcessor.performDelivery(OnlineDeployProcessor.java:213)
... 8 more
Caused by: com.sap.engine.services.deploy.server.utils.DSRemoteException: ASJ.dpl_ds.006193 Operation [deploy] of [/usr/sap/A6D/J00/j2ee/cluster/server0/temp/tc~bl~deploy_controller/archives/1418/DC-I205.sda] failed
at com.sap.engine.services.deploy.server.DeployServiceImpl.catchDeploymentExceptionWithDSRem(DeployServiceImpl.java:3370)
at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:315)
at com.sap.engine.services.dc.gd.impl.ApplicationDeployer.deploy(ApplicationDeployer.java:139)
... 11 more
Caused by: com.sap.engine.services.deploy.container.DeploymentException: TxException
at com.sap.glx.repository.deploy.content.ContentArchiveDeployContainer.deployArchive(ContentArchiveDeployContainer.java:1280)
at com.sap.glx.repository.deploy.content.ContentArchiveDeployContainer.deploy(ContentArchiveDeployContainer.java:137)
at com.sap.engine.services.deploy.server.utils.container.ContainerWrapper.deploy(ContainerWrapper.java:310)
at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:519)
at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:183)
at com.sap.engine.services.deploy.server.application.DeploymentTransaction.begin(DeploymentTransaction.java:203)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:421)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:473)
at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:1836)
at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:360)
at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:313)
... 12 more
Caused by: java.lang.Exception: com.sap.engine.services.ts.transaction.TxRollbackException: Current transaction is marked for rollback
at com.sap.engine.services.ts.transaction.TxManagerImpl.commitLevel(TxManagerImpl.java:621)
at com.sap.transaction.TxManager.commitLevel(TxManager.java:237)
at com.sap.glx.repository.deploy.content.ContentArchiveDeployContainer.deployArchive(ContentArchiveDeployContainer.java:1277)
at com.sap.glx.repository.deploy.content.ContentArchiveDeployContainer.deploy(ContentArchiveDeployContainer.java:137)
at com.sap.engine.services.deploy.server.utils.container.ContainerWrapper.deploy(ContainerWrapper.java:310)
at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:519)
at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:183)
at com.sap.engine.services.deploy.server.application.DeploymentTransaction.begin(DeploymentTransaction.java:203)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:421)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:473)
at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:1836)
at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:360)
at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:313)
at com.sap.engine.services.dc.gd.impl.ApplicationDeployer.deploy(ApplicationDeployer.java:139)
at com.sap.engine.services.dc.gd.impl.InitialApplicationDeployer.performDeployment(InitialApplicationDeployer.java:138)
at com.sap.engine.services.dc.gd.impl.InitialGenericDeliveryImpl.deploy(InitialGenericDeliveryImpl.java:57)
at com.sap.engine.services.dc.cm.deploy.impl.OnlineDeployProcessor.performDelivery(OnlineDeployProcessor.java:213)
at com.sap.engine.services.dc.cm.deploy.impl.BulkOnlineDeployProcessor.deploy(BulkOnlineDeployProcessor.java:67)
at com.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor$DeployProcessorHelper.visit(AbstractDeployProcessor.java:282)
at com.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:84)
at com.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor.deploy(AbstractDeployProcessor.java:100)
at com.sap.engine.services.dc.cm.deploy.impl.DeployThread.run(DeployThread.java:39)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101)
at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:328)
Caused by: java.lang.IllegalStateException: Galaxy commit failed (for a possible cause, refer to the nested exception(s)
at com.sap.glx.core.kernel.execution.TransitionManagerImpl$BoundPrimaryTransaction.beforeCompletion(TransitionManagerImpl.java:117)
at com.sap.engine.services.ts.jta.impl.SynchronizationWrapper.beforeCompletion(SynchronizationWrapper.java:36)
at com.sap.engine.services.ts.jta.impl2.TXR_TransactionImpl.beforePrepare(TXR_TransactionImpl.java:589)
at com.sap.engine.services.ts.jta.impl2.TXR_TransactionImpl.commit(TXR_TransactionImpl.java:1120)
at com.sap.engine.services.ts.jta.impl2.TXR_TransactionManagerImpl.commit(TXR_TransactionManagerImpl.java:333)
at com.sap.engine.services.ts.transaction.TxManagerImpl.commitLevel(TxManagerImpl.java:610)
... 24 more
Caused by: com.sap.glx.core.kernel.api.TransitionRollbackException: Transaction locked for rollback; Commit refused.
at com.sap.glx.core.kernel.mmtx.AbstractTransactionBase.rollback(AbstractTransactionBase.java:701)
at com.sap.glx.core.kernel.mmtx.AbstractTransaction.do_precommit(AbstractTransaction.java:186)
at com.sap.glx.core.kernel.mmtx.AbstractTransaction.commit(AbstractTransaction.java:75)
at com.sap.glx.core.kernel.execution.TransitionManagerImpl$BoundPrimaryTransaction.beforeCompletion(TransitionManagerImpl.java:115)
... 29 more
Caused by: com.sap.glx.core.dock.api.DockException: Adapter com.sap.glx.adapter.internal.Transformer didn't comply with configuration
at com.sap.glx.core.dock.impl.DockingPortal.configure(DockingPortal.java:693)
at com.sap.glx.core.dock.impl.DockingPortal.configureCallback(DockingPortal.java:495)
at com.sap.glx.core.dock.impl.DockingPortal.runConfigureCallback(DockingPortal.java:998)
at com.sap.glx.deploy.impl.DeployControllerImpl$DeployProcessor.runProcessorWork(DeployControllerImpl.java:801)
at com.sap.glx.deploy.impl.DeployControllerImpl$Processor.run(DeployControllerImpl.java:624)
at com.sap.glx.deploy.impl.DeployControllerImpl$Processor.access$1300(DeployControllerImpl.java:585)
at com.sap.glx.deploy.impl.DeployControllerImpl$ProcessorList.run(DeployControllerImpl.java:549)
at com.sap.glx.deploy.impl.DeployControllerImpl$ProcessorList.run(DeployControllerImpl.java:543)
at com.sap.glx.core.kernel.DefaultRuntimeManager.requestRuntimeMode(DefaultRuntimeManager.java:1110)
at com.sap.glx.deploy.impl.DeployControllerImpl$InternalActuator.executeDeployWork(DeployControllerImpl.java:1177)
at com.sap.glx.core.resource.impl.j2ee.rrdeploy.CoreServiceRRHandler$DeployActuatorCallback.executeDeployActuatorCallbackWork(CoreServiceRRHandler.java:138)
at com.sap.glx.core.resource.impl.j2ee.rrdeploy.CoreServiceRRHandler$DeployActuatorCallback.access$400(CoreServiceRRHandler.java:50)
at com.sap.glx.core.resource.impl.j2ee.rrdeploy.CoreServiceRRHandler.callCoreServiceHandlers(CoreServiceRRHandler.java:314)
at com.sap.glx.core.resource.impl.j2ee.rrdeploy.CoreServiceRRHandler.addVersion(CoreServiceRRHandler.java:337)
at com.sap.glx.repository.service.impl.RuntimeRepositoryDeployManager.handlerDistributionForDeployment(RuntimeRepositoryDeployManager.java:2565)
at com.sap.glx.repository.service.impl.RuntimeRepositoryDeployManager.deployArchive(RuntimeRepositoryDeployManager.java:1535)
at com.sap.glx.repository.service.impl.RuntimeRepositoryDeployManager.deploy(RuntimeRepositoryDeployManager.java:339)
at com.sap.glx.repository.service.impl.RuntimeRepositoryDeployManager.deploy(RuntimeRepositoryDeployManager.java:261)
at com.sap.glx.repository.service.impl.RuntimeRepositoryDeployManager.deploy(RuntimeRepositoryDeployManager.java:251)
at com.sap.glx.repository.deploy.content.ContentArchiveDeployContainer.deployArchive(ContentArchiveDeployContainer.java:1265)
... 22 more
Caused by: com.sap.glx.adapter.api.AdapterException: Adapter com.sap.glx.adapter.internal.Transformer has refused deploy unit 7b9afc88c8f151c20d38cef0d370f416 using configuration mode DEPLOYMENT
at com.sap.glx.core.dock.impl.DockingPortal.configure(DockingPortal.java:669)
... 41 more
Caused by: java.lang.RuntimeException: Transformer could not get lock within 60 seconds
at com.sap.glx.core.internaladapter.Transformer$Share.acquireWrite(Transformer.java:875)
at com.sap.glx.core.internaladapter.Transformer$TransformerTemplateAccessor$GeneratorTemplate$GeneratorConfigurationAccessor$GeneratorLocalProvider$ImplementedGeneratorLocal.acquireWrite(Transformer.java:2317)
at com.sap.glx.core.internaladapter.Transformer$TransformerTemplateAccessor$GeneratorTemplate$GeneratorConfigurationAccessor.insertRule(Transformer.java:2775)
at com.sap.glx.core.internaladapter.Transformer$TransformerTemplateAccessor$GeneratorTemplate$GeneratorConfigurationHandler.configure(Transformer.java:2930)
at com.sap.glx.core.internaladapter.Transformer$TransformerTemplateAccessor$GeneratorTemplateHandler.configure(Transformer.java:3472)
at com.sap.glx.core.internaladapter.Transformer.configure(Transformer.java:3675)
at com.sap.glx.core.dock.impl.DockingPortal.configure(DockingPortal.java:666)
... 41 more
at com.sap.engine.services.ts.transaction.TxRollbackException.writeReplace(TxRollbackException.java:163)
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 java.io.ObjectStreamClass.invokeWriteReplace(ObjectStreamClass.java:1040)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1116)
at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1531)
at java.io.ObjectOutputStream.defaultWriteObject(ObjectOutputStream.java:423)
at com.sap.exception.BaseExceptionInfo.writeObject(BaseExceptionInfo.java:1033)
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 java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:953)
at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1482)
at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1413)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1159)
at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1531)
at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1496)
at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1413)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1159)
at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1531)
at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1496)
at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1413)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1159)
at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1531)
at java.io.ObjectOutputStream.defaultWriteObject(ObjectOutputStream.java:423)
at com.sap.exception.BaseExceptionInfo.writeObject(BaseExceptionInfo.java:1033)
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 java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:953)
at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1482)
at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1413)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1159)
at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1531)
at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1496)
at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1413)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1159)
at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1531)
at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1496)
at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1413)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1159)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:331)
at com.sap.engine.services.rmi_p4.DispatchImpl.throwException(DispatchImpl.java:139)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:488)
at com.sap.engine.services.rmi_p4.server.ServerDispatchImpl.run(ServerDispatchImpl.java:81)
at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:72)
at com.sap.engine.services.rmi_p4.P4Message.execute(P4Message.java:43)
at com.sap.engine.services.cross.fca.FCAConnectorImpl.executeRequest(FCAConnectorImpl.java:999)
at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:59)
at com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:55)
... 3 more

Hi,
i have not done any changes to any process. I have created new DC and created new process.
new DC is not getting deployed with error "Adapter com.sap.glx.adapter.internal.Transformer didn't comply with configuration". If you will check error log above then you will find it their.

BPM throws: "Error while trying to retrieve the task"

Hi,
 
When clicking on a task(WD-UI) in UWL, BPM throws an error message: 
Error while trying to retrieve the task 
Though, I am able to open up the task when I restart the server ( CE 7.1 EHP1 SP04 patched).
 
Anyone an idea?
 
Regards,
 
Wesley
 
The log file presents the following information (partially):
 
Caused by: java.lang.IllegalStateException: com.sap.glx.core.kernel.api.TransitionRollbackException: Exception during prepare, rolling back
at com.sap.bpem.tm.adapter.core.TaskAdapter$TicketSynchronization.beforeCompletion(TaskAdapter.java:581)
at com.sap.engine.services.ts.jta.impl.SynchronizationWrapper.beforeCompletion(SynchronizationWrapper.java:27)
at com.sap.engine.services.ts.jta.impl.TransactionImpl.commit(TransactionImpl.java:234)
... 86 more
Caused by: com.sap.glx.core.kernel.api.TransitionRollbackException: Exception during prepare, rolling back
at com.sap.glx.core.kernel.mmtx.AbstractTransactionBase.rollback(AbstractTransactionBase.java:544)
at com.sap.glx.core.kernel.mmtx.AbstractTransaction.do_prepare(AbstractTransaction.java:174)
at com.sap.glx.core.kernel.mmtx.AbstractTransaction.commit(AbstractTransaction.java:77)
at com.sap.bpem.tm.adapter.core.TaskAdapter$TicketSynchronization.beforeCompletion(TaskAdapter.java:579)
... 88 more
Caused by: com.sap.glx.core.kernel.trigger.TriggerLockingException: Cannot acquire lock for update <Context_0_TaskAttributes_ac33d162fa908f8198b3c740708bb6c5{919e4f4b-1581-11df-c72f-02004c4f4f50}(Instance_0_TaskHelloWorld2_ac33d162fa908f8198b3c740708bb6c5{919e4f45-1581-11df-b4f9-02004c4f4f50}(?),Scope_13_TaskHelloWorld2_ac33d162fa908f8198b3c740708bb6c5{919e4f4a-1581-11df-94e6-02004c4f4f50}(?),3,true)|Context_0_TaskAttributes_ac33d162fa908f8198b3c740708bb6c5(Instance_0_TaskHelloWorld2_ac33d162fa908f8198b3c740708bb6c5{919e4f45-1581-11df-b4f9-02004c4f4f50}(Instance_0_bpmboundary_new_24449a1f1a041ff7cd7deb8d764c6405{0d4c2925-157b-11df-b84e-02004c4f4f50}(?),null,Token_0_bpmboundary_new_24449a1f1a041ff7cd7deb8d764c6405{917829a3-1581-11df-b6e0-02004c4f4f50}(?),false),Scope_13_TaskHelloWorld2_ac33d162fa908f8198b3c740708bb6c5{919e4f4a-1581-11df-94e6-02004c4f4f50}(Instance_0_TaskHelloWorld2_ac33d162fa908f8198b3c740708bb6c5{919e4f45-1581-11df-b4f9-02004c4f4f50}(?)),4,*true)>
at com.sap.glx.core.kernel.trigger.node.LockingTreeJoinNode.process(LockingTreeJoinNode.java:638)
at com.sap.glx.core.kernel.trigger.core.BFSController.update(BFSController.java:173)
at com.sap.glx.core.kernel.trigger.impl.TriggerNetworkManagerImpl$SequentialController.update(TriggerNetworkManagerImpl.java:550)
at com.sap.glx.core.kernel.mmtx.AbstractTransaction.do_trigger(AbstractTransaction.java:199)
at com.sap.glx.core.kernel.mmtx.AbstractTransaction.do_prepare(AbstractTransaction.java:170)
... 90 more
Caused by: com.sap.glx.core.kernel.trigger.TriggerLockingException: Cannot acquire read row lock for after image (key = Instance_0_TaskHelloWorld2_ac33d162fa908f8198b3c740708bb6c5{919e4f45-1581-11df-b4f9-02004c4f4f50}(Instance_0_bpmboundary_new_24449a1f1a041ff7cd7deb8d764c6405{0d4c2925-157b-11df-b84e-02004c4f4f50}(?),null,Token_0_bpmboundary_new_24449a1f1a041ff7cd7deb8d764c6405{917829a3-1581-11df-b6e0-02004c4f4f50}(?),false), name = JOIN_CompletionDeadlineWithRealDelayConditionalSequenceConnector_context_join_0_69)
at com.sap.glx.core.kernel.trigger.node.LockingTreeJoinNode.lockAfterRow(LockingTreeJoinNode.java:308)
at com.sap.glx.core.kernel.trigger.node.LockingTreeJoinNode.process(LockingTreeJoinNode.java:636)
... 94 more

Hi,
sounds like an program error. That is an problem which occurs if one or multiple components try to lock the same galaxy object at the same point in time. Did you configured something special on the given task? e.g deadlines?
My proposal is to open an Customer Message so that we can have a detailed look onto the system. If this is not possible could you please provide the complete trace file and some more details about the modeled task?
Best Regards
Andreas

Handle to a Task in BPM

Hi active contributors of BPM,
I have a scenario where one of the steps in a process is a human activity. There is a WebDynpro UI corresponding to the task mapped to the human activity, which works well. However, an email with a custom MS Outlook form will be sent to the corresponding owner of the task when task gets generated. The user can respond to the task directly either through the Outlook form itself or using the SAP Portal / UWL. So, I would like to if there are any APIs / interfaces that could be used to trigger the task completion programmaticlly from my code similar to how it happens on click of an WebDynpro UI element mapped with the Complete event.
Any pointers will be highly appreciated.
BR,
Bala

Hi Bala,
As Benny already pointed out it's cruicial for the processes that the users management is built on the repository provided by the UME. If you want to bypass this anyway and want to implement the completion by a service user then you could try splitting up your process into the 'sending part' and the 'receiving part':
'the sending part'
This particular process is responsible for gathering all the needed data (via services, UI input, ...) and finally sends out the mails to the users.
'the receiving part'
Here it is getting a little bit more tricky: You could implement a message driven bean which is waiting for the responses of your users and queues them up for further processing. Then - for each item - it extracts the needed data and starts off a new process instance which could then do the final processing.
Of course one major drawback is that you will lose the 'overall process view' in that case by decoupling the both steps. Nevertheless you could benefit of NW BPM in each of them.
What might be interesting for you are the so called offline forms that have been mentioned in the thread below.
Galaxy Frontends
Galaxy Frontends
Best regards,
Martin

BPM Process stop to work

when i start a bpm process during the runtime the process stop to work and in the default trace i found this error:
2011 09 26 15:24:11:785--+0200--Error--com.sap.glx.core.kernel.mmtx.PrimaryTransaction--
com.sap.BPM.core_svc.000064--BC-BMT-BPM-SRV--com.sap.glx.core.svc--F65520AD5DBD13F60000000000004958--29830050000000004----com.sap.glx.core.kernel.mmtx.PrimaryTransaction--SAP_BPM_Service--0----217287D5E83F11E0AF57000001C72BA2--217287d5e83f11e0af57000001c72ba2--217287d5e83f11e0af57000001c72ba2--0--Galaxy 2079 / Follower Worker--Plain----
afterCompletion(int):Unexpected error during deferred transaction commit: java.lang.IllegalMonitorStateException: Attempted to release a write lock, but the ticket-local lock count is zero (danger, inconsistency detected!)
     at com.sap.glx.core.dock.impl.GalaxyCowLock$LockImpl$WriteLockImpl.unlock(GalaxyCowLock.java:378)
     at com.sap.glx.core.kernel.mmtx.AbstractTransactionBase.localImageRelease(AbstractTransactionBase.java:798)
     at com.sap.glx.core.kernel.mmtx.AbstractTransactionBase.clean(AbstractTransactionBase.java:240)
     at com.sap.glx.core.kernel.mmtx.PrimaryTransaction.clean(PrimaryTransaction.java:86)
     at com.sap.glx.core.kernel.mmtx.AbstractTransaction.internalComplete(AbstractTransaction.java:392)
     at com.sap.glx.core.kernel.mmtx.AbstractTransaction.complete(AbstractTransaction.java:345)
     at com.sap.glx.core.kernel.mmtx.AbstractTransaction.rollback(AbstractTransaction.java:305)
     at com.sap.glx.core.kernel.mmtx.PrimaryTransaction$PersistentCommit.afterCompletion(PrimaryTransaction.java:401)
     at com.sap.engine.services.ts.jta.impl.SynchronizationWrapper.afterCompletion(SynchronizationWrapper.java:48)
     at com.sap.engine.services.ts.jta.impl2.TXR_TransactionImpl.rollback_internal(TXR_TransactionImpl.java:1286)
     at com.sap.engine.services.ts.jta.impl2.TXR_TransactionImpl.rollback(TXR_TransactionImpl.java:1048)
     at com.sap.engine.services.ts.jta.impl2.TXR_TransactionManagerImpl.rollback(TXR_TransactionManagerImpl.java:509)
     at com.sap.engine.services.ts.jta.impl2.TXR_UserTransaction.rollback(TXR_UserTransaction.java:170)
     at com.sap.glx.core.resource.impl.j2ee.J2EETransactionManagerFactory$JTATransactionManagerImpl.rollback(J2EETransactionManagerFactory.java:158)
     at com.sap.glx.core.kernel.mmtx.PrimaryTransaction.inRollback(PrimaryTransaction.java:274)
     at com.sap.glx.core.kernel.mmtx.AbstractTransaction.rollback(AbstractTransaction.java:279)
     at com.sap.glx.core.kernel.mmtx.AbstractTransactionBase.rollback(AbstractTransactionBase.java:778)
     at com.sap.glx.core.kernel.mmtx.AbstractTransaction.do_prepare(AbstractTransaction.java:202)
     at com.sap.glx.core.kernel.mmtx.AbstractTransaction.commit(AbstractTransaction.java:81)
     at com.sap.glx.core.kernel.execution.LeaderWorkerPool$Follower.run(LeaderWorkerPool.java:129)
     at com.sap.glx.core.resource.impl.common.WorkWrapper.run(WorkWrapper.java:58)
     at com.sap.glx.core.resource.impl.j2ee.J2EEResourceImpl$Sessionizer.run(J2EEResourceImpl.java:231)
     at com.sap.glx.core.resource.impl.j2ee.ServiceUserManager$ServiceUserImpersonator$1.run(ServiceUserManager.java:150)
     at java.security.AccessController.doPrivileged(Native Method)
     at javax.security.auth.Subject.doAs(Subject.java:337)
     at com.sap.glx.core.resource.impl.j2ee.ServiceUserManager$ServiceUserImpersonator.run(ServiceUserManager.java:147)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:182)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:299
(in other post i insert the rest of the default trace)
anyone know how can i resolve it?

011 09 26 15:34:27:382--+0200--Error--com.sap.glx.core.kernel.mmtx.AbstractTransactionBase--
com.sap.BPM.core_svc.000127--BC-BMT-BPM-SRV--com.sap.glx.core.svc--F65520AD5DBD14090000000000004958--29830050000000004----com.sap.glx.core.kernel.mmtx.AbstractTransactionBase--SAP_BPM_Service--0----217287D5E83F11E0AF57000001C72BA2--217287d5e83f11e0af57000001c72ba2--217287d5e83f11e0af57000001c72ba2--0--Galaxy 4198 / Follower Worker / Script [ita18.ferrero.com/fce_ita18_bu_bp_etl_lib/ETL_DB_MappingParallel_Run_POOL/4a8be0fffb1191332ea3088e50c48cf2/BLACK_HOLE]--Plain----
getLocalImage0(DockObject, boolean, boolean, boolean, boolean, boolean, long):Someone attempted to stain an object, which has already been deleted (OID = 3d806fd7-e844-11e0-a45d-000001c72ba2, separation = 3e58308c-e83f-11e0-b267-000001c72ba2, class = com.sap.glx.adapter.BPMNAdapter:Instance_0_TaskRun_1ae30a59b281399e4cf102c2ac458587). Blame this code: java.lang.NullPointerException: Object has been terminated (OID = 3d806fd7-e844-11e0-a45d-000001c72ba2, separation = 3e58308c-e83f-11e0-b267-000001c72ba2, class = com.sap.glx.adapter.BPMNAdapter:Instance_0_TaskRun_1ae30a59b281399e4cf102c2ac458587)
     at com.sap.glx.core.kernel.mmtx.AbstractTransactionBase.getLocalImage0(AbstractTransactionBase.java:560)
     at com.sap.glx.core.kernel.mmtx.AbstractTransactionBase.getLocalImage(AbstractTransactionBase.java:499)
     at com.sap.glx.core.kernel.mmtx.AbstractTransactionBase.getWritableImage(AbstractTransactionBase.java:612)
     at com.sap.glx.core.dock.impl.DockObjectImpl.bind(DockObjectImpl.java:386)
     at com.sap.glx.core.dock.impl.DockObjectImpl.bindChecked(DockObjectImpl.java:402)
     at com.sap.glx.process.adapter.bpmn.impl.BPMNAdapter.deleteChildInstances(BPMNAdapter.java:2245)
     at com.sap.glx.process.adapter.bpmn.impl.BPMNInstanceHandler.onDestruction(BPMNInstanceHandler.java:157)
     at com.sap.glx.core.dock.impl.DockObjectImpl.deletion(DockObjectImpl.java:226)
     at com.sap.glx.core.dock.impl.DockObjectImpl.delete(DockObjectImpl.java:563)
     at com.sap.glx.process.adapter.bpmn.impl.BPMNAdapter.deleteFirstChildOfFrameIfInstanceOrTask(BPMNAdapter.java:2947)
     at com.sap.glx.process.adapter.bpmn.impl.BPMNFrameHandler.onDestruction(BPMNFrameHandler.java:69)
     at com.sap.glx.core.dock.impl.DockObjectImpl.deletion(DockObjectImpl.java:226)
     at com.sap.glx.core.dock.impl.DockObjectImpl.delete(DockObjectImpl.java:563)
     at com.sap.glx.core.kernel.trigger.config.Script$DeleteInstance.execute(Script.java:298)
     at com.sap.glx.core.kernel.trigger.config.Script.execute(Script.java:798)
     at com.sap.glx.core.kernel.execution.transition.ScriptTransition.execute(ScriptTransition.java:78)
     at com.sap.glx.core.kernel.execution.transition.Transition.commence(Transition.java:138)
     at com.sap.glx.core.kernel.execution.LeaderWorkerPool$Follower.run(LeaderWorkerPool.java:127)
     at com.sap.glx.core.resource.impl.common.WorkWrapper.run(WorkWrapper.java:58)
     at com.sap.glx.core.resource.impl.j2ee.J2EEResourceImpl$Sessionizer.run(J2EEResourceImpl.java:231)
     at com.sap.glx.core.resource.impl.j2ee.ServiceUserManager$ServiceUserImpersonator$1.run(ServiceUserManager.java:150)
     at java.security.AccessController.doPrivileged(Native Method)
     at javax.security.auth.Subject.doAs(Subject.java:337)
     at com.sap.glx.core.resource.impl.j2ee.ServiceUserManager$ServiceUserImpersonator.run(ServiceUserManager.java:147)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:182)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:299)

Automated activity not executing in BPM process

Hi All,
We have created a BPM process in NWCE72, and it was executing fine.
When we added an automated activitiy and assigned a Web Service created from a rule and run the process, it is possible to run the process till the automated activity only. The automated activity is throwing error a snapshot of the same pasted belw
If anyone has encountered simllar problem kindly let us know how to overcome.
Lookforward for help in overcoming this problem
Down below it is saying that "You may have not assigned the Service Group to a Provider System, or the generation of the configuration has failed. "
=====================================================================================================
An error occurred while executing transition AUTOMATED_ACTIVITY_Determine_Criticality(Token_0_Equipment_Issue_Reporting_Process_2baa0100a79b04782f33bbea2160cdf3{64810061-7973-11df-872e-02004c4f4f50}(Instance_0_Equipment_Issue_Reporting_Process_2baa0100a79b04782f33bbea2160cdf3{4be7da15-7973-11df-b824-02004c4f4f50}(?),1,null,operator,ff12474b71b3fa29a516e53e125eaa18), Instance_0_Equipment_Issue_Reporting_Process_2baa0100a79b04782f33bbea2160cdf3{4be7da15-7973-11df-b824-02004c4f4f50}(null,null,null,false), Context_0_DO_IssueTrackingProcess_2baa0100a79b04782f33bbea2160cdf3{4be7da30-7973-11df-c7a0-02004c4f4f50}(Instance_0_Equipment_Issue_Reporting_Process_2baa0100a79b04782f33bbea2160cdf3{4be7da15-7973-11df-b824-02004c4f4f50}(?),Scope_14_Equipment_Issue_Reporting_2baa0100a79b04782f33bbea2160cdf3{4be7da2f-7973-11df-cc05-02004c4f4f50}(?),1,true,false,null)): com.sap.glx.core.kernel.api.TransitionException: An exception occurred while executing the script "_Equipment_Issue_Reporting:AUTOMATED_ACTIVITY_Determine_Criticality(
      com.sap.glx.adapter.BPMNAdapter:Token_0_Equipment_Issue_Reporting_Process_2baa0100a79b04782f33bbea2160cdf3 token,
      com.sap.glx.adapter.BPMNAdapter:Instance_0_Equipment_Issue_Reporting_Process_2baa0100a79b04782f33bbea2160cdf3 parent,
      com.sap.glx.adapter.internal.ContainerAdapter:Context_0_DO_IssueTrackingProcess_2baa0100a79b04782f33bbea2160cdf3 context_1){
exit=new com.sap.glx.adapter.BPMNAdapter:Exit();
exit:onActivation("E01DFA6EF00BAFC0797011DFB05502004C4F4F50", parent, token);
delete exit;
controller=new com.sap.glx.adapter.internal.ExceptionAdapter:ExceptionController();
controller:setContext(token);
delete controller;
callscope=new com.sap.glx.adapter.internal.TypeRegistry:Scope_7_Equipment_Issue_Reporting_2baa0100a79b04782f33bbea2160cdf3(parent);
call=new com.sap.glx.adapter.UnifiedConnectivityAdapter:Call_0_Determine_Criticality_2baa0100a79b04782f33bbea2160cdf3(callscope);
ppUsername=token:ppUsername;
ppHash=token:ppHash;
call:setPrincipal(ppHash, ppUsername, token);
request=callscope:instantiate("http://www.sap.com", "#RulesTypes-demo.sap.com-equuipissueruledc-CriticalityRuleSet-CriticalityRuleSet");
mapper=new com.sap.glx.adapter.internal.Transformer:DataMapper();
yves_in=new com.sap.glx.adapter.internal.Transformer:Data();
yves_out=new com.sap.glx.adapter.internal.Transformer:Data();
data=context_1:getData();
yves_in:setData("demo.sap.com/reportissueprocessdc/Equipment_Issue_Reporting_Process/Equipment_Issue_Reporting", "$demo.sap.com/reportissueprocessdc/Equipment_Issue_Reporting_Process/Equipment_Issue_Reporting:DO_IssueTrackingProcess", data, "C000F957BEB5AA9E0E98E96A67EE2D06");
yves_out:setData("http://www.sap.com", "$http://www.sap.com:Request-demo.sap.com-equuipissueruledc-CriticalityRuleSet-CriticalityRuleSet", request, "8F3954721A11A18DF1A2321F9544700D");
mapper:map("E01DFA6EF00DF9B0797011DFC8A002004C4F4F50_2baa0100a79b04782f33bbea2160cdf3", yves_in, yves_out);
request=yves_out:getData("http://www.sap.com", "$http://www.sap.com:Request-demo.sap.com-equuipissueruledc-CriticalityRuleSet-CriticalityRuleSet", "8F3954721A11A18DF1A2321F9544700D");
delete yves_in;
delete yves_out;
delete mapper;
call:setInputData("http://www.sap.com", "$http://www.sap.com:Request-demo.sap.com-equuipissueruledc-CriticalityRuleSet-CriticalityRuleSet", request);
response=callscope:instantiate("http://www.sap.com", "#RulesTypes-demo.sap.com-equuipissueruledc-CriticalityRuleSet-CriticalityRuleSet");
call:setOutputData("http://www.sap.com", "$http://www.sap.com:Response-demo.sap.com-equuipissueruledc-CriticalityRuleSet-CriticalityRuleSet", response);
call:invoke();
response=call:getOutputData("http://www.sap.com", "$http://www.sap.com:Response-demo.sap.com-equuipissueruledc-CriticalityRuleSet-CriticalityRuleSet");
mapper=new com.sap.glx.adapter.internal.Transformer:DataMapper();
yves_in=new com.sap.glx.adapter.internal.Transformer:Data();
yves_out=new com.sap.glx.adapter.internal.Transformer:Data();
yves_in:setData("http://www.sap.com", "$http://www.sap.com:Response-demo.sap.com-equuipissueruledc-CriticalityRuleSet-CriticalityRuleSet", response, "8F3954721A11A18DF1A2321F9544700D");
data=context_1:getData();
yves_in:setData("demo.sap.com/reportissueprocessdc/Equipment_Issue_Reporting_Process/Equipment_Issue_Reporting", "$demo.sap.com/reportissueprocessdc/Equipment_Issue_Reporting_Process/Equipment_Issue_Reporting:DO_IssueTrackingProcess", data, "C000F957BEB5AA9E0E98E96A67EE2D06");
bind context_1;
data=context_1:getData();
scope=new com.sap.glx.adapter.internal.TypeRegistry:GenericScope(null, "C000F957BEB5AA9E0E98E96A67EE2D06");
copy=scope:copy(data);
delete scope;
yves_out:setData("demo.sap.com/reportissueprocessdc/Equipment_Issue_Reporting_Process/Equipment_Issue_Reporting", "$demo.sap.com/reportissueprocessdc/Equipment_Issue_Reporting_Process/Equipment_Issue_Reporting:DO_IssueTrackingProcess", copy, "C000F957BEB5AA9E0E98E96A67EE2D06");
mapper:map("E01DFA6EF0106AB0797011DFBC6D02004C4F4F50_2baa0100a79b04782f33bbea2160cdf3", yves_in, yves_out);
data=yves_out:getData("demo.sap.com/reportissueprocessdc/Equipment_Issue_Reporting_Process/Equipment_Issue_Reporting", "$demo.sap.com/reportissueprocessdc/Equipment_Issue_Reporting_Process/Equipment_Issue_Reporting:DO_IssueTrackingProcess", "C000F957BEB5AA9E0E98E96A67EE2D06");
context_1:setData(data);
delete yves_in;
delete yves_out;
delete mapper;
delete call;
delete callscope;
token:state=0;
at com.sap.glx.core.kernel.execution.transition.ScriptTransition.execute(ScriptTransition.java:68)
at com.sap.glx.core.kernel.execution.transition.Transition.commence(Transition.java:138)
at com.sap.glx.core.kernel.execution.LeaderWorkerPool$Follower.run(LeaderWorkerPool.java:126)
at com.sap.glx.core.resource.impl.common.WorkWrapper.run(WorkWrapper.java:58)
at com.sap.glx.core.resource.impl.j2ee.ServiceUserManager$ServiceUserImpersonator$1.run(ServiceUserManager.java:121)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:337)
at com.sap.glx.core.resource.impl.j2ee.ServiceUserManager$ServiceUserImpersonator.run(ServiceUserManager.java:118)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:169)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:277)
Caused by: com.sap.glx.core.kernel.api.TransitionException: An exception occurred while executing the script command "call:invoke()"
at com.sap.glx.core.kernel.trigger.config.Script.execute(Script.java:796)
at com.sap.glx.core.kernel.execution.transition.ScriptTransition.execute(ScriptTransition.java:63)
... 11 more
Caused by: java.lang.RuntimeException: com.sap.glx.adapter.api.AdapterException: com.sap.engine.interfaces.sca.exception.SCADASException: Could not invoke service reference name b51513b6-379d-4c0b-be2a-a3b13d7fe23b, component name demo.sap.comreportissueprocessdcBPMcomponent, application name demo.sap.com/reportissueprocessdc.
at com.sap.glx.adapter.app.ucon.UnifiedWebServiceCallObject$PropagatedCall.run(UnifiedWebServiceCallObject.java:127)
at com.sap.glx.core.login.LoginPersisterProxy$1.run(LoginPersisterProxy.java:76)
at com.sap.glx.core.resource.impl.j2ee.J2EELoginPersisterImpl$1.run(J2EELoginPersisterImpl.java:80)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:396)
at com.sap.glx.core.resource.impl.j2ee.J2EELoginPersisterImpl.invokeAsPropagated(J2EELoginPersisterImpl.java:74)
at com.sap.glx.core.login.LoginPersisterProxy.invokeAsPropagated(LoginPersisterProxy.java:72)
at com.sap.glx.adapter.app.ucon.UnifiedWebServiceCallObject.invokeWebServiceOperation(UnifiedWebServiceCallObject.java:93)
at com.sap.glx.adapter.app.ucon.UnifiedWebServiceCallClass.invoke(UnifiedWebServiceCallClass.java:174)
at com.sap.glx.core.dock.impl.DockObjectImpl.invokeMethod(DockObjectImpl.java:528)
at com.sap.glx.core.kernel.trigger.config.Script$MethodInvocation.execute(Script.java:245)
at com.sap.glx.core.kernel.trigger.config.Script.execute(Script.java:791)
... 12 more
Caused by: com.sap.glx.adapter.api.AdapterException: com.sap.engine.interfaces.sca.exception.SCADASException: Could not invoke service reference name b51513b6-379d-4c0b-be2a-a3b13d7fe23b, component name demo.sap.comreportissueprocessdcBPMcomponent, application name demo.sap.com/reportissueprocessdc.
at com.sap.glx.adapter.app.ucon.SCADASWrapperImpl.invoke(SCADASWrapperImpl.java:151)
at com.sap.glx.adapter.app.ucon.UnifiedWebServiceCallObject$PropagatedCall.run(UnifiedWebServiceCallObject.java:125)
... 23 more
Caused by: com.sap.engine.interfaces.sca.exception.SCADASException: Could not invoke service reference name b51513b6-379d-4c0b-be2a-a3b13d7fe23b, component name demo.sap.comreportissueprocessdcBPMcomponent, application name demo.sap.com/reportissueprocessdc.
at com.sap.engine.services.sca.das.SCADASImpl.invokeReference(SCADASImpl.java:362)
at com.sap.glx.adapter.app.ucon.SCADASWrapperImpl.invoke(SCADASWrapperImpl.java:116)
... 24 more
Caused by: com.sap.engine.interfaces.sca.config.exception.ESBConfigurationException: Configuration not found for application: demo.sap.com/reportissueprocessdc,composite:reportissueprocessdc,component:demo.sap.comreportissueprocessdcBPMcomponent,reference:b51513b6-379d-4c0b-be2a-a3b13d7fe23b,bindingType:WS
at com.sap.esi.esp.service.server.ESPServiceInterfaceImpl.getConfiguration(ESPServiceInterfaceImpl.java:450)
at com.sap.engine.services.sca.plugins.ws.WebServiceImplementationInstance.initWsdas(WebServiceImplementationInstance.java:193)
at com.sap.engine.services.sca.plugins.ws.WebServiceImplementationInstance.accept(WebServiceImplementationInstance.java:76)
at com.sap.engine.services.sca.das.SCADASImpl.invokeReference(SCADASImpl.java:335)
... 25 more
Caused by: com.sap.esi.esp.lib.mm.config.exceptions.ObjectNotExistsException: Configuration not found for application: demo.sap.com/reportissueprocessdc,composite:reportissueprocessdc,component:demo.sap.comreportissueprocessdcBPMcomponent,reference:b51513b6-379d-4c0b-be2a-a3b13d7fe23b,bindingType:WS
at com.sap.esi.esp.service.server.esb.ConnectivityConfigurationManagerImpl.readConfiguration(ConnectivityConfigurationManagerImpl.java:276)
at com.sap.esi.esp.service.server.ESPServiceInterfaceImpl.getConfiguration(ESPServiceInterfaceImpl.java:443)
... 28 more
Caused by: com.sap.esi.esp.lib.mm.config.exceptions.ObjectNotExistsException: Configuration not found for application: demo.sap.com/reportissueprocessdc,serviceRefId:reportissueprocessdc_demo.sap.comreportissueprocessdcBPMcomponent_b51513b6-379d-4c0b-be2a-a3b13d7fe23b_WS. Please check the configuration details from the NWA. You may have not assigned the Service Group to a Provider System, or the generation of the configuration has failed.
at com.sap.esi.esp.service.server.esb.ConnectivityConfigurationManagerImpl.readConfiguration(ConnectivityConfigurationManagerImpl.java:334)
at com.sap.esi.esp.service.server.esb.ConnectivityConfigurationManagerImpl.readConfiguration(ConnectivityConfigurationManagerImpl.java:263)
... 29 more
Date: 2010-06-16
Time: 19:17:16:800
Category: com.sap.glx.core.kernel.execution.LeaderWorkerPool
Location: com.sap.glx.core.kernel.execution.LeaderWorkerPool
Application: sap.com/com.sap.glx.process.ear
Thread: Galaxy 340 / Follower Worker
Data Source: j2ee\cluster\server0\log\defaultTrace_00.trc
Arguments:
DSR Transaction: c6a0ff48796211dfca1602004c4f4f50
Message ID: com.sap.BPM.core_svc.000047
Session: 0
Transaction:
User: SAP_BPM_Service
Time Zone: +0100
Customer Message Component: BC-BMT-BPM-SRV
DC Name: com.sap.glx.core.svc
Correlation ID: 5164050000004002
DSR Root Context ID: C6A0FF48796211DFCA1602004C4F4F50
DSR Connection: c6a0ff48796211dfca1602004c4f4f50
DSR Counter: 0
Host: dcwwwx11871
System: CE2
Instance: J00
Node: server0
Log ID: 02004C4F4F50039E000000010000162C

Hi,
Your Error Says
You may have not assigned the Service Group to a Provider System, or the generation of the configuration has failed. at com.sap.esi.esp.service.server.esb.ConnectivityConfigurationManagerImpl.readConfiguration
Procedure to Create Provide System
https://cw.sdn.sap.com/cw/docs/DOC-101203 (From the service where you are consuming)
Procedure to Create and Assign ServiceGroup
While importing the Enterprise Service into Automated Activity it will ask the name of Service Group.Please check what is the Service Group Name and Assign the Service Group to the Provider System by following the Below Procedure.
https://cw.sdn.sap.com/cw/docs/DOC-109461
Thanks
Srikanth

BPM Workspace User view related issue

PROBLEM SUMMARY_
Unable to see filtering options like SEARCH, ASSIGNEE and STATE in User View, I am able to see this in Generic Inbox of BPM workspace
DETAILED DESCRIPTION_
I am new to BPM & need some assistance on below scenario-
TASKS INVOLVED-*
My BPM process contains 2 tasks
1.     Initiator task-[Part of Requester role in my JDev Swim lane]
2.     User Task-To review the request-[Part of Reviewer role in my JDev Swim lane]
SCENARIO-+
Flow would be something like, requester enters details in request message & says submit. If request message length is less than 6 characters a review would be required & therefore process flow would go to reviewer task. Reviewer can Approve or Reject the request, if he approves the process will write the request message contents to a file, if the reviewer Rejects the request, requester task would be created again so as to ask requester to enter a message of length>6.
If entered request message is having length greater than 6, no review would be required. It will be a direct file write.
CHALLENGE-+
The challenge is each of these tasks –Initiator task & Review task would be created with DIFFERENT task numbers in BPM workspace, which I do NOT want. I want the Requester tasks task number to be propagated to Reviewer task and I would want to populate this as task number (May be under different column, say Request Id) of Reviewer task as well.
After reading Oracle BPM docs, I studied that this can achieved using Human tasks-Mapped variable concept.
I used protected mapped variable/flex variable:*Request Id* in both the above tasks to achieve this.
PROBLEM-*
Problem is in BPM workspace’s user view, here we go-
I created a user view:*HelloWorld* to display the task details, the columns I want are the default columns+Column for mapped attribute:*Request Id*.
Now even though the Request Id column is populated as expected, I cannot filter the View entries based on Assignee, State or perform any kind of other searches.
I understand that User views are built based basically on certain filters itself. But post the view creation if user has to make a search-say based on Mapped attribute:*Request Id* in this case, he won’t be able to do so.
This defeats the entire purpose of Mapped attributes. Oracle document says (check the last bullet point)-
+"Human workflow mapped attributes (formerly referred to as flex fields) store and query use case-specific custom attributes. These custom attributes typically come from the task payload values. Storing custom attributes in mapped attributes provides the following benefits:+
+•     They can be displayed as a column in the task listing+
+•     They can filter tasks in custom views and advanced searches+
*+•     They can be used for a keyword-based search"+*
So is this a bug with user views in workspace?
One more thing that I would like to add-Reason behind using Custom user views is-
1)     Generic Inbox of BPM Workspace does not give option to make the mapped attribute get displayed/Searched
2)     I want to customize the Tasklist.
Edited by: user12183391 on Oct 3, 2011 9:57 PM

Oh well...
It seems there's a bug with the XE Database... Sometimes it freezes some components and the SOA Plataform goes crazy.
Simple system reboot solved.

Deployment Exception after restore BPM Project from Consolidation system

Hi everybody,
in order to restore my bpm project in NWDS i overwrite all files under "_comp" folder with the same files from the cons_track
After that i could build and activate the project but i can not deploy it to the application server.
The old project was just undeployed.
How can i restore my projekt and deploy it to the application Server.
Should i change the BPM-Project name, if yes how can i do that? In context menu i can not rename the project.
In next Thread i will add the DeploymentException message.
Please help!
regards,
Sid

Hi everybody,
hier is the deployment exception:
Hi everybody,
hier is the deployment exception:
com.sap.engine.services.dc.api.deploy.DeployException: [ERROR CODE DPL.DCAPI.1027] DeploymentException.
Reason: ASJ.dpl_dc.001085 An error occurred while deploying the deployment item [company.com_bpmprochangebpm_process].
; nested exception is:
 com.sap.engine.services.dc.gd.DeliveryException: [ERROR CODE DPL.DC.3298] An error occurred during deployment of [company.com_bpmprochangebpm_process]. Cannot deploy it.
 at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deployItems(DeployProcessorImpl.java:891)
 at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deploy(DeployProcessorImpl.java:259)
 at com.sap.ide.eclipse.deployer.dc.deploy.DeployProcessor70.deploy(DeployProcessor70.java:104)
 at com.sap.ide.tools.services.dc.EngineDcDeployService.deployFiles(EngineDcDeployService.java:178)
 at com.sap.ide.tools.services.dc.EngineDcDeployService.deploy(EngineDcDeployService.java:92)
 at com.sap.ide.dii05.ui.internal.actions.dc.DcDeployAction$3.run(DcDeployAction.java:236)
 at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
Caused by: com.sap.engine.services.dc.cm.deploy.DeploymentException: ASJ.dpl_dc.001085 An error occurred while deploying the deployment item [company.com_bpmprochangebpm_process].
; nested exception is:
 com.sap.engine.services.dc.gd.DeliveryException: [ERROR CODE DPL.DC.3298] An error occurred during deployment of [company.com_bpmprochangebpm_process]. Cannot deploy it.
 at com.sap.engine.services.dc.cm.deploy.impl.OnlineDeployProcessor.performDelivery(OnlineDeployProcessor.java:244)
 at com.sap.engine.services.dc.cm.deploy.impl.BulkOnlineDeployProcessor.deploy(BulkOnlineDeployProcessor.java:62)
 at com.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor$DeployProcessorHelper.visit(AbstractDeployProcessor.java:273)
 at com.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:84)
 at com.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor.deploy(AbstractDeployProcessor.java:95)
 at com.sap.engine.services.dc.cm.deploy.impl.DeployThread.run(DeployThread.java:39)
 at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122)
 at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101)
 at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:328)
Caused by: com.sap.engine.services.dc.gd.DeliveryException: [ERROR CODE DPL.DC.3298] An error occurred during deployment of [company.com_bpmprochangebpm_process]. Cannot deploy it.
 at com.sap.engine.services.dc.gd.impl.ApplicationDeployer.deploy(ApplicationDeployer.java:134)
 at com.sap.engine.services.dc.gd.impl.InitialApplicationDeployer.performDeployment(InitialApplicationDeployer.java:130)
 at com.sap.engine.services.dc.gd.impl.InitialGenericDeliveryImpl.deploy(InitialGenericDeliveryImpl.java:57)
 at com.sap.engine.services.dc.cm.deploy.impl.OnlineDeployProcessor.performDelivery(OnlineDeployProcessor.java:210)
 ... 8 more
Caused by: com.sap.engine.services.deploy.server.utils.DSRemoteException: ASJ.dpl_ds.006193 Error while deploying ear file /usr/sap/PD3/J00/j2ee/cluster/server0/temp/tcbldeploy_controller/archives/23854/company.combpmprochange~bpm_process.sda; nested exception is:
 com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception during generating components of [company.com/bpmprochangebpm_process] application in [Galaxy_Content_Archive] container.
 at com.sap.engine.services.deploy.server.DeployServiceImpl.catchDeploymentExceptionWithDSRem(DeployServiceImpl.java:3729)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:336)
 at com.sap.engine.services.dc.gd.impl.ApplicationDeployer.deploy(ApplicationDeployer.java:116)
 ... 11 more
Caused by: com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception during generating components of [company.com/bpmprochangebpm_process] application in [Galaxy_Content_Archive] container.
 at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:541)
 at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:264)
 at com.sap.engine.services.deploy.server.application.DeploymentTransaction.begin(DeploymentTransaction.java:212)
 at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:429)
 at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:481)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:1860)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:384)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:334)
 ... 12 more
Caused by: com.sap.engine.services.deploy.container.DeploymentException: TxException
 at com.sap.glx.repository.deploy.content.ContentArchiveDeployContainer.deployArchive(ContentArchiveDeployContainer.java:1280)
 at com.sap.glx.repository.deploy.content.ContentArchiveDeployContainer.deploy(ContentArchiveDeployContainer.java:137)
 at com.sap.engine.services.deploy.server.utils.container.ContainerWrapper.deploy(ContainerWrapper.java:242)
 at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:538)
 ... 19 more
Caused by: java.lang.Exception: com.sap.engine.services.ts.transaction.TxRollbackException: Current transaction is marked for rollback
 at com.sap.engine.services.ts.transaction.TxManagerImpl.commitLevel(TxManagerImpl.java:587)
 at com.sap.transaction.TxManager.commitLevel(TxManager.java:237)
 at com.sap.glx.repository.deploy.content.ContentArchiveDeployContainer.deployArchive(ContentArchiveDeployContainer.java:1277)
 at com.sap.glx.repository.deploy.content.ContentArchiveDeployContainer.deploy(ContentArchiveDeployContainer.java:137)
 at com.sap.engine.services.deploy.server.utils.container.ContainerWrapper.deploy(ContainerWrapper.java:242)
 at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:538)
 at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:264)
 at com.sap.engine.services.deploy.server.application.DeploymentTransaction.begin(DeploymentTransaction.java:212)
 at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:429)
 at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:481)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:1860)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:384)
 at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:334)
 at com.sap.engine.services.dc.gd.impl.ApplicationDeployer.deploy(ApplicationDeployer.java:116)
 at com.sap.engine.services.dc.gd.impl.InitialApplicationDeployer.performDeployment(InitialApplicationDeployer.java:130)
 at com.sap.engine.services.dc.gd.impl.InitialGenericDeliveryImpl.deploy(InitialGenericDeliveryImpl.java:57)
 at com.sap.engine.services.dc.cm.deploy.impl.OnlineDeployProcessor.performDelivery(OnlineDeployProcessor.java:210)
 at com.sap.engine.services.dc.cm.deploy.impl.BulkOnlineDeployProcessor.deploy(BulkOnlineDeployProcessor.java:62)
 at com.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor$DeployProcessorHelper.visit(AbstractDeployProcessor.java:273)
 at com.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:84)
 at com.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor.deploy(AbstractDeployProcessor.java:95)
 at com.sap.engine.services.dc.cm.deploy.impl.DeployThread.run(DeployThread.java:39)
 at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122)
 at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101)
 at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:328)
Caused by: java.lang.IllegalStateException: Galaxy commit failed (for a possible cause, refer to the nested exception(s)
 at com.sap.glx.core.kernel.execution.TransitionManagerImpl$BoundPrimaryTransaction.beforeCompletion(TransitionManagerImpl.java:115)
 at com.sap.engine.services.ts.jta.impl.SynchronizationWrapper.beforeCompletion(SynchronizationWrapper.java:36)
 at com.sap.engine.services.ts.jta.impl2.TXR_TransactionImpl.beforePrepare(TXR_TransactionImpl.java:518)
 at com.sap.engine.services.ts.jta.impl2.TXR_TransactionImpl.commit(TXR_TransactionImpl.java:1026)
 at com.sap.engine.services.ts.jta.impl2.TXR_TransactionManagerImpl.commit(TXR_TransactionManagerImpl.java:317)
 at com.sap.engine.services.ts.transaction.TxManagerImpl.commitLevel(TxManagerImpl.java:576)
 ... 24 more
Caused by: com.sap.glx.core.kernel.api.TransitionRollbackException: Transaction locked for rollback; Commit refused.
 at com.sap.glx.core.kernel.mmtx.AbstractTransactionBase.rollback(AbstractTransactionBase.java:801)
 at com.sap.glx.core.kernel.mmtx.AbstractTransaction.do_precommit(AbstractTransaction.java:192)
 at com.sap.glx.core.kernel.mmtx.AbstractTransaction.commit(AbstractTransaction.java:79)
 at com.sap.glx.core.kernel.execution.TransitionManagerImpl$BoundPrimaryTransaction.beforeCompletion(TransitionManagerImpl.java:113)
 ... 29 more
Caused by: com.sap.glx.core.dock.api.DockException: Adapter com.sap.glx.adapter.internal.Transformer didn't comply with configuration
 at com.sap.glx.core.dock.impl.DockingPortal.configure(DockingPortal.java:691)
 at com.sap.glx.core.dock.impl.DockingPortal.configureCallback(DockingPortal.java:494)
 at com.sap.glx.core.dock.impl.DockingPortal.runConfigureCallback(DockingPortal.java:1008)
 at com.sap.glx.deploy.impl.DeployControllerImpl$InternalActuator.runStdDeploy(DeployControllerImpl.java:720)
 at com.sap.glx.deploy.impl.DeployControllerImpl$InternalActuator.run(DeployControllerImpl.java:531)
 at com.sap.glx.core.kernel.RuntimeManager.requestRuntimeMode(RuntimeManager.java:989)
 at com.sap.glx.deploy.impl.DeployControllerImpl$InternalActuator.execute(DeployControllerImpl.java:478)
 at com.sap.glx.deploy.impl.DeployControllerImpl$InternalActuator.deploy(DeployControllerImpl.java:445)
 at com.sap.glx.core.resource.impl.j2ee.rrdeploy.KernelHandlerImpl.addVersion(KernelHandlerImpl.java:92)
 at com.sap.glx.repository.service.impl.RuntimeRepositoryDeployManager.handlerDistributionForDeployment(RuntimeRepositoryDeployManager.java:2548)
 at com.sap.glx.repository.service.impl.RuntimeRepositoryDeployManager.deployArchive(RuntimeRepositoryDeployManager.java:1522)
 at com.sap.glx.repository.service.impl.RuntimeRepositoryDeployManager.deploy(RuntimeRepositoryDeployManager.java:335)
 at com.sap.glx.repository.service.impl.RuntimeRepositoryDeployManager.deploy(RuntimeRepositoryDeployManager.java:257)
 at com.sap.glx.repository.service.impl.RuntimeRepositoryDeployManager.deploy(RuntimeRepositoryDeployManager.java:247)
 at com.sap.glx.repository.deploy.content.ContentArchiveDeployContainer.deployArchive(ContentArchiveDeployContainer.java:1265)
 ... 22 more
Caused by: com.sap.glx.adapter.api.AdapterException: Adapter com.sap.glx.adapter.internal.Transformer has refused deploy unit 7f61b77fdf52c705313469f8de76de24 using configuration mode DEPLOYMENT
 at com.sap.glx.core.dock.impl.DockingPortal.configure(DockingPortal.java:669)
 ... 36 more
Caused by: java.lang.IllegalStateException: Rule for trigger '<"company.com/bpmpro/change/bpm_process/StartChangeProcess","Change">', reactor '<"com.sap.glx.adapter.BPMNAdapter","Event_0_Start_7f61b77fdf52c705313469f8de76de24">', attribute 'ppHash' present
 at com.sap.glx.core.internaladapter.Transformer$TransformerTemplateAccessor$GeneratorTemplate$GeneratorConfigurationAccessor.insertRule(Transformer.java:2634)
 at com.sap.glx.core.internaladapter.Transformer$TransformerTemplateAccessor$GeneratorTemplate$ImplementedConfigurationHandler.configure(Transformer.java:2717)
 at com.sap.glx.core.internaladapter.Transformer$TransformerTemplateAccessor$GeneratorTemplateHandler.configure(Transformer.java:3224)
 at com.sap.glx.core.internaladapter.Transformer.configure(Transformer.java:3408)
 at com.sap.glx.core.dock.impl.DockingPortal.configure(DockingPortal.java:666)
 ... 36 more
regards,
Sid
regards,
Sid

BPM Deployment Exception

Hi ALl,
while deploying my BPM application i'm getting this exception, can any body let me know what's could be the problem.
Thanks
com.sap.engine.services.dc.api.deploy.DeployException: [ERROR CODE DPL.DCAPI.1027] DeploymentException.
Reason: ASJ.dpl_dc.001085 [ERROR CODE DPL.DC.3077] An error occurred while deploying the deployment item [demo.sap.com_requestbpm].
; nested exception is:
     com.sap.engine.services.dc.gd.DeliveryException: [ERROR CODE DPL.DC.3298] An error occurred during deployment of [demo.sap.com_requestbpm]. Cannot deploy it.
     at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deployItems(DeployProcessorImpl.java:891)
     at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deploy(DeployProcessorImpl.java:259)
     at com.sap.ide.eclipse.deployer.dc.deploy.DeployProcessor70.deploy(DeployProcessor70.java:104)
     at com.sap.ide.tools.services.dc.EngineDcDeployService.deployFiles(EngineDcDeployService.java:162)
     at com.sap.ide.tools.services.dc.EngineDcDeployService.deploy(EngineDcDeployService.java:85)
     at com.sap.ide.dii05.ui.internal.actions.dc.DcDeployAction$3.run(DcDeployAction.java:234)
     at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
Caused by: com.sap.engine.services.dc.cm.deploy.DeploymentException: ASJ.dpl_dc.001085 [ERROR CODE DPL.DC.3077] An error occurred while deploying the deployment item [demo.sap.com_requestbpm].
; nested exception is:
     com.sap.engine.services.dc.gd.DeliveryException: [ERROR CODE DPL.DC.3298] An error occurred during deployment of [demo.sap.com_requestbpm]. Cannot deploy it.
     at com.sap.engine.services.dc.cm.deploy.impl.OnlineDeployProcessor.performDelivery(OnlineDeployProcessor.java:188)
     at com.sap.engine.services.dc.cm.deploy.impl.BulkOnlineDeployProcessor.deploy(BulkOnlineDeployProcessor.java:57)
     at com.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor$DeployProcessorHelper.visit(AbstractDeployProcessor.java:229)
     at com.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:83)
     at com.sap.engine.services.dc.cm.deploy.impl.AbstractDeployProcessor.deploy(AbstractDeployProcessor.java:91)
     at com.sap.engine.services.dc.cm.deploy.impl.DeployThread.run(DeployThread.java:34)
     at com.sap.engine.core.thread.execution.Executable.run(Executable.java:115)
     at com.sap.engine.core.thread.execution.Executable.run(Executable.java:96)
     at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:314)
Caused by: com.sap.engine.services.dc.gd.DeliveryException: [ERROR CODE DPL.DC.3298] An error occurred during deployment of [demo.sap.com_requestbpm]. Cannot deploy it.
     at com.sap.engine.services.dc.gd.impl.ApplicationDeployer.deploy(ApplicationDeployer.java:118)
     at com.sap.engine.services.dc.gd.impl.InitialApplicationDeployer.performDeployment(InitialApplicationDeployer.java:108)
     at com.sap.engine.services.dc.gd.impl.InitialGenericDeliveryImpl.deploy(InitialGenericDeliveryImpl.java:51)
     at com.sap.engine.services.dc.cm.deploy.impl.OnlineDeployProcessor.performDelivery(OnlineDeployProcessor.java:163)
     ... 8 more
Caused by: com.sap.engine.services.deploy.server.utils.DSRemoteException: [ERROR CODE DPL.DS.6193] Error while ; nested exception is:
     com.sap.engine.services.deploy.container.DeploymentException: Deploy Exception
     at com.sap.engine.services.deploy.server.DeployServiceImpl.catchDeploymentExceptionWithDSRem(DeployServiceImpl.java:4712)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:327)
     at com.sap.engine.services.dc.gd.impl.ApplicationDeployer.deploy(ApplicationDeployer.java:104)
     ... 11 more
Caused by: com.sap.engine.services.deploy.container.DeploymentException: Deploy Exception
     at com.sap.glx.repository.deploy.content.ContentArchiveDeployContainer.deployArchive(ContentArchiveDeployContainer.java:1110)
     at com.sap.glx.repository.deploy.content.ContentArchiveDeployContainer.deploy(ContentArchiveDeployContainer.java:133)
     at com.sap.engine.services.deploy.server.utils.container.ContainerWrapper.deploy(ContainerWrapper.java:195)
     at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:526)
     at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:249)
     at com.sap.engine.services.deploy.server.application.DeploymentTransaction.begin(DeploymentTransaction.java:188)
     at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:493)
     at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:544)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:2534)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:380)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:325)
     ... 12 more
Caused by: com.sap.glx.repository.exceptions.RuntimeRepositoryException: com.sap.glx.repository.exceptions.RuntimeRepositoryException: The runtime repository handler "Exception Handler" reported an exception while trying to add new versions for component demo.sap.com/requestbpm
     at com.sap.glx.repository.service.impl.RuntimeRepositoryDeployManager.deploy(RuntimeRepositoryDeployManager.java:272)
     at com.sap.glx.repository.deploy.content.ContentArchiveDeployContainer.deployArchive(ContentArchiveDeployContainer.java:1103)
     ... 22 more
Caused by: com.sap.glx.repository.exceptions.RuntimeRepositoryException: The runtime repository handler "Exception Handler" reported an exception while trying to add new versions for component demo.sap.com/requestbpm
     at com.sap.glx.repository.service.impl.RuntimeRepositoryDeployManager.deployArchive(RuntimeRepositoryDeployManager.java:1261)
     at com.sap.glx.repository.service.impl.RuntimeRepositoryDeployManager.deploy(RuntimeRepositoryDeployManager.java:246)
     ... 23 more
Caused by: com.sap.glx.repository.exceptions.HandlerException: com.sap.glx.deploy.api.DeployException: java.io.IOException: Could not instantiate network 766fd376b1d8b36bea9b92a25fa35004/StartDeadlineIsCriticalException.
The given network does exceed the maximum revision number. The given network has revision number 2.2 (Galaxy exception compiler as of NetWeaver CE 7.20. Give yourself to the dark side.) but maximum possible revision number is 1.1.
     at com.sap.glx.core.resource.impl.j2ee.rrdeploy.KernelHandlerImpl.addVersion(KernelHandlerImpl.java:84)
     at com.sap.glx.repository.service.impl.RuntimeRepositoryDeployManager.deployArchive(RuntimeRepositoryDeployManager.java:1255)
     ... 24 more
Caused by: com.sap.glx.deploy.api.DeployException: java.io.IOException: Could not instantiate network 766fd376b1d8b36bea9b92a25fa35004/StartDeadlineIsCriticalException.
The given network does exceed the maximum revision number. The given network has revision number 2.2 (Galaxy exception compiler as of NetWeaver CE 7.20. Give yourself to the dark side.) but maximum possible revision number is 1.1.
     at com.sap.glx.deploy.impl.DeployControllerImpl$InternalActuator.deploy(DeployControllerImpl.java:448)
     at com.sap.glx.core.resource.impl.j2ee.rrdeploy.KernelHandlerImpl.addVersion(KernelHandlerImpl.java:78)
     ... 25 more
Caused by: java.io.IOException: Could not instantiate network 766fd376b1d8b36bea9b92a25fa35004/StartDeadlineIsCriticalException.
The given network does exceed the maximum revision number. The given network has revision number 2.2 (Galaxy exception compiler as of NetWeaver CE 7.20. Give yourself to the dark side.) but maximum possible revision number is 1.1.
     at com.sap.glx.core.kernel.trigger.config.CSVNetBuilder.parse(CSVNetBuilder.java:1022)
     at com.sap.glx.core.kernel.trigger.config.CSVNetBuilder.parse(CSVNetBuilder.java:274)
     at com.sap.glx.deploy.impl.DeployControllerImpl$InternalActuator.deploy(DeployControllerImpl.java:430)
     ... 26 more

Hi Raman,
As Harsha suggested , both NWDS and your CE engine should be in sync
Log says issue with the versions.
"The given network has revision number 2.2 (Galaxy exception compiler as of NetWeaver CE 7.20. Give yourself to the dark side.) but maximum possible revision number is 1.1. at "
Anil

Nw-bpm and ccbpm

hi,
can someone explain to me the difference between nw-bpm ("galaxy") and ccbpm (part of nw-pi):
-> what is the usage for both?
-> how are they related?
-> will ccbpm be replaced by nw-bpm some time in the future?
-> for new projects, is it still recommended to use ccbpm?
thanks a lot for your help!
heiko

Hello Heiko,
to make it short:
ccBPM:
- special-purpose process engine for System-centric processes (orchestrate PI messages on the PI integration hub)
- BPEL-compliant
- no end-user involvement (--> no Human Tasks)
NetWeaver BPM:
- general-purpose process engine with a very good support of Human-centric processes
- standards-based (e.g. BPMN, WSDL, XSD, WS-Human Task, ...)
There is no explicit relationship between those two environments. Currently, the intersection of common use cases they cover is quite small, although this may change in the future.
Best regards,
Markus
Edited by: Markus Kinateder on May 6, 2009 11:15 AM

Problem in Build BPM DC

hello all,
I am getting error while building a BPM Dc follwing error shows in Build log
"BC-BMT-BPM-SRV com.sap.tc.glx.BpemTask execute() - Event def: com.sap.glx.ide.model.galaxy.workflow.ErrorEventDefinition (Java Type)
Galaxy.Workflow.ErrorEventDefinition (MOF Type)PF.DefaultDataArea:DCs/sysco.com/mdm/vendor/mgmt/prc/maint_vend/_comp/src/bpmn/localsme_sub_prc.bpmn#E01DFA6E343573EF926711E0A21400216A4F8A83 (MRI)"
can anybody tell me how to avoid this error.
thanks in advance

Hi,
Can you paste the entire trace.
Thanks,
Arun.

BPM - Formerly galaxy

Similar Messages

Maybe you are looking for