community-content

Forum Replies Created

Viewing 15 posts - 3,826 through 3,840 (of 9,648 total)
  • Author
    Posts
  • in reply to: Passing Nulls to WCF (Published Orch) #20709

     

    One of our ideas was to override the proxy, but I like your idea of putting it in a different location.

    A co-worker is doing a similar project to mine, and surprisingly, he has the “Specified” suffixes on almost all of his fields.  I cannot figure out why he has them and I don’t.  We both have minOccurs=0.  He tried changing a Nillable from false to true, and still has the Specified suffix.

    Another question is how to handle nulls on a retrieval. Suppose we do a getData from a database, and it it has nulls.  How do we get those nulls to deserialize back into C# GUI program (that calls the orch – published as websvc)?

    Thanks,
    Neal

    P.S.  Did Steve do a “tag your it”?  His photo was a dog with it’s tongue hanging out, and now his photo is normal, and your photo is a dog with it’s tongue hanging out.  Hmmmm???

     

    in reply to: Microsoft ESB Guidance #20708

    Well there is BizTalk tracking and HAT, but let’s face it.  Who want’s to use HAT to look up messages?  It’s a painful experience for developers, just think how painful it would be for business users.  You can’t track all messages with the ESB Guidance out-of-the-box.  However, the exception framework does give us some good guidance about how we might build such a tracking solution.  The basics are:

    1. Create an audit XML schema and database.

    2.  Define a context property to indicate a message should be audited (maybe call it “DoAudit”)

    3.  Create a send port that subscribes to DoAudit messages and pushes the message into an auditing database.

    4.  Use custom send pipelines and/or maps to get the message into a good audit format.

    I used this auditing model in my last project and it is working great.

    in reply to: Handling large messages in BizTalk #20707

    If I remember correctly, depending on what you need to do to the message, BizTalk might never load the DOM.  For example, if you used a messaging only solution with passthrough pipelines, the DOM wouldn’t get loaded.  Better performance.  However, if you need to map the message it’s definately getting loaded.  Performance hit.

    in reply to: Microsoft ESB Guidance #20704

     Hi.

    I can now see the faults on my Esb.Portal and the fault table of EsbExceptionDb.

    The problem was that there was a wrong sql server name on the All.Exceptions port on the Microsoft.Practices.ESB.

    What I need to know is: Can we track all the messages that were processed even if they did not have any exceptions?

    in reply to: Microsoft ESB Guidance #20703

     Hi,

    the All.Exceptions is started. On the GlobalBank.ESB, the EAIProcess generates the fault message when the shape tries to divide by zero. I thought that was suppose to show on the esb.portal.

    On my other test orchestration, I do get an exception on on the event viewer when I pass an xml message that does not conform to the specified schema. Is this not suppose to show as one of the fault on my esb.portal. Or even be populated to the fault table of the EsbExceptionDb?

    in reply to: Handling large messages in BizTalk #20702

     Hi ,

    I have experience in handling large messages in BizTalk. It’s really a major performance bottleneck.The performance bottleneck comes into play when the entire file is received, parsed by the XMLReceive pipeline, and then stored into the Messagebox. You can use custom decode pipeline component which will help you to identify the  Biztalk message size & if it exceeds the message limit ( say 50 MB) then store the file to disk in a uniquely named file  and store the path to the file in the IBaseMessagePart.Data property. The end result will be a message that only contains the path.

    Throughout the custome pipeline encoder you can take that large message back in to your process.

    But you need to be careful if you load this large message in to XML DOM . You will get out of memory exception .

    So better way to use XMLReader .

    Let me know if you need more information on this.

     

    Thanks & Best regards,

    Nandika

     

    in reply to: Central Florida BizTalk User Group Started! #20701

     go to http://cfbtug.org for more information

    in reply to: Handling large messages in BizTalk #20699

    I don’t think there is any hard size limit, but you need to be very careful with large messages to avoid performance problems.  I would go ahead and build out the solution using the 200 MB messages, and then performance test it.  If the performance is bad, then one approach is to split the large messages into a bunch of smaller messages so the processing can be distributed across multiple servers or processors.  Here is more info on how BizTalk processes large messages:  http://msdn.microsoft.com/en-us/library/aa560481.aspx.

    in reply to: Consuming webservice in biztalk #20698

    Based on what you said, I am not sure if you are able to view the wsdl file in a browser. If you are able to view the wsdl file in browser and using 2006 R2 then download the wsdl file and use WCF-basichttp adapter to consume the web service.

    If you are unable to view the wsdl file in browser itself then it could be a problem with the web service itself.

    in reply to: Exception while sending message thru WCF-BasicHTTP adapter #20696

    Thanks ruselw.

    I have a virtual machine copy of my machine. However, I have reinstalled every thing to get it worked.

    Thanks for all your support. Let me know if you come across this any time.

    in reply to: Passing Nulls to WCF (Published Orch) #20695

    Maybe you could use svcutil to generate the proxy, and then make updates like the following:

    decimal CurrentGrossRate;

    ->

    decimal? CurrentGrossRate;

    The svcutil proxy would be a C# file you could keep in source control, so it is a little less likely to get overwritten than a service reference.

    in reply to: Passing Nulls to WCF (Published Orch) #20694

     

    Here’s more info as I continue to investigate:

    1) I have a field in my XML called CurrentGrossRate that has “Nillable” set to true (and minOccurs=0).

    2) The C# proxy generated by doing an “Add Service Reference” generates the following definition:  

     

    [System.Runtime.Serialization.

    OptionalFieldAttribute()]
    private decimal CurrentGrossRateField;

    The corresponding property is defined as follows:

            [System.Runtime.Serialization.DataMemberAttribute(Order=56)]
            public decimal CurrentGrossRate {
                get {
                    return this.CurrentGrossRateField;
                }
                set {
                    if ((this.CurrentGrossRateField.Equals(value) != true)) {
                        this.CurrentGrossRateField = value;
                        this.RaisePropertyChanged(“CurrentGrossRate”);
                    }
                }
            }

    3) There is no fiedl called CurrentGrossRateSpecified nor CurrentGrossRateIsSpecified or anything similar.

    4) Using the proxy, I get a compile error if I do this:

     

    loan1.CurrentGrossRate =

    null;

     

     

    error CS0037: Cannot convert null to ‘decimal’ because it is a non-nullable value type 

    5) I created an xml file with the field CurrentGrossRate missing, and have the C# test program deserialize it.  I immediately show the value of the field CurrentGrossRate and it’s value is zero.

    Thanks,
    Neal

     

     

     

     

    in reply to: Microsoft ESB Guidance #20692

    Is the ALL.Exceptions send port started?  Are you receiving any suspended messages or exceptions in the event viewer?  

    in reply to: Problem in promoting fields of an Unbounded Record #20690

    You cannot promote multiple values into the same property – a property can only have one value – hence the restriction.

    What is it you are trying to acheive. If you need to extract a recurring value from a message in an orchestration loop then using the xpath function is the simplest way.

    in reply to: Recoverable Interchange for Custom pipeline component #20689

    There is no guidance about implementing Recoverable Interchange for custom pipeline in BizTalk Help.

Viewing 15 posts - 3,826 through 3,840 (of 9,648 total)