Web Service Publishing Wizard & Simple Types

Home Page › Forums › BizTalk 2004 – BizTalk 2010 › Web Service Publishing Wizard & Simple Types

Viewing 1 reply thread
  • Author
    Posts
    • February 4, 2009 at 5:42 AM #21639
      community-content

        I am having trouble with a partner, who wants to post XML invoices to a Web Service.  I have used the BizTalk Web Services Publishing Wizard to expose an Orchestration as a WS.  Problem is my partner, cannot use the WS for some reason in his “Remedy” System.  I have had some people who know a great deal more about WS than I look at my BT WS, and the example he sent me on one which works with his system.  We believe that he is expecting Simple Types in the WS, and BizTalk creates Web Services with Complex Types.  That is just our theory as we cannot figure anything else out.   He seems to be ignoring the <wsdl:types> tag, so we believe his system cannot use Complex Types.

        I am able to add the reference to a Dev Box, and do not have any trouble seeing the Doc Definitions, so I do not know what else to do.  Can BizTalk create a WS like he wants?

         

         His email give me…

        An example of what he wants…

        – <wsdl:message name=”CreateDefectWithAttachmentRequest“>
          <wsdl:part name=”CreatorLoginId“ type=”soapenc:string“ />
          <wsdl:part name=”OwnerType“ type=”soapenc:string“ />
          <wsdl:part name=”OwnerCode“ type=”soapenc:string“ />
          <wsdl:part name=”Remedy_Ticket_Name“ type=”soapenc:string“ />
          <wsdl:part name=”Remedy_Ticket_ID“ type=”soapenc:string“ />
          <wsdl:part name=”Business_User_Login_Name“ type=”soapenc:string“ />
          <wsdl:part name=”Name_Of_The_Business_User“ type=”soapenc:string“ />
          <wsdl:part name=”Business_User_Email_ID“ type=”soapenc:string“ />
          <wsdl:part name=”VIP“ type=”soapenc:string“ />
          <wsdl:part name=”Phone_Number“ type=”soapenc:string“ />
          <wsdl:part name=”Cell_Number“ type=”soapenc:string“ />
          <wsdl:part name=”Department_of_Business_User“ type=”soapenc:string“ />
          <wsdl:part name=”Helpdesk_Person_Name“ type=”soapenc:string“ />
          <wsdl:part name=”Support_Group“ type=”soapenc:string“ />
          <wsdl:part name=”Remedy_Ticket_Description“ type=”soapenc:string“ />
          <wsdl:part name=”Remedy_Ticket_Summary“ type=”soapenc:string“ />
          <wsdl:part name=”Remedy_Ticket_Source“ type=”soapenc:string“ />
          <wsdl:part name=”Category_1“ type=”soapenc:string“ />
          <wsdl:part name=”Category_2“ type=”soapenc:string“ />
          <wsdl:part name=”Category_3“ type=”soapenc:string“ />
          <wsdl:part name=”Priority_Business_User“ type=”soapenc:string“ />
          <wsdl:part name=”Severity_Business_User“ type=”soapenc:string“ />
          <wsdl:part name=”Remedy_Ticket_Status“ type=”soapenc:string“ />
          <wsdl:part name=”Remedy_Ticket_Creation_DateTime“ type=”xsd:dateTime“ />
          <wsdl:part name=”FileName“ type=”soapenc:string“ />
          <wsdl:part name=”AttachmentData“ type=”soapenc:base64Binary“ />
          </wsdl:message>

        Here is my WS…

        –

          <wsdl:part name=”parameters“ element=”tns:PearsonXMLOrder“ />
          </wsdl:message>
          <wsdl:part name=”parameters“ element=”tns:PearsonXMLOrderResponse“ />
          </wsdl:message>

        – <wsdl:message name=”PearsonXMLOrderSoapIn“>– <wsdl:message name=”PearsonXMLOrderSoapOut“>

        His probmel with the WS…

         

                       The <wsdl:message> tag is used for defining operations and In this tag Parameters are also defined. This is a rule for creating operations and defining the parameters for operations.  But in the web service sent by you there is only one operation “Operation_1” having two parameters

         

        1 – Operation_1

        2 – Operation_1Response

         

      • February 4, 2009 at 5:45 AM #21640
        community-content
          – <wsdl:message name=”PearsonXMLOrderSoapIn“>
            <wsdl:part name=”parameters“ element=”tns:PearsonXMLOrder“ />
            </wsdl:message>
          – <wsdl:message name=”PearsonXMLOrderSoapOut“>
            <wsdl:part name=”parameters“ element=”tns:PearsonXMLOrderResponse“ />
            </wsdl:message>
          I think what I sent as my web service got screwed up, lets see if this looks better.
          • February 12, 2009 at 7:38 AM #21718
            community-content

              more from my customer

               

                       I am not able to map the fields of web service with Remedy form as Remedy is not able to see the fields. In SOAP Sonar when you select an operation then it will directly show the fields of the operation for a normal or you can say simple web service. But when you will open your web service then it looks complex it will show “POHeader” and “POLineItems”. And after expending these two it will show you the field names.

               

                       But in normal condition and in case of Remedy, fields are captured directly from the operations. And this is the reason Remedy can not capture the fields as the fields are deep down the sub-branches “POHeader” and “POLineItems”.

               

              How do I do this in BizTalk???

              • February 27, 2009 at 7:12 AM #21801
                community-content

                  With some help from a few guys on the BMC Remedy forum, I think I may have found the issue, now I have to figure out how to make BizTalk create a WS that does not use references.

                  The guy that helped me said he replaced the ref=”s1:PORequest” with the actual elements from the reference, and the fields populated in his sytem.  Should I manually modify my .asmx like he did, or is there a way for BizTalk to create this with using the references?

                   

                  <wsdl:types>

                  – <s:schema elementFormDefault=”qualified“ targetNamespace=http://edidev4.mycompany.com>
                    <s:import namespace=”http://Pearson_Inbound_XML_Orders“ />
                    <s:import namespace=”http://Pearson_Inbound_XML_Orders2“ />
                  – <s:element name=”PearsonXMLOrder“>
                  – <s:complexType>
                  – <s:sequence>
                    <s:element minOccurs=”0“ maxOccurs=”1“ ref=”s1:PORequest“ />
                    </s:sequence>
                    </s:complexType>
                    </s:element>
                  + <s:element name=”PearsonXMLOrderResponse“>
                  – <s:complexType>
                  – <s:sequence>
                    <s:element minOccurs=”0“ maxOccurs=”1“ ref=”s2:POResponse“ />
                    </s:sequence>
                    </s:complexType>
                    </s:element>
                  + <s:element name=”PearsonXMLOrder2“>
                  – <s:complexType>
                  – <s:sequence>
                    <s:element minOccurs=”0“ maxOccurs=”1“ ref=”s3:PORequest“ />
                    </s:sequence>
                    </s:complexType>
                    </s:element>
                  + <s:element name=”PearsonXMLOrder2Response“>
                  – <s:complexType>
                  – <s:sequence>
                    <s:element minOccurs=”0“ maxOccurs=”1“ ref=”s4:POResponse“ />
                    </s:sequence>
                    </s:complexType>
                    </s:element>
                    </s:schema>
                  – <s:schema elementFormDefault=”qualified“ targetNamespace=”http://Pearson_Inbound_XML_Orders“>
                  – <s:element name=”PORequest“>
                  – <s:complexType>
                  – <s:sequence>
                  – <s:element minOccurs=”0“ maxOccurs=”1“ form=”unqualified“ name=”POHeader“>
                  – <s:complexType>
                  – <s:sequence>
                  – <s:element minOccurs=”0“ maxOccurs=”1“ form=”unqualified“ name=”ReqType“>
                  – <s:complexType>
                  – <s:sequence>
                    <s:element minOccurs=”0“ maxOccurs=”1“ form=”unqualified“ name=”ReqTypeCode“ type=”s:string“ />
                    <s:element minOccurs=”0“ maxOccurs=”1“ form=”unqualified“ name=”ReqTypeDesc“ type=”s:string“ />
                    </s:sequence>
                    </s:complexType>
          • Author
            Posts
          Viewing 1 reply thread
          • The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.