QoS issue: Specify Best Effort, but message header contains Exactly Once

I'm using a SOAP sender Adapter to process messages. I specify Quality of Service as "Best Effort" in the adapter, but whenever a message comes in, it has this in the header:
<SAP:QualityOfService>ExactlyOnce</SAP:QualityOfService>
I cannot change this and it is stopping the process working (it works in test but behaves like this in production).
If I send in a test message the from the Configuration and Monitoring home page, I can set "Best Effort" there and it appears correctly in the header. The process works then.
How can it be that even though the adapter is specified as "Best Effort", the message has "ExactlyOnce" in the header?

Hi,
I did both of those; it is coming through the correct channel, and the flush of the cache didn't help.
Anyway, thanks for proposing.
BR,
Tony.

Similar Messages

Issue with "Best Effort" QoS

Hi All,
I have an issue with the Quality of Service "Best Effort" for a Sender SOAP Adapter. The interface is a synchronous SOAP - to - Proxy scenario.
Q1 - How does Best Effort Work? If 10 users are sending the synchronous SOAP request, say to a BAPI to display orders, Will all the users get the response, ofcourse for different input Parameters? or the requests will be served first come first serve basis. For eg: user1 will get the response first and then user 2s request is processed?
Q2 - I am having issues with this scenario like sometimes the end users are getting a blank response message. The message in PI has no errors and the sync SOAP call is successfully completed. So What could possibly be the reasons for the blank responses when the BAPI's, Webservices, PI system and SOAP call everything is successful?
Request urgent assistance. Thanks a lot.
Rashmi.

Q1 - How does Best Effort Work? If 10 users are sending the synchronous SOAP request, say to a BAPI to display orders, Will all the users get the response, ofcourse for different input Parameters? or the requests will be served first come first serve basis. For eg: user1 will get the response first and then user 2s request is processed?
Best Effort is meant for synchronous communication. Unlike EOIO, Best effort will not guarantee that mesg will be processed in sequential order(one after another) the way it received. First of all, users can input concurrently (all at the same time) or one after another in very short span time difference. SAP services those users request based on the availability of work process during that runtime. BE only gurantees your message delivery and again based on the nature of the data and processing time and synchronous mode, messages will get processed based on the availability of work process during that time.
Q2 - I am having issues with this scenario like sometimes the end users are getting a blank response message. The message in PI has no errors and the sync SOAP call is successfully completed. So What could possibly be the reasons for the blank responses when the BAPI's, Webservices, PI system and SOAP call everything is successful
Due to many reasons. Are you expecting blank response instead of valid response? or you are getting blank response based on the user's request message. Since you see success mesg log everywhere, the blank response might be based on the request message. Check your mapping and see any logic that cause blank response for some messages?

Exchange 2007 - content-language in message header

Exchange 2007
The Regional Settings on client computer is set to Bulgarian (Formats/Location/non Unicode/System Account)
The Regional Settings in Outlook Web Access for user1 is set to Bulgarian.
On the exchange server, the language of mailbox of user1 is set to Bulgarian with powershell command
Set-Mailbox -Identity "user1" -Languages "bg-BG"
And the check shows
[PS] C:\Windows\system32>$Mailbox = Get-Mailbox -Identity "user1"
[PS] C:\Windows\system32>$mailbox.languages
LCID Name DisplayName
1026 bg-BG Bulgarian (Bulgaria)
If user1 sends a new message using Outlook, the message header contains:
Accept-Language: bg-BG, en-US
Content-Language: en-US
But if user1 sends a new message to same recepient using Outlook Web Access, the message header contains:
Accept-Language: bg-BG, en-US
Content-Language: bg-BG
The recepient uses some Blackberry smartphone.
The problem comes with cyrrilic text in the message:
If the messaqge is sent using OWA, the recepient can visualize and read cyrillic text.
But if the message is sent from Outlook, the recepient see symbols "????...?" instead cyrillic text
Is there a way when use Outlook the message header to be
Content-Language: bg-BG
This problem with incorrect cyrrilic text can be observed only on this Blackberry smartphone. There are not any problems if recepient uses computer with correct regional settings and various mail clients

Hi,
Have you resolved this issue?
If there is any update, please feel free to post here for further research.
Best regards,
Belinda
Belinda Ma
TechNet Community Support

Proxy generation terminated: Message must have exactly one part

hi experts,
i have tryed to create a proxy in abap but it gives an error message
Proxy generation terminated: Message must have exactly one part
Message no. SPRX046
can any one help me
the wsdl document is
- <wsdl:definitions targetNamespace="urn:sap-com:document:sap:rfc:functions">
−
     <wsdl:types>
−
     <xsd:schema targetNamespace="urn:sap-com:document:sap:rfc:functions" elementFormDefault="unqualified" attributeFormDefault="qualified">
−
     <xsd:simpleType name="char1">
−
     <xsd:restriction base="xsd:string">
<xsd:maxLength value="1"/>
</xsd:restriction>
</xsd:simpleType>
−
     <xsd:simpleType name="char10">
−
     <xsd:restriction base="xsd:string">
<xsd:maxLength value="10"/>
</xsd:restriction>
</xsd:simpleType>
−
     <xsd:simpleType name="char100">
−
     <xsd:restriction base="xsd:string">
<xsd:maxLength value="100"/>
</xsd:restriction>
</xsd:simpleType>
−
     <xsd:simpleType name="char20">
−
     <xsd:restriction base="xsd:string">
<xsd:maxLength value="20"/>
</xsd:restriction>
</xsd:simpleType>
−
     <xsd:simpleType name="char220">
−
     <xsd:restriction base="xsd:string">
<xsd:maxLength value="220"/>
</xsd:restriction>
</xsd:simpleType>
−
     <xsd:simpleType name="char30">
−
     <xsd:restriction base="xsd:string">
<xsd:maxLength value="30"/>
</xsd:restriction>
</xsd:simpleType>
−
     <xsd:simpleType name="char32">
−
     <xsd:restriction base="xsd:string">
