BPM process most of the time not started,

[Former Member]

Hi XI dudes,

In our latest XI scenario we read a file from a shared folder (on the same host as the xi server is installed) and we pass the input into an BPM scenario.

There is however a very annoying behaviour: the file is always read correctly, but is most of the time (75% fails) not passed towards the BPM. It seems that in some cases the route determination is not working correctly.

Inside the BPM scenario we do a number of action, but we can divide them in 2categories:

1) RFC calls

2) File creation

The RFC calls do always succeed, the file interaction almost never.

Also, when we try to write the result of the xi scenario into a file, this fail 90% of the time. The calling of the RFC always happens correctly.

What we do at the moment is just copy exact the same file again and rerun the scenario, until is works. This is however not the way it should be.

On monday we are having a very important demo. All input is apreciated and will be rewarded.

Kind regards

Joris

[Former Member]

Additional info:

Server version = XI3.0 SP7.

I've just tried initiating the scenario via a webservice call, but this gives the result.

The messages goes 75% of the cases in the "to be delivered state".

[Former Member]

Internal messages:

When verything goes fine the soap header of the first message contains following receiver information:

-

---

<SAP:Main xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" versionMajor="003" versionMinor="000" SOAP:mustUnderstand="1" wsu:Id="wsuid-main-92ABE13F5C59AB7FE10000000A1551F7">

<SAP:MessageClass>ApplicationMessage</SAP:MessageClass>

<SAP:ProcessingMode>asynchronous</SAP:ProcessingMode>

<SAP:MessageId>E4F74F70-B9F5-11DA-C2DE-000D56B9D8A6</SAP:MessageId>

<SAP:TimeSent>2006-03-22T22:47:52Z</SAP:TimeSent>

- <SAP:Sender>

<SAP:Service>ADDRESSCHANGE</SAP:Service>

<SAP:Interface namespace="urn:cernum.com/xi/demo/ADDRESSCHANGE">MI_OUTB_BUPAINPUT</SAP:Interface>

</SAP:Sender>

<b>- <SAP:Receiver>

<SAP:Party agency="" scheme="" />

<SAP:Service>BPM_AddressChange</SAP:Service>

<SAP:Interface namespace="urn:cernum.com/xi/demo/ADDRESSCHANGE">MI_ABS_BPMINPUT</SAP:Interface>

</SAP:Receiver>

<SAP:Interface namespace="urn:cernum.com/xi/demo/ADDRESSCHANGE">MI_ABS_BPMINPUT</SAP:Interface></b> </SAP:Main>

-

---

When it goes wrong, it looks like this:

-

---

<SAP:Main xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" versionMajor="003" versionMinor="000" SOAP:mustUnderstand="1" wsu:Id="wsuid-main-92ABE13F5C59AB7FE10000000A1551F7">

<SAP:MessageClass>ApplicationMessage</SAP:MessageClass>

<SAP:ProcessingMode>asynchronous</SAP:ProcessingMode>

<SAP:MessageId>47D5D3A0-B9F6-11DA-BD78-000D56B9D8A6</SAP:MessageId>

<SAP:TimeSent>2006-03-22T22:50:37Z</SAP:TimeSent>

- <SAP:Sender>

<SAP:Service>ADDRESSCHANGE</SAP:Service>

<SAP:Interface namespace="urn:cernum.com/xi/demo/ADDRESSCHANGE">MI_OUTB_BUPAINPUT</SAP:Interface>

</SAP:Sender>

<SAP:Interface namespace="urn:cernum.com/xi/demo/ADDRESSCHANGE">MI_OUTB_BUPAINPUT</SAP:Interface>

</SAP:Main>

-

---

No receiver tag is added ... .