on 08-06-2006 11:49 AM
Hi,
we upgraded XI from SP9 to SP16. After upgrade to SP16 the scenario does not work properly anymore because the receiver party information is lost.
In the receiver determination I've set 2 receivers 1) party 'test' and service 'testservice1' and 2) party 'test and service 'testservice2' as configured receivers. I also set up conditions for both receivers.
Before the upgrade everything worked fine the way it should work. Check the section <SAP:Party agency="http://sap.com/xi/XI" scheme="XIParty">test</SAP:Party> in the trace. Agency and scheme is filled !
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!-- Receiver Grouping
-->
- <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>A05BD560-2143-11DB-A641-001125BF4287</SAP:MessageId>
<SAP:TimeSent>2006-08-01T09:56:14Z</SAP:TimeSent>
- <SAP:Sender>
<SAP:Service>QS6</SAP:Service>
<SAP:Interface namespace="http://company.com/NS">ORDER</SAP:Interface>
</SAP:Sender>
- <SAP:Receiver>
<SAP:Party agency="http://sap.com/xi/XI" scheme="XIParty">test</SAP:Party>
<SAP:Service>testservice1</SAP:Service>
<SAP:Interface namespace="http://company.com/NS">ORDER_Abstract</SAP:Interface>
<SAP:Mapping />
</SAP:Receiver>
<SAP:Interface namespace="http://company.com/NS">ORDER</SAP:Interface>
</SAP:Main>
After upgrade to SP16 there is an 'error' i.e. the configured receiver is not a party anymore:
1. In the header of the message part of the receiver info is lost. The agency and scheme fields of the receiver are empty ! See section <SAP:Party agency="" scheme="">test</SAP:Party> in the trace.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!-- Receiver Grouping
-->
- <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>195F4610-22B9-11DB-806C-001125BF4287</SAP:MessageId>
<SAP:TimeSent>2006-08-03T07:10:51Z</SAP:TimeSent>
- <SAP:Sender>
<SAP:Service>QS6</SAP:Service>
<SAP:Interface namespace="http://company.com/NS">ORDER</SAP:Interface>
</SAP:Sender>
- <SAP:Receiver>
<SAP:Party agency="" scheme="">test</SAP:Party>
<SAP:Service>testservice1</SAP:Service>
<SAP:Interface namespace="http://company.com/NS">ORDER_Abstract</SAP:Interface>
- <SAP:Mapping notRequired="M">
<SAP:ObjectId>hKAeuEOzNreit0V6EJweUA==</SAP:ObjectId>
<SAP:SWCV>aGWZ0Dv7EdrMCON1CpZ4Bg==</SAP:SWCV>
<SAP:SP>-1</SAP:SP>
</SAP:Mapping>
</SAP:Receiver>
<SAP:Interface namespace="http://company.com/NS">ORDER</SAP:Interface>
</SAP:Main>
2. There is a new section in the message which looks like bad/corrupt data
- <SAP:Mapping notRequired="M">
<SAP:ObjectId>hKAeuEOzNreit0V6EJweUA==</SAP:ObjectId>
<SAP:SWCV>aGWZ0Dv7EdrMCON1CpZ4Bg==</SAP:SWCV>
<SAP:SP>-1</SAP:SP>
</SAP:Mapping>
Could the new feature 'extended Receiver Determination' be involved in this problem though I do not use it ? In SP9 the feature was not available.
Could somebody post a Receiver Determination trace with party from section Receiver Grouping with at least SP16 in order to compare ?
Hi,
this issue was fixed by an oss
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
88 | |
23 | |
11 | |
9 | |
8 | |
5 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.