<xsd:maxLength value="32"/>
</xsd:restriction>
</xsd:simpleType>
−
     <xsd:simpleType name="char50">
−
     <xsd:restriction base="xsd:string">
<xsd:maxLength value="50"/>
</xsd:restriction>
</xsd:simpleType>
−
     <xsd:simpleType name="clnt3">
−
     <xsd:restriction base="xsd:string">
<xsd:maxLength value="3"/>
</xsd:restriction>
</xsd:simpleType>
−
     <xsd:simpleType name="numeric15">
−
     <xsd:restriction base="xsd:string">
<xsd:maxLength value="15"/>
<xsd:pattern value="\d*"/>
</xsd:restriction>
</xsd:simpleType>
−
     <xsd:simpleType name="numeric3">
−
     <xsd:restriction base="xsd:string">
<xsd:maxLength value="3"/>
<xsd:pattern value="\d*"/>
</xsd:restriction>
</xsd:simpleType>
−
     <xsd:simpleType name="numeric6">
−
     <xsd:restriction base="xsd:string">
<xsd:maxLength value="6"/>
<xsd:pattern value="\d*"/>
</xsd:restriction>
</xsd:simpleType>
−
     <xsd:complexType name="ZCAF_DEP_QUEST">
−
     <xsd:sequence>
<xsd:element name="MANDT" type="tns:clnt3"/>
<xsd:element name="DEPQTN_ID" type="tns:numeric15"/>
<xsd:element name="QTNID" type="tns:numeric15"/>
<xsd:element name="ANS_CHOICE_ID" type="tns:numeric15"/>
</xsd:sequence>
</xsd:complexType>
−
     <xsd:complexType name="ZCAF_ANSWER_META">
−
     <xsd:sequence>
<xsd:element name="MANDT" type="tns:clnt3"/>
<xsd:element name="ANS_META_ID" type="tns:numeric15"/>
<xsd:element name="HAS_COMMENT" type="tns:char1"/>
<xsd:element name="HAS_MULTI_CHOICE" type="tns:char1"/>
<xsd:element name="MULTISELECT_ALLO" type="tns:char1"/>
<xsd:element name="NA_POSSIBLE" type="tns:char1"/>
<xsd:element name="DATA_TYPE" type="tns:char1"/>
<xsd:element name="VALUE_TYPE" type="tns:char1"/>
<xsd:element name="DISPLAY_TYPE" type="tns:char1"/>
</xsd:sequence>
</xsd:complexType>
−
     <xsd:complexType name="ZCAF_QUEST_GROUP">
−
     <xsd:sequence>
<xsd:element name="MANDT" type="tns:clnt3"/>
<xsd:element name="QTNGRPID" type="tns:numeric15"/>
<xsd:element name="TITLE" type="tns:char30"/>
<xsd:element name="REPLACE_TEXT" type="tns:char30"/>
<xsd:element name="LANGUAGE" type="tns:char10"/>
<xsd:element name="DESCRIPTION" type="tns:char30"/>
<xsd:element name="HEADER_TEXT" type="tns:char20"/>
<xsd:element name="CREATED_BY" type="tns:char20"/>
<xsd:element name="ANS_META_ID" type="tns:numeric15"/>
<xsd:element name="RELEASE_STATUS" type="tns:char10"/>
<xsd:element name="VERSION" type="tns:char10"/>
</xsd:sequence>
</xsd:complexType>
−
     <xsd:complexType name="ZCAF_COMMENT_ANS">
−
     <xsd:sequence>
<xsd:element name="MANDT" type="tns:clnt3"/>
<xsd:element name="COMMENT_ANS_ID" type="tns:numeric15"/>
<xsd:element name="ANSSHEET_ID" type="tns:numeric15"/>
<xsd:element name="ANS_META_ID" type="tns:numeric15"/>
<xsd:element name="ANS_CHOICE_ID" type="tns:numeric15"/>
<xsd:element name="TEXT_COMMT_ID" type="tns:numeric15"/>
</xsd:sequence>
</xsd:complexType>
−
     <xsd:complexType name="ZCAF_ANS_CHOICE">
−
     <xsd:sequence>
<xsd:element name="MANDT" type="tns:clnt3"/>
<xsd:element name="ANS_CHOICE_ID" type="tns:numeric15"/>
<xsd:element name="ANS_META_ID" type="tns:numeric15"/>
<xsd:element name="HAS_COMMENT" type="tns:char1"/>
<xsd:element name="SEQ_NUM" type="xsd:int"/>
<xsd:element name="ANSWER_TEXT" type="tns:char50"/>
<xsd:element name="LANGUAGE" type="tns:char10"/>
<xsd:element name="WEIGHT" type="xsd:int"/>
<xsd:element name="HAS_DEP_QTN" type="tns:char1"/>
<xsd:element name="HAS_DEP_QTNGRP" type="tns:char1"/>
</xsd:sequence>
</xsd:complexType>
−
     <xsd:complexType name="ZCAF_QUESTION">
−
     <xsd:sequence>
<xsd:element name="MANDT" type="tns:clnt3"/>
<xsd:element name="QTNID" type="tns:numeric15"/>
<xsd:element name="QTNGRPID" type="tns:numeric15"/>
<xsd:element name="ANS_META_ID" type="tns:numeric15"/>
<xsd:element name="QTN_TEXT" type="tns:char100"/>
<xsd:element name="LANGUAGE" type="tns:char10"/>
<xsd:element name="CREATED_BY" type="tns:char20"/>
<xsd:element name="QTNWEIGHTAGE" type="xsd:int"/>
<xsd:element name="VERSION" type="tns:char10"/>
<xsd:element name="RELEASE_STATUS" type="tns:char10"/>
</xsd:sequence>
</xsd:complexType>
−
     <xsd:complexType name="ZCAF_MULTI_ANS">
−
     <xsd:sequence>
