community-content

Forum Replies Created

Viewing 15 posts - 3,946 through 3,960 (of 9,648 total)
  • Author
    Posts
  • in reply to: BizTalk 2006 Tutorial 3 #20545

    I’ve found that you have to restart some things to get a new promoted property to take effect.  I’ve never had to go as far as restarting the computer, but I usually need to restart the host instance, the BizTalk admin console, and Visual Studio.

    in reply to: BizTalk 2006 Tutorial 3 #20544

    The solution now suddenly seem to work after. I don’t have good explanation for this. All I did this morning was that I restarted my computer.  If anyone experiences the same error as above please consider restarting your computer after you installed the tutorial updates. A restart of the host instant wasn’t enough in my case.

    Have you tried calling the web service with the WCF-BasicHttp adapter?  You shouldn’t get a serialization error using this adapter because it doesn’t have to serialize anything.  You are just sending an XML message.  It is already serialized.  If you use the SOAP adapter and a proxy class,  suspect the proxy class is taking the XML from BizTalk, loading it into an object variable, then trying to serialize it to send it over the wire.  Hence your receive a serialization error.

    That said, object parameters are not the best contract design, so it wouldn’t be a bad idea to get them to type it.  If you really need to accept any XML, then I guess they are a good choice, but usually that is not the case.

     

    I spoke with a former colleague of mine about this issue yesterday. He mentioned that if the “add reference” in a BizTalk project fails that should give a warning signal.  I explained to him how I used wsdl.exe tool to generate a proxy and that the proxy expects an “object” as parameters when invoking the web service. He quickly responded that the problem is that BizTalk can’t just serialize the “object” as the type is unknown. With that said this practically leaves me with the options to convince the exposer of the web service to rewrite the interface to “typed method signature” or rewrite the service.

    //Ershad

    in reply to: Receiving an MDN #20539

    An AS2 receive port should be configured using As2Receive. Are you expecting a synchronous or asynchronous MDN? You can setup both under the party’s AS2 properties. You may need to setup a send port filter using an AS2 context property to get the MDN to be received successfully. Here is a link to the AS2 context properties: http://msdn.microsoft.com/en-us/library/bb226483.aspx. You can use IsAS2MdnResponseMessage==true to get a synchronous MDN and there is a similar boolean, IsAS2AsynchronousMdn, to catch an asynchronous MDN.

    Thanks,

    Its obviously weird that the BizTalk engine is thinking of looking in c:\Windows\System32 for the DTD file. There must be some executable in the System32 folder that will be used for processing the DTD.

    You might try having a send port outbound map be used for adding the DTD DocType line back in.

    Thanks,

    If you have more than one receive location for a single receive port, each one will execute and if one fails the other will still try to receive a message. So the scenario you mention is possible.

    Thanks,

    in reply to: Installation error #20535

    This happens sometimes when the name you are specifying for a BizTalk management database already exists. There are also some other scenarios in which this message could occur. I would look at the right part of the BizTalk configuration wizard window and see if you can find any yellow caution icons or red error icons. These indicate that an item is not specified properly. You can then double click on the icon to get the error or warning message.

    Thanks,

    in reply to: Correlation of messages by using time #20534

    This sounds like a poor way of identifying that the messages are related because there will always be times when the messages cannot be received approximately 3 seconds apart. There must be other characteristics or properties on the messages that indicates to you the messages are related.

    Thanks,

    in reply to: Confirm MDN Receive #20533

    I think you have to configure the BizTalk EDI parties so that you use a synchronous MDN. Then you could have a send port setup with a filter that looks for MDN messages and writes the MDN message out to disk. You would need to have something monitoring the disk location to determine which MDN messages are received. You can setup a send port filter using the AS2 context properties (see http://msdn.microsoft.com/en-us/library/bb226483.aspx for more information on these), and use IsAS2MdnResponseMessage == true as the filter.

    Thanks,

    in reply to: Is there any dummy adapter? #20532

    Thanks nick.  The framework of this adapter is cool, saved a lot of our time.

    in reply to: hi all #20531

     The trick is to do then when creating a new map.  You cannot easily do this to an existing Map.  To do this to an existing map you need to open the MAP up in a XML Editor and manually configure it.  If already have a map then just ‘practice’ on  new map so that you can see the structure and then make those changes to an existing map

    in reply to: Custom Message Tracking #20530

     

     I would suggest taking a look at BAM (Business Activity Monitoring).  BAM will allow you to configure tracking profiles to track specific elements of your data(messages).  So for instance lets say that you have a PO and you have Customer Name, Address, Price etc in your message and you would like to later Report on this information then BAM is a great solution.  You basically configure BAM to track these specific elements and they will be placed into the BAMPrimaryImport database.  From there you get BAM Portal (out of the box).  This is essentially a Web Portal where you can query your BAM repository.  I will admit that BAM lacks in the area of printed reports, it is more an adhoc query tool, but since all of this data is in SQL Server and BizTalk will create the necessary views it is very easy to hook up SQL Reporting Services or even an ASP.Net application to view this info.

    Part of the problem with HAT is that you need to keep your BizTalkDTADb database ‘lean and mean’ in order for optimal performance.  So I would try to avoid any dependencies on this database for long term reporting needs.  The other thing is that unless are querying on promoted properties, HAT wil not give you element level information since your message is essentially stored as a ‘blob’ in the database.

    Here are a couple links to get you started

    http://aspalliance.com/840_Business_Activity_Monitoring_BAM_with_BizTalk_Server_2006_from_Start_to_Finish

    http://msdn.microsoft.com/en-us/library/aa972199.aspx

    in reply to: Is there any dummy adapter? #20529

    Prashant,

    Take a look at the BizTalk Scheduled Task Adapter over on Codeplex – http://www.codeplex.com/BizTalkScheduledTask

    Rgds, Nick.

    in reply to: .NET Assembly vs Web Services #20527

    I appreciate the input, Nick!

    I was hovering over option 1 and wasn’t fully aware of the redirection option so that may have solidifed the argument in my own mind, thanks for that tid-bit.  I do have some WS’s out there simply as adapter solutions for third-party apps, but wasn’t sure if it was feasible for an internal hub for such logic.

    Funny you mention the challenge you’re encountering…I had the same thing here for the longest time until I was able to finally get them to ‘see’ what I can do in BizTalk that actually made their lives that much easier.  It was a hard fought batte, but know that it can be won. 🙂

    Thanks again!
    -Rich

Viewing 15 posts - 3,946 through 3,960 (of 9,648 total)