community-content

Forum Replies Created

Viewing 15 posts - 856 through 870 (of 9,648 total)
  • Author
    Posts
  • in reply to: Default Receive Pipeline #25364

    I had similar problem and all i did was remove old assembly from GAC, change assembly version and reploy… all worked  [:)]

    Hi,

    Do you need something like this – http://www.biztalkgurus.com/forums/t/14720.aspx ? In my profile, there’s a sample for download (VS 2008 + BTS 2009 + WCF-SQL adapter sample)

    It works in the same way for SQL adapter too (more or less)

    in reply to: Schedule Question – Receive Location #25361

    Hi Wolfgang,

     

       The start time in the service window only specifies the time the receive location starts polling every day. You set the stop time and the polling interval depending on how many files you expect to receive every day.

     

       Daniel.

     

    in reply to: Flat file not flat #25360

    Hi,

     

       Change the Document Schema property of the Flat File Assembler component in your Send Pipeline to “(None)” and see if that fixes your issue.

    in reply to: BAM Problem Again :-( #25358

    I am also facing the same issue,  please share the solution for this problem..

    in reply to: Property promotion in orchestration #25356

    It sounds like we have done^ we use before a loop by some dummy message which goes to message box, and from there – picked by send port with NullAdapter.

    The purpose of dummy is exactly for promoting. Afer dummy is gone – the loop is running in iterations, and we create n Messages with promoted field.

     

    in reply to: Poll While Data Found #25355

    Hi,

    On MSDN it is explained pretty clear:

    Specifies whether the SQL adapter ignores the polling interval and continuously executes the SQL statement specified for the PolledDataAvailableStatement binding property, if data is available in the table being polled. If no data is available in the table, the adapter reverts to execute the SQL statement at the specified polling interval. Default is false.

    Consider a scenario where the polling interval is set to 60 seconds, and the statement specified for PolledDataAvailableStatement returns that data is available for polling. The adapter then executes the statement specified for the PollingStatement binding property. Assuming that the adapter takes just 10 seconds to execute the polling statement, it will now have to wait for 50 seconds before executing the PolledDataAvailableStatement again, and then subsequently execute the polling statement. Instead, to optimize the performance you can set the PollWhileDataFound binding property to true so that the adapter can start executing the next polling cycle as soon as the previous

    http://msdn.microsoft.com/en-us/library/dd787981(BTS.10).aspx

     

     

     

    in reply to: How to handle response messages you don’t want? #25354

    Hi,

    Maybe you would like to use null adapter? We use it for throwing a dummy message in one of processes (to promote some value in orchestration), and in couple of others – to collect unwanted response messages.

    This adapter is free, simple to install, works with both 32 and 64 bit systems. We use it on Windows server 2008/2003, BizTalk 2009 (it also works with BTS 2010)

    http://winterdom.com/2005/03/biztalk2004nullsendadaptersample

    For installing it – I put the DLL to gac, and run reg file (pay attention that path in reg file is pointing to dll in your file system.)

     

    in reply to: How to handle response messages you don’t want? #25353

    Hi Christophe,

     

       You can interrogate the context of the message (which gets passed to your custom pipeline’s component Execute method), or, if that does not work, you can parse its body part for a pattern that indicates that it is an unwanted message, and if that is found, then return null from the method.

     

       For a sample code of general pipeline component, check the following blog. Please note that for your purpose, you don’t need to rebuild the contents of your message, assign to a memory stream and assign it back to the message body part, as detailed in the example shown by the blog.

    http://blogs.msdn.com/b/brajens/archive/2006/11/25/how-to-develop-biztalk-custom-pipeline-components-part1.aspx

     

       Good luck and let me know how you make out on this.

     

       Daniel.

     

    in reply to: How to handle response messages you don’t want? #25349

    Hi Daniel,

    Thanks for the reply!

    One more question… If we try and build that custom pipeline, how can we discard the messages we don’t want in that pipeline? Would we need to check the message type for example, and if it’s one of those we don’t want, we just don’t process it any further?

    Thanks,
    Christophe

    in reply to: SQl Adapter Questions #25346

    Hi Daniel.

     

    I found the issue … it was a parameter in the properties I had to change.

    I found the solution here: http://www.biztalkgurus.com/forums/p/12800/25176.aspx

     

    Best regards

    Wolfgang

    in reply to: Need Deployment Help #25345

    as I understand, you want to deploy you new app in a UAT server.

    For this, you have to copy the dll of the pipeline in the pipeline folder and Gac the custom functoid.(it’s not necessary to gac the pipeline, because BizTalk Instance check the Pipeline folder), you have to copy the custom functoid in the mapper extensions folder if you want to use the pipeline in VS.

    If the custom pipeline and custom functoid are used only in this solution you can embed this in a MSI package. Before export, go to the ressources of the app.

    Click on Add ressources, then choose you dll:

    • for the pipeline dll, put on destination location %PROGRAMFILES%\Microsoft BizTalk Server 2006 R2\Pipeline Components\NameofYouDll.dll
    • for the functoid dll, check the box add to the global assembly cache on MSI file Install and put on destination location %BTAD_InstallDir%\NameOfYouDll.dll

    Export your msi

    the on the UAT environment, Deployment people have to Import the MSI first and THEN INSTALL the MSI (this step will copy the differents dll on the differents location)

    Restart the hosts and use your application

     

    Hope this help

     

    in reply to: How to handle response messages you don’t want? #25344

    Hi ChristopheT,

     

       Personally, I would keep the current setup that you have. There is no way for BizTalk to simply “ignore” those unwanted response messages.

     

       Another alternative would be for you to build a custom pipeline component (that will discard the unwanted messages) and use it in the Receive pipeline of any Send port where you are making calls to services and expecting (wanted and unwanted) response messages. This is a better way to handle your situation but it’s not the easiest way to implement, in my opinion.

     

       Daniel.

     

    in reply to: How to handle response messages you don’t want? #25343

    Thanks for the reply!

    In fact, we don’t want to do anything with those messages… If it were possible, we would not catch them. But when we don’t have a send port that processes those messages, we end up with errors in the event log.

    Is there a way to “ignore” those messages?

    If not, what is the best way to get easily, rapidely, nicely, … rid of those messages?

    in reply to: How to handle response messages you don’t want? #25341

    Hi,

     

       The question you and your colleagues should be asking yourselves is what do you really want to do with the response messages that are not needed? Do you want to throw them away? Keep and archive them on the file system or a database?

Viewing 15 posts - 856 through 870 (of 9,648 total)