<xsd:element name="MANDT" type="tns:clnt3"/>
<xsd:element name="MULTIPLE_ANS_ID" type="tns:numeric15"/>
<xsd:element name="ANSSHEET_ID" type="tns:numeric15"/>
<xsd:element name="ANS_META_ID" type="tns:numeric15"/>
<xsd:element name="ANS_CHOICE_ID" type="tns:numeric15"/>
<xsd:element name="ANSWER_TEXT" type="tns:char50"/>
<xsd:element name="ANS_VALUE" type="xsd:int"/>
</xsd:sequence>
</xsd:complexType>
−
     <xsd:complexType name="ZCAF_COMENT_TEXT">
−
     <xsd:sequence>
<xsd:element name="MANDT" type="tns:clnt3"/>
<xsd:element name="TEXT_COMMT_ID" type="tns:numeric15"/>
<xsd:element name="TEXT_COMMENT" type="tns:char50"/>
</xsd:sequence>
</xsd:complexType>
−
     <xsd:complexType name="ZCAF_DEP_QTNGRP">
−
     <xsd:sequence>
<xsd:element name="MANDT" type="tns:clnt3"/>
<xsd:element name="DEP_QTNGRP_ID" type="tns:numeric15"/>
<xsd:element name="QTNGRPID" type="tns:numeric15"/>
<xsd:element name="ANS_CHOICE_ID" type="tns:numeric15"/>
</xsd:sequence>
</xsd:complexType>
−
     <xsd:complexType name="ZCAF_ANS_SHEET">
−
     <xsd:sequence>
<xsd:element name="MANDT" type="tns:clnt3"/>
<xsd:element name="ANSSHEET_ID" type="tns:numeric15"/>
<xsd:element name="QTNRID" type="tns:numeric15"/>
<xsd:element name="STATUS" type="tns:char1"/>
</xsd:sequence>
</xsd:complexType>
−
     <xsd:complexType name="ZCAF_QTNR_QTNGRP">
−
     <xsd:sequence>
<xsd:element name="MANDT" type="tns:clnt3"/>
<xsd:element name="QTNRID" type="tns:numeric15"/>
<xsd:element name="QTNGRPID" type="tns:numeric15"/>
</xsd:sequence>
</xsd:complexType>
−
     <xsd:complexType name="ZCAF_QUESTIONIRE">
−
     <xsd:sequence>
<xsd:element name="MANDT" type="tns:clnt3"/>
<xsd:element name="QTNRID" type="tns:numeric15"/>
<xsd:element name="TITLE" type="tns:char30"/>
<xsd:element name="REPLACE_TEXT" type="tns:char30"/>
<xsd:element name="LANGUAGE" type="tns:char10"/>
<xsd:element name="DESCRIPTION" type="tns:char30"/>
<xsd:element name="HEADER_TEXT" type="tns:char20"/>
<xsd:element name="CREATED_BY" type="tns:char20"/>
<xsd:element name="RELEASE_STATUS" type="tns:char10"/>
<xsd:element name="VERSION" type="tns:char10"/>
</xsd:sequence>
</xsd:complexType>
−
     <xsd:complexType name="BAPIRET2">
−
     <xsd:sequence>
<xsd:element name="TYPE" type="tns:char1"/>
<xsd:element name="ID" type="tns:char20"/>
<xsd:element name="NUMBER" type="tns:numeric3"/>
<xsd:element name="MESSAGE" type="tns:char220"/>
<xsd:element name="LOG_NO" type="tns:char20"/>
<xsd:element name="LOG_MSG_NO" type="tns:numeric6"/>
<xsd:element name="MESSAGE_V1" type="tns:char50"/>
<xsd:element name="MESSAGE_V2" type="tns:char50"/>
<xsd:element name="MESSAGE_V3" type="tns:char50"/>
<xsd:element name="MESSAGE_V4" type="tns:char50"/>
<xsd:element name="PARAMETER" type="tns:char32"/>
<xsd:element name="ROW" type="xsd:int"/>
<xsd:element name="FIELD" type="tns:char30"/>
<xsd:element name="SYSTEM" type="tns:char10"/>
</xsd:sequence>
</xsd:complexType>
−
     <xsd:complexType name="ZCAF_ST_GET_QUESTIONNAIRE">
−
     <xsd:sequence>
<xsd:element name="QTNID" type="tns:numeric15"/>
<xsd:element name="QTN_TEXT" type="tns:char100"/>
<xsd:element name="ANS_META_ID" type="tns:numeric15"/>
<xsd:element name="HAS_COMMENT" type="tns:char1"/>
<xsd:element name="HAS_MULTI_CHOICE" type="tns:char1"/>
<xsd:element name="MULTISELECT_ALLO" type="tns:char1"/>
<xsd:element name="NA_POSSIBLE" type="tns:char1"/>
<xsd:element name="DATA_TYPE" type="tns:char1"/>
<xsd:element name="VALUE_TYPE" type="tns:char1"/>
<xsd:element name="DISPLAY_TYPE" type="tns:char1"/>
<xsd:element name="ANS_CHOICE" type="tns:ZTCAF_GET_ANS_CHOICE"/>
</xsd:sequence>
</xsd:complexType>
−
     <xsd:complexType name="ZSCAF_ANS_CHOICE">
−
     <xsd:sequence>
<xsd:element name="ANS_CHOICE_ID" type="tns:numeric15"/>
<xsd:element name="ANS_META_ID" type="tns:numeric15"/>
<xsd:element name="HAS_COMMENT" type="tns:char1"/>
<xsd:element name="SEQ_NUM" type="xsd:int"/>
<xsd:element name="ANSWER_TEXT" type="tns:char50"/>
<xsd:element name="LANGUAGE" type="tns:char10"/>
<xsd:element name="WEIGHT" type="xsd:int"/>
<xsd:element name="HAS_DEP_QTN" type="tns:char1"/>
<xsd:element name="HAS_DEP_QTNGRP" type="tns:char1"/>
<xsd:element name="DEP_QTN" type="tns:ZTCAF_DEP_QTN"/>
<xsd:element name="DEP_QTNGRP" type="tns:ZTCAF_DEP_QTN_GRP"/>
</xsd:sequence>
</xsd:complexType>
−
     <xsd:complexType name="ZTCAF_GET_DATA_QUESTIONNAIRE">
