Forum Replies Created
-
AuthorPosts
-
Can you explain a little bit more about what you want to do? I’m sure it is possible to write a query that joins across the instances, but there is probably a better way to get the data you need.
This issue seems like it should be addressed at the transport level. Chunked transfer encoding is a perfectly valid transport protocol, so the Java WS is not breaking any rules. I would try using the WCF-BasicHttp adapter to consume the Java WS instead of the SOAP adapter (it’s OK that the WS on the other end of the wire is Java and not WCF). The WCF adapters have many more configuration settings than SOAP, so maybe they can handle chunked transfer. Here is a walkthrough: http://msdn.microsoft.com/en-us/library/bb246019.aspx.
If that doesn’t work, a custom pipeline might do the trick, but the MIME decoder is not the way to do it. A custom decoder pipeline component is probably the way to go. The custom component might contain C# that walks the message data stream and removes the extra hex characters.
I’m able to process EDI without a problem now. EDI processing is setup the same as FILE processing, which is much better than R1. I followed the instructions here and #9 – #12 here to generate a 997 and it doesn’t seem to be working.
There are no errors in the event log, the location where the 997 file is being written is local (no permissions issues), it’s just not being created. Is there something missing from that MSDN article? Is there a flag that needs to be set somewhere to indicate that 997 should be generated?
The first problem is about the Java WS, it is not mine! I’m triying to get that they delete the chunked from their Apache server, it is the best option without any doubt!
I’m thinking in create a pipe that read the response message with a MIME decoder because the exception information is the next:
“Inner exception: The XLANG/s message has no part at index ‘0’. The total number of parts found in the message is ‘0’. If you expect a multipart message, check that the pipeline supports multipart messages such as MIME. “
Perhaps I can use this to get a solution,
I don’t believe you can (however I’m happy to be proved wrong!).
This sounds like a configuration issue with your Java WS that is sending the response – is it possible to re-configure the response message?
Nick.
October 7, 2008 at 4:58 AM in reply to: Error while starting BizTalk Server Application Service in Services.msc #20918Thanks Nickh [:)]
October 7, 2008 at 2:19 AM in reply to: Error while starting BizTalk Server Application Service in Services.msc #20916The 14001 error appears to be a generic error when a windows service fails to start (according to Google at least).
I would suggest you try the following:
- Create a new host instance through the BizTalk Admin Console and attempt to start that – i.e. try and isolate the problem to a specific windows service/Biztalk host instance
- Re-install – not the best option I know, but you should be able to resolve this with a repair of your runtime (this won’t affect your databases).
Rgds, Nick.
Sidhu,
Take a look at the Microsoft.BizTalk.Streaming namespace (http://technet.microsoft.com/en-us/library/microsoft.biztalk.streaming.aspx), specifically the XmlTranslatorStream (http://technet.microsoft.com/en-us/library/microsoft.biztalk.streaming.xmltranslatorstream.aspx).
If you extend this class in a decode pipeline component (for example), you can override the TranslateDocType method and strip the DOCTYPE declaration from the incoming message; its a bit fiddly, but it is possible.
If you want a more low-tech approach, load the Xml Message into a string and remove the DOCTYPE using a find/replace pattern, or stick it through some XSLT that maps back to itself but without the DOCTYPE. Both of these approaches are easily doable, but you will incur a large performance hit with large messages.
Rgds, Nick.
October 6, 2008 at 11:00 AM in reply to: BizTalk orchestration – Accessing request message from Receive Port #20911It does sound like you haven’t promoted your message properties (either as distinguished field or as a promoted (context) property).
There is loads of info on the web re.the two methods so I won’t go into them here, try starting with:
As a general rule of thumb however, promoted (context) properties are used for message subscription (and require a lot more overhead); if you’re not looking to do subscription on your property, go with distinguished.
Kind regards, Nick.
Hmmmmm…….
The install that the blog post talks about was BizTalk 2006 ‘R1’ – I’m wondering whether R2 does things differently (orhas a bug?); unfortunately, I don’t have a spare 64-bit machine to try it out on.
Nick,
Thanks for responding. I’ll check out your blog from last year. To answer your question, no–the installation looks like it all went under x86–the bins that are x64 specific are under the bin path under x86…
October 6, 2008 at 12:00 AM in reply to: BizTalk orchestration – Accessing request message from Receive Port #20907yeah. Need to do Distinguished promte which used in your orchestration expressions for get/set operations aginst your message
Nandika
I haven’t seen any document but when u go to BT administrator console –> Help -> About BT Administrator console, I can see the version # is 3.6.1404.0 which is BizTalk 2006 r2 .
I blogged about a 64-bit install last year (http://www.modhul.com/2007/07/28/biztalk-installation-on-a-64-bit-machine/) and from what I can remember, the installer only installs the 32-bit components in the x86 Program Files folder, but I can’t remember what was contained in that folder – do you have a BizTalk installation in the (non) x86 folder?
Nick.
seems something is crashing your application. look for some special characters in your input file (a hidden one). http://www.editoxml.com
-
AuthorPosts