Message structure in imported WSDL

Hi All,
         I have the following structure in a imported WSDL:
    <xsd:complexType name="CustomersUpdate">
            <xsd:complexContent>
               <xsd:extension base="p0:CustomersCreate">
                  <xsd:sequence>
                     <xsd:element name="recordIdentification" type="p0:CustomersID" minOccurs="0" nillable="true" />
                  </xsd:sequence>
               </xsd:extension>
            </xsd:complexContent>
         </xsd:complexType>
When I see the message I see the recordIdentification first ,then CustomerCreate.Is that a bug in SAP while using extensions?
Regards,
Premjit

Hi,
It depnds upon the standards used for WSDL and compatibility of it with PI.
Thanks
Swarup

Similar Messages

No messages under the 'Messages' tab for imported WSDL in External Definitions

Dear All,
I import this WSDL to the External Definitions but it is not showing any messages in the 'Messages' tab while WSDL clearly has message interfaces in it. Attached is the WSDL. You help is very much appreciated.
Regards,
Adil Khalil

Hi, imported wsdl shouldn't have any import instruction.
All import instruction should be changed to content of importing file.
I see the code <xsd:import namespace="http://ouaf.oracle.com/"/> in your file.
Hmm. but I imported you file and everything is fine
Message was edited by: Mikhail Koshkin

In Message tab message missing while importing wsdl

My scenario is a file to webservice to Idoc scenario.
1.We first send a request file to XI to start the BPM receive step.
2.the request message goes to a webservice and fetches a response structure and
3.The response structure maps to idoc and finally posts to R/3.
The java team has made the webservice and sent it to me but when I import it as a External definition I donu2019t get any message in the message tab.
So please suggest what I can do in this scenario.

<?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions targetNamespace="http://bean.getinvoiceinformation.ewscservices.ewsc.nesas.nissan.com" xmlns:impl="http://bean.getinvoiceinformation.ewscservices.ewsc.nesas.nissan.com" xmlns:intf="http://bean.getinvoiceinformation.ewscservices.ewsc.nesas.nissan.com" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:wsi="http://ws-i.org/profiles/basic/1.1/xsd" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<wsdl:types>
<schema targetNamespace="http://bean.getinvoiceinformation.ewscservices.ewsc.nesas.nissan.com" xmlns="http://www.w3.org/2001/XMLSchema">
   <element name="generateInvoiceInformationResponse">
    <complexType>
     <sequence>
      <element name="generateInvoiceInformationReturn" nillable="true" type="xsd:string"/>
     </sequence>
    </complexType>
   </element>
   <element name="generateInvoiceInformation">
    <complexType>
     <sequence>
      <element name="fromDate" nillable="true" type="xsd:string"/>
      <element name="toDate" nillable="true" type="xsd:string"/>
      <element name="countryCode" nillable="true" type="xsd:string"/>
      <element name="specType" nillable="true" type="xsd:string"/>
     </sequence>
    </complexType>
   </element>
</schema>
</wsdl:types>
   <wsdl:message name="generateInvoiceInformationResponse">
     <wsdl:part element="impl:generateInvoiceInformationResponse" name="parameters"/>
</wsdl:message>
   <wsdl:message name="generateInvoiceInformationRequest">
     <wsdl:part element="impl:generateInvoiceInformation" name="parameters"/>
</wsdl:message>
   <wsdl:portType name="GetInvoiceInformation">
     <wsdl:operation name="generateInvoiceInformation">
       <wsdl:input message="impl:generateInvoiceInformationRequest" name="generateInvoiceInformationRequest"/>
       <wsdl:output message="impl:generateInvoiceInformationResponse" name="generateInvoiceInformationResponse"/>
    </wsdl:operation>
</wsdl:portType>
   <wsdl:binding name="GetInvoiceInformationSoapBinding" type="impl:GetInvoiceInformation">
     <wsdlsoap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
     <wsdl:operation name="generateInvoiceInformation">
       <wsdlsoap:operation soapAction=""/>
       <wsdl:input name="generateInvoiceInformationRequest">
         <wsdlsoap:body use="literal"/>
      </wsdl:input>
       <wsdl:output name="generateInvoiceInformationResponse">
         <wsdlsoap:body use="literal"/>
      </wsdl:output>
    </wsdl:operation>