−
     <xsd:sequence>
<xsd:element name="item" minOccurs="0" maxOccurs="unbounded" type="tns:ZCAF_ST_GET_QUESTIONNAIRE"/>
</xsd:sequence>
</xsd:complexType>
−
     <xsd:complexType name="ZTCAF_GET_ANS_CHOICE">
−
     <xsd:sequence>
<xsd:element name="item" minOccurs="0" maxOccurs="unbounded" type="tns:ZSCAF_ANS_CHOICE"/>
</xsd:sequence>
</xsd:complexType>
−
     <xsd:complexType name="ZTCAF_DEP_QTN">
−
     <xsd:sequence>
<xsd:element name="item" minOccurs="0" maxOccurs="unbounded" type="tns:ZCAF_DEP_QUEST"/>
</xsd:sequence>
</xsd:complexType>
−
     <xsd:complexType name="ZTCAF_DEP_QTN_GRP">
−
     <xsd:sequence>
<xsd:element name="item" minOccurs="0" maxOccurs="unbounded" type="tns:ZCAF_DEP_QTNGRP"/>
</xsd:sequence>
</xsd:complexType>
</xsd:schema>
</wsdl:types>
−
     <wsdl:message name="ZMCAF_CRUD_QUESTIONNAIRE">
<wsdl:part name="IS_ANSCHOICE" type="tns:ZCAF_ANS_CHOICE"/>
<wsdl:part name="IS_ANSMETA" type="tns:ZCAF_ANSWER_META"/>
<wsdl:part name="IS_ANS_SHEET" type="tns:ZCAF_ANS_SHEET"/>
<wsdl:part name="IS_COMM_ANS" type="tns:ZCAF_COMMENT_ANS"/>
<wsdl:part name="IS_COMM_TXT" type="tns:ZCAF_COMENT_TEXT"/>
<wsdl:part name="IS_DEPQTN" type="tns:ZCAF_DEP_QUEST"/>
<wsdl:part name="IS_DEPQTNGRP" type="tns:ZCAF_DEP_QTNGRP"/>
<wsdl:part name="IS_MULT_ANS" type="tns:ZCAF_MULTI_ANS"/>
<wsdl:part name="IS_QTNR_QTNGRP" type="tns:ZCAF_QTNR_QTNGRP"/>
<wsdl:part name="IS_QTN_GRP" type="tns:ZCAF_QUEST_GROUP"/>
<wsdl:part name="IS_QUESTION" type="tns:ZCAF_QUESTION"/>
<wsdl:part name="IS_QUESTIONNAIRE" type="tns:ZCAF_QUESTIONIRE"/>
<wsdl:part name="IV_CHOICE" type="tns:char1"/>
<wsdl:part name="IV_QTNR_ID" type="tns:numeric15"/>
<wsdl:part name="IV_TYPE" type="tns:char10"/>
</wsdl:message>
−
     <wsdl:message name="ZMCAF_CRUD_QUESTIONNAIREResponse">
<wsdl:part name="ET_QTNR_GET_DATA" type="tns:ZTCAF_GET_DATA_QUESTIONNAIRE"/>
<wsdl:part name="RETURN" type="tns:BAPIRET2"/>
</wsdl:message>
−
     <sap:Feature name="design_0 " uri="http://www.sap.com/webas/630/soap/features/authentication/">
−
     <sap:Property qname="n0:AuthenticationLevel">
<sap:Option value="n0:Basic"/>
</sap:Property>
</sap:Feature>
−
     <wsdl:portType name="zwsquestionnaire">
<sap:useFeature feature="tns:design_0 "/>
−
     <wsdl:operation name="ZMCAF_CRUD_QUESTIONNAIRE">
<wsdl:input message="tns:ZMCAF_CRUD_QUESTIONNAIRE"/>
<wsdl:output message="tns:ZMCAF_CRUD_QUESTIONNAIREResponse"/>
</wsdl:operation>
</wsdl:portType>
−
     <wsdl:binding name="zwsquestionnaireSoapBinding" type="tns:zwsquestionnaire">
<soap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http"/>
−
     <wsdl:operation name="ZMCAF_CRUD_QUESTIONNAIRE">
<soap:operation soapAction=""/>
−
     <wsdl:input>
<soap:body use="literal" namespace="urn:sap-com:document:sap:rfc:functions"/>
</wsdl:input>
−
     <wsdl:output>
<soap:body use="literal" namespace="urn:sap-com:document:sap:rfc:functions"/>
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
−
     <wsdl:service name="zwsquestionnaireService">
−
     <wsdl:port name="zwsquestionnaireSoapBinding" binding="tns:zwsquestionnaireSoapBinding">
<soap:address location="http://localhost:8000/sap/bc/srt/rfc/sap/ZWSQUESTIONNAIRE?sap-client=000"/>
</wsdl:port>
</wsdl:service>
</wsdl:definitions>

