Block next calls to integration process

Hi,
I have a BPM which makes 2 succesive calls to web service (synchronous).
If there is a problem in the calls to any of the 2 web services, I want to raise an error and stop all other calls to this BPM to go through.
Right now, if I make 1 call and the BPM is in error. When I make the second call, it still goes and tries to execute.
The problem is , the sequence of calls must be maintained so , if the first call fails , the second should wait until the first is resolved.
Is this possible ?
Thanks.

If there is a problem in the calls to any of the 2 web services, I want to raise an error and stop all other calls to this BPM
to go through.
Can do this using the Sync Step in a block and then define an Exception Branch and then in this exception branch use a Control Step (Action-> Throw Alert).....then have another Control Step (Action> Cancel Process)....both Control Steps in the Exception Branch....
Now for the catch:
The problem is , the sequence of calls must be maintained so , if the first call fails , the second should wait until the first is resolved.
As Michal said this is not possible.....you cannot (rather no one can) design the BPM to wait for resolution of Step1 and then again excute the Step1 and then execute Step2.....this is the functionality of the BPM.....
Regards,
Abhishek.

Similar Messages

Integration Process not continuing after Synchronous BAPI call

I have an integration process that splits up a batch file of purchase orders into single purchase order messages. This allows me to use the "ForEach" block to call the synchronous BAPI_PO_CREATE1.
I have managed to get the process to call the BAPI and create the purchase order. The response message arrives back though the abstract synchronous interface and is mapped to the asyncronous response message. After that the process seems to hold where I am expecting it to continue on the process and be appended to a container storage list for mapping to a single return message.
I have not set up any correlation sets as I thought they wouldn't be needed for a sychronous call.
Has anyone got any advice on my approach to this process and how I might fix it.
Thanks in advance

Hi Bhavesh,
There are no errors as such in the SXMB_MONI but it gets as far as the Inbound Message (PE_ADAPTER) stage after the Sych BAPI call.
Also the SOAP Header at this stage seems to be missing "sysnchronous" or "asynchronous" in the SAP:ProcessingMode tags.
The technical workflow is as follows
FTP Batch file outbound to Integratin Process Receive (Async)
Transform message into a Multiline list of BAPI_PO_CREATE1.request (async abstract)
Enter "For Each" Block using the multiline list.
BAPI_PO_CREATE1 mapped to synchronous abstract interface
synchronous abstract interface mapped to BAPI_PO_CREATE.request and response
BAPI_PO_CREATE.response mapped to async BAPI_PO_CREATE.response
async BAPI_PO_CREATE.response appended to multiline list
Exit block
Transform multiline response list into single line response
FTP inbound
As far as I can make out I have not correctly configured the receiver of PO_CREATE1.response after it has been mapped from the sync to async so it just persists it and sits there waiting or it is waiting for somethign else to happen.
Let me know if I can clarify anything further.
Thanks
Ben

Block in Integration Process produce error

Hi,
there is a strange problem with an Integration Process.
I have a loop for collecting messages.
If I paste a new Block in the process after the loop there is no problem,
but if I put the loop inside the Block the process ends with an error
right after collecting the first message.
Somebody has an idea?
Thanks and regards
Patrick

Hi,
guess i have exactly the problem like in this thread:
BPM error
Problem is solved now with using a new SPS (14 for NW04s).
Regards
Patrick
Edited by: Patrick Koehnen on Apr 8, 2008 2:37 PM

IN PROCESS INSPECTION, QM operation blocking next PP Operation

Evening dear members.
It is possible to create a QM operation which could block the next PP operation on a PP recipe/route, until the QM one is released/confirmed/finished.?
Example:
10 PP operation CLEANING
20 QM operation MICROBIOLOGY TESTS
**if results of 20 are A-OK,,,,release/open/allow**
30 PP operation 1st PP OPERATION
40 QM operation DOESNT BLOCK next operation
50 PP....... and so on
If yes, what do I have to mantain to do so?
Appreciate your feedback

hi,
Create one new Control key for Inspection operations in:
QCC0>Quality Planning>Inspection Planning>Operation>Define Control Keys for Insp. Operations.
If it is for QM operation, do not forget to flag "insp char. required".
And in "Confirmation" field, Select "1" Milestone Confirmation.
now, if you assign this key (With Milestone Confirmation) for Operation 0020,0030, 0040;
System will not allow to Confirm 0030,0040 unless 0020 is not confirmed.
Check this in your Case. i hope it will solve your problem.
Regards,
Amol