</wsdl:binding>
   <wsdl:service name="GetInvoiceInformationService">
     <wsdl:port binding="impl:GetInvoiceInformationSoapBinding" name="GetInvoiceInformation">
       <wsdlsoap:address location="http://localhost:9083/EWSCWsAppQA/services/GetInvoiceInformation"/>
    </wsdl:port>
</wsdl:service>
</wsdl:definitions>

Issue with XML namespace and Message structure

Hi All,
I am using Oracle SOA Suite 11.1.1.4. I have SOA web service application one-way messaging wherein I keep receiving messages from the third party. The issue I am facing is with the XML namespaces which conflicts with the third party's message structure. The details are as below.
Our Web-service WSDL*
<schema attributeFormDefault="unqualified" elementFormDefault="qualified"
targetNamespace="http://amb.com/cad/RealTimeService"
xmlns:cad="http://amb.com/cad/RealTimeService"
xmlns:avl="http://schemas.com/asiapac/cad/datamodel/avl/1.0.0"
xmlns:evn="http://schemas.com/asiapac/cad/datamodel/event/1.0.0"
xmlns:uni="http://schemas.com/asiapac/cad/datamodel/unit/1.0.0"
xmlns:dvt="http://schemas.com/asiapac/cad/datamodel/divert/1.0.0"
xmlns:sui="http://schemas.com/asiapac/cad/datamodel/suppinfo/1.0.0"
xmlns="http://www.w3.org/2001/XMLSchema">
<import namespace="http://schemas.com/cad/datamodel/avl/1.0.0"
schemaLocation="AvlCadSchema.xsd"/>
<import namespace="http://schemas.com/cad/datamodel/unit/1.0.0"
schemaLocation="UnitCadSchema.xsd"/>
<import namespace="http://schemas.com/cad/datamodel/event/1.0.0"
schemaLocation="EventCadSchema.xsd"/>
<import namespace="http://schemas.com/cad/datamodel/divert/1.0.0"
schemaLocation="HewsCadSchema.xsd"/>
<import namespace="http://schemas.com/cad/datamodel/suppinfo/1.0.0"
schemaLocation="SupplementalInformationCadSchema.xsd"/>
<element name="AvlAuxData" type="avl:AvlAuxData" nillable="true"/>
<element name="AgencyEvent" type="evn:AgencyEvent"/>
<element name="Diversion" type="dvt:HospitalDiversionMessage"/>
<element name="SupplementalInformation" type="sui:SupplementalInformation"/>
<element name="UnitDetail" type="uni:UnitDetail"/>
</schema>
Using SOAP UI tool a HospitalDiversionMessage Request for the above WSDL will look like*
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:real="http://amb.com/cad/RealTimeService" xmlns:ns="http://schemas.com/cad/datamodel/divert/1.0.0">
<soapenv:Header/>
<soapenv:Body>
<*real*:Diversion>
<ns:Action>?</ns:Action>
<ns:Open>?</ns:Open>

<ns:Location>?</ns:Location>
<ns:Type>?</ns:Type>
<ns:SubType>?</ns:SubType>

<ns:ExpiryTimestamp>?</ns:ExpiryTimestamp>

<ns:Comment>?</ns:Comment>

<ns:ItemNumber>?</ns:ItemNumber>

<ns:Notifications>?</ns:Notifications>
<ns:CreatedTerminal>?</ns:CreatedTerminal>
<ns:CreatedTimestamp>?</ns:CreatedTimestamp>

<ns:ClosedBy>?</ns:ClosedBy>

<ns:ClosedComments>?</ns:ClosedComments>

<ns:ClosedTerminal>?</ns:ClosedTerminal>

<ns:ClosedTimestamp>?</ns:ClosedTimestamp>
</real:Diversion>
</soapenv:Body>
</soapenv:Envelope>
Now the third party sends a HospitalDiversionMessage in this format_
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns0="http://amb.com/cad/RealTimeService" xmlns:ns="http://schemas.com/cad/datamodel/divert/1.0.0">
<soapenv:Header/>
<soapenv:Body>
<ns0:Diversion>
<ns0:Action>?</ns0:Action>
<ns0:Open>?</ns0:Open>

<ns0:Location>?</ns0:Location>
<ns0:Type>?</ns0:Type>
<ns0:SubType>?</ns0:SubType>

<ns0:ExpiryTimestamp>?</ns0:ExpiryTimestamp>

<ns0:Comment>?</ns0:Comment>