OK , could you please help me?
SAP error message;
Proxy generation terminated: Message must have exactly one part
Diagnosis
In a WSDL document, a <message> must contain exactly one <part>, therefore:
<message name="check_serviceHttpGetIn">
<part .../>
</message>
WSDL document;
<?xml version="1.0" encoding="utf-8"?>
<wsdl:definitions xmlns:s="http://www.w3.org/2001/XMLSchema" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:tns="http://tempuri.org/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tm="http://microsoft.com/wsdl/mime/textMatching/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" targetNamespace="http://tempuri.org/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">
   <wsdl:types>
     <s:schema elementFormDefault="qualified" targetNamespace="http://tempuri.org/">
       <s:element name="check_service">
         <s:complexType />
       </s:element>
       <s:element name="check_serviceResponse">
         <s:complexType>
           <s:sequence>
             <s:element minOccurs="1" maxOccurs="1" name="check_serviceResult" type="s:boolean" />
           </s:sequence>
         </s:complexType>
       </s:element>
       <s:element name="get_puantaj_data">
         <s:complexType>
           <s:sequence>
             <s:element minOccurs="0" maxOccurs="1" name="personel_sicilno" type="s:string" />
             <s:element minOccurs="1" maxOccurs="1" name="yil" type="s:int" />
             <s:element minOccurs="1" maxOccurs="1" name="ay" type="s:int" />
           </s:sequence>
         </s:complexType>
       </s:element>
       <s:element name="get_puantaj_dataResponse">
         <s:complexType>
           <s:sequence>
             <s:element minOccurs="0" maxOccurs="1" name="get_puantaj_dataResult">
               <s:complexType>
                 <s:sequence>
                   <s:any minOccurs="0" maxOccurs="unbounded" namespace="http://www.w3.org/2001/XMLSchema" processContents="lax" />
                   <s:any minOccurs="1" namespace="urn:schemas-microsoft-com:xml-diffgram-v1" processContents="lax" />
                 </s:sequence>
               </s:complexType>
             </s:element>
           </s:sequence>
         </s:complexType>
       </s:element>
       <s:element name="boolean" type="s:boolean" />
       <s:element name="DataTable" nillable="true">
         <s:complexType>
           <s:sequence>
             <s:any minOccurs="0" maxOccurs="unbounded" namespace="http://www.w3.org/2001/XMLSchema" processContents="lax" />
             <s:any minOccurs="1" namespace="urn:schemas-microsoft-com:xml-diffgram-v1" processContents="lax" />
           </s:sequence>
         </s:complexType>
       </s:element>
     </s:schema>
   </wsdl:types>
   <wsdl:message name="check_serviceSoapIn">
     <wsdl:part name="parameters" element="tns:check_service" />
   </wsdl:message>
   <wsdl:message name="check_serviceSoapOut">
     <wsdl:part name="parameters" element="tns:check_serviceResponse" />
   </wsdl:message>
   <wsdl:message name="get_puantaj_dataSoapIn">
     <wsdl:part name="parameters" element="tns:get_puantaj_data" />
   </wsdl:message>
   <wsdl:message name="get_puantaj_dataSoapOut">
     <wsdl:part name="parameters" element="tns:get_puantaj_dataResponse" />
   </wsdl:message>
   <wsdl:message name="check_serviceHttpGetIn" />
   <wsdl:message name="check_serviceHttpGetOut">
     <wsdl:part name="Body" element="tns:boolean" />
   </wsdl:message>
   <wsdl:message name="get_puantaj_dataHttpGetIn">
     <wsdl:part name="personel_sicilno" type="s:string" />
     <wsdl:part name="yil" type="s:string" />
     <wsdl:part name="ay" type="s:string" />
   </wsdl:message>
   <wsdl:message name="get_puantaj_dataHttpGetOut">
     <wsdl:part name="Body" element="tns:DataTable" />
   </wsdl:message>
   <wsdl:message name="check_serviceHttpPostIn" />
   <wsdl:message name="check_serviceHttpPostOut">
     <wsdl:part name="Body" element="tns:boolean" />
   </wsdl:message>
   <wsdl:message name="get_puantaj_dataHttpPostIn">
     <wsdl:part name="personel_sicilno" type="s:string" />
     <wsdl:part name="yil" type="s:string" />
     <wsdl:part name="ay" type="s:string" />
   </wsdl:message>
   <wsdl:message name="get_puantaj_dataHttpPostOut">
     <wsdl:part name="Body" element="tns:DataTable" />
   </wsdl:message>
   <wsdl:portType name="Aktarim_ServiceSoap">
     <wsdl:operation name="check_service">
       <wsdl:input message="tns:check_serviceSoapIn" />
       <wsdl:output message="tns:check_serviceSoapOut" />
     </wsdl:operation>
     <wsdl:operation name="get_puantaj_data">
       <wsdl:input message="tns:get_puantaj_dataSoapIn" />
       <wsdl:output message="tns:get_puantaj_dataSoapOut" />
     </wsdl:operation>
   </wsdl:portType>
   <wsdl:portType name="Aktarim_ServiceHttpGet">
     <wsdl:operation name="check_service">
       <wsdl:input message="tns:check_serviceHttpGetIn" />
       <wsdl:output message="tns:check_serviceHttpGetOut" />
     </wsdl:operation>
     <wsdl:operation name="get_puantaj_data">
       <wsdl:input message="tns:get_puantaj_dataHttpGetIn" />
       <wsdl:output message="tns:get_puantaj_dataHttpGetOut" />
     </wsdl:operation>
   </wsdl:portType>
   <wsdl:portType name="Aktarim_ServiceHttpPost">
     <wsdl:operation name="check_service">
       <wsdl:input message="tns:check_serviceHttpPostIn" />
       <wsdl:output message="tns:check_serviceHttpPostOut" />
     </wsdl:operation>
     <wsdl:operation name="get_puantaj_data">
       <wsdl:input message="tns:get_puantaj_dataHttpPostIn" />
       <wsdl:output message="tns:get_puantaj_dataHttpPostOut" />
     </wsdl:operation>
   </wsdl:portType>
   <wsdl:binding name="Aktarim_ServiceSoap" type="tns:Aktarim_ServiceSoap">
     <soap:binding transport="http://schemas.xmlsoap.org/soap/http" />
     <wsdl:operation name="check_service">
       <soap:operation soapAction="http://tempuri.org/check_service" style="document" />
       <wsdl:input>
         <soap:body use="literal" />
       </wsdl:input>
       <wsdl:output>
         <soap:body use="literal" />
       </wsdl:output>
     </wsdl:operation>
     <wsdl:operation name="get_puantaj_data">
       <soap:operation soapAction="http://tempuri.org/get_puantaj_data" style="document" />
       <wsdl:input>
         <soap:body use="literal" />
       </wsdl:input>
       <wsdl:output>
         <soap:body use="literal" />
       </wsdl:output>
     </wsdl:operation>
   </wsdl:binding>
   <wsdl:binding name="Aktarim_ServiceSoap12" type="tns:Aktarim_ServiceSoap">
     <soap12:binding transport="http://schemas.xmlsoap.org/soap/http" />
     <wsdl:operation name="check_service">
       <soap12:operation soapAction="http://tempuri.org/check_service" style="document" />
       <wsdl:input>
         <soap12:body use="literal" />
       </wsdl:input>
       <wsdl:output>
         <soap12:body use="literal" />
       </wsdl:output>
     </wsdl:operation>
     <wsdl:operation name="get_puantaj_data">
       <soap12:operation soapAction="http://tempuri.org/get_puantaj_data" style="document" />
       <wsdl:input>
         <soap12:body use="literal" />
       </wsdl:input>
       <wsdl:output>
         <soap12:body use="literal" />
       </wsdl:output>
     </wsdl:operation>
   </wsdl:binding>
   <wsdl:binding name="Aktarim_ServiceHttpGet" type="tns:Aktarim_ServiceHttpGet">
     <http:binding verb="GET" />
     <wsdl:operation name="check_service">
       <http:operation location="/check_service" />
       <wsdl:input>
         <http:urlEncoded />
       </wsdl:input>
       <wsdl:output>
         <mime:mimeXml part="Body" />
       </wsdl:output>
     </wsdl:operation>
     <wsdl:operation name="get_puantaj_data">
       <http:operation location="/get_puantaj_data" />
       <wsdl:input>
         <http:urlEncoded />
       </wsdl:input>
       <wsdl:output>
         <mime:mimeXml part="Body" />
       </wsdl:output>
     </wsdl:operation>
   </wsdl:binding>
   <wsdl:binding name="Aktarim_ServiceHttpPost" type="tns:Aktarim_ServiceHttpPost">
     <http:binding verb="POST" />
     <wsdl:operation name="check_service">
       <http:operation location="/check_service" />
       <wsdl:input>
         <mime:content type="application/x-www-form-urlencoded" />
       </wsdl:input>
       <wsdl:output>
         <mime:mimeXml part="Body" />
       </wsdl:output>
     </wsdl:operation>
     <wsdl:operation name="get_puantaj_data">
       <http:operation location="/get_puantaj_data" />
       <wsdl:input>
         <mime:content type="application/x-www-form-urlencoded" />
       </wsdl:input>
       <wsdl:output>
         <mime:mimeXml part="Body" />
       </wsdl:output>
     </wsdl:operation>
   </wsdl:binding>
   <wsdl:service name="Aktarim_Service">
     <wsdl:port name="Aktarim_ServiceSoap" binding="tns:Aktarim_ServiceSoap">
       <soap:address location="http://192.168.10.151:7979/sap_aktarim/Aktarim_Service.asmx" />
     </wsdl:port>
     <wsdl:port name="Aktarim_ServiceSoap12" binding="tns:Aktarim_ServiceSoap12">
       <soap12:address location="http://192.168.10.151:7979/sap_aktarim/Aktarim_Service.asmx" />
     </wsdl:port>
     <wsdl:port name="Aktarim_ServiceHttpGet" binding="tns:Aktarim_ServiceHttpGet">
       <http:address location="http://192.168.10.151:7979/sap_aktarim/Aktarim_Service.asmx" />
     </wsdl:port>
     <wsdl:port name="Aktarim_ServiceHttpPost" binding="tns:Aktarim_ServiceHttpPost">
       <http:address location="http://192.168.10.151:7979/sap_aktarim/Aktarim_Service.asmx" />
     </wsdl:port>
   </wsdl:service>
