XI thread count per Receiver Determination rule

Does XI create interface instances/threads per rule found within a Receiver Determination? Such that we should expect one thread per rule? How are threads related to each rule within the receiver determination? What is the ratio, 1 thread per rule, or one thread per receiver determination? What is the impact on system performance in relation to rule count?

See an Adapter works in AE and Receiver Dtermination in IE......for receiver Determination to work the message should be first picked by your sender adapter.....only then it comes to determination (in IE).
But note that messages picked up by one sender channel will be coming to the determination (even if it has n conditions)......we wont have multiple channels picking the message and delivering to same determination...
The number of conditions satisfied by the determination will initiate that many receiver adapter threads.....and it is just because of the conditions being validated (as true) and not because of the number of conditions being maintained.

Similar Messages

"Problem evaluating a condition" at Receiver Determination

Hi,
I've created a complex mail to rfc interface, in which, message is being send as mail attachment and service inbound interface has multiple operations (each for corresponding rfc).
at Receiver Determination, rule was created with multiple conditions, in order to determine correct "Communication Component" (multiple receiver agreement and interface determination were created to supported this "multi interfaces" scenario).
If no receiver was found message is ignored.
once in a while, bad non-xml messages (e.g., "asdfasdfasdfffdfdsasdf") are being send, is this case, while PI is trying to determining the receiver (i.e., evaluate Receiver Determination conditions) exception is being thrown, message is therefor has system error status* (at sxmb_moni) and it can not be ignored (as i wanted it to be).
how can i workaround this problematic scenario?
Regards
Uri
*Error message (sxmb_moni)
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="RCVR_DETERMINATION">CX_RD_PLSRV</SAP:Code>
<SAP:P1>Problem evaluating a condition: An exception has occurred.</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>Error when determining the receiver: Problem evaluating a condition: An exception has occurred. Problem evaluating a condition: An exception has occurred. An exception has occurred. An exception has occurred. An exception has occurred. An exception has occurred. An exception has occurred. Problem extracting values from the Payload: Check line 2 column 1 of the XML document</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>

Abhishek,
10x for your replay, but as far as i understand this is exactly the case here.
conditions are:
cond1: (/rfc: RFC1 ~ *)
cond2: (/rfc: RFC2 ~ *)
this works as expected in cases of xml messages (in case no cond is satisfied) message is ignored. but, in case of non-xml message exception is being thrown while cond is assessed.
Regards
Uri

Receiver determination - Xpath expression problem with count

I am working with a scenario where I pick up records from a JDBC connection and if the number of records I pick up is less than a certain number I want to call a webservice. If it is greater than the number I want to write out a file to be processed by a different process on the receiving end. I have created the receiver determination condition with the following conditions:
(/p1:MT_HOG_Data/row[count(row) > 3] EX)
(/p1:MT_HOG_Data/row[count(row) <= 3] EX)
The integration is always processing the second condition no matter how many records come in. I have tried with and without the multiline option. Can anyone help with this?
I have searched through the forum and checked the following links without any resolution:
http://wiki.sdn.sap.com/wiki/display/XI/XpathConditioninReceiverDetermination
http://help.sap.com/saphelp_nwpi71/helpdata/EN/ab/13bf7191e73a4fb3560e767a2525fd/frameset.htm
/people/shabarish.vijayakumar/blog/2006/06/07/customise-your-xpath-expressions-in-receiver-determination
I can't find any examples where a count of records is checked in the expression editor. Thanks in advance for any help.

You can not use the EX operator in that case, because that is used only for node existence checks, not for value checks.
Do you have a row number in your structure ? Then you could write the xpath expression with that counter tag and value
Example: you want to send to receiver A if count > 3, else to B:
you set /rowNumber EQUAL 4 for sender A
and /rowNumber NOT EQUAL 4 for sender B
The condition is applied to the whole document. If one of the node/values are true for that condition, then the whole condition is set to true.
Problem with that is that the second condition also will be true because nodes for that condition will be found
better would be to have a rowcount tag in the structure. If that is not possible, you can use the "Enhanced Receiver determination" where you can define a mapping which determines the receivers. There you can do anything complicated you want.
CSY