<ns0:ItemNumber>?</ns0:ItemNumber>

<ns0:Notifications>?</ns0:Notifications>
<ns0:CreatedTerminal>?</ns0:CreatedTerminal>
<ns0:CreatedTimestamp>?</ns0:CreatedTimestamp>

<ns0:ClosedBy>?</ns0:ClosedBy>

<ns0:ClosedComments>?</ns0:ClosedComments>

<ns0:ClosedTerminal>?</ns0:ClosedTerminal>

<ns0:ClosedTimestamp>?</ns0:ClosedTimestamp>
</ns0:Diversion>
</soapenv:Body>
</soapenv:Envelope>
Questions*
1) I cannot figure out how the SOAPUI tool or SOA substitutes "real" as the namespace prefix for the WSDL based HospitalDiversionMessage and what I need to do at my end to match the message structure as per what the third party needs.
2) I need ns0 namespace prefix to whole of Diversion xml element. Currently it is "real" at top Diversion element and "ns" for its children
Please suggest, I can attach the other imported XSD if need be.
Thanks
Edited by: user5108636 on Jun 13, 2011 6:55 PM
Edited by: user5108636 on Jun 13, 2011 6:57 PM
Edited by: user5108636 on Jun 13, 2011 7:02 PM

Questions
1) I cannot figure out how the SOAPUI tool or SOA substitutes "real" as the namespace prefix for the WSDL based HospitalDiversionMessage and what I need to do at my end to match the message structure as per what the third party needs.The xml namespace suffixes like real and ns0 are just references used by the XML Parsers. For that matter the "real" can be xyz as well.
You dont need to make any changes as long as the xml namespace suffixes refer to the same namespace.
If you see the first soapUI xml and the third party xml have the same namespace references and hence it is not a problem:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:real="*http://amb.com/cad/RealTimeService*" xmlns:ns="http://schemas.com/cad/datamodel/divert/1.0.0">
<soapenv:Header/>
<soapenv:Body>
<*real*:Diversion>
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns0="*http://amb.com/cad/RealTimeService*" xmlns:ns="http://schemas.com/cad/datamodel/divert/1.0.0">
<soapenv:Header/>
<soapenv:Body>
<*ns0*:Diversion>
2) I need ns0 namespace prefix to whole of Diversion xml element. Currently it is "real" at top Diversion element and "ns" for its childrenBased on this, logically both the xmls represent the same xml message. And hence you dont need to make any changes.
Please refer to the basics of xml namespaces using the following links:
http://en.wikipedia.org/wiki/XML_namespace
http://zvon.org/comp/r/tut-Namespace.html#Pages~Introduction
Let us know if you still need clarification.
Hope this helps.
Thanks,
Patrick

Unable to import WSDL in PI 7.1

Hi All,
I am getting the following error when I import a wsdl as an external definition in PI 7.1
Unable to convert imported document to WSDL
Reason:
Node "/definitions/portType("CallerServiceSoap")" already contains the child element "operation" with the value "submitData" of the attribute "name"Check the selected category
Please help..
Strangely i am able to extract the Request structure by importing the same wsdl in SOAP UI...
WSDLsnippet:
<wsdl:portType name="CallerServiceSoap">
     <wsdl:operation name="submitData">
          <wsdl:input name="InformationDesimation" message="tns:InformationDesimationSoapIn"/>
          <wsdl:output name="InformationDesimation" message="tns:InformationDesimationSoapOut"/>
     </wsdl:operation>
     <wsdl:operation name="submitData">
          <wsdl:input name="ResponseCapture" message="tns:ResponseCaptureSoapIn"/>
          <wsdl:output name="ResponseCapture" message="tns:ResponseCaptureSoapOut"/>
     </wsdl:operation>
     <wsdl:operation name="getResult">
          <wsdl:input message="tns:getResultSoapIn"/>
          <wsdl:output message="tns:getResultSoapOut"/>
     </wsdl:operation>
</wsdl:portType>
regards,
Piyush
Edited by: Piyush Mathur SAP on Nov 20, 2009 9:40 AM

Hi Piyush,
It is a problem with WSDL.. Can you atleast paste the portion where the error message is pointing so that we can have a better understanding
Regards
Suraj

Problem while Importing wsdl( Generated in XI) in Visual Studio

