Forum Replies Created
-
AuthorPosts
-
Hi Ravi,
Please rephrase the description of your processes, I do not quite understand the scenario.
Kind Regards
Martin BringIf you have an example Xml document you can generate a schema from this.
In Visual Studio Biztalk Project, Add, Add Generated Items…, Generate Schemas, Add, Well-Formed XML, select your Xml file, OK.
You may not have the correct schema generator installed but you will get an error message telling you where the VB script is to install the schema generator.
Did you ever figure this out I am getting the same error message?
Please let me know what you figured out
Greg
thanks for the pointer, I’ve got example XML messages, so I’ll have a bash at creating an XSD
Weird that int or string don’t generated the Reference.xsd, as mentioned on this page, http://geekswithblogs.net/evankoch/archive/2007/09/26/115647.aspx
If the method includes something other than primitive data types, there
will also be a Reference.xsd file under Reference.map. After adding
this reference, we’ll be able to create messages to communicate with
the web service defining the type as a Web Message and choosing the
appropriate schema.Thanks, so would it just be a case of creating the Schema to only contain those fields in SQL?
Would you have an example of a stored procedure that I could have a look at please as I have only used the updategrams so far..
Thanks.
Depends. How exactly are you inserting the data into SQL. Are you using an updategram? Are you ecursively calling a stored proc? Are you calling a stored proc once with all the data?
April 22, 2009 at 4:44 AM in reply to: Newbie – Copying the raw receive file to another location before orchestration #22191Mike,
I have a receive pipeline component that I can send you that will archive messages as they are received by BizTalk. The component can be used in either the Receive Decode or ResolveParty stages.
Drop me a line at [email protected] and I will forward you a copy.
Cheers, Nick.
I assume your ordering system is not capable of storing this reference and returning it with the invoice.
One option is to store the reference in the orchestration instance and reuse this orchestration instance to process the invoice. Have a long running orchestration that receives the order, saves the reference in an orchestration variable, sends the order, waits for the invoice (correlating on order number) receives the invoice, injects the order reference and send the invoice.
Otherwise create a SQL table with three columns, order number and order reference. Insert the order number and reference when processing the order When processing the invoice retrieve the order reference using the order number and when the invoice send successfully completes delete the row from the database. Use SQL adapter with three stored procedures to insert, retrieve and delete..
Use dynamic port and in expression shape write something like this:
SendToWcfProxy(Microsoft.XLANGs.BaseTypes.Address) =
AdressS;
SendToWcfProxy(Microsoft.XLANGs.BaseTypes.TransportType) =
“FILE”;April 21, 2009 at 10:25 PM in reply to: Newbie: Flat file input sequence does not match Schema #22186Sure, my email is greg.forsythe at gmail.com
April 21, 2009 at 8:44 PM in reply to: Newbie: Flat file input sequence does not match Schema #22185Hi Greg,
If you are interested, I have a flat file similar to the one above and having lots of trouble creating a schema in biztalk for it. If I could send you through a sample of the flat file do you think you could pass on some help with how to create the schema.
Thanks
April 21, 2009 at 1:10 PM in reply to: How to take leading zeros from a string in BizTalk mapper #22184How about using the Math Add functoid and add zero to this value
You will need to get the Xml schema for the embedded xml from the web service provider. Add this schema to a Biztalk project and deploy.
In an orchestration you will need to parse the Xml using a System.Xml.XmlDocument variable
e.g. xmlDocument.LoadXml(webserviceresponse)Or maybe you could ask the web service provider to not flatten all their structured messages in to strings
Thank you for providing the right direction. I now parse thru using xpath and use position() . I also have the pipeline for FTP transfer. but am struck at one point.
After I take each item, i need to transform that order to a format compatible with my pipeline schema. I have the transform in a construct message for this.
This transform results in a empty xml document jus with nodenames and namespace. I can see that the input message to this transform is perfectly correct. Both input and output messages for this transform have the namespaces defines.
Any help appreciated.
Greg,
yeap you’re spot on …. the web service is just returning a string, which is actually XML
WSDL below ….
<?xml version=”1.0″ encoding=”utf-8″?>
<wsdl:definitions xmlns:http=”http://schemas.xmlsoap.org/wsdl/http/” xmlns:soap=”http://schemas.xmlsoap.org/wsdl/soap/” xmlns:s=”http://www.w3.org/2001/XMLSchema” xmlns:soapenc=”http://schemas.xmlsoap.org/soap/encoding/” xmlns:tns=”http://www.aniteps.com/AniteFusionAdapter/” xmlns:tm=”http://microsoft.com/wsdl/mime/textMatching/” xmlns:mime=”http://schemas.xmlsoap.org/wsdl/mime/” targetNamespace=”http://www.aniteps.com/AniteFusionAdapter/” xmlns:wsdl=”http://schemas.xmlsoap.org/wsdl/”>
<wsdl:types>
<s:schema elementFormDefault=”qualified” targetNamespace=”http://www.aniteps.com/AniteFusionAdapter/”>
<s:element name=”AddDocumentType”>
<s:complexType>
<s:sequence>
<s:element minOccurs=”0″ maxOccurs=”1″ name=”XML” type=”s:string” />
</s:sequence>
</s:complexType>
</s:element>
<s:element name=”AddDocumentTypeResponse”>
<s:complexType>
<s:sequence>
<s:element minOccurs=”0″ maxOccurs=”1″ name=”AddDocumentTypeResult” type=”s:string” />
</s:sequence>
</s:complexType>
</s:element>
<s:element name=”CopyFileSystem”>
<s:complexType>
<s:sequence>
<s:element minOccurs=”0″ maxOccurs=”1″ name=”XML” type=”s:string” />
</s:sequence>
</s:complexType>
</s:element>
<s:element name=”CopyFileSystemResponse”>
<s:complexType>
<s:sequence>
<s:element minOccurs=”0″ maxOccurs=”1″ name=”CopyFileSystemResult” type=”s:string” />
</s:sequence>
</s:complexType>
</s:element>
<s:element name=”DocumentSearchFullDetail”>
<s:complexType>
<s:sequence>
<s:element minOccurs=”0″ maxOccurs=”1″ name=”XML” type=”s:string” />
</s:sequence>
</s:complexType>
</s:element>
<s:element name=”DocumentSearchFullDetailResponse”>
<s:complexType>
<s:sequence>
<s:element minOccurs=”0″ maxOccurs=”1″ name=”DocumentSearchFullDetailResult” type=”s:string” />
</s:sequence>
</s:complexType>
</s:element>
<s:element name=”DocumentSearchByUDR”>
<s:complexType>
<s:sequence>
<s:element minOccurs=”0″ maxOccurs=”1″ name=”XML” type=”s:string” />
</s:sequence>
</s:complexType>
</s:element>
<s:element name=”DocumentSearchByUDRResponse”>
<s:complexType>
<s:sequence>
<s:element minOccurs=”0″ maxOccurs=”1″ name=”DocumentSearchByUDRResult” type=”s:string” />
</s:sequence>
</s:complexType>
</s:element>
<s:element name=”Folder1Maintenance”>
<s:complexType>
<s:sequence>
<s:element minOccurs=”0″ maxOccurs=”1″ name=”XML” type=”s:string” />
</s:sequence>
</s:complexType>
</s:element>
<s:element name=”Folder1MaintenanceResponse”>
<s:complexType>
<s:sequence>
<s:element minOccurs=”0″ maxOccurs=”1″ name=”Folder1MaintenanceResult” type=”s:string” />
</s:sequence>
</s:complexType>
</s:element>
<s:element name=”Folder1MaintenanceMultiFS”>
<s:complexType>
<s:sequence>
<s:element minOccurs=”0″ maxOccurs=”1″ name=”XML” type=”s:string” />
</s:sequence>
</s:complexType>
</s:element>
<s:element name=”Folder1MaintenanceMultiFSResponse”>
<s:complexType>
<s:sequence>
<s:element minOccurs=”0″ maxOccurs=”1″ name=”Folder1MaintenanceMultiFSResult” type=”s:string” />
</s:sequence>
</s:complexType>
</s:element>
<s:element name=”Folder2Maintenance”>
<s:complexType>
<s:sequence>
<s:element minOccurs=”0″ maxOccurs=”1″ name=”XML” type=”s:string” />
</s:sequence>
</s:complexType>
</s:element>
<s:element name=”Folder2MaintenanceResponse”>
<s:complexType>
<s:sequence>
<s:element minOccurs=”0″ maxOccurs=”1″ name=”Folder2MaintenanceResult” type=”s:string” />
</s:sequence>
</s:complexType>
</s:element>
<s:element name=”Folder2MaintenanceMultiFS”>
<s:complexType>
<s:sequence>
<s:element minOccurs=”0″ maxOccurs=”1″ name=”XML” type=”s:string” />
</s:sequence>
</s:complexType>
</s:element>
<s:element name=”Folder2MaintenanceMultiFSResponse”>
<s:complexType>
<s:sequence>
<s:element minOccurs=”0″ maxOccurs=”1″ name=”Folder2MaintenanceMultiFSResult” type=”s:string” />
</s:sequence>
</s:complexType>
</s:element>
<s:element name=”Folder3Maintenance”>
<s:complexType>
<s:sequence>
<s:element minOccurs=”0″ maxOccurs=”1″ name=”XML” type=”s:string” />
</s:sequence>
</s:complexType>
</s:element>
<s:element name=”Folder3MaintenanceResponse”>
<s:complexType>
<s:sequence>
<s:element minOccurs=”0″ maxOccurs=”1″ name=”Folder3MaintenanceResult” type=”s:string” />
</s:sequence>
</s:complexType>
</s:element>
<s:element name=”Folder3MaintenanceMultiFS”>
<s:complexType>
<s:sequence>
<s:element minOccurs=”0″ maxOccurs=”1″ name=”XML” type=”s:string” />
</s:sequence>
</s:complexType>
</s:element>
<s:element name=”Folder3MaintenanceMultiFSResponse”>
<s:complexType>
<s:sequence>
<s:element minOccurs=”0″ maxOccurs=”1″ name=”Folder3MaintenanceMultiFSResult” type=”s:string” />
</s:sequence>
</s:complexType>
</s:element>
<s:element name=”ImportIndexDocument”>
<s:complexType>
<s:sequence>
<s:element minOccurs=”0″ maxOccurs=”1″ name=”XML” type=”s:string” />
</s:sequence>
</s:complexType>
</s:element>
<s:element name=”ImportIndexDocumentResponse”>
<s:complexType>
<s:sequence>
<s:element minOccurs=”0″ maxOccurs=”1″ name=”ImportIndexDocumentResult” type=”s:string” />
</s:sequence>
</s:complexType>
</s:element>
<s:element name=”UserMaintenance”>
<s:complexType>
<s:sequence>
<s:element minOccurs=”0″ maxOccurs=”1″ name=”XML” type=”s:string” />
</s:sequence>
</s:complexType>
</s:element>
<s:element name=”UserMaintenanceResponse”>
<s:complexType>
<s:sequence>
<s:element minOccurs=”0″ maxOccurs=”1″ name=”UserMaintenanceResult” type=”s:string” />
</s:sequence>
</s:complexType>
</s:element>
<s:element name=”UserMaintenanceMultiFS”>
<s:complexType>
<s:sequence>
<s:element minOccurs=”0″ maxOccurs=”1″ name=”XML” type=”s:string” />
</s:sequence>
</s:complexType>
</s:element>
<s:element name=”UserMaintenanceMultiFSResponse”>
<s:complexType>
<s:sequence>
<s:element minOccurs=”0″ maxOccurs=”1″ name=”UserMaintenanceMultiFSResult” type=”s:string” />
</s:sequence>
</s:complexType>
</s:element>
<s:element name=”Test”>
<s:complexType>
<s:sequence>
<s:element minOccurs=”0″ maxOccurs=”1″ name=”XML” type=”s:string” />
</s:sequence>
</s:complexType>
</s:element>
<s:element name=”TestResponse”>
<s:complexType>
<s:sequence>
<s:element minOccurs=”0″ maxOccurs=”1″ name=”TestResult” type=”s:string” />
</s:sequence>
</s:complexType>
</s:element>
<s:element name=”OutstandingDocCount”>
<s:complexType>
<s:sequence>
<s:element minOccurs=”0″ maxOccurs=”1″ name=”XML” type=”s:string” />
</s:sequence>
</s:complexType>
</s:element>
<s:element name=”OutstandingDocCountResponse”>
<s:complexType>
<s:sequence>
<s:element minOccurs=”0″ maxOccurs=”1″ name=”OutstandingDocCountResult” type=”s:string” />
</s:sequence>
</s:complexType>
</s:element>
<s:element name=”OutstandingDocDetails”>
<s:complexType>
<s:sequence>
<s:element minOccurs=”0″ maxOccurs=”1″ name=”XML” type=”s:string” />
</s:sequence>
</s:complexType>
</s:element>
<s:element name=”OutstandingDocDetailsResponse”>
<s:complexType>
<s:sequence>
<s:element minOccurs=”0″ maxOccurs=”1″ name=”OutstandingDocDetailsResult” type=”s:string” />
</s:sequence>
</s:complexType>
</s:element>
</s:schema>
</wsdl:types>
<wsdl:message name=”AddDocumentTypeSoapIn”>
<wsdl:part name=”parameters” element=”tns:AddDocumentType” />
</wsdl:message>
<wsdl:message name=”AddDocumentTypeSoapOut”>
<wsdl:part name=”parameters” element=”tns:AddDocumentTypeResponse” />
</wsdl:message>
<wsdl:message name=”CopyFileSystemSoapIn”>
<wsdl:part name=”parameters” element=”tns:CopyFileSystem” />
</wsdl:message>
<wsdl:message name=”CopyFileSystemSoapOut”>
<wsdl:part name=”parameters” element=”tns:CopyFileSystemResponse” />
</wsdl:message>
<wsdl:message name=”DocumentSearchFullDetailSoapIn”>
<wsdl:part name=”parameters” element=”tns:DocumentSearchFullDetail” />
</wsdl:message>
<wsdl:message name=”DocumentSearchFullDetailSoapOut”>
<wsdl:part name=”parameters” element=”tns:DocumentSearchFullDetailResponse” />
</wsdl:message>
<wsdl:message name=”DocumentSearchByUDRSoapIn”>
<wsdl:part name=”parameters” element=”tns:DocumentSearchByUDR” />
</wsdl:message>
<wsdl:message name=”DocumentSearchByUDRSoapOut”>
<wsdl:part name=”parameters” element=”tns:DocumentSearchByUDRResponse” />
</wsdl:message>
<wsdl:message name=”Folder1MaintenanceSoapIn”>
<wsdl:part name=”parameters” element=”tns:Folder1Maintenance” />
</wsdl:message>
<wsdl:message name=”Folder1MaintenanceSoapOut”>
<wsdl:part name=”parameters” element=”tns:Folder1MaintenanceResponse” />
</wsdl:message>
<wsdl:message name=”Folder1MaintenanceMultiFSSoapIn”>
<wsdl:part name=”parameters” element=”tns:Folder1MaintenanceMultiFS” />
</wsdl:message>
<wsdl:message name=”Folder1MaintenanceMultiFSSoapOut”>
<wsdl:part name=”parameters” element=”tns:Folder1MaintenanceMultiFSResponse” />
</wsdl:message>
<wsdl:message name=”Folder2MaintenanceSoapIn”>
<wsdl:part name=”parameters” element=”tns:Folder2Maintenance” />
</wsdl:message>
<wsdl:message name=”Folder2MaintenanceSoapOut”>
<wsdl:part name=”parameters” element=”tns:Folder2MaintenanceResponse” />
</wsdl:message>
<wsdl:message name=”Folder2MaintenanceMultiFSSoapIn”>
<wsdl:part name=”parameters” element=”tns:Folder2MaintenanceMultiFS” />
</wsdl:message>
<wsdl:message name=”Folder2MaintenanceMultiFSSoapOut”>
<wsdl:part name=”parameters” element=”tns:Folder2MaintenanceMultiFSResponse” />
</wsdl:message>
<wsdl:message name=”Folder3MaintenanceSoapIn”>
<wsdl:part name=”parameters” element=”tns:Folder3Maintenance” />
</wsdl:message>
<wsdl:message name=”Folder3MaintenanceSoapOut”>
<wsdl:part name=”parameters” element=”tns:Folder3MaintenanceResponse” />
</wsdl:message>
<wsdl:message name=”Folder3MaintenanceMultiFSSoapIn”>
<wsdl:part name=”parameters” element=”tns:Folder3MaintenanceMultiFS” />
</wsdl:message>
<wsdl:message name=”Folder3MaintenanceMultiFSSoapOut”>
<wsdl:part name=”parameters” element=”tns:Folder3MaintenanceMultiFSResponse” />
</wsdl:message>
<wsdl:message name=”ImportIndexDocumentSoapIn”>
<wsdl:part name=”parameters” element=”tns:ImportIndexDocument” />
</wsdl:message>
<wsdl:message name=”ImportIndexDocumentSoapOut”>
<wsdl:part name=”parameters” element=”tns:ImportIndexDocumentResponse” />
</wsdl:message>
<wsdl:message name=”UserMaintenanceSoapIn”>
<wsdl:part name=”parameters” element=”tns:UserMaintenance” />
</wsdl:message>
<wsdl:message name=”UserMaintenanceSoapOut”>
<wsdl:part name=”parameters” element=”tns:UserMaintenanceResponse” />
</wsdl:message>
<wsdl:message name=”UserMaintenanceMultiFSSoapIn”>
<wsdl:part name=”parameters” element=”tns:UserMaintenanceMultiFS” />
</wsdl:message>
<wsdl:message name=”UserMaintenanceMultiFSSoapOut”>
<wsdl:part name=”parameters” element=”tns:UserMaintenanceMultiFSResponse” />
</wsdl:message>
<wsdl:message name=”TestSoapIn”>
<wsdl:part name=”parameters” element=”tns:Test” />
</wsdl:message>
<wsdl:message name=”TestSoapOut”>
<wsdl:part name=”parameters” element=”tns:TestResponse” />
</wsdl:message>
<wsdl:message name=”OutstandingDocCountSoapIn”>
<wsdl:part name=”parameters” element=”tns:OutstandingDocCount” />
</wsdl:message>
<wsdl:message name=”OutstandingDocCountSoapOut”>
<wsdl:part name=”parameters” element=”tns:OutstandingDocCountResponse” />
</wsdl:message>
<wsdl:message name=”OutstandingDocDetailsSoapIn”>
<wsdl:part name=”parameters” element=”tns:OutstandingDocDetails” />
</wsdl:message>
<wsdl:message name=”OutstandingDocDetailsSoapOut”>
<wsdl:part name=”parameters” element=”tns:OutstandingDocDetailsResponse” />
</wsdl:message>
<wsdl:portType name=”AdapterSoap”>
<wsdl:operation name=”AddDocumentType”>
<documentation xmlns=”http://schemas.xmlsoap.org/wsdl/”>Allows the addition of Anite@Work Document Types.</documentation>
<wsdl:input message=”tns:AddDocumentTypeSoapIn” />
<wsdl:output message=”tns:AddDocumentTypeSoapOut” />
</wsdl:operation>
<wsdl:operation name=”CopyFileSystem”>
<documentation xmlns=”http://schemas.xmlsoap.org/wsdl/”>Allows the creation of a File System based on an existing File System.</documentation>
<wsdl:input message=”tns:CopyFileSystemSoapIn” />
<wsdl:output message=”tns:CopyFileSystemSoapOut” />
</wsdl:operation>
<wsdl:operation name=”DocumentSearchFullDetail”>
<documentation xmlns=”http://schemas.xmlsoap.org/wsdl/”>Allows searching and retrieval of information appertaining to a Document.</documentation>
<wsdl:input message=”tns:DocumentSearchFullDetailSoapIn” />
<wsdl:output message=”tns:DocumentSearchFullDetailSoapOut” />
</wsdl:operation>
<wsdl:operation name=”DocumentSearchByUDR”>
<documentation xmlns=”http://schemas.xmlsoap.org/wsdl/”>Allows searching and retrieval of a document by the unique document reference.</documentation>
<wsdl:input message=”tns:DocumentSearchByUDRSoapIn” />
<wsdl:output message=”tns:DocumentSearchByUDRSoapOut” />
</wsdl:operation>
<wsdl:operation name=”Folder1Maintenance”>
<documentation xmlns=”http://schemas.xmlsoap.org/wsdl/”>Allows the addition or update of Folder1 References.</documentation>
<wsdl:input message=”tns:Folder1MaintenanceSoapIn” />
<wsdl:output message=”tns:Folder1MaintenanceSoapOut” />
</wsdl:operation>
<wsdl:operation name=”Folder1MaintenanceMultiFS”>
<documentation xmlns=”http://schemas.xmlsoap.org/wsdl/”>Allows the addition or update of Folder1 References across multiple file systems.</documentation>
<wsdl:input message=”tns:Folder1MaintenanceMultiFSSoapIn” />
<wsdl:output message=”tns:Folder1MaintenanceMultiFSSoapOut” />
</wsdl:operation>
<wsdl:operation name=”Folder2Maintenance”>
<documentation xmlns=”http://schemas.xmlsoap.org/wsdl/”>Allows the addition or update of Folder2 References.</documentation>
<wsdl:input message=”tns:Folder2MaintenanceSoapIn” />
<wsdl:output message=”tns:Folder2MaintenanceSoapOut” />
</wsdl:operation>
<wsdl:operation name=”Folder2MaintenanceMultiFS”>
<documentation xmlns=”http://schemas.xmlsoap.org/wsdl/”>Allows the addition or update of Folder2 References across multiple file systems.</documentation>
<wsdl:input message=”tns:Folder2MaintenanceMultiFSSoapIn” />
<wsdl:output message=”tns:Folder2MaintenanceMultiFSSoapOut” />
</wsdl:operation>
<wsdl:operation name=”Folder3Maintenance”>
<documentation xmlns=”http://schemas.xmlsoap.org/wsdl/”>Allows the addition or update of Folder3 References.</documentation>
<wsdl:input message=”tns:Folder3MaintenanceSoapIn” />
<wsdl:output message=”tns:Folder3MaintenanceSoapOut” />
</wsdl:operation>
<wsdl:operation name=”Folder3MaintenanceMultiFS”>
<documentation xmlns=”http://schemas.xmlsoap.org/wsdl/”>Allows the addition or update of Folder3 References across multiple file systems.</documentation>
<wsdl:input message=”tns:Folder3MaintenanceMultiFSSoapIn” />
<wsdl:output message=”tns:Folder3MaintenanceMultiFSSoapOut” />
</wsdl:operation>
<wsdl:operation name=”ImportIndexDocument”>
<documentation xmlns=”http://schemas.xmlsoap.org/wsdl/”>Allows the importation and indexing of Documents.</documentation>
<wsdl:input message=”tns:ImportIndexDocumentSoapIn” />
<wsdl:output message=”tns:ImportIndexDocumentSoapOut” />
</wsdl:operation>
<wsdl:operation name=”UserMaintenance”>
<documentation xmlns=”http://schemas.xmlsoap.org/wsdl/”>Allows the addition or update of a Users.</documentation>
<wsdl:input message=”tns:UserMaintenanceSoapIn” />
<wsdl:output message=”tns:UserMaintenanceSoapOut” />
</wsdl:operation>
<wsdl:operation name=”UserMaintenanceMultiFS”>
<documentation xmlns=”http://schemas.xmlsoap.org/wsdl/”>Allows the addition or update of a Users across multiple file systems.</documentation>
<wsdl:input message=”tns:UserMaintenanceMultiFSSoapIn” />
<wsdl:output message=”tns:UserMaintenanceMultiFSSoapOut” />
</wsdl:operation>
<wsdl:operation name=”Test”>
<documentation xmlns=”http://schemas.xmlsoap.org/wsdl/”>Allows a client to test Web Service connectivity.</documentation>
<wsdl:input message=”tns:TestSoapIn” />
<wsdl:output message=”tns:TestSoapOut” />
</wsdl:operation>
<wsdl:operation name=”OutstandingDocCount”>
<documentation xmlns=”http://schemas.xmlsoap.org/wsdl/”>Count of Outstanding documents based on the search criteria.</documentation>
<wsdl:input message=”tns:OutstandingDocCountSoapIn” />
<wsdl:output message=”tns:OutstandingDocCountSoapOut” />
</wsdl:operation>
<wsdl:operation name=”OutstandingDocDetails”>
<documentation xmlns=”http://schemas.xmlsoap.org/wsdl/”>Outstanding documents based on the search criteria.</documentation>
<wsdl:input message=”tns:OutstandingDocDetailsSoapIn” />
<wsdl:output message=”tns:OutstandingDocDetailsSoapOut” />
</wsdl:operation>
</wsdl:portType>
<wsdl:binding name=”AdapterSoap” type=”tns:AdapterSoap”>
<soap:binding transport=”http://schemas.xmlsoap.org/soap/http” style=”document” />
<wsdl:operation name=”AddDocumentType”>
<soap:operation soapAction=”http://www.aniteps.com/AniteFusionAdapter/AddDocumentType” style=”document” />
<wsdl:input>
<soap:body use=”literal” />
</wsdl:input>
<wsdl:output>
<soap:body use=”literal” />
</wsdl:output>
</wsdl:operation>
<wsdl:operation name=”CopyFileSystem”>
<soap:operation soapAction=”http://www.aniteps.com/AniteFusionAdapter/CopyFileSystem” style=”document” />
<wsdl:input>
<soap:body use=”literal” />
</wsdl:input>
<wsdl:output>
<soap:body use=”literal” />
</wsdl:output>
</wsdl:operation>
<wsdl:operation name=”DocumentSearchFullDetail”>
<soap:operation soapAction=”http://www.aniteps.com/AniteFusionAdapter/DocumentSearchFullDetail” style=”document” />
<wsdl:input>
<soap:body use=”literal” />
</wsdl:input>
<wsdl:output>
<soap:body use=”literal” />
</wsdl:output>
</wsdl:operation>
<wsdl:operation name=”DocumentSearchByUDR”>
<soap:operation soapAction=”http://www.aniteps.com/AniteFusionAdapter/DocumentSearchByUDR” style=”document” />
<wsdl:input>
<soap:body use=”literal” />
</wsdl:input>
<wsdl:output>
<soap:body use=”literal” />
</wsdl:output>
</wsdl:operation>
<wsdl:operation name=”Folder1Maintenance”>
<soap:operation soapAction=”http://www.aniteps.com/AniteFusionAdapter/Folder1Maintenance” style=”document” />
<wsdl:input>
<soap:body use=”literal” />
</wsdl:input>
<wsdl:output>
<soap:body use=”literal” />
</wsdl:output>
</wsdl:operation>
<wsdl:operation name=”Folder1MaintenanceMultiFS”>
<soap:operation soapAction=”http://www.aniteps.com/AniteFusionAdapter/Folder1MaintenanceMultiFS” style=”document” />
<wsdl:input>
<soap:body use=”literal” />
</wsdl:input>
<wsdl:output>
<soap:body use=”literal” />
</wsdl:output>
</wsdl:operation>
<wsdl:operation name=”Folder2Maintenance”>
<soap:operation soapAction=”http://www.aniteps.com/AniteFusionAdapter/Folder2Maintenance” style=”document” />
<wsdl:input>
<soap:body use=”literal” />
</wsdl:input>
<wsdl:output>
<soap:body use=”literal” />
</wsdl:output>
</wsdl:operation>
<wsdl:operation name=”Folder2MaintenanceMultiFS”>
<soap:operation soapAction=”http://www.aniteps.com/AniteFusionAdapter/Folder2MaintenanceMultiFS” style=”document” />
<wsdl:input>
<soap:body use=”literal” />
</wsdl:input>
<wsdl:output>
<soap:body use=”literal” />
</wsdl:output>
</wsdl:operation>
<wsdl:operation name=”Folder3Maintenance”>
<soap:operation soapAction=”http://www.aniteps.com/AniteFusionAdapter/Folder3Maintenance” style=”document” />
<wsdl:input>
<soap:body use=”literal” />
</wsdl:input>
<wsdl:output>
<soap:body use=”literal” />
</wsdl:output>
</wsdl:operation>
<wsdl:operation name=”Folder3MaintenanceMultiFS”>
<soap:operation soapAction=”http://www.aniteps.com/AniteFusionAdapter/Folder3MaintenanceMultiFS” style=”document” />
<wsdl:input>
<soap:body use=”literal” />
</wsdl:input>
<wsdl:output>
<soap:body use=”literal” />
</wsdl:output>
</wsdl:operation>
<wsdl:operation name=”ImportIndexDocument”>
<soap:operation soapAction=”http://www.aniteps.com/AniteFusionAdapter/ImportIndexDocument” style=”document” />
<wsdl:input>
<soap:body use=”literal” />
</wsdl:input>
<wsdl:output>
<soap:body use=”literal” />
</wsdl:output>
</wsdl:operation>
<wsdl:operation name=”UserMaintenance”>
<soap:operation soapAction=”http://www.aniteps.com/AniteFusionAdapter/UserMaintenance” style=”document” />
<wsdl:input>
<soap:body use=”literal” />
</wsdl:input>
<wsdl:output>
<soap:body use=”literal” />
</wsdl:output>
</wsdl:operation>
<wsdl:operation name=”UserMaintenanceMultiFS”>
<soap:operation soapAction=”http://www.aniteps.com/AniteFusionAdapter/UserMaintenanceMultiFS” style=”document” />
<wsdl:input>
<soap:body use=”literal” />
</wsdl:input>
<wsdl:output>
<soap:body use=”literal” />
</wsdl:output>
</wsdl:operation>
<wsdl:operation name=”Test”>
<soap:operation soapAction=”http://www.aniteps.com/AniteFusionAdapter/Test” style=”document” />
<wsdl:input>
<soap:body use=”literal” />
</wsdl:input>
<wsdl:output>
<soap:body use=”literal” />
</wsdl:output>
</wsdl:operation>
<wsdl:operation name=”OutstandingDocCount”>
<soap:operation soapAction=”http://www.aniteps.com/AniteFusionAdapter/OutstandingDocCount” style=”document” />
<wsdl:input>
<soap:body use=”literal” />
</wsdl:input>
<wsdl:output>
<soap:body use=”literal” />
</wsdl:output>
</wsdl:operation>
<wsdl:operation name=”OutstandingDocDetails”>
<soap:operation soapAction=”http://www.aniteps.com/AniteFusionAdapter/OutstandingDocDetails” style=”document” />
<wsdl:input>
<soap:body use=”literal” />
</wsdl:input>
<wsdl:output>
<soap:body use=”literal” />
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
<wsdl:service name=”Adapter”>
<documentation xmlns=”http://schemas.xmlsoap.org/wsdl/”>Anite Fusion Adapter.</documentation>
<wsdl:port name=”AdapterSoap” binding=”tns:AdapterSoap”>
<soap:address location=”http://testserver/AniteFusionAdapterTEST/adapter.asmx” />
</wsdl:port>
</wsdl:service>
</wsdl:definitions> -
AuthorPosts