Problem in receiver rule of configured receivers in receiver determination

Hi, Experts!
Can anyone please help me with an issue regarding the receiver determination part of IB? I currently have 2 different receiver rules, each having a different condition but under the same communication component. When I check the message status in the runtime workbench however, both rules are considered and thus 2 messages are sent instead of just 1 from the selection. Please help me send the message according to the selected interface. Thanks!

Hi Brent,
You may write the rule as follows:
if (Receiver='CHDB') OR (Receiver='CIF') then send the incoming message to the relevant Receiver Business Component/System.
You may use the X Path editor for configuring this rule in the Content based Receiver Determination of your scenario.
I hope this will help.
Regards, Gaurav

Alert to Error in Receiver determination mapping

Hi everyboy.
Im using a mapping to decide the receiver determination (ReceiverDetermination - http://sap.com/xi/XI/System).
I can´t configure an alert when the mapping fails.
How could I do that????
Thanks a lot

Hi Christian,
As per my understanding you are using extended receiver determination by creating an interface mapping in between your outbound interface and standard receiver interface of SAP BASIS.Do you mean to say that if source data doesnot fulfill the condition to determine any receiver.If so, then I believe in SXMB_MONI we can find the error as unable to determine receiver.Since it belongs to mapping so it will be executed in Integration engine.
create an alert category in ALRTCATDEF
Define Alert Rule in RWB -> Alert Configuration
Select the our own Alert Category
Click to Add Rule and activate the corresponding rule
Regards,
Nutan

XPath Error in Receiver Determination

Hi All,
I hav an outbound message coming out of ERP (Non IDoc). I have to route the message based on the field DESTINATION in the message. The payload in the SXMB_MONI is as follows.
<?xml version="1.0" encoding="utf-8" ?>
<nr1:OLabelling_OB xmlns:nr1="http://cpe.com/cpe_ftp_wms/Labelling/OL">
<Label>
<DESTINATION>XXXX</DESTINATION>
<PRPRORD>0001005683</PRPRORD>
</Label>
</nr1:OLabelling_OB>
In the receiver determination, I hav chosen the XPath button and given the following value
/nr1:OLabelling_OB/Label/DESTINATION.
This doesn't work. i had also tried giving the namespace and the prefix as
nr1 http://cpe.com/cpe_ftp_wms/Labelling/OL. but that dint help either.
If i remove the condition, then it is working fine.
Any help in this regard?
Thnx in Advance.
Anil

I had activated and checked......it was not getting displayed.......
But i checked the xpath rules and used a work around solution for this. as per the xpath rules if i enter xpath as //DESTINATION, it picks up the DESTINATION field from anywhere in the document. and that worked.
Thnx for ur help so far...
anil

Receiver determination for Split Message - Bulk message handling

All,
I have a scenario where MATMAS message is split to multiple receivers via multi mapping 1:n; the split is based on plant specific data, all works fine the mapping splits the message perfectly.
The problem I have is in configuring the receiver determiniation. I have put conditions based on plant specific data the message should be distributed to the appropriate receiver. At runtime the MATMAS message received is treated as a bulk message and it produces mutiple sub-documents however in my case if the MATMAS has 3 plant specific data the data is send to all the 3 receivers instead of sending just one message per plant to the appropriate receiver.
Its IDOC to File scenario on XI 3.0, SP20.
Receiver Determination:
/MATMAS05/IDOC/E1MARAM/E1MARCM/WERKS = 'xxxx' -> send to XXXX_receiver
/MATMAS05/IDOC/E1MARAM/E1MARCM/WERKS = 'yyyy' -> send to YYYY_receiver
Though the receiver determiniation splits the message by plant it could be that a material is maintained for both xxxx and yyyy plants and in this case both should receive the message but the contents would be different. The problem I have is both messages are delivered to both receivers.
I appreciate those who have taken the time to read the thread and thank you all in advance supporting with advices.
/ Saj

Please find attached the source xml before transormation used for the xpath that I have indicated in my original message. From the below message E1MARCM-BESKZ differs on each plant and also has a corresponding warehouse view E1MLGNM where for example LHMG1 value differs for each warehouse.
<?xml version="1.0" encoding="UTF-8" ?>
- <MATMAS05>
- <IDOC BEGIN="1">
- <E1MARAM SEGMENT="1">
<MSGFN>005</MSGFN>
<MATNR>000000000001002201</MATNR>
<MTART>ZFGS</MTART>
<MATKL>1111003</MATKL>
- <E1MAKTM SEGMENT="1">
<MSGFN>005</MSGFN>
<SPRAS>E</SPRAS>
<MAKTX>AA Ni-MH Rechargeable Batteries</MAKTX>
</E1MAKTM>
- <E1MARCM SEGMENT="1">
<WERKS>4911</WERKS>
<BESKZ>F</BESKZ>
</E1MARCM>
- <E1MARCM SEGMENT="1">
<WERKS>4912</WERKS>
<BESKZ>X</BESKZ>
</E1MARCM>
- <E1MARCM SEGMENT="1">
<WERKS>5020</WERKS>
<BESKZ>E</BESKZ>
</E1MARCM>
- <E1MARMM SEGMENT="1">
<MEINH>CS</MEINH>
</E1MARMM>
- <E1MLGNM SEGMENT="1">
<LGNUM>020</LGNUM>
<LHMG1>2020.000</LHMG1>
<LETY1>E2</LETY1>
</E1MLGNM>
- <E1MLGNM SEGMENT="1">
<LGNUM>023</LGNUM>
<LHMG1>2323.000</LHMG1>
<LETY1>E2</LETY1>
</E1MLGNM>
- <E1MLGNM SEGMENT="1">
<LGNUM>024</LGNUM>
<LHMG1>2424.000</LHMG1>
<LETY1>E2</LETY1>
</E1MLGNM>
- <E1MVKEM SEGMENT="1">
<VKORG>4900</VKORG>
<PRAT1>X</PRAT1>
</E1MVKEM>
- <E1MVKEM SEGMENT="1">
<VKORG>5000</VKORG>
<PRAT1>/</PRAT1>
</E1MVKEM>
</E1MARAM>
</IDOC>
</MATMAS05>
so in this example above:
Receiver 4911 (WERKS) should receive:
F + 2020 (BESKZ + LHMG1)
Receiver 4912 (WERKS) should receive:
F + 2323 (BESKZ + LHMG1)
Receiver 5020 (WERKS) should receive:
F + 2424 (BESKZ + LHMG1)
The problem is all these 3 messages are delivered to all the 3 plants thus making it 9 messages delivered in total as against 3.
/ Saj

Redarding receiver determination

hi all
iam ajay,
here i faced a problem at xi server. even i created the receiver determination it alerts an error in receiver determination.i furnished my error below.
let me know the solution
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="RCVR_DETERMINATION">CX_RD_PLSRV</SAP:Code>
<SAP:P1>Problem extracting values from the message: The exception occurred (program: CL_SAI_SWF_RULE_ENGINE========CP, include CL_SAI_SWF_RULE_ENGINE========CM006, line: 93)</SAP:P1>
<SAP:P2 />

Hi Ajay,
Have you defined a rule for the receiver determination.
Please can you check on this thread. Same issue
Error evaluation condition in receiver determination
Regards
Vijaya

High thread count on store.exe

I understand that the mdb store process utilizes as much memory as is available. My question is regarding the thread count on the process. One of the three mailbox servers tends to have a higher thread count than the other two. It
usually ranges from 150 to 200 (while the other two are usually 130 to 150) but today it is a little over 300. The rpc thread count on all the mailbox servers stays pretty low (60 or under) and the rpc thread count on the CAS servers usually
hang out around 55-65, so that's all good. All three mailbox servers also use VERY close to the same amount of memory all the time, so that doesn't seem to be making a difference. I am just trying to determine why the thread count is noticably
higher. This server and one of other mailbox servers replicate the public folder database, and I can understand why that would account for some additional activity, but you would think the thread count would be higher on the other server with the public
folder database as well, but it stays pretty low. Hardware-wise these servers are all identical. So is there something I can monitor in perf mon for instance? I don't want to use experfwiz because that monitors everything under the sun and
I need it a bit more centralized. I have googled all over the place and the only thing I can find is that with newer versions of exchange this thread count ranges from 200-300 on heavy usage, and exch07 can handle up to 500 threads, so I can't even find
which specific things to monitor that directly correlate with this issue. So while I understand that it's not really too high, I would like to find out why it deviates from the norm if the other two servers are equal for all intents and purposes (same
hardware, balanced DAG. etc). I would like to mitigate any potential issues. Thank you.