Handling fault messages in an Integration Process (bpm)

I have a bpm in PI 7.11 which performs a synch call to an external webservice. In addition to the request/response, that webservice can also generate two faults: ObjectNotFoundFault and generalfault. I am having trouble handling these faults - when a fault occurs my handler is not being invoked and thus the bpm process stops/errors. When I look at the underlying process (via txn swi1), I see the exact error text:
"No exception defined for fault message ObjectNotFoundFault http://www.companyb.com/services/olsa_v1_0/"
From what I understand within the bpm synch call step to the webservice I need to do the following to handle the exception/fault:
- put the synch call (to the webservice) into a block
- add an exception branch to that block named let's say A & set the exception handler of that block to be A
- in the exception setting of that synch step, select A
In my case, I don't care about the fault details other than to ensure it does not stop the whole Integration Process, so in my exception branch I don't do anything. I did try adding a control step within it too (as per SAP Press text book).
Is there anything else I need to do here? I am not mapping the returned fault - does the fault need to be mapped (not sure how I would do this given that the synch step uses an abstract interface and therefore to my knowledge no fault mapping can be done)?
There are 2 Notes that describe my issue exactly:
https://service.sap.com/sap/support/notes/1484903
https://service.sap.com/sap/support/notes/1158699 <-- this one refers more to me, but we already have in 7.11
Can anyone let me know exactly the steps I would perform to handle these faults - does the exception name / handler A above need to be named the actual exception / fault ObjectNotFoundFault?
Any help appreciated.
Thanks,
Keith)?
Any help appreciated.
Thanks,
Keith

Thanks - my scenario I guess is #2 of that blog. But is your take that even if I don't care what is in the fault message, i.e. I don't care about the contents of it but rather I just want to continue on from it, that I still need to perform this java coding? It's not clear to me from what he says - it seems to me he does the java coding to actually capture the contents of the message. I am in fact using the soap axis adapter too, as he is. The screen shot showing the exception branch is basically what I have.
Regards,
Keith

Spliting a Message to reuse an Integration Process made for a single one.

Hi,
I have a Integration Process that works well for a XML message of the type:
<EMESSAGE>
<PERSON>
 <TAG_1>
 <TAG_2>
</PERSON>
</EMESSAGE>
My BPM process the data for the Person correctly.
Now I want to be able to tried more than one person per input message, some thing like:
<EMESSAGE>
<PERSON>
 <TAG_1>
 <TAG_2>
</PERSON>
<PERSON>
 <TAG_1>
 <TAG_2>
</PERSON>
<PERSON>
 <TAG_1>
 <TAG_2>
</PERSON>
</EMESSAGE>
I build a 1:n Interface Mapping that creates me the following structure:
<Messages>
<Message1>
<EMESSAGE>
<PERSON>
 <TAG_1>
 <TAG_2>
</PERSON>
</EMESSAGE>
</Message1>
<Message2>
<EMESSAGE>
<PERSON>
 <TAG_1>
 <TAG_2>
</PERSON>
</EMESSAGE>
</Message2>
<Message3>
<EMESSAGE>
<PERSON>
 <TAG_1>
 <TAG_2>
