Automated activity not executing in BPM process

Question

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

Answer 1

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