Hello XPert's,
I am working on a scenario where I have to call SAP XI web service in client .Net application using Visual Studio5.
I have already generated my wsdl using SAP XI Web Service wizard. Here is the part of my wsdl...
<?xml version="1.0" encoding="ISO-8859-1"?>
<wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:p1="http://ccsd.net/sapr3/wm/manifest" name="MI_MULT_IMAGES" targetNamespace="http://ccsd.net/sapr3/wm/manifest">
     <wsdl:documentation>
     Message interface for outbound
     </wsdl:documentation>
     <wsdl:types>
          <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://ccsd.net/sapr3/wm/manifest" targetNamespace="http://ccsd.net/sapr3/wm/manifest">
               <xsd:element name="MT_RECORD_MULTIPLE" type="SAVEIMAGE_MULTIPLE" />
               <xsd:complexType name="SAVEIMAGE_MULTIPLE">
                    <xsd:annotation>
                         <xsd:appinfo source="http://sap.com/xi/TextID">
                         f3999640f96e11dcae470003bab2aa70
                         </xsd:appinfo>
                    </xsd:annotation>
                    <xsd:sequence>
                         <xsd:element name="DT_IMAGES" maxOccurs="unbounded">
                              <xsd:annotation>
                                   <xsd:appinfo source="http://sap.com/xi/TextID">
                                   7b023f10f91011dca4280011439c56bd
                                   </xsd:appinfo>
                              </xsd:annotation>
                              <xsd:complexType>
                                   <xsd:sequence>
                                        <xsd:element name="ImageName" type="xsd:string">
                                             <xsd:annotation>
                                                  <xsd:appinfo source="http://sap.com/xi/TextID">
                                                  7b023f11f91011dcb4b70011439c56bd
                                                  </xsd:appinfo>
                                             </xsd:annotation>
                                        </xsd:element>
                                        <xsd:element name="ImageData" type="xsd:base64Binary">
                                             <xsd:annotation>
                                                  <xsd:appinfo source="http://sap.com/xi/TextID">
                                                  7b023f12f91011dc9ded0011439c56bd
                                                  </xsd:appinfo>
                                             </xsd:annotation>
                                        </xsd:element>
                                   </xsd:sequence>
                              </xsd:complexType>
                         </xsd:element>
                    </xsd:sequence>
               </xsd:complexType>
          </xsd:schema>
     </wsdl:types>
     <wsdl:message name="MT_RECORD_MULTIPLE">
          <wsdl:documentation>
          Message type
          </wsdl:documentation>
          <wsdl:part name="MT_RECORD_MULTIPLE" element="p1:MT_RECORD_MULTIPLE" />
     </wsdl:message>
     <wsdl:portType name="MI_MULT_IMAGES">
          <wsdl:operation name="MI_MULT_IMAGES">
               <wsdl:output message="p1:MT_RECORD_MULTIPLE" />
          </wsdl:operation>
     </wsdl:portType>
     <ifr:properties xmlns:ifr="urn:com-sap:ifr:v2:wsdl">
          <ifr:category>
          ifmmessif
          </ifr:category>
          <ifr:methods>
               <ifr:method name="MI_MULT_IMAGES">
                    <ifr:isSynchron>
                    false
                    </ifr:isSynchron>
                    <ifr:isInbound>
                    false
                    </ifr:isInbound>
                    <ifr:interfaceCategory>
                    outbound
                    </ifr:interfaceCategory>
               </ifr:method>
          </ifr:methods>
          <ifr:messages>
               <ifr:message name="MT_RECORD_MULTIPLE">
                    <ifr:messType>
                    ifmmessage
                    </ifr:messType>
                    <ifr:technicalNamespace>
                    http://ccsd.net/sapr3/wm/manifest
                    </ifr:technicalNamespace>
               </ifr:message>
          </ifr:messages>
     </ifr:properties>
</wsdl:definitions>
However,
Whenever I tried to import the wsdl in visual studio, it do not create / generate the classes for the element with maxoccurs="unbounded" ( here DT_IMAGES)...its just disappear...and makes diifficult for calling webservice-method in client application.
Anybody has faced this problem before? there is any workaround for this?
All help/suggestion would be highly appreciated.
Thanks & Rgds,
Nilesh