</PERSON>
</EMESSAGE>
</Message3>
</Messages>
But when I use a ForEach Block in my new BPM, it doesn't work if there is more then 1 person in the input. The error message I got is:
<?xml version="1.0" encoding="utf-8" ?>
- <MappingTrace>
<Trace level="1" type="T">Mapping-Namespace:http://domain.com/xi/domain_4</Trace>
<Trace level="1" type="T">Mapping-Name:IM_CPM_AbsSync_to_N_CPM_AbsSync</Trace>
<Trace level="1" type="T">Mapping-SWCV:3E235261F43111DDB40AC952C0A80C15</Trace>
<Trace level="1" type="T">Mapping-Step:1</Trace>
<Trace level="1" type="T">Mapping-Type:XSLT</Trace>
<Trace level="1" type="T">Mapping-Program:CPM_to_N_ContextPersonMessage</Trace>
<Trace level="3" type="T">Mapping has one input message.</Trace>
<Trace level="3" type="T">Dynamic Configuration Is Empty</Trace>
<Trace level="3" type="T">Multi mapping required.</Trace>
<Trace level="3" type="T">Creating XSLT mapping CPM_to_N_ContextPersonMessage.</Trace>
<Trace level="3" type="T">Load 3e235261-f431-11dd-b40a-c952c0a80c15, http://domain.com/xi/domain_4, -1, CPM_to_N_ContextPersonMessage.xsl.</Trace>
<Trace level="3" type="T">Search CPM_to_N_ContextPersonMessage.xsl (http://domain.com/xi/domain_4, -1) in swcv 3e235261-f431-11dd-b40a-c952c0a80c15.</Trace>
<Trace level="2" type="T">Call XSLT processor with stylsheet CPM_to_N_ContextPersonMessage.xsl.</Trace>
<Trace level="2" type="T">Returned form XSLT processor.</Trace>
<Trace level="3" type="T">XSLT transformation: CPM_to_N_ContextPersonMessage.xsl completed with 0 warning(s).</Trace>
<Trace level="3" type="T">Dynamic Configuration Is Empty</Trace>
<Trace level="1" type="T">Content Type application/xml</Trace>
<Trace level="1" type="T">No interface specified for parameter 2</Trace>
</MappingTrace>
Does someone have any idea or a suggestion on how to reuse my BPM that works for a single person?
Thanks in advance for your suggestions.
greg

ok no success for the moment, so I will try to describe my BPM more precisely:
The DT I use can contain up to 1'000 PERSON record inside a unique EMESAGE reccord (the root element)
My containers: (all are of type Abstract Interface of my DT)
Input (Process)
requestList(Process) Multiline
request(block)
response(block)
Receive Request Step
Message: input
Start Process: Yes
Mode : Async.
Split (Transformation) Step
IM: My Interface that does the 1Message with N PERSON records to N Messsages with 1 PERSON record
Create new transaction: Yes
Source: input
Target: requestList
Block Step
Mode: ForEach
Block Start: New transaction
Block End: New transaction
Multiline_Element: RequestList
CurrentLine: request
No end condition
Inside the block
My Sync Send call to a BAPI
Source: request
Target: response
A final Async Send step
Message: response.
The workflow stop at the Transform step, as if hte fact that many messages come in result could not be handled back. Here are the details for the Interface mapping used in the transformation step:
Source: MyDataTypeAbstractAsynchroneInterface
Occurrence: 1
Destination:
Occurrences: 0:unbounded
Mapping program: the following XSLT:
<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet version="2.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
 <xsl:output method="xml" version="1.0" encoding="UTF-8" indent="yes"/>
 <xsl:template match="EPERSON">
 <ns0:Messages xmlns:ns0="http://sap.com/xi/XI/SplitAndMerge">
 <xsl:for-each select="CONTEXTPERSON">
 <xsl:element name="ns0:Message{position()}">
 <EPERSON xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="ContextPersonMessage">
 <xsl:element name="CONTEXTPERSON">
 <xsl:attribute name="personid"><xsl:value-of select="@personid"/></xsl:attribute>
 </xsl:element>
 
 </EPERSON>
 </xsl:element>
 </xsl:for-each>
 </ns0:Messages>
 </xsl:template>
</xsl:stylesheet>
Still any suggestions ?
The trace of the error is the same as before, so I won't copy paste it again.

Integration Process does not start

Hi guru's
My scenario is this. From ECC we send Idocs to PI. We have an integration process to receive the idocs because only max 9999 are passed in the port.
We run just around 11000 CREMAS idocs now.
The problem is that the integration process does not start on our QA environment while it does start on DEV environment.
I've run many checks on both environments and they all look the same.
To name a few:
* Cache are all green and up-to-date.
* I checked the WF models which are behind the Integration Process and they are the same.
* Event correlation is correct in both environments
* When i test the idocs are correctly sent from ECC to PI.
However on DEV I see in transaction SXMB_MONI_BPE i see that the integration process is triggered and started. It waits 10 minutes and collects any messages that come in, and then bundles these and sends them on to the receiver.
On QA i do not see the Integration Process being started. Only records i see in SXMB_MONI_BPE are three work items, 2 completed, 1 ready, all 3 are called waiting for event.
I'm probably missing some configuration somewhere but what could it be?
Regards
Robert

Hi Eng Swee,
Thx. I checked it already and it works fine.
Meanwhile i did do some changes and some retests and now i saw somewhere that all my tests were creating more steps in an already started integration process, that was still waiting.
I now cleared some old workitems and started afresh.
What i see now is:
1) the BPM process start correctly
2) it receives 1 or 2 or 3 or n messages
3) it then waits for the deadline to finish, i.e. it should run for 10 minutes and then proceed to the next step which is sending the collected idocs to receiver.
On DEV the deadline works fine. On QA it doesn't.
IN SWU3 i have done the customizing and it shows green, so that part is OK.
Still the deadline is passed and it doesn't have the desired effect on mu BPM process (workflow).
Are there any other checks i can do to see if the deadline mechanism is properly working?
Is there a maybe a manual step i can do to trigger the deadline? Then at least i get some information on where the real problem is.
(Sorry for earlier confusion but i hadnt realized that there was still a process running)
Regards
Robert

