Forum Replies Created
-
AuthorPosts
-
Hi Daniel,
Thanks for your answer. I’m currently using Biztalk 2006, not Biztalk 2006 R2. Maybe I should upgrade to Biztalk 2006 R2, but I prefer not to upgrade at the moment.
Regards,
Bart
November 14, 2009 at 12:40 PM in reply to: Error handling in the biztalk without using the Scope Shape? #23775Hi,
The following BizTalkGurus blog should give you clues towards solving your problem:
Daniel.
Hi Bart,
Check the following BizTalkGurus thread on adding custom Soap header:
http://www.biztalkgurus.com/forums/t/10739.aspx
Basically, you can use WCF-BasicHttp adapter to connect to the web service and do what is described in this MSDN article:
http://msdn.microsoft.com/en-us/library/bb246026(BTS.20).aspx
Hope this helps.
Daniel.
Thank you Daniel! I think is what I needed.
Regards
Diego
Hello BizTalk Experts,
Need your help to solve my issue please.I am positively waiting for solution from one of you.I don’t even have option of raising a ticket to Microsoft for help 🙁 .
Thanks in advance for your kind help.
Regards,
Bhupal.Hello
I have a problem to catch the System.Xml.Schema.XmlSchemaException in the orchestration.
Exception Object Type = System.Xml.Schema.XmlSchemaException
it works only with the Exception Object Type = System.Exception
This excpetion would be seen when there no subscribres for the messages published. It could either an orchestration or send port. Try to create any of it for subscribing the message of that type.
you can even introdcue exception handling with Persistence Exception caught for handling it.
Thanks Daniel.
Expert please share your experience on this …….
One other piece of info. The performance counter “In-process message count” stays at 0 (zero) and the “In-process message count threshold” is set to 1000.
Thanks, but “OH, YEAH” — I’ve been through that page several times.
The question relates more to the throughput and if there is some registry setting that may improve the performance here. There is a good discussion about throttling at http://msdn.microsoft.com/en-us/library/aa559628(BTS.10).aspx but it has not helped in this case.
November 12, 2009 at 12:02 PM in reply to: Flat File Messages Processing Slow in File Adapter #23762Hi JLingenfelder,
Consult the following MSDN article on best practices to increase performance of BizTalk Server in processing large messages:
http://technet.microsoft.com/en-us/library/aa560481(BTS.20).aspx
You probably have done some of the things mentioned in the article, but it’s always good to have another look so as not to overlook any options.
Daniel.
I actually did buy that book. The source schema they use is extremely basic. My scenario involves using Crystal reports to extract the data from the ERP and create a flat file output. I am simply trying to correctly design this source schema so that it is structurally correct to map to the X12 equivalent. And not give me any hangups when implementing the book’s logic for the HL segment.
I dont have a lot of experience with creating schemas and was looking for some guidance in the contruction it and was just wondering if anyone else had created a source flat file that I could borrow ideas from…
Thanks
Below is the WSDL of the web service I am calling to ….
<?
xml version=“1.0“ encoding=“utf-8“?>
<
wsdl:definitions xmlns:soap=“http://schemas.xmlsoap.org/wsdl/soap/“ xmlns:tm=“http://microsoft.com/wsdl/mime/textMatching/“ xmlns:soapenc=“http://schemas.xmlsoap.org/soap/encoding/“ xmlns:mime=“http://schemas.xmlsoap.org/wsdl/mime/“ xmlns:tns=“http://tempuri.org/“ xmlns:s1=“http://ConsureWebService.Order“ xmlns:s=“http://www.w3.org/2001/XMLSchema“ xmlns:soap12=“http://schemas.xmlsoap.org/wsdl/soap12/“ xmlns:http=“http://schemas.xmlsoap.org/wsdl/http/“ targetNamespace=“http://tempuri.org/“ xmlns:wsdl=“http://schemas.xmlsoap.org/wsdl/“>
<
wsdl:documentation xmlns:wsdl=“http://schemas.xmlsoap.org/wsdl/“>BizTalk assembly “ConsureWebService, Version=1.0.0.0, Culture=neutral, PublicKeyToken=e4898e48ff8ecc3e” published web service.</wsdl:documentation>
<
wsdl:types>
<
s:schema elementFormDefault=“qualified“ targetNamespace=“http://tempuri.org/“>
<
s:import namespace=“http://ConsureWebService.Order“ />
<
s:element name=“Operation_1“>
<
s:complexType>
<
s:sequence>
<
s:element minOccurs=“0“ maxOccurs=“1“ ref=“s1:Order“ />
</
s:sequence>
</
s:complexType>
</
s:element>
<
s:element name=“Operation_1Response“>
<
s:complexType>
<
s:sequence>
<
s:element minOccurs=“0“ maxOccurs=“1“ ref=“s1:Order“ />
</
s:sequence>
</
s:complexType>
</
s:element>
</
s:schema>
<
s:schema elementFormDefault=“qualified“ targetNamespace=“http://ConsureWebService.Order“>
<
s:element name=“Order“>
<
s:complexType>
<
s:sequence>
<
s:element minOccurs=“0“ maxOccurs=“1“ form=“unqualified“ name=“OrderId“ type=“s:string“ />
<
s:element minOccurs=“0“ maxOccurs=“1“ form=“unqualified“ name=“OrderName“ type=“s:string“ />
</
s:sequence>
</
s:complexType>
</
s:element>
</
s:schema>
</
wsdl:types>
<
wsdl:message name=“Operation_1SoapIn“>
<
wsdl:part name=“parameters“ element=“tns:Operation_1“ />
</
wsdl:message>
<
wsdl:message name=“Operation_1SoapOut“>
<
wsdl:part name=“parameters“ element=“tns:Operation_1Response“ />
</
wsdl:message>
<
wsdl:portType name=“WebService_ConsureWebServiceSoap“>
<
wsdl:operation name=“Operation_1“>
<
wsdl:input message=“tns:Operation_1SoapIn“ />
<
wsdl:output message=“tns:Operation_1SoapOut“ />
</
wsdl:operation>
</
wsdl:portType>
<
wsdl:binding name=“WebService_ConsureWebServiceSoap“ type=“tns:WebService_ConsureWebServiceSoap“>
<
soap:binding transport=“http://schemas.xmlsoap.org/soap/http“ />
<
wsdl:operation name=“Operation_1“>
<
soap:operation soapAction=“http://tempuri.org/WebService_ConsureWebService/Operation_1“ 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=“WebService_ConsureWebServiceSoap12“ type=“tns:WebService_ConsureWebServiceSoap“>
<
soap12:binding transport=“http://schemas.xmlsoap.org/soap/http“ />
<
wsdl:operation name=“Operation_1“>
<
soap12:operation soapAction=“http://tempuri.org/WebService_ConsureWebService/Operation_1“ style=“document“ />
<
wsdl:input>
<
soap12:body use=“literal“ />
</
wsdl:input>
<
wsdl:output>
<
soap12:body use=“literal“ />
</
wsdl:output>
</
wsdl:operation>
</
wsdl:binding>
<
wsdl:service name=“WebService_ConsureWebService“>
<
wsdl:documentation xmlns:wsdl=“http://schemas.xmlsoap.org/wsdl/“>BizTalk assembly “ConsureWebService, Version=1.0.0.0, Culture=neutral, PublicKeyToken=e4898e48ff8ecc3e” published web service.</wsdl:documentation>
<
wsdl:port name=“WebService_ConsureWebServiceSoap“ binding=“tns:WebService_ConsureWebServiceSoap“>
<
soap:address location=“http://localhost:3693/ConsureWebService_Proxy/WebService_ConsureWebService.asmx“ />
</
wsdl:port>
<
wsdl:port name=“WebService_ConsureWebServiceSoap12“ binding=“tns:WebService_ConsureWebServiceSoap12“>
<
soap12:address location=“http://localhost:3693/ConsureWebService_Proxy/WebService_ConsureWebService.asmx“ />
</
wsdl:port>
</
wsdl:service>
</
wsdl:definitions>
Hi,
It would help if you can publish the contents of your web service’s WSDL to help troubleshoot your problem. I might not be able to answer this, but other gurus might be…
Daniel.
Hi Frank,
Are you referring to the mapping problems related to the HL Loop in the X12 856 Advanced Ship Notice (ASN)? If yes, you might want to read up on this book “Pro Mapping in BizTalk Server 2009” by Jim Dawson and John Wainwright. Here’s a link to an extract of a chapter in that book “Taming the Dreaded 856 ASN HL Loop”:
http://www.springerlink.com/content/tw88798145234125/
I hope this leads to what you are looking for…
Daniel.
-
AuthorPosts