Hi pchw,
Thank you for your question.
I am sorry that we could not find the specific things to monitor this issuer directly, because there are many reason which caused it. For example: virus, big size attachment in queue, hardware performance and so on. We could refer to the following steps
to troubleshoot:
Restart the service of “Microsoft Exchange transport”;
Create a new database and move mailbox to new mailbox;
We could do some disk health check if the load test is normal;
Collect related application log and system log to
[email protected] for our troubleshooting.
We could run SDP on Exchange server and send it to
[email protected] for our troubleshooting.
http://blogs.msdn.com/b/askie/archive/2012/05/22/introduction-to-support-diagnostics-platform-sdp.aspx
We could use tools and logs to analysis if there are anything wrong or abnormal on Exchange server 2013. our bottle neck is disk IO latency, store.exe do require some CPU usage, but if our disk IO speed can keep in a normal range, the
CPU usage will be smaller. Exchange is highly rely on disk IO performance because it need lots of IO operation regarding to transaction log and database file. If Disk IO has a high latency, I will definitely impact store.exe, if it`s getting seriously sometimes
it may cause store.exe no response.
We could refer to the following link:
https://technet.microsoft.com/en-us/library/ee832791(v=exchg.141).aspx
If there are any questions regarding this issue, please be free to let me know.
Best Regard,
Jim

Receiver determination step - Send context

Hi Experts,
I have understood from SAP library and others threads that send context in the receiver determination step is used to send value for the conditions we have added in ther receiver determination and fetch only receivers those satisfy the cretiria.
Please validate whether my understand is right or not?
If its correct, then my question is can we populate this value dyanmically, say field value from another message.
Please clarify.
Thanks,
Kar

Check if the below link is of any interest to you:
http://help.sap.com/saphelp_nwpi71/helpdata/en/46/8015de950e6be3e10000000a155369/frameset.htm
From the link:
Condition: when the AirlineID field in the message payload has the value LH, then the message is
forwarded to the receiver business system BUS_100. A context object of the same name from the ES
Repository is used to access the AirlineID field in the message.
It talks about normal receiver determination as against the receiver determination step (of BPM) which you want....

BPM : Receiver Determination Step

Hi,
I was wondering why we need a Reciever determination step since on send step xi automatically find that there are multiple receiver and sends them accordingly to the different system as per reciever agreement.
Is it that the receiver determination is only useful for multicast which is for send and waiting for the message response from those receiver.
Kindly let me know your comments.
THnks

Hello chinna,
You need receiver determination step becoz even though in BPM u define what are ur receivers but not what service its handling. Lets say this is the scenario :
File>RFC>FILE
ex: /people/arpit.seth/blog/2005/06/27/rfc-scenario-using-bpm--starter-kit
You dont specify in the receivers of BPM where to write the file and how to write the file?
Please elaborate ur scenario i coudlnt get the second part?
Vara
[PLEASE REWARD FOR POSTING]

Error in receiver determination - Client proxy to IDOC using PI-IS

Hi,
I am using client proxy to send the order acknowledgement from SCM to R/3 , I am getting below error
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="RCVR_DETERMINATION">NO_RECEIVER_CASE_ASYNC</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>No receiver could be determined</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
I am using the standard SAP message interface in the sproxy.
Also I am getting error in Proxy generation "Logical port template not determined" "LPT could not be created without DT".
Thanks,
Menaga

<SAP:Code area="RCVR_DETERMINATION">NO_RECEIVER_CASE_ASYNC</SAP:Code>
The above error occurs due to:
1) You have configured a wrong receiver service in the Receiver Determination
2) You have configured the correct receiver but the cache is not updated
So check if the receiver service exists and the cache is updated.
Also I am getting error in Proxy generation "Logical port template not determined" "LPT could not
be created without DT".
Check if you get any lead from this thread:
Failed to time to generate proxy - TRX SPROXY
Does it mean that you have no proxy generated and you are testing??....if yes then you will get the above error (NO_RECEIVER_CASE_ASYNC).
Regards,
Abhishek.

Interface Determination causing issue in Receiver Determination

Hi
I am having an issue with interface and receiver determination as follows:
- Inbound message may be sent to two receivers.
- Message gets sent to first receiver, fails during interface determination. There are multiple inbound interfaces found based on a set of XPATH conditions. This creates an error 'Inbound interface found more than once for outbound interface '. That is itself is not the issue.
- Issue is that the message is stopped from going to the other receiver even if there are no issues in the interface determination for that receiver.
Is there a way to resolve this? Appreciate any help. Thx, Duncan

Again, thanks for the replies.
MONI for RD
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
- <Trace level="1" type="B" name="CL_RD_PLSRV-ENTER_PLSRV">
<Trace level="1" type="T">R E C E I V E R - D E T E R M I N A T I O N</Trace>
<Trace level="1" type="T">Cache Content is up to date</Trace>
<Trace level="2" type="T">Start without given receiver</Trace>
<Trace level="2" type="T">Classic Receiver Determination via Rules.</Trace>
<Trace level="2" type="T">Check conditions for rule line no. 1</Trace>
<Trace level="3" type="T">...create rule engine</Trace>
<Trace level="3" type="T">...call rule engine for Condition %CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:despatchAdvice")% EX and %CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:despatchAdvice/deliveryNote/referenceIdentification")% CE COSTCENTRE or %CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:despatchAdvice")% EX and %CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:despatchAdvice/deliveryNote/referenceIdentification")% CE INTERPLANT or %CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:despatchAdvice")% EX and %CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:despatchAdvice/deliveryNote/referenceIdentification")% CE INTERPLANT_ONESTEP or %CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:despatchAdvice")% EX and %CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:despatchAdvice/deliveryNote/referenceIdentification")% CE INTRAPLANT or %CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:despatchAdvice")% EX and %CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:despatchAdvice/deliveryNote/referenceIdentification")% CE INTRAPLANT_ONESTEP or %CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:receivingAdvice")% EX or %CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:inventoryActivityOrInventoryStatus")% EX</Trace>
<Trace level="2" type="T">......extracting (new) for Extractor: XP /p2:despatchAdvice</Trace>
<Trace level="2" type="T">......extracting values found: 0</Trace>
<Trace level="2" type="T">......extracting (new) for Extractor: XP /p2:receivingAdvice</Trace>
<Trace level="2" type="T">......extracting values found: 1</Trace>
<Trace level="2" type="T">...valid Receiver with Condition: - GLR430</Trace>
<Trace level="2" type="T">Check conditions for rule line no. 2</Trace>
<Trace level="3" type="T">...call rule engine for Condition %CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:despatchAdvice")% EX and %CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:despatchAdvice/deliveryNote/referenceIdentification")% NE COSTCENTRE and %CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:despatchAdvice/deliveryNote/referenceIdentification")% NE INTERPLANT and %CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:despatchAdvice/deliveryNote/referenceIdentification")% NE INTERPLANT_ONESTEP and %CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:despatchAdvice/deliveryNote/referenceIdentification")% NE INTRAPLANT and %CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:despatchAdvice/deliveryNote/referenceIdentification")% NE INTRAPLANT_ONESTEP</Trace>
<Trace level="2" type="T">...invalid Receiver: P_3PL_XML_ME_ODTH - despatchAdviceToE1EDT20</Trace>
<Trace level="2" type="T">Check conditions for rule line no. 3</Trace>
<Trace level="2" type="T">...valid Receiver w/o Condition: P_3PL_XML_ME_ODTH - S_HTTP</Trace>
<Trace level="2" type="T">No Receiver found behaviour: 0</Trace>
<Trace level="2" type="T">Number of Receivers:2</Trace>
</Trace>
</Trace>
</Trace>
Here, you see that both receivers are found.
MONI for ID
<Trace level="1" type="B" name="PLSRV_INTERFACE_DETERMINATION" />
- 
<Trace level="1" type="Timestamp">2007-02-26T20:06:49Z CET Start of pipeline service processing PLSRVID= PLSRV_INTERFACE_DETERMINATION</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="3" type="T">Calling pipeline service: PLSRV_INTERFACE_DETERMINATION</Trace>
<Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
<Trace level="3" type="T">PLSRVID = PLSRV_INTERFACE_DETERMINATION</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
<Trace level="3" type="T">P_CLASS = CL_ID_PLSRV</Trace>
<Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
<Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
<Trace level="3" type="T">FL_LOG =</Trace>
<Trace level="3" type="T">FL_DUMMY = 0</Trace>
<Trace level="3" type="T" />
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
- 
- <Trace level="1" type="B" name="CL_ID_PLSRV-ENTER_PLSRV">
<Trace level="1" type="T">I N T E R F A C E - D E T E R M I N A T I O N</Trace>
<Trace level="1" type="T">Cache Content is up to date</Trace>
<Trace level="2" type="T">Check conditions for (Inb: Party Srvc If) GLR430 WMMBXY.WMMBID01</Trace>
<Trace level="3" type="T">...create rule engine</Trace>
<Trace level="3" type="T">...call rule engine for Condition%CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p1:inventoryActivityOrInventoryStatus/inventoryDocumentType")% CE INVENTORY_STATUS</Trace>
<Trace level="2" type="T">......extracting (new) for Extractor: XP /p1:inventoryActivityOrInventoryStatus/inventoryDocumentType</Trace>
<Trace level="2" type="T">......extracting values found: 0</Trace>
<Trace level="2" type="T">...invalid InbIf: WMMBXY.WMMBID01</Trace>
<Trace level="2" type="T">Check conditions for (Inb: Party Srvc If) GLR430 WMMBXY.WMMBID01</Trace>
<Trace level="3" type="T">...call rule engine for Condition%CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p1:inventoryActivityOrInventoryStatus/inventoryDocumentType")% CE INVENTORY_ACTIVITY</Trace>
<Trace level="2" type="T">......extracting (new) for Extractor: XP /p1:inventoryActivityOrInventoryStatus/inventoryDocumentType</Trace>
<Trace level="2" type="T">......extracting values found: 0</Trace>
<Trace level="2" type="T">...invalid InbIf: WMMBXY.WMMBID01</Trace>
<Trace level="2" type="T">Check conditions for (Inb: Party Srvc If) GLR430 WMMBXY.WMMBID01</Trace>
<Trace level="3" type="T">...call rule engine for Condition%CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:receivingAdvice/receivingAdviceItemContainmentLineItem/purchaseOrder/documentReference/uniqueCreatorIdentification")% EX</Trace>
<Trace level="2" type="T">......extracting (new) for Extractor: XP /p2:receivingAdvice/receivingAdviceItemContainmentLineItem/purchaseOrder/documentReference/uniqueCreatorIdentification</Trace>
<Trace level="2" type="T">......extracting values found: 2</Trace>
<Trace level="2" type="T">...valid InbIf with Condition: WMMBXY.WMMBID01</Trace>
<Trace level="2" type="T">Check conditions for (Inb: Party Srvc If) GLR430 WMMBXY.WMMBID01</Trace>
<Trace level="3" type="T">...call rule engine for Condition%CL_SAI_SWF_RULE_ENGINE.MSG_GET(MSG=&_MSG&;NSP=&_NSM&;XPATH="/p2:receivingAdvice/carrier/additionalPartyIdentification/additionalPartyIdentificationValue")% CE SHUTTLE</Trace>
<Trace level="2" type="T">......extracting (new) for Extractor: XP /p2:receivingAdvice/carrier/additionalPartyIdentification/additionalPartyIdentificationValue</Trace>
<Trace level="2" type="T">......extracting values found: 1</Trace>
<Trace level="2" type="T">...valid InbIf with Condition: WMMBXY.WMMBID01</Trace>
</Trace>
</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
<Trace level="3" type="T">Persisting message after plsrv call</Trace>
<Trace level="3" type="T">Message-Version = 002</Trace>
<Trace level="3" type="T">Message version 002</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</Trace>
<Trace level="3" type="System_Error">Error exception return from pipeline processing!</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="3" type="T">Persisting message Status = 014</Trace>
<Trace level="3" type="T">Message version 003</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</SAP:Trace>
Here, you see that the ID runs for the first receiver. It hits an error because two conditions on the ID for the first receiver are satisfied. However, it then stops rather than allow the processing for the other receiver to continue.
Any ideas? Thx, Duncan

Dynamic receiver Determination for Sync Scenario??

Hello Experts,
I have a SOAP -> Xi -> R3 sync scenario i,e, R3 to send back response to SOAP client.
Also I need the Dynamic receiver determination.
When I try to create the Interface Mapping, I get the error:
"Interface modi are different. "
Source interface MI_My_sync_iface is synchronous.
Target interface ReceiverDetermination | http://sap.com/xi/XI/System is asynchronous
I coud find few threads on forum related to this but i think there is no clear solution provided.
I do not wanna use BPM.
Please suggest.
Thanks in Advance!
Appropriate point will be awarded.

> So when I try to define a interface Mapping using a Sync interface as Source and Async interface as target, XI does not allow me to do so.
You are getting this error because in Interface mapping when you use sync source then it generates request and response tab so if at target side if you put anync interface then definetly it will go into error. You have to make both the interfaces as sync.
BTW, after getting the message in R3, how are processing the message? Are you using sync proxy??
You can solve the problem by creating one additional message interface of type inbound-asyn. Use this additional Message interfce in your Interface Determination. And create additional Receiver Agreement to deliver the message to it's destination.
Note: When you careate additional Interface Determination then you have to chose the response message interface (Sync message interface which returns the response from R3) as a source.
Regards,
Sarvesh

Thread count tuning

Hi!
We are running a weblogic 5.1 server for jsp/servlet/ejb behind an apache web
server, via the wls/apache bridge. As the number of users increased we expereienced
slow response times. We checked thread dumps from peak hours and saw that all
servlet threads were busy writing to network sockets. Still, if we check the internet
line usage, we are not using up all our bandwith.
We've managed to solve this by adding more threads to our wls server (36 servlet
threads, 46 totally). This has however slowed down our database somewhat since
we have to increase the connection pool size with the number of server threads.
So my question would be: is there some other, more elegant, way to solve this?
Having 46 execute threads seems pretty much (15 is recommended from BEA). Ideally
I would like the wls threads to write their results as quickly as they can to
the apache server, disconnect from the socket and leave actual work of writing
all the data back to the end user's browser to apache. My network knowledge is
pretty limited so I'm not sure if this is possible.
/Mattias

Why do you need to have the maximum thread count equal to the maximum number of simulatneous users? You'll never end up with a system that has 60,000 threads.
If you are doing traditional-style HTTP, then typically you can support many thousands of users with just a few threads. For example, our SPECjAppServ er submissions use about 40 threads to handle 4000 clients. It all depends on how many requests each client actually makes per second, and how long each request takes. If the clients are idle for long periods of time, you could handle 10s of thousands with just a few threads.
The keep-alive tuning is also critical in that scenario, as the server will eventually start disconnecting clients, who will re-create the TCP connections. That works seemlessly from a functional point of view, but isn't necessarily the optimal thing for performance.
On the other hand, if you're trying to use a Web 2.0-style HTTP request where you simulate server pushes by having the servlet request block, then yes, in 8.1 you will need one thread per client, but you'll be bound by OS and other system constraints on the number of threads the process can have. You'd be much better off in that case using the Asynchronous Request processing features being added to AS 9.1 (see Sun's project glassfish for details).
For information on configuring the thread count for 8.1, see:
http://docs.sun.com/source/819-0215/httpservice.html
In particular -- the section on Configuring HTTP Service Request Processing Threads.

XI thread count per Receiver Determination rule

Similar Messages

Maybe you are looking for