</wsdl:definitions>

Message must have exactly one part

hi,
I have tryed to create a proxy in ECC 6.0 abap but it gives an error message:
Proxy generation terminated: Message must have exactly one part
Message no. SPRX046
Background
During proxy generation, an interface description in WSDL format is fetched from the Integration Builder or from another source and interpreted. This WSDL document must describe the whole interface correctly.
==> Display Query
==> Display WSDL Document
Diagnosis
In a WSDL document, a <message> must contain exactly one <part>, therefore:
<message name="ObtenerLicenciaRequest">
<part .../>
</message>
In this case, a <message> has no <part> or multiple <part> entries. Proxy generation cannot process such messages.
System Response
Proxy generation is terminated.*
can any one help me?
The WSDL is:
http://200.0.156.42/lme_pruebas/webservices/webservicesEmpleadores.php?wsdl
Thanks

Here is the fragment from your WSDL. You have more than one line with <part name...>:
- <message name="ObtenerLicenciaRequest">
<part name="rut_empleador" type="xsd:int" />
<part name="dv_rut_empleador" type="xsd:string" />
<part name="rut_usuario" type="xsd:int" />
<part name="dv_rut_usuario" type="xsd:string" />
<part name="password" type="xsd:string" />
<part name="fecha_proceso" type="xsd:dateTime" />
</message>
According to the error message, you must have only one of those, e.g.:
- <message name="ObtenerLicenciaRequest">
<part name="rut_empleador" type="xsd:int" />
</message>

I am trying to burn an iDVD but get message menu contains no buttons. How do I fix this issue?

I am trying to burn an iDVD, but get message menu contains no buttons. How do I fix this issue?

That essentially means that there's been no videos or slideshows added to the project as each of those items will create a button to play. What have you added to the project?
OT

Http sender adapter: QoS is interpreted as Best Effort by PI 7.11

Hi
I have a scenario, where I receive an xml OrderResponse via an http sender adapter and I then map it to an iDoc which is sent to the backend system.
BUT: for some reason, PI thinks, that the Quality of Service is BE, and I get the error "Only asynchronous processing supported for IDoc adapter outbound processg".
I have checked both the http sender adapter, the sender agreement, the interface mapping, the service interface and the operation mapping and nowhere can I see, that best effort is selected.
The OrderResponse is sent from an external partner and is routed through a load balancer and an SAP web dispatcher before arriving to PI.
Any suggestions would be highly appreciated.
MIkael Lund