Slow paralel processing (parforeach) in an integration process

Hi all,
I've an integration process with the following steps:
1) Receive a message;
2) Transform: map this message to a multiline message;
3) Block: configured for parforeach mode, it send assynchronously the message n times (each line from the multiline message is a new message).
I'm putting 50 messages in this integration process and the difference between the first and the last message processed is 65 seconds. I have the following questions:
1) Is this process slow in our system or this time is expected?
2) Where can I make this process faster?
Another question is: Is BPM and Integration process the same thing?
Thanks for any help,
Alessandro.
XI 3.0, SP10 in HPUX with much RAM

Hi Frank,
in case you are using QoS EO you will be able to tune partially through the tuning parameters in the integration engine (sxmb_adm), although I think you probably know that. However there are additionally some issues you could consider.
Regarding your question of setting the rfc adapter max connections to 50 I would strongly suggest you NOT to do it. I imagine you will get outofmemmory errors in doing that. Start with a lower number, perhaps 5 is ok, and then you can test, raising this value a bit, but 50 seems to me to be too high. You could also think about tuning in the visual admin, the Messaging system service, that is, SAP XI AF Messaging, parameter "messaging connections", the values for consumers, recvmaxConsumers, call max consumers, rqst max consumers etc. Additionally tune the MaxThreadcount parameter. The tuning guide advises you to set a 300, but you could test other values too.
Be careful, again when doing this tuning, because when trying to have high numbers, as I explained you, you may have memory problems because the heap size runs out. It will not always be good to increase the heap size excesively. Instead, it is much better to add an extra node for this purpose.
I hope this helps you a bit. Regards, Jaime

How to catch the error occurred in Integration Process, and then save it?

1. how to catch the error occurred in Integration Process, and then save the detailed error message to the file?
2. there are fault message type for inbound message interface, how to use the fault message type in IR?
Thanks,
Michael
Message was edited by: Spring Tang
inital
Message was edited by: Spring Tang
detailed message output
Message was edited by: Spring Tang
fault message type

Hi Spring,
If u give an exception step along with your Transformation Step, whenever some error occurs in your message mapping, this exception block wil be triggered.
You can configure your exception block to do all exception processing that you want. This exception handling is like any other java Exceptio n Handler. You can do anything that you want in your exception handler block on the basis of your requirements.
If an exception is triggered at runtime, the system first searches for the relevant exception handler in surrounding blocks. If it does not find the correct exception handler, it continues the search in the next block in the block hierarchy.
When the system finds the correct system handler, it stops all active steps in the block in which the exception handler is defined and then continues processing in the exception handler branch. Once the exception handler has finished processing, the process is continued after the block.
If the system fails to find an exception handler, it terminates the integration process with an error.
Regards,
Bhavesh

Integration Process - Exception Handling

Hi,
I have developed an integration process, which call web-service, and catch it's exception. The problem is that the WS returns generic exception (SYSTEM) for all exceptions, but with different text for each one.
Is there any way to get the exception text (the text itself and not the type), analyze it and handle the process correspondingly?

Hi Shai,
When you are calling the web-service method in BPM, put it in a block.....in the exception branch of the block, the control will go when the web-service will give exception.........so then put a switch in the exception branch - put the exception message as a condition for switching - do switching on basis of message text - and in the switch branches, do what you want to do for those exceptions.
Hope it solves your query.
Thanks,
Rajeev Gupta