Hi Nilesh,
Can you try modifying your WSDL a bit by defining DT_IMAGES as complex type directly in definition because your previous WSDL is causing ambiguity. It will not affect your message structure.Please see the BOLD Lines.
<xsd:element name="MT_RECORD_MULTIPLE" type="SAVEIMAGE_MULTIPLE" />
<xsd:complexType name="SAVEIMAGE_MULTIPLE">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
f3999640f96e11dcae470003bab2aa70
</xsd:appinfo>
</xsd:annotation>
<xsd:sequence>
<xsd:complexType name="DT_IMAGES" maxOccurs="unbounded">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
7b023f10f91011dca4280011439c56bd
</xsd:appinfo>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="ImageName" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
7b023f11f91011dcb4b70011439c56bd
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="ImageData" type="xsd:base64Binary">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
7b023f12f91011dc9ded0011439c56bd
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:sequence>
</xsd:complexType>
</xsd:schema>
</wsdl:types>
Regards,
Piyush

Map CDATA to Message Structure

Recently, I've been asked to map generic message data embedded in a XML body's CDATA container to a complete message structure defined in XI.
When I searched on SDN, I could only find information about the other way around (wrapping XML structured data into CDATA) which is why I'm posting this thread. The solution is so easy, yet doesn't seem to be straightforward, which is why I absolutely wanted to document and share it with you.
This is the message sent to SAP PI:
<?xml version="1.0" encoding="UTF-8"?>
<Envelope>
     <Header>
          <To>Danny</To>
          <MsgType>test</MsgType>
     </Header>
     <Body><![CDATA[<hr:TestMsgRequest xsi:schemaLocation="http://tatis.com/test/schemas/ testcdata.xsd" xmlns:hr="http://danny.com/manifest/schemas/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><hr:customer><hr:name>aaaaaaaaaaaaaaaaaaaaaaa</hr:name><hr:code>1234</hr:code><hr:address>     <hr:name>test Customer</hr:name><hr:postalcode>BE9876</hr:postalcode><hr:town>Somewhere</hr:town><hr:country>Belgium</hr:country></hr:address></hr:customer>
</hr:TestMsgRequest>]]></Body>
</Envelope>
As you see it consists of a Header and a Body. The Body contains the CDATA which should be unserialized and mapped to the following message structure
<customer>
     <name>aaaaaaaaaaaaaaaaaaaaaaa</name>
     <code>1234</code>
     <address>
          <name>test Customer</name>
          <postalcode>BE9876</postalcode>
          <town>Somewhere</town>
          <country>Belgium</country>
     </address>
</customer>
I've created an xslt mapping, imported it as an archive and used the XSLT mapping in the interface mapping.
The following source code did the trick:
<?xml version="1.0"?>
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:ns0="http://tatis.com/schemas/msg/envelope/ext">
     <xsl:template match="ns0:Envelope">
               <xsl:value-of select="ns0:Body" disable-output-escaping="yes"/>
     </xsl:template>
</xsl:stylesheet>
As you might have noticed during mapping testing, XI adds a namespace to your source XML structure (ns0, ns1, etc.). You should pay attention to include this namespace in the XSLT!
If you have questions, don't hesitate to drop a mail, Danny.

Hi.
Thanks. I am still not understanding.
Where did / How did you derive the ns "xmlns:ns0="http://tatis.com/schemas/msg/envelope/ext"???
Thanks.
Sean

IDoc Message Structure Missing from Condition Editor - SWCV Dependency

Hi All,
I have an issue whereby I am missing the Message Structure in the Condition Editor Dialog while doing Receiver determination. I have seen others posts with the issue but none of the solutions seem to apply to me. My config:
I have a SWCV called MY_SAP_BASIS, which is defined in the SLD with SAP BASIS as prereq. I import this SWCV into IR and build some objects. I wish to use an IDoc, so I import it into SAP BASIS, and it appears under my SWCV (MY_SAP_BASIS) in the "Basis Objects" section, but not directly under "Imported Objects" - as I would expect because of the relationship created in the SLD.
My issue comes when I try to create a Rec. Determination. I want to use the condition editor, for multiple receivers, but when I click on the button to bring that up, first I get the error "Message interface does not exist in any software components installed on this business system", then when I try to use the Structure of the IDoc for an XPath, the structure browser is empty.
I can't see why this would be. If I look in the SLD, and look at the Business System in question, it lists MY_SAP_BASIS and SAP BASIS as being installed.
Also, when I do a "Where used" in IR on that IDoc, using my own SWCV and SAP BASIS, I get the same list. I have also checked the GUID's between the SLD and IR, and they are identical (except fpr hyphens in the display, which I am assuming don't matter).
Anyone have any ideas? I assume that if I import the IDocs directly in MY_SAP_ERP, I will be able to solve this. But I would rather the Software Dependency worked!
Many thanks.