The external partner is sending the OrderResponse to this URL (external URL):
https://xxxxxx.xxxxxxxx.dk/sap/xi/adapter_plain?service=LM&namespace=http://xxxxxxxx.dk/XCBL/OrderResponse&interface=xCBLOrderResponse35Out
this URL is being translated to an internal URL:
https://yyyyyyy.yyyyyyy.dk/sap/xi/adapter_plain?service=LM&namespace=http://xxxxxxxx.dk/XCBL/OrderResponse&interface=xCBLOrderResponse35Out
So how should the external and/or internal URL be altered?
Thanks for a very quick answer by the way
MIkael

HT1539 I purchased the Bu Ray/Digital Copy of "Voyage of the Dawn Treader" today at Best Buy, but when attempt to install the digital copy, I get a message about 3 minutes into the download that says that the download has been interrupted, and to check av

I purchased the Bu Ray/Digital Copy of "Voyage of the Dawn Treader" today at Best Buy, but when attempt to install the digital copy, I get a message about 3 minutes into the download that says that the download has been interrupted, and to check available download in the store drop down menu in Itunes. Nothing there! The digital copy disc does not seem to play smoothly on my Imac, which may be the cause of the problem. What do I need to do to download the digital copy to my computer/Itunes?
Thank you,
Jonathan Mink

I purchased the Bu Ray/Digital Copy of "Voyage of the Dawn Treader" today at Best Buy, but when attempt to install the digital copy, I get a message about 3 minutes into the download that says that the download has been interrupted, and to check available download in the store drop down menu in Itunes. Nothing there! The digital copy disc does not seem to play smoothly on my Imac, which may be the cause of the problem. What do I need to do to download the digital copy to my computer/Itunes?
Thank you,
Jonathan Mink

MessageId missing in SOAP message header

I am trying to execute a SAP (IDoc) -> XI -> SAP (ABAP Proxy). The SAP machines are 6.2, the XI machine is 6.4. I have generated and tested the ABAP proxy, works without issue. Per previous threads I also tested the message mapping in the repository, also works successfully. When I review the SXI_Monitor in XI, the message is received successfully, mapped successfully, but errors in the Adater Call step. There is no message listed as received in the sxi_monitor on the recevier SAP system. Error Message is as follows:
<?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="1">
<SAP:Category>XIProtocol</SAP:Category>
<SAP:Code area="PARSER">ITEM_MISSING</SAP:Code>
<SAP:P1>/MessageHeader/MessageId</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>XML tag /MessageHeader/MessageId missing in SOAP message header (SAP XI Extension)</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Looking at the message in the monitor it does have a message id assigned. Only other interesting thing is in the trace section where it says :
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
<Trace level="1" type="System_Error">Error exception return from pipeline processing!</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
All other messages are successful in this persistence(send to file, Idoc, etc).
What is the issue?

Hi Darin,
Check your receiver communication channel. Make sure that the protocol is set to XI 2.0 for 6.2.
Hope that helps.
Best Regards,
Doo

Envelope missing in SOAP message header (SAP XI Extension)

I have scenario where in I am sending a file from XI to PCK. BUt i am getting a following error.
<?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>XIProtocol</SAP:Category>
<SAP:Code area="PARSER">ITEM_MISSING</SAP:Code>
<SAP:P1>Envelope</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>XML tag Envelope missing in SOAP message header (SAP XI Extension)</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
I am enclosing the file i am trying to send.
<?xml version="1.0" encoding="UTF-8" ?>
- <ns0:CFP_SENDER_MT xmlns:ns0="HTTP://PCKXI.WORLDBANK.ORG">
- <SEND>
<TF_Number>12</TF_Number>
<TF_Desc>1212</TF_Desc>
</SEND>
</ns0:CFP_SENDER_MT>
Can somebody please enlighten me about this error? Points would be rewarded immediately
Regards,
Manish

Dear Manish,
quite often the reason for this kind of error
is the fact that the receiver of the XI message is
returning a http response to the Integration Server.
As of XI3.0 SP21 / PI7.0 SP13 this response
is also properly parsed and visible in the error
header of the XI message.
For almost all prior support package levels an
advanced correction is available as per OSS note:
1064346 Improved error output for connection problems
Please check whether this applies to your system.
If so, you will see detailed information on the error
in the error header object of the XI message as soon
as this issue re-occurs.
Best Regards,
Harald Keimer
XI Development Support
SAP AG, Walldorf

QoS issue with OSB publish to JMS business service

Hi,
1. I have a http OSB proxy service which is publishing an audit message to a JMS queue through OSB business service.
MainProxyService (http) --> Publish (best-effort) --> AuditBusinessService (JMS) --> Audit Queue
2. I want 'Publish to JMS business service' to be a non-blocking call so that proxy service message flow can continue. Transaction support is disabled in proxy service as well as in JMS connection factory.
3. As default value of QoS (quality of service) for publish action is best-effort, ideally proxy service should continue its message flow immediately after dispatching the message to publish action and it should not block the main proxy flow.
4. But in my case, proxy service is blocking the message flow until the message is delivered to JMS business service/JMS queue. This is degrading performance of my application.
5. I think default 'best-effort' QoS is not working with JMS business service as there is a significant time lag between publish action and its next subsequent action.
6. If I replace the JMS business service with HTTP business service, then it seems to be a non-blocking call and message flow immediately proceeds to next actions.
Correct me if I am going wrong anywhere or my understanding is wrong.
Many thanks.

HI,
u can use Conditional Branching
http://docs.oracle.com/cd/E13159_01/osb/docs10gr3/userguide/modelingmessageflow.html#wp1061670
Split join would be used in case u need to split your request and call your Business Service in Serial/parallel & then gather resposnes from multiple callouts to have single response
http://docs.oracle.com/cd/E13159_01/osb/docs10gr3/userguide/splitjoin.html#wp1137258
Abhinav

Best effort

Hi all
I have difficulty with translating of term "best effort" what does it mean?
i know that it is QoS for synchronius interface...but why "best effort". How many efforts and which of them best?