Exception in Integration Process?

Hi,
How can I create an exception in the integration process?
Thanks for yiur help.
Regards.
Stefan

hi Stefan,
While designing ur Integration Process , u have a step called "BLOCK" . In which u have to types of branches 'Exception Handler' and a 'Dead line Branch'.
U can design ur Exception handling steps in the 'Exception handler' branch and move the control to that branch in case if some Exception Occurs.
For Further Information
http://help.sap.com/saphelp_erp2004/helpdata/en/33/4a773f12f14a18e10000000a114084/frameset.htm
Regards
Shailesh

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.

Missing sender information in message from Integration Process

Hi All,
I am testing a scenario uses Integration Process. This Integration process sends out a async message but this message has empty sender tag in header , Because of this routing rules and agreements defined for this are not triggered and message goes into error state.
There is sender interface Information in message header but not integration process information. I am working on SAP NetWeaver PI 7.1 system. This is working from other synchronous interface in same process.
Routing rule and receiver agreement has sender as mandatory field, so can not define generic set without sender component.
I went through SAP Note 807640 But there is no information about such error.
Am I missing something in configuration? Please let me know how can i configure Routing Rule and Interface Determination for this scenario.

Thanks for replying to the post.
Integration process is used as a async-sync bridge. Following are high level steps.
1. Receive async FI message from sender
2. Map message to BAPI SAP FI document
3. call Sync BAPI.
4. Map the response of BAPI.
5. Post it back to sender in async mode.
I am having problem in step 5 where message is coming out of BPE without its own name (i.e sender name). Thus it does not triggers Routing rules and fails.

Changes to Integration Process not reflected at runtime.

I have changed an Integration Process (eg removed a loop) and then activated this in IR and ensured that RunTime Cache is refreshed - I even forced another Run Time Cache refresh via SXI_CACHE.
however the Process is still running under the old version (I can see this from SXMB_MONI_BPE and drilling down into the workflow graphic).
How do I get XI to run the next time with the new version of my process ?

I think you will get an answer sooner when you post in the XI forum which you can find[here.|Process Integration (PI) & SOA Middleware;
Regards,
Martin
Edited by: Martin Nooteboom on Apr 18, 2008 1:20 PM

Sending step in Integration Process waiting for Acknowledgement infinitely

In process I had to send an MATMAS, CLFMAS and CNPMAS. The data for
this IDoc comes in one message from third party system. So, my
Integration Process has receive step (to collect a data), and three
send-steps (for MATMAS, for CLFMAS, for CNPMAS), one by one. The
receive-step catch an inbound message and then (without transforms)
send this message to each of this three send-steps in Asynchronous
mode. The inbound message transforms in Interface Determination to
IDoc. Three steps, one Interface Determination with three conditions,
that looks
like «ProcessStep=send_matmas», «ProcessStep=send_clfmas», «ProcessStep=s
end_cnpmas», and in this place I set a mapping to transform inbound
message to IDoc. All send-steps has property Acknowledgement, which set
to Transport value. So in first send-step MATMAS goes to R3, then R3 in
response send ALEAUD IDoc (trans WE05 shows an incoming MATMAS and
outgoing ALEAUD); ALEAUD comes to XI (trans IDX5 shows inbound and
outbound messages), but ALEAUD didnu2019t transforms to XI Acknowledgement.
And there is no any CLFMAS or CNPMAS, because all processes sleeps in
their first send-steps (trans SWWL shows a many STARTED processes).
Each send-step waits for event u2018SEND_OK_TRANSPORTu2019. Moreover, if I use
trans sxmb_moni to monitor this situation and if I press refresh (F5
button) every time, sxmb_moni every time requests a status of
Acknowledgements, XI transform ALEAUD to Ack, send-step in process
catch this status, process wake up and moves to next send-step (which
sends an CLFMAS and waits for Ack). By continuously pressing refresh
(F5) in sxmb_moni all process becomes COMPLETED (trans SWWL), all
ALEAUD transforms to XI Ack and all IDocs goes to R3. But pressing F5
itu2019s not a solution for integration.

Hi Igor,
I dont think your manual refresh changes the status . The status changes is the status change of GUI . The system will take how much so ever it needs to take and not as per your manual refresh.
Regards
joel

Block next calls to integration process

Similar Messages

Maybe you are looking for