community-content

Forum Replies Created

Viewing 15 posts - 3,631 through 3,645 (of 9,648 total)
  • Author
    Posts
  • in reply to: Complex Type – Return type of webservice #20994

     Cool. Thanks, OK, Now I need to map the elements between the wsdl xsd with another xsd. There is filed called Employee Info which includes First Name, Lst Name etc.. This element is unbounded in schema so it will be infinite. How can map such elements.

    in reply to: Complex Type – Return type of webservice #20993

     The complex type should be available after you add web reference under  WebmessageType.

    in reply to: Biznoob problem with flat file ReceivePipeline #20990

     Solution …

    In the end I had to make sure that my dll version on my orchestration application was updated.  For some reason, even though it was uninstalled from the GAC it must have been caching the old version somehow. 

    Changing the version fixed everything for me.

    in reply to: Communication with web service java #20989

    Sorry, I don’t know anything about JBoss, but I do have another idea: Use a WCF message inspector to strip out the chunking characters.  A message inspector would give you a chance to strip out the charcters before the the data hits BizTalk.  To apply the message inspector, you would need to use the WCF-Custom adapter and apply the inspector through a custom behavior.  If you want to investigate this route, it might be a little easier to test the inspector using a WCF client generated with svc-util before adding it into your BizTalk solution.  Here is a good link on message inspectors:

     

    http://weblogs.asp.net/paolopia/archive/2007/08/23/writing-a-wcf-message-inspector.aspx

     

    in reply to: Biznoob problem with flat file ReceivePipeline #20988

     I did try that but I am getting the same error.

    in reply to: Emailing on Failed Send port submissions #20986

    hi I’m not too keen on attaching other applications to the solution tho, when i should be able to keep this contained within biztalk

    Thanks

     

    Simon

    in reply to: Emailing on Failed Send port submissions #20985

    Rather than creating a system management application within Biztalk, you might like to look at using MOM, CA Unicenter or Tivoli, etc 
    These software products are specifically designed for detecting errors and applying rules to handle them.

    in reply to: Emailing on Failed Send port submissions #20984

    Hi thanks for the response: Yeh will go with this need to as this is the ‘BIZTALK’ default method for this.

    However our solution is architected in such a way that we rely on retries being generated from an originating database call (i.e. which send the original biztalk request via the recive port), so was looking at how you could interogate the biztalk sql database to do some more sophisticated queries, like only send an email if there have been 100 failed messages on that send port in the last 10 minutes?

    Of which this could prob be donw via an orchestration, but was looking for a non code change i.e server admin or sql query.

    Thanks

    Simon

    in reply to: How to ignore unexpected message types #20983

    A couple of options occur to me. In either one, the first thing to do is to enable the AllowUnrecognized property of the XML Disassembler so that it doesn’t generate an error if the document schema cannot be found. The second part is discarding unrecognized messages. For this, I can think of two options:

    1. Set up a second subscription that will get messages from the receive location and route them (so that they don’t get suspended) and then discard them. This could be done by simply dumping them to a folder you clean periodically, or using something like my /dev/null adapter.
    2. Create a custom pipeline component that runs after the xml disassembler looks for unrecognized messages (not sure exactly how, but I think it can be done) and then simply swallows them.

     

    in reply to: Biznoob problem with flat file ReceivePipeline #20982

    It looks like your Flat File will have more than 1 line? If so you need to defined an envelope schema where you can set the child delimiter as a CRLF (0x0A 0x0D)

    in reply to: Problem with WCF Net.TCP and Certificates #20978

     

    I will put the problem description here also:

    have created a BizTalk project, the receive port uses NetTcp, security mode is message and message client credentialtype is certificate.

    Then I publish this receive port as WCF service with Biztalk WCF publishing wizard. In web.config I set the serviceSertificate to match with the certificate that I have given to receiveLocation in BizTalk.

    When I do all this I get the service working, and I can get the reference to this service with svcutil. When I create a client with svcutil and I add the clientCertificate, I get an error:

     The caller was not authenticated by the service.

     So does anyone have an idea what I’m doing wrong?

     Or could someone give me a step by step instructions how to do this right, I’m using Vista, IIS7 and BizTalk 2006 R2.

     

    I think that this is a NetTcp issue, because this works fine if I use the same certificates with basicHttp.

    These are my server side ans client side config:

    Server

    <?xml version=”1.0″ encoding=”utf-8″?>
    <!–
        Note: As an alternative to hand editing this file you can use the
        web admin tool to configure settings for your application. Use
        the Website->Asp.Net Configuration option in Visual Studio.
        A full list of settings and comments can be found in
        machine.config.comments usually located in
        \Windows\Microsoft.Net\Framework\v2.x\Config
    –>
    <configuration xmlns=”http://schemas.microsoft.com/.NetConfiguration/v2.0“>
      <!–
        The <configSections> section declares handlers for custom configuration sections.
      –>
      <configSections>
        <section name=”bizTalkSettings” type=”Microsoft.BizTalk.Adapter.Wcf.Runtime.BizTalkConfigurationSection, Microsoft.BizTalk.Adapter.Wcf.Runtime, Version=3.0.1.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35″ />
      </configSections>
      <!–
        The <bizTalkSettings> section specifies BizTalk specific configuration.
      –>
      <bizTalkSettings>
        <!–
          mexServiceHostFactory debug:
          Set to “true” to launch debugger when MexServiceHostFactory.CreateServiceHost(…) is called by IIS.
          Used to debug from initial point of activation by IIS.
          Default value is “false” for normal operation.
        –>
        <mexServiceHostFactory debug=”false”>
          <receiveLocationMappings>
            <!–add markupFileName=”*.svc” receiveLocationName=”?” publicBaseAddress=”protocol://host[Stick out tongueort]” /–>
            <add markupFileName=”Microsoft_Samples_BizTalk_WCFBasicHttpReceiveAdapter_BizTalkApp_DeliveryProcess_DeliveryRequestPort.svc” receiveLocationName=”WcfService_Microsoft.Samples.BizTalk.WCFBasicHttpReceiveAdapter.BizTalkApp/Microsoft_Samples_BizTalk_WCFBasicHttpReceiveAdapter_BizTalkApp_DeliveryProcess_DeliveryRequestPort” publicBaseAddress=”http://localhost/” />
          </receiveLocationMappings>
        </mexServiceHostFactory>
        <!–
          webServiceHostFactory debug:
          Set to “true” to launch debugger when WebServiceHostFactory.CreateServiceHost(…) is called by IIS.
          Used to debug from initial point of activation by IIS.
          Default value is “false” for normal operation.
        –>
        <webServiceHostFactory debug=”false” />
        <!–
          isolatedReceiver disable:
          Set to “true” to skip IBTTransportProxy.RegisterIsolatedReceiver(…) and IBTTransportProxy.TerminateIsolatedReceiver(…) calls.
          Used for testing metadata exchange without having to setup receive location.
          Default value is “false” for normal operation.
        –>
        <isolatedReceiver disable=”false” />
        <!–
          btsWsdlExporter disable:
          Set to “true” to skip adding BtsWsdlExporter behavior extension to service endpoint.
          Used for testing or comparing strongly-typed WSDL customization versus weakly-typed WSDL of generic WCF service.
          Default value is “false” for normal operation.
        –>
        <btsWsdlExporter disable=”false” />
      </bizTalkSettings>
      <appSettings />
      <connectionStrings />
      <system.web>
        <!–
          Set compilation debug=”true” to insert debugging symbols into the compiled page.
          Because this affects performance, set this value to true only during development.
        –>
        <compilation defaultLanguage=”c#” debug=”false”>
          <assemblies>
            <add assembly=”mscorlib, version=2.0.0.0, culture=neutral, publickeytoken=b77a5c561934e089″ />
            <add assembly=”Microsoft.BizTalk.Adapter.Wcf.Common, Version=3.0.1.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35″ />
            <add assembly=”Microsoft.BizTalk.Adapter.Wcf.Runtime, Version=3.0.1.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35″ />
          </assemblies>
        </compilation>
        <!–
          The <authentication> section enables configuration of the security authentication mode
          used by ASP.NET to identify an incoming user.
        –>
        <authentication mode=”Windows” />
        <!–
          The <customErrors> section enables configuration of what to do if/when an unhandled error
          occurs during the execution of a request. Specifically, it enables developers to configure
          html error pages to be displayed in place of a error stack trace.
        –>
        <!–
        <customErrors mode=”RemoteOnly” defaultRedirect=”GenericErrorPage.htm”>
          <error statusCode=”403″ redirect=”NoAccess.htm” />
          <error statusCode=”404″ redirect=”FileNotFound.htm” />
        </customErrors>
        –>
      </system.web>
      <!–
        The <system.serviceModel> section specifies Windows Communication Foundation (WCF) configuration.
      –>
      <system.serviceModel>
        <behaviors>
          <serviceBehaviors>
            <behavior name=”ServiceBehaviorConfiguration”>
              <serviceDebug httpHelpPageEnabled=”true” httpsHelpPageEnabled=”false” includeExceptionDetailInFaults=”false” />
              <serviceMetadata httpGetEnabled=”true” httpsGetEnabled=”false” />
              <serviceCredentials>
                <serviceCertificate findValue=”41A1ED6BD18A4B3FDF37949D9A30537B732283AB”
                                    storeLocation=”CurrentUser”
                                    storeName=”My”
                                    x509FindType=”FindByThumbprint” />
              </serviceCredentials>
            </behavior>
          </serviceBehaviors>
        </behaviors>
        <services>
          <!– Note: the service name must match the configuration name for the service implementation. –>
          <service name=”Microsoft.BizTalk.Adapter.Wcf.Runtime.BizTalkServiceInstance” behaviorConfiguration=”ServiceBehaviorConfiguration”>
            <endpoint name=”HttpMexEndpoint” address=”mex” binding=”mexHttpBinding” bindingConfiguration=”” contract=”IMetadataExchange” />
            <!–<endpoint name=”HttpsMexEndpoint” address=”mex” binding=”mexHttpsBinding” bindingConfiguration=”” contract=”IMetadataExchange” />–>
          </service>
        </services>
      </system.serviceModel>
    </configuration>

     

    Client

    <?xml version=”1.0″ encoding=”utf-8″?>
    <configuration>
        <system.serviceModel>
            <behaviors>
                <endpointBehaviors>
                    <behavior name=”NewBehavior”>
                        <clientCredentials>
                            <clientCertificate findValue=”B2A988CC3B571C1B0E114C418BEDFA12D49F6E36″
                                x509FindType=”FindByThumbprint” />
                        </clientCredentials>
                    </behavior>
                </endpointBehaviors>
            </behaviors>
            <bindings>
                <netTcpBinding>
                    <binding name=”NetTcpBinding_ITwoWayAsync” closeTimeout=”00:01:00″
                        openTimeout=”00:01:00″ receiveTimeout=”00:10:00″ sendTimeout=”00:01:00″
                        transactionFlow=”false” transferMode=”Buffered” transactionProtocol=”OleTransactions”
                        hostNameComparisonMode=”StrongWildcard” listenBacklog=”10″
                        maxBufferPoolSize=”524288″ maxBufferSize=”65536″ maxConnections=”10″
                        maxReceivedMessageSize=”65536″>
                        <readerQuotas maxDepth=”32″ maxStringContentLength=”8192″ maxArrayLength=”16384″
                            maxBytesPerRead=”4096″ maxNameTableCharCount=”16384″ />
                        <reliableSession ordered=”true” inactivityTimeout=”00:10:00″
                            enabled=”false” />
                        <security mode=”Message”>
                            <transport clientCredentialType=”Windows” protectionLevel=”EncryptAndSign” />
                            <message clientCredentialType=”Certificate” />
                        </security>
                    </binding>
                </netTcpBinding>
            </bindings>
            <client>
                <endpoint address=”net.tcp://ikvistapuntavil/WcfBasic” behaviorConfiguration=”NewBehavior”
                    binding=”netTcpBinding” bindingConfiguration=”NetTcpBinding_ITwoWayAsync”
                    contract=”Microsoft_Samples_BizTalk_WCFBasicHttpReceiveAdapter_BizTalkApp_DeliveryProcess_DeliveryRequestPort”
                    name=”NetTcpBinding_ITwoWayAsync”>
                    <identity>
                        <certificate encodedValue=”AwAAAAEAAAAUAAAAQaHta9GKSz/fN5SdmjBTe3Mig6sgAAAAAQAAAIwEAAAwggSIMIIDcKADAgECAgoZ8/0IAAAAAAANMA0GCSqGSIb3DQEBBQUAMDQxMjAwBgNVBAMTKUluZGlzcHV0YWJsZUtleVJvb3RDZXJ0aWZpY2F0aW9uQXV0aG9yaXR5MB4XDTA4MTAwMzA3NTMxMFoXDTA5MTAwMzA4MDMxMFowGjEYMBYGA1UEAxMPSUtWaXN0YVB1bnRhdmlsMIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCvAIpOIlGF/5Yql2iOsDyW4dYwh5bTL/JZvk8O1RXsuDs8nqXprXK684ZK97TUJ1QqRmzX5DOXAVHqRX2T9NHHpjITWi7HU67nHTRI1hxhkn4NxSy3CLdmEwxxl05/rUPVmwUCFg6WS5OsP1oXks+Eat9q/ccJA4DWHoLi5LdZgQIDAQABo4ICODCCAjQwDgYDVR0PAQH/BAQDAgTwMBMGA1UdJQQMMAoGCCsGAQUFBwMBMB0GA1UdDgQWBBSmKicrwRtRvXbiYHGKkQ1sMQq0BTAfBgNVHSMEGDAWgBRv76rsmaOZIB5FRUTAWL8mPKoq8TCBxAYDVR0fBIG8MIG5MIG2oIGzoIGwhlVodHRwOi8vdnc5OTk5MDIuZXUudGlldG8uY29tL0NlcnRFbnJvbGwvSW5kaXNwdXRhYmxlS2V5Um9vdENlcnRpZmljYXRpb25BdXRob3JpdHkuY3JshldmaWxlOi8vXFxWVzk5OTkwMi5ldS50aWV0by5jb21cQ2VydEVucm9sbFxJbmRpc3B1dGFibGVLZXlSb290Q2VydGlmaWNhdGlvbkF1dGhvcml0eS5jcmwwggEEBggrBgEFBQcBAQSB9zCB9DB3BggrBgEFBQcwAoZraHR0cDovL3Z3OTk5OTAyLmV1LnRpZXRvLmNvbS9DZXJ0RW5yb2xsL1ZXOTk5OTAyLmV1LnRpZXRvLmNvbV9JbmRpc3B1dGFibGVLZXlSb290Q2VydGlmaWNhdGlvbkF1dGhvcml0eS5jcnQweQYIKwYBBQUHMAKGbWZpbGU6Ly9cXFZXOTk5OTAyLmV1LnRpZXRvLmNvbVxDZXJ0RW5yb2xsXFZXOTk5OTAyLmV1LnRpZXRvLmNvbV9JbmRpc3B1dGFibGVLZXlSb290Q2VydGlmaWNhdGlvbkF1dGhvcml0eS5jcnQwDQYJKoZIhvcNAQEFBQADggEBAD5dfODg6dWjFkTAxK+DP5nuaHTi7MPtOiBGhbDGG0zgEMWXHEGJfaaWkx7tWF05CFaFWne5T+rRr2Ur0YR6GeT30ocvpmntVGlT5Ox5xMRG+vEQ5SMIJrKAk80hu08VunPF42u6thpor6XDjBFZ5gVzxtqee9RdK6VCTIELnW2+w0MO/ti3gqrUt6wn9UP1jSnCaOAyWB9kAPOsYN11eWJGdXNJMPFtYgyxNcqmCgRxk8dL0w62/S1CJU6RXE23wFdqscCYGAeKbwE3UBBD6KYTuprSerTkruQugAFcbzY3P9pO2ie3uYMghA7xyHoWdEcBqO9FCW79s+RT0yEhw3g=” />
                    </identity>
                </endpoint>
            </client>
        </system.serviceModel>
    </configuration>

     

    I’m out of ideas, so I hope someone can help me.

    Consider following example:

    <persons>
       <person id=”1″>
          <name>Tarzan</name>
       </person>
       <person id=”2″>
          <name>Jane</name>
       </person>
    </persons>

    person with id: 1 is a sibling to person with id: 2
    person is a child of persons and a parent of name

    id is an attribute
    persons, person and name are elements

    So:
    person is a “Child Field Element” of persons
    name is a “Child Field Element” of person
    id is a “Child Field Attribute” of person

    Hope that’s clear enough.

    //Niklas Häggström – Connecta AB, Sweden

     Difference Between Child Field Element & Child Field Attribute

    Please any one tell me difference

    in reply to: Emailing on Failed Send port submissions #20974

     Hi!

    Did you check the settings on the “Transport Advanced Options”-tab of the port? There you might see a block called “Transport Options”. Therein are the options for port-retrying. The port will not terminate to “suspended”-state before it has executed the given number of tries with the given interval. After this, the port will suspend and the failed message routing-process will kick in. In your case, as far as I can see, failed message routing may not even be nessecary (spelling on that one, anyone?). You might be able to utilize the “Backup Transport”.

    Go through the port settings and fiddle around with that for a while and you might take a step in the right direction.

    Regards, Niklas Häggström – Connecta AB, Sweden

    in reply to: Communication with web service java #20971

    Hi all, deeping in this problem, any solution finded in .Net. The WCF-BasicHttp adapter doesn’t work and the custom pipe doesn’t receive the message neither. At the end (two last posts) we find the next info in this web: http://www.theserverside.com/discussions/thread.tss?thread_id=42032

    Re: Web Service Response encoding problem
    Posted by: Alan Jones on septiembre 14, 2006 in response to Message #217623
    OK, so after a bit of digging, I’ve made some progress.

    The ‘junk’ characters aren’t junk at all! They are just control characters for the ‘chunked’ transfer-encoding that JBoss appears to be using! It would appear that Java tools (such as my Java test client, and the SoapUI tool) can understand messages sent using chunked encoding (hence why we’d never seen this ‘problem’ before), but as soon as we use a .NET tool, such as our suppliers client or the MSSoapT tool, they don’t seem to understand the output, and hence display the control characters as part of the message.

    So, I suppose the next question is, does anybody know anything about the different setting for transfer-encoding, and more specifically how I can use something other than ‘chunked’ in JBoss?

    Re: Web Service Response encoding problem
    Posted by:  Alan Jones  on septiembre 19, 2006 in response to Message #217907

    OK, I found the solution (and cause) of the problem. Apparently .NET doesn’t implement HTTP/1.1 correctly, so needs the following line adding to the connector element of the Tomcat server.xml file:
    restrictedUserAgents=”^.*MS Web Services Client Protocol.*$”

    As with everything, once you know what to look for, you find it! There is an entry in the JBoss Wiki about it 😉 

    Now, I’m absolutly stopped. Does someone know about a hotfix in .Net to solve this?

    Thanks a lot

Viewing 15 posts - 3,631 through 3,645 (of 9,648 total)