Jai/Michal,
Many thanks for your replies. But unfortunately I had already checked this and I don't think it is the issue. My first message probably wan't as clear as it should have been: I have a Product "MY_SAP_BASIS" - this has one SWCV under it, also called "MY_SAP_BASIS". This SWCV has a dependency on "SAP BASIS 4.6c". Now, on the Technical and Business systems involved, the Product "MY_SAP_BASIS" is installed. This, as you would expect from the dependency, brings across the "MY_SAP_BASIS" SWCV and the "SAP BASIS 4.6c" SWCV, so they are both installed on the technical system . So I don't know what else I should be adding? Unless my understanding of Software dependencies is incorrect, I think my config looks right in the SLD. The SWCV under which the IDoc imports are done is "SAP BASIS 4.6c", and this is installed on both the technical and business system. The only difference is that it gets there through a software dependency, and is not added "directly". In IR I can see the imported objects under the "MY_SAP_BASIS" SWCV - in the "Basis Objects" section.
Is there anything else anyone can suggest?

Import WSDL file along with XSD

Hi,
I have a WSDL file which has complex Data types (abc.wsdl). This complex data types are defined in the XSD file (abc-data.xsd).
If I just import WSDL file in ED I am unable to find the Complex Data types in Message Mapping.
How can I use the XSD file along with the WSDL file? Is there any source path as to give or what?
Could you please help me out?

first i will tell how my wsdl file is defined
<xs:element name="authInfo" type="<b>xx:AuthInfo</b>">                                   <xs:annotation>                              <xs:documentation xml:lang="en">                                   Authentication information                         </xs:documentation>                    </xs:annotation>                              </xs:element>
and in my xsd file for xx:AuthInfo
<xs:complexType name="AuthInfo">
          <xs:sequence>
               <xs:element name="acctName" type="tns:CustName">
                    <xs:annotation>
                         <xs:documentation xml:lang="en">
                         account name.
                    </xs:documentation>
                    </xs:annotation>
               </xs:element>
               <xs:element name="password" type="tns:AcctPswd">
                    <xs:annotation>
                         <xs:documentation xml:lang="en">
                        Specify the password                    </xs:documentation>
                    </xs:annotation>
               </xs:element>
          </xs:sequence>
     </xs:complexType>
when i import wsdl file in Ed i will get two inputs there but only one as "AuthInfo"
but "AuthInfo" has two inputs.
this is how my Target Message Look like
Tree          Occurences          Type
authInfo     1..1                      xx:AuthInfo
i hope i have cleared u..

PeopleSoft Import WSDL utility fails for BPELs deloyed on linux server?

We have installed Oracle AS 10.1.2 on a LINUX server and deployed few BPELs there. I am trying to import BPEL in PeopleSoft Financials 8.8 using Integration Broker Import WSDL utility.
Its throwing following error message
java.lang.StringIndexOutOfBoundsException: String index out of range: -7
     at java.lang.String.substring(String.java:1480)
     at psft.pt8.pshttp.PSHttp.getCookies(PSHttp.java:455)
     at com.peoplesoft.pt.integrationgateway.targetconnector.HttpTargetConnector.send(HttpTargetConnector.java:383)
     at com.peoplesoft.pt.integrationgateway.service.BasicConnectorInvocator.execute(BasicConnectorInvocator.java:120)
     at com.peoplesoft.pt.integrationgateway.framework.GatewayManager.invokeService(GatewayManager.java:130)
     at com.peoplesoft.pt.integrationgateway.framework.GatewayManager.manageRequest(GatewayManager.java:286)
     at com.peoplesoft.pt.integrationgateway.framework.GatewayManager.connect(GatewayManager.java:211)
     at com.peoplesoft.pt.integrationgateway.listeningconnector.PeopleSoftListeningConnector.doPost(PeopleSoftListeningConnector.java:123)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:971)
     at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:402)
     at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:305)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6350)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
     at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3635)
     at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2585)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
