Forum Replies Created
-
AuthorPosts
-
May 28, 2009 at 8:24 PM in reply to: SQL Adapter – returning only the first response….not returning all responses #22524
Então e ires levar na bufa, oh meu granda paniscas ?
Hi Alex,
When you have large message, obviously it will take longer to process the message, hence occupy more CPU cycle and impact biztalk server performance. If you have a large batch size with large messages, the impact to biztalk server performance will be enormous.
The reason there’s more round trip to database when batch size is smaller is as follow: assuming you have 100 messages that need to be processed. If normal batch size is 20 messages, only 5 round trips to the database (MessageBox) is required in order to process all 100 messages. However, if the batch size is only 10 messages, it will need 10 round trips to the database (MessageBox) is required in order to process all 100 messages.
I hope this answers your questions.
I’ve gone through this problem and the solution is placing data into the trailer block this will cause the assembler to automatically place the end text block tag.
It seems to me that the technical explaination to this is that the end text block tag is placed as a tag into the parent node of the trailer block, that’s what I saw when I checked the XSD code of the messages.
Regards…
Ahmed Zakaria
Hi there!
Try the following syntax to set a value:
xpath(Msg_Message, “//*[1]/*[local-name() = ‘Header’]/*[local-name() = ‘Value’]”) = varValue;
Or the following syntax to get a value:
varValue = xpath(Msg_Message, “string(//*[1]/*[local-name() = ‘Header’]/*[local-name() = ‘Value’]/text())”);
//Niklas
Custom pipelines can be overkill as per instance configuration allows you to change the pipeline component properties without rebuilding your application. Although this is not available with Biztalk 2004.
In fact I usually build a project with a Flat File Receive pipeline and Flat File Send pipeline and deploy these in a common application that can be shared. When needed I use my standard FF Receive pipeline and specify the DocumentSpec via the Admin Console.
The Xml Receive pipeline contains the Xml Disassebler. This identifies the message type, using root node name and namespace from the incoming message and matches this to a deployed schema. If the schema is an envelope it will debatch the message and propagate the child messages. It uses the schema to determine which properties to promote and distinguished fields to write to the message context. it can also validate the message against the schema if you turn this option on.
The XmlTransmit pipeline contains the Xml Assembler. This is required if you are using envelopes and need to wrap a message in an envelope. You can’t aggregate child messages into an envelope, only a single message so this function is not used much.
You also need the XmlTransmit pipeline if you wish to demote property values back into the message you are sending.
You can also mess around with processing instructions in the Xml document, – you might need this with InfoPath forms which rely on processing instructions.May 28, 2009 at 12:04 AM in reply to: how to take arguments from a web page to uze them in an orchestration? #22518Well yes.
There are three steps to this:
- Create an request/response-orchestration where you trigger on reciving a message containg the data you want to pass to it.
- Publish this orchestration using the BizTalk Web Services Publishing Wizard. http://technet.microsoft.com/en-us/library/aa578703.aspx
- Consume the web-service from your web page. http://msdn.microsoft.com/en-us/library/t745kdsh.aspx
//Niklas
Hi Tony!
For starters, when you say “Xml Write” I’m going to assume you mean Xml Transmit.
– When you receive an Xml message you usually want to validate the message against a schema and let the pipeline set context properties like “MessageType” for subscriptions, when you use passthrough this will not happen.
– But when it comes to flat-files you’ll create your own pipeline, why not in the Xml-case?
– You can (and maybe should) create custom pipelines for xml-messages as well, but you really don’t need to. You see, xml-messages have means of identification (namespace and root-node name) that tells BizTalk what schema (of all the deployed ones) to use for validation. So BizTalk is able to figure this out by itself. Most of the times at least. If you have more than one schema deployed with the same root-name and namespace, BizTalk will get confused and not know which one to use for validation and parsing. Here you either want to set the “DocumentSpecNames”-property of the Default Xml Receive/Transmit pipeline or to create your own custom pipeline to do the (dis-)assembler and validation against your specified schema.
Custom pipelines should allways be considered, though not allways needed. For example, you don’t know when another developer, creating an entirely new solution on “your” BizTalk server decides to deploy a new schema that happens to have the same root-node and namespace as one of your schemas, causing – maybe two years after its release – your solution to stop functioning.
Sorry for the long post. Hope I was clear enough. 🙂
//Niklas Häggström – Connecta AB, Stockholm, Sweden
Hi Nick,
Thanks for the reply.
Let me explain my exact scenario:
We have an SAP ECC Server and a third-party application connected via biztalk. Now we need to connect SAP ECC system with SAP Enterprise Portal via a SAP PI System.
I need to know what would be the disadvantages of using 2 middlewares as mentioned above.
Also any documents you have to support would be appreciated.
Thanks in advance,
Malita
Now, the send port instance is doing something different. It stays active for a while. I was on the phone with the guy while he was printing – he ran a batch through and they printed and he quit printing, however the send port instance in the BizTalk Query Analyzer stayed in the ACTIVE state. Do you have any ideas as to why this would happen? Is it not a big deal?
Zach
The user called and said printing was a bit laggy after making the changes. This is probably because of the retry interval. Normally everything prints right away. So here are my thoughts on the cause of this recent delay. **Please let me know if ordered delivery resolves my hypothesis or not**
The FTP server can have only 1 simultaneous connection. So, if the user sends (this sending is done through a batch process, so multiple label requests exists simultaneously) ..sends print jobs through the batch process, does BizTalk send one file of all the print jobs to the printer, or does each different print job in the batch process exists as a file? If BizTalk sends multiple files, then the first will fail and then the next will now wait 1 minute before retrying.
What is causing this is the FTP server will disconnect the connection after 5 seconds of being IDLE. I changed this to 5 seconds – the default was 5 minutes. So that tells me BizTalk does not disconnect from the FTP after each print request. So, to resolve the user’s problem (at least as far as i know) i’ll have to either change the retry interval back to 0 OR, make BizTalk disconnect from the FTP server after it sends through a print job. So, would that mean I need to edit the SEND port and click ‘Configure’ on the FTP portion and insert a command on the ‘AFTER PUT’ field? I assume if that is the case I would insert the command of ‘quit’ or ‘bye’. Would that make BizTalk disconnect from the FTP server after each print attempt?
Thanks for the help.
Zach
Thank you for the reply. I made the suggested changes. I have also set up a temporary scheduled task to restart the host instances every morning at 3:45 AM. I will pause this. I’d rather not use it anyways because it’s not a permanent solution – but it does keep me from getting called in the AM most of the time.
I’ll keep you posted on the results.
I guess you dont need to put “System.XML”.
I used something similar to this
Declare variable countInvoices – Int type
Then i have to following in the expression shape
val = System.Convert.ToInt32(xpath(MessageName,”count(path of node)”));
Siva
When you queue 20 print requests to a single printer, Biztalk will initiate 20 send port instances which will each attempt to send. The first one will succeed the rest will fail. Each failed port will retry immediately up to 90 times before suspending the message. This is like a machinegun approach to message delivery. Although in your case you have a backup transport which will attempt to send the message but only retry 3 times.
My first suggestion is to set Ordered Delivery on the send port (Advanced options). This will result in a single send port instance sending all the messages (one ftp connection – no errors). I would also set a retry interval to greater than zero. Also probably remove the backup transport – if it doesn’t work the first 90 times having 3 last attempts probably won’t work.
Thanks for the reply. I will try that, however I have my doubts about the FTP server on the printer being the issue – here are my thoughts on that.
Like clockwork, I have to restart the host instances every morning at 4AM. We have a couple of facilities that use the printing method described in my original post. One of the warehouses starts at 5AM EST and we’re on CST, so when they start at 4AM CST, I need to restart the host instances. Once this is done, 99% of the time, the printing will be successful until the next morning at 4AM.
We have our ERP system put the Zebra label files in a Receive folder. Then Biztalk picks them up from this folder, they run through the orchestration and format them into an XML file and send that product to a Send folder. We have send ports for each printer that constanty query that folder looking for an XML file with ‘PRINTERNAME=”myprinter” in the file. Each send port has a filter for their printer name of course.
Now – I don’t think it is the printer. The printers FTP server can only have one simultaneous FTP connection. So, when 20 label files go through basically instantaneously, one prints, 19 fail. Then 1 prints and 18 fail. So on down until they all print. This process is rather quick because each file is about 9KB and prints rather quickly. From the user’s perspective, the printer is going non stop until all labels are printed. There is no wait time. When the problem occurs, the RECEIVE folder gets backed up, meaning that the orchestration has not picked up the file to format it. If the printer FTP was an issue, i’d expect the SEND folder to be full. Also, i can open a dos prompt and ‘ftp open ip’ to the printer and get connected – meaning the FTP connecdtion is not in use. Also, If i am logged into the FTP on the printer, consuming the only active FTP connection to that printer, BizTalk throws errors when printing saying connection refused. I do not get these errors at 4AM.
Unfortunately, I do not see any errors indicating the printing is failing. I find out be either getting a phone call, or checking the RECEIVE folder and it has files in it. The files should go from that folder instantaneously. With that said, there are errors in the application log. For example, we’ll get a
rror: 1 (Field level error)
SegmentID: BIG
Position in TS: 1
Data Element ID: BIG04
Position in Segment: 4
Data Value:
6: Invalid character in data elementor a
A message sent to adapter “FILE” on send port “sprt.DynamicsAX.EDI.Outbound.vendor_name.Parts” with URI “\\server\edi$\4.Outbound\%MessageID%.edi” is suspended.
Error details: Unable to read the stream produced by the pipeline.
Details: Error in serialization
MessageId: {13506294-409B-4393-8BDF-238ADE858F74}
InstanceID: {FC45A184-FAA9-4F44-81BB-6D64CC4127E3}Could those errors cause the printing to fail? I don’t see why. So assuming that is not the problem and since there are no errors in the application log about printing, that leads me to believe perhaps we have unknowingly set this up to do this on purpose. IE – after X minutes of being idle, BizTalk thinks it is done until the host instances are reset.
Let me explain – in the properties of one of the send ports for one of the printers, we have the FTP adapter used with the appropriate information using the XML Transmit Pipeline. On the ‘Transport Advanced Options’ and the ‘BackupTransport’ tabs, there are places for service windows and retry intervals and retry counts. What is the difference between these two? For transport options, we have retry count at 90, retry interval at 0 and priority at 2. On the backup transport tab, we have ‘Type’ as none – retry count at 3 and retry interval at 5. Neither have a service window. I’m not exactly sure what is going to retry 90 times and what will retry 3 times, from the previous example.
Then of course the receive locations have retry properties as well. For ‘Network Failure’ on the receive location for the RECEIVE folder, we have ‘Retry Count’ at 90 and ‘Retry Interval’ at 0. For the advanced settings we have polling interval at 5000ms (5 sec) for ‘Removing of old files’ we have the ‘Retry Count’ at 5, the retry interval at 5000ms and the maximum retry interval at 300,000 ms ( 5 min). So once again, im not sure what will retry 90 times, and what will retry when…
Do you think it is possible the printing is failing because of being incorrectly setup with the retries and etc as described above?
Hello
I have a license for 1 CPU Biztalk 2006 R2.
I can set how many Host instances i want and the only limitation is that i use only one phiscal machine?
I in my solution i have 7 orchestrations that call 7 diferent web services. The web service called returns an untyped message. It is an ideea to set 7 host instances one for each orchestration. and another two for the receive ports and for send ports.
The files returned by webservice can reach 200 mb and they don’t have a fixed structure (xsd schema) (untyped messages).
-
AuthorPosts