Hi !
Mikhail
XI.QualityOfService=<QualityOfService>
Specifies how the Integration Engine should process a message. The following values are permitted:
■ XI.qualityOfService=BE(Best Effort, means synchronous processing)
■ XI.qualityOfService=EO(Exactly Once, means asynchronous processing with guaranteed execution exactly once)
■ XI.qualityOfService=EOIO(Exactly Once in Order, means asynchronous processing using queues,
Best Effort --> Used for Synchronous Calls.
EO and EOIO --> Asynchronous Calls.
EOIO --> Asynchronous with Sequential Processing Guranteed.
Check this help:
http://help.sap.com/saphelp_nw04/helpdata/en/41/b714fe5ffc11d5b3ea0050da403d6a/frameset.htm
Thanks!
pls reward if useful

Accessing SAP:HopList element in message header from JAVA-mapping

Dear Experts,
Is it possible to access the SAP:HopList element from message header in JAVA-mapping?
I need this to get the list off all receivers of current message (I have a ReceiverDetermination with two receivers, without any conditions, so both receivers are receiving each message and in InterfaceDetermination to one of the receivers I have a JAVA-mapping, in which I need to know the name of another receiver. And the SAP:HopList is containing this information).
Or maybe where is some other solution?
Best Regards,
Artsiom Anichenka

That's tricky, since the proper way of doing it would be through BPM.
Anyway, if you expose your XI interface as a WebService (Soap sender cc) you could access it through Mapping Lookup (lookup works for RFC, DB and Soap lookups). Check https://help.sap.com/javadocs/NW04S/current/pi/index.html
But be aware that Mapping Lookup API is not intended for inserts/updates (since it doesn't contain any transacational handling), just mere lookups (selects in tables), so I'm not sure it is the best approach for your case.
Regards,
Henrique.

Despite my best efforts, I am unable to remove iTunes 11.1.4 from my PC, this being made necessary because the original installation had a flaw and did not load properly. Effor to use the control panel, deleting dll. files, etc. all failed. iTune out??

Despite my best efforts, I am unable to remove iTunes 11.1.4 from my PC, this being made necessary because the original installation had a flaw and did not load properly. Effor to use the control panel, deleting dll. files, etc. all failed. And, of course, on startup, a window opens with the error and tells me find QTMovie.dll and delete it because this may be the source of the hangup. Also, in trying to delete iTunes, I get the additional message that I must get approval from the System Administrator to take this action. I am the System Administrator.
Any ideas would be welcomed.
Thank you.
James
<E-mail Edited by Host>

Thank you for asking this question. I'm having the same issues.
Liz

Message Header value is not written to DynamicConfiguration

Hi Forum,
I have a scenario on a PI 7.11 SP06, where a SOAP message is sent via HTTP to a SAP WAS Java.
The response contains in header a parameter"set-cookie" which has to be written in dynamic configuration.
For example: Set-Cookie: JSESSIONID=DF4D3F35636D8E3549490B678SAP9403229; Path=/
Therefore, i use SOAP adapter with axis extension, but the "set-cookie" content is not written to dynamicconfiguration.
Here is my axis adapter configuration. Do you see something wrong here?
**Processing Sequence**
1    AF_Adapters/axis/AFAdapterBean                afreq
2    AF_Adapters/axis/HandlerBean                     xireq----------------------O/B Handler
3    AF_Adapters/axis/HandlerBean                     trp--------------------------- HTTPSender
4    AF_Adapters/axis/HandlerBean                     dcres----------------------This is for Dynamic Configuration (read)
5    AF_Adapters/axis/HandlerBean                     xires------------------------O/BHandler
6    AF_Adapters/axis/AFAdapterBean                afres
**Module Configuration**
dcres          handler.type     java:com.sap.aii.axis.xi.XI30DynamicConfigurationHandler
dcres          key.1          read http://sap.com/xi/XI/System/HTTP SetCookie
dcres          location.1      header
dcres          value.1          set-cookie
trp             handler.type     java:com.sap.aii.adapter.axis.ra.transport.http.HTTPSender
trp             module.pivot     true
xireq          handler.type     java:com.sap.aii.axis.xi.XI30OutboundHandler
xires          handler.type     java:com.sap.aii.axis.xi.XI30OutboundHandler
I followed the [How To Guide|http://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/b092777b-ee47-2a10-17b3-c5f59380957f] which is unfortunately for 7.0.
Also i tried with "set-cookie" and "Set-Cookie" without success. I have written a small java test which is accessing
this service and I can see parameter "set-cookie" in the header. So with small letters should be okay.
I have also read this very similar [sdn thread|DynamicConfiguration to Message Header;.
Tests with writing constants to dynamicconfiguration works without any problem.
I'm not sure if i have the correct handler classes. Is there any documentation about the handlers?
Any help is very appreciated.
Thanks in forward and best regards,
Sigi

Hi all,
thanks for response.
I'm aware of these functions so I tried the test to create a dummy entry in header and read it from there.
So first i used which wrote constant to ASMA
dcres1     key.1    insert http://sap.com/xi/XI/System/HTTP dummy
dcres1     value.1 12345
Then I used write to move that constant from ASMA to header
dcres2     key.1   write http://sap.com/xi/XI/System/HTTP dummy
dcres2     location.1 header
dcres2     value.1 dummy
Finally i used read on that dummy value, creating a new entry in ASMA based upon that dummy entry
dcres3     key.1   read http://sap.com/xi/XI/System/HTTP SetCookie
dcres3     location.1 header
dcres3     value.1 dummy
So the "read" entry is correct in my origin settings. So now I know that the "set-cookie" header parameter from Java WAS response is not passed through SOAP Axis adapter.
Does anybody know if there are settings which have to be changed in system? Or is that a design as usual, that the set-cookie parameter is not passed to SOAP AXIS HTTP-header params?
Thanks in forward and best regards,
Sigi
Edited by: Siegfried Ertl on Apr 13, 2011 3:06 PM

QoS issue: Specify Best Effort, but message header contains Exactly Once

Similar Messages

Maybe you are looking for