and
Request Content could not be retrieved because of Exception:IBRequest:getInfoXMLString(). MessageName is a required field.
But I am able to import java webservice WSDL deployed on same server.
Moreover, I am able to import BPEL WSDLs deployed on a windows m/c.
Can somebody suggest a solution ?

Hi,
This is the B2B forum. Please repost your question to the BPEL forum.
Thanks,
Eng

Way to change the Message based on Imported IDoc

Hi,
I just want to know if there is way to change the message based on Imported IDoc?
Basically I imported an IDoc from R/3, this Imported Object would display just one of the Segment for where there are max allowable limit is n segment (the same segment), now during message mapping I need to have more than one Segment of same type...Wasn't sure how to add more segments?
Thanking in advance

Hi Rajan,
If I have understood you correctly you,you mean that you have imported an Idoc with a segment with cardinality 0..unbounded(n) and you want to reproduce the segment n times in the target structure.
you need not change the cardinality.This needs to be done in the mapping itself.just map the source structure to the target segment, handling the context properly such that for every occurence of the source structure the corresponding segment is produced in the target.
Regards,
Sulakshana

Importing WSDL with external references issue

Hi guys,
pls help me on this:
I have a WSDL file which referes to external data types. Obviously, if I want to create a message mapping I can't see the WSDL data type. How are such situations resolved? How to import external types into PI?
Thx, A.

HI,
You have to inport the WSDL alongwith all its external references.
You can refer the following threads:
Import WSDL with external reference
Re: PI 7.1: Importing a wsdl file with references to other xsd files
http://help.sap.com/saphelp_nwesrce/helpdata/en/26/9e97b0f525d743882936c2d6f375c7/content.htm

Import WSDL in WLW

Hello,
Does WLW not support importing WSDL as a URL ? It looks like I have to save the
WSDL file locally and import it.
Thanks
Sara

One way is the following:
Right-click > new Java Control > Select Web Service > Name the control >
Next > Give the URI / URL
"sara" <[email protected]> wrote in message
news:3f7c6e10$[email protected]..
>
>
Hello,
Does WLW not support importing WSDL as a URL ? It looks like I have tosave the
WSDL file locally and import it.
Thanks
Sara

My LR 4 suddenly no longer recognized my memory cards. I am using the same cards and cameras but consisitently get the error message:"files not imported because the files could not be read. they are jpg and nef files...I am stuck without my workhorse! Any

My LR 4 suddenly no longer recognized my memory cards. I am using the same cards and cameras but consisitently get the error message:"files not imported because the files could not be read. they are jpg and nef files...I am stuck without my workhorse! Any advice is helpful. This has never happened in 6 years

answered in your other thread LR 4 suddenly no longer recognizes files.

Different message structures on one communication channel

Hello,
we've got the situation where on on single communication channel, we will have multiple message structures. We need to discriminate between them and then handle them according to their structure.
All messages have a header section in which the message type is stored. So I've created a dummy structure:
<ns0:dummy>
<header>
    <message_type></message_type>
</header>
</ns0:dummy>
the actual messges will have a different root element, but you can ignore this by using xpath. So, I've created a sender agremeent with this dummy message as the interface. I have a interface determination with conditions:
/*/header/message_type = MT_A
and receiving interface MT_A. Same for MT_B and so forth. There's no interface mapping in between.
The receiving system now has a receiver agreement with MT_A as the interface. This all works. But in the receiver agreement you set up a communication channel where the message is sent to.
But at this point, MT_A was what the original system sended. All we did was figuring out what message type we're dealing with. Now we need to handle this message as MT_A and using a interface mapping, map it to MT_A_New. We cannot do this in the original receiver determination / interface determination combi, sinse this would mean a message mapping from dummy to something, and we need from MT_A -> MT_A_NEW.
Does anyone have thoughts on how to do this?
Thanx in advance!
Greetings, Walter.

Hello All,
thanks for all your input, it gave me quite a few possible directions to look.
we eventually solved our issue by creating a "generic" structure. It contains the header part (which is the same in structure A and B) and both the A body and B body as optional parts.
now we can make a mapping which only operates on the A part and ignores the B part and also one which does the B part.
<root>
<header>
    <MT></MT>
</header>
<MT_A>
</MT_A>
<MT_B>
   </MT_B>
</root>
we can still define which mapping to use based on the header information. It all seems to work.
Thanks again for all your input!
Greetings, Walter.

Message structure in imported WSDL

Similar Messages

Maybe you are looking for