community-content

Forum Replies Created

Viewing 15 posts - 8,551 through 8,565 (of 9,648 total)
  • Author
    Posts
  • in reply to: BizTalk Server 2006 tutorial #14507

    The Biztalk 2006 product comes with a number of tutorials:
    [url]http://msdn.microsoft.com/library/default.asp?url=/library/en-us/bts06gettingstarted/html/58019f98-e91a-4705-b689-c269174d6bae.asp[/url]

    in reply to: Connecting Biztalk to Exchange #13328

    You should be able to use a combination of SMTP Send Adapter and POP3 Receive adapter to send emails and retrieve responses.
    You will need to add a mailbox for responses and set the From address on the Biztalk send port to this mailbox. You will need POP3 functionality on the exchange server and have a POP3 adapter polling this mailbox.

    Your biggest difficulty is going to be determining if an email has been delivered. In the age of spam most people have disabled external delivery receipts and read receipts. You will possibly get bounce messages so you will have to deal with acks and nacks.
    The response messages are meant for human consumption so they will not be structured data so parsing the responses will be a nightmare. As will correllating the responses to the originating messages.

    Best of luck.

    in reply to: BizTalk 2006 installation fails #14496

    I think you can use register.exe or something like that to manually requester a dll. Not sure how that will work out through. I know in the 2004 days, sometimes I’d just give up – re image. Then, the next time everything would work. Doesn’t make sense to me

    Best of luck.

    in reply to: Re:Rules Engine #13314

    Make sure any .net components called by the rules are in the GAC. Also, might want to check permissions and make the rules are deployed.

    in reply to: Biztalk Server Tutorial #13357

    Ok, I’m biased, this is my site: http://Biztalk-Training.com.
    My tutorials have helped many people get off to a quick start.

    Neal Walters

    in reply to: BizTalk programming helping tools #13353

    Hi!
    i’m new in BizTalk, and i need a little help.

    What kind of programs, tools or utilities do you guys use, in order to help you program in BizTalk( i’m thinking about things like XMLSpy, UltraEdit and stuff of the kind)?
    every suggestions is welcomed!
    thanks.

    in reply to: BPM Scenario #14454

    Sounds like the web service that’s getting called is failing and you’re getting the ASP.NET default error page instead. Have you tried opening up the service in the browser and checking what the error is? You might also want to check if ASP.NET 2.0 is enabled for the site and not 1.1.

    in reply to: Getting Error #13351

    Hello All

    I m new to Biztalk, So please Help Me

    I am getting Following Error when i m dropping one xml file in In Folder.
    The File Removes from that folder but doesn’t give any output and everytime generate Following Error in Health and Activity Tracking.

    Error in accessing the part data or one of its fragments. The part or fragment may not exist in the database.

    Please give me solution ASAP.

    Thanks & Regards
    Jignesh Darji

    in reply to: Custom XSLT — Need some assistance, please #13349

    Just the first one, so my new output looks like:

    [code:1:31f9befa88]
    …
    <Detail>
    <Field1>Value1</Field1>
    …
    <Spec>
    <Field1>Value1</Field1>
    <Field2>Value2</Field2>
    </Spec>
    …
    </Detail>
    …
    [/code:1:31f9befa88]

    in reply to: Custom XSLT — Need some assistance, please #13345

    Rich,

    Ignore my alternate suggestion, it won’t work as the <Spec> node will be dropped from the output.

    Does the <xsl:if> construct pick up all the <Spec> nodes or just the first one.

    You could also use:
    [code:1:856fdf2b37]<xsl:for-each select=\"Detail/Spec\">
    <Spec>
    <xsl:for-each select=\"Info\">
    <xsl:element name=\"{string(@Name)}\">
    <xsl:value-of select=\"string(@Value)\" />
    </xsl:element>
    </xsl:for-each>
    </Spec>
    </xsl:for-each> [/code:1:856fdf2b37]

    in reply to: Custom XSLT — Need some assistance, please #13348

    Hi Greg, you were the one that helped me with the original XSLT, good to hear from you.

    I have my change working as needed and verified the ‘new’ output with the developer who will consume the data so I think all is well with what I have. But to answer your questions and to help me understand XSLT a little better, here you go…

    [quote:8e6b8e67a7]
    What does the output look like for the second instance?
    [/quote:8e6b8e67a7]Identical, aside from the ‘Spec’ element and child nodes. Some messages have them which I need to preserve, and other messages will not have the Spec element so I won’t need the output to contain the element.

    [quote:8e6b8e67a7]Do you want the <spec> element included or just the <Info> elements mapped[/quote:8e6b8e67a7]I need the Spec element included as well, a consumer of the modified data will require the format if it’s there.

    [quote:8e6b8e67a7]In your sample you have indented the <Spec> elements but they are not child elements of the preceding <Info> element.[/quote:8e6b8e67a7]Correct, so the change I used above works, as I don’t need it to particularly show in a certain order of the output message. As long as Spec remains a child of Detail, I’m golden.

    [quote:8e6b8e67a7]Is there some relationship between the <Spec> element and preceding <Info> element that is derived from its position and does this relationship have to be maintained across the map?[/quote:8e6b8e67a7]No, just that Spec remains the child of Detail is the only requirement.

    in reply to: Custom XSLT — Need some assistance, please #13344

    An alternative would be to change this line from the original XSLT:

    <xsl:for-each select=\”Detail/Info\”>
    To
    <xsl:for-each select=\”Detail//Info\”>

    in reply to: Custom XSLT — Need some assistance, please #13347

    OK, looks like I got it….I did the following if any cares to see:
    [code:1:29576332f5]
    …
    <xsl:if test=\"/Root/Detail/Spec\">
    <Spec>
    <xsl:for-each select=\"Detail/Spec/Info\">
    <xsl:element name=\"{string(@Name)}\">
    <xsl:value-of select=\"string(@Value)\" />
    </xsl:element>
    </xsl:for-each>
    </Spec>
    </xsl:if>
    …
    [/code:1:29576332f5]

    Good times!

    Take care,
    -Rich

    in reply to: Orchestration exposed as web service — XmlDocument Type #13310

    Thank you sir, got it working!

    in reply to: Custom XSLT — Need some assistance, please #13346

    Hi all,

    I have a custom XSLT used within some maps I execute inside some orchestartions and the publishing app threw a kink at me with some XML changes I didn’t expect. Unfortunately, the XSLT was provided to me by a member of the boards here, as I’m not as well versed in XSLT as I’d like to be (but working on it).

    Here’s my situation:
    My incoming messages come into me in a name/value pair setup as below:
    [code:1:8a2c0b04e5]<Root>
    <Header>
    <Info Name=\"field1\" Value=\"value1\" />
    <Info Name=\"field2\" Value=\"value2\" />
    </Header>
    <Detail>
    <Info Name=\"field1\" Value=\"value1\" />
    <Info Name=\"field2\" Value=\"value2\" />
    </Detail>
    </Root>[/code:1:8a2c0b04e5][/code]

    The XSLT converts the XML to output the following:
    [code:1:8a2c0b04e5]<Root>
    <Header>
    <field1>value1</field1>
    <field2>value2</field2>
    </Header>
    <Detail>
    <field1>value1</field1>
    <field2>value2</field2>
    </Detail>
    </Root>[/code:1:8a2c0b04e5]

    The XSLT:
    [code:1:8a2c0b04e5]
    …
    <xsl:template match=\"/\">
    <xsl:apply-templates select=\"/Root\" />
    </xsl:template>
    <xsl:template match=\"/Root\">
    <Root>
    <Header>
    <xsl:for-each select=\"Header/Info\">
    <xsl:element name=\"{string(@Name)}\">
    <xsl:value-of select=\"string(@Value)\" />
    </xsl:element>
    </xsl:for-each>
    </Header>
    <Detail>
    <xsl:for-each select=\"Detail/Info\">
    <xsl:element name=\"{string(@Name)}\">
    <xsl:value-of select=\"string(@Value)\" />
    </xsl:element>
    </xsl:for-each>
    </Detail>
    </Root>
    </xsl:template>
    …
    [/code:1:8a2c0b04e5]

    Whew…now, here is the change that occurred in the incoming XML:
    [code:1:8a2c0b04e5]<Root>
    <Header>
    <Info Name=\"field1\" Value=\"value1\" />
    <Info Name=\"field2\" Value=\"value2\" />
    </Header>
    <Detail>
    <Info Name=\"field1\" Value=\"value1\" />
    <Spec>
    <Info Name=\"field1\" Value=\"value1\" />
    <Info Name=\"field2\" Value=\"value2\" />
    </Spec>
    <Info Name=\"field2\" Value=\"value2\" />
    <Spec>
    <Info Name=\"field1\" Value=\"value1\" />
    <Info Name=\"field2\" Value=\"value2\" />
    </Spec>
    </Detail>
    </Root>[/code:1:8a2c0b04e5]

    As seen above, the new elment of ‘Spec’ has been added. The current XSLT is not seeing this new element and therefore, is not creating the output with the new element nested in the XML where I’d like it to do so. Also, the ‘Spec’ element may or may not be in the feed so I need to only output the ‘Spec’ data if it’s in the incoming message…so I won’t be creating the element if it’s not in the incoming message.

    Can anybody see how I can make the necessary change to the XSLT to reach my goal?

    Thanks in advance!
    -Rich

Viewing 15 posts - 8,551 through 8,565 